It would be nice to have the ability to reattach civil labels to a new element or terrain. A good example is for jointing/geometric sheets with a lot of spot elevations. Fairly often a new terrain is created and the spots break and need to be replaced. I know ideally we use one terrain and continuously update it, but often enough the terrain get recreated for a variety of reasons. I don't see this having much use for a single label, since you can just place a new one, but for the large volume of notes that are all referencing one element this would be very helpful.
| Civil Product Used | OpenSite Designer, OpenRoads Designer, OpenRail Designer |
0
Future consideration
0
Future consideration
0
Future consideration
You can label the active terrrain which allows you to swap out the terrain if needed. Agree though this is very much needed in the software!
Reassign the new baseline to existing civil labels (as a future enhancement). We had already labeled the roadway plans, and the baseline needed to be revised. When incorporating the new alignment, all the labels reset to zero.
We are also looking for a way to "heal" or "reassociate" Civil Labels to elements without having to replace the Civil Labels. Can the associated element be tagged in the Civil Label's properties and be remapped based on new selection prompts to remap the association (as a future enhancement)?
We have had issues with regular plan view labeling that references the alignment and if we remove the alignment from the file, all of our labels go to zero. There should be a way that we can get all the labels that reference that alignment and have them reassigned to the new alignment reference or even to a new alignment if another alignment was created.
We have set all of our elevation labels to label the Active Terrain. The label does update even if you completely delete the original terrain model. Only minor nuisance is that you can only label spots from one terrain (the active one).
I believe this already exists under the dimension tool "Reassociate Dimensions."
I agree however I think the software should hold the GUID of the terrain that way when you created an updated terrain the annotation would hold.