I would to request additional functionality of the civil labeler. Currently, the civil labeler only works in the design space and in the drawing model space IF the reference is associated with a named boundary. There are several times when we don't create a named boundary for a 1-sheet plan and used the sheets drawing model space as the "container" file which we then reference into the sheet. For example, on a single sheet plan, we may have a low-level designer/technician who creates the container file, adds the existing conditions base files, creates the sheet before any actual OpenRoads data is created. i.e. geometry, corridors, etc.. As that data is generated, its added to the container file. The other non-ORD CAD data can also be added to the sheets as well.

Its a common thing when we're trying to keep staff busy and get a start on basic project setup. Again, this is just specific to single plan sheets, multiple sheets are generally created from the named boundaries.

The workarounds are;

1. using the label command using the text favorite, however, if the label needs moved, the in-line leader does NOT stay horiiz. defeating the purpose of using that tool.

2. create a container "design" model file, reference all the required files, label everything and reference that model into the sheet.

I would like to request/suggest the civil labeler functionality be available in ALL model types regardless if a named boundary exists.