Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Already exists
Created by Guest
Created on Dec 15, 2022

Inconsistent terrain labeling

I am having an issue where symbology overrides and annotation scale is not impacting my sheet file (default, drawing and sheet models) the way it should. It seems to be emulating the situation described by the user who posted to Bentley Communities in "ORD Contour Line Scaling" about 3 years ago.

First, I switch annotation scale in my drawing model and my existing contours (in own file) and proposed contours (separate file) do not change. I did try the fix described in this Communities post by manually overriding the feat def and symbology of the referenced terrains. It worked for my proposed terrain, but completely took away the labels on the existing terrain, as described in the post.

I also was unable to use symbology overrides successfuly in my sheet file to change the weight of my contours. Overrides are working for color and linestyle, but not weight. So I do know how to use the view flags from the parent file. Again, going into the sheeted file and overriding the feat def in the properties box, not symb overrides.

I am getting very frustrated with ORD plan production process. It seems to be tenfold as difficult as the old method of simply referencing a titleblock in coordinate space. We have advocated to our users on Bentley's behalf and truly want these tools to work. But it seems to make things overly complicated when files are live nested from the default model to the drawing model to the sheet model. There are too many places to adjust settings, costing valuable time. Please advise.


Civil Product Used OpenSite Designer, OpenRoads Designer, OpenRail Designer
  • ADMIN RESPONSE
    Jan 4, 2023

    Please try the Label Terrain Contours and Label Terrain Spots in the Terrain tab of the ribbon. Please let us know if this meets your needs.

  • Guest
    Reply
    |
    Feb 6, 2023

    That would provide a solve for the annotation of the existing terrain. However, that was meant to be an example of the larger issue of clumsy workflow for symbology overrides in regards to default, drawing and sheet models.