Hi everyone,
I’m currently working with Civil 3D 2024 and Camber 4.2.6.
I’m using the Camber node ProfileViewStationElevationLabel.ByStationElevation to create and modify station-elevation labels in a Profile View. However, I’ve encountered an issue: some of the elevation data points fall outside the current elevation range of the Profile View.
When the graph runs, the node fails on these out-of-range points, throwing the following error:
Because of this, the labels for these specific points fail to be created/modified, and it sometimes interrupts the rest of the workflow.
My question is:
What is the best practice to handle this? Should I filter out the out-of-range stations/elevations before passing them into the Camber node, or is there a built-in way to make the node gracefully skip these points without throwing an error?
Any advice or workaround would be greatly appreciated! Thanks in advance.
Quick point of clarity- this is a warning, not an error.
The ‘fix’ would be to filter in advance, or use function passing to suppress the warning, though you’ll likely add new issues (resulting nulls to deal with, and other warnings also being suppressed) and slow graph execution by doing the later.
Currently, when an elevation value exceeds the vertical range of the Profile View, the node throws an error and completely fails to create the label for that point.
However, my actual goal is different: I do not want to filter out these out-of-range points. I still want the labels to be created for them, even if the elevation is slightly out of bounds. I am perfectly fine with the label being placed slightly outside the visible area of the Profile View.
Is there a way to bypass this elevation boundary check in Camber? Or could this be considered as a feature request to add an optional input (e.g., a boolean toggle like IgnoreElevationLimits) to force the node to create the label regardless of the Profile View’s vertical range?
Any workarounds or insights would be highly appreciated!
Can you create such a label in the UI?
Yes. Station-elevation labels can be created successfully for points with elevation values within the vertical bounds of the profile view.
In which case Camber would need an update. Unlikely (almost assuredly) won’t happen if it only is needed in 2024, as from 2025 there are a TON of changes in Dynamo for Civil 3D. So your next step is to see if there is an out of the box replacement in the newer builds (test 2027 as a start).
