• Design Cross Slope report values is not matching.

    I am trying to generate cross slope report @ 10 m interval by station base or station offset report but i am not getting appropriate values of cross slope in report. It seems correctly in cross-section view. Am missing something ?? Images is ready for…
  • profile station in sheet profile is showing uneven intervals after using chainage equation?

    Hi Guys, I cant figure out how to correct station intervals in my production profile sheet . After using chainage equation, ahead station of my profile showing unevenly. Regards , Lalit
  • ORD DWG Export issues

    Hi, Using ORD 2021 Release 1 and Autocad C3D 2022. Profile Geometry Annotation lose values in export, K-value and grade change to 0.0 and Lines are exported between Profile IPs on Layer 0. Please find the Images. Thanks Lalit
  • strip grades OpenRoads Designer

    Hello- We have created annotation groups to display profile strip grades, both existing and proposed. We have feature definitions and annotation groups assigned to both existing terrain and to the proposed design profile. When testing, we can get the…
  • Placing relative associated note for station and offset

    OpenRoads Designer Release 3 Hello everyone, I am trying to label Station and Offsets that are linked to the geometry, that way if the geometry changes so will the note. What I have so far: A text favorite for STA and OFF, and a Dimension…
  • is there an accepted standard working unit for ORD?

    Is there an accepted standard working unit for ORD? If i set the units to 10,000/FT annotation seems to work correctly. if i use a different unit, such as our company standard or a client standard, the annotation does not come in at the correct size.…
  • Dimension Styles Prefix - Terrain Spot Elevation - ORD

    Two questions regarding Terrain Spot Elevations: First - I am trying to add the prefix "EL: " in my dimension style, but you are restricted to one character. Is there any way to have the prefix "EL: " in this label? Second - How do you remove the…
  • Quantity Manager for ORD?

    We as a DOT are in process of switching from SS4 to ORD. I am very comfortable calculating quantities so far in ORD but there seems to be no equivalent of Quantity Manager. This was a great feature for recording all of our pay items and quickly harvesting…
  • ORD - Annotating points in plan view

    I can't get any text fields to work with civil points that I create using the horizontal geometry tools. I'm using ORD 10.06.00.38. My end goal is to create a text favorite then an annotation group for a particular point feature definition. I want the…
  • [ORD 2018R4] Enhancement Request - Annotation Group Management Utility

    Good Morning, I'm working on doing some fine tuning on our workspace and realized that there is not currently a utility to convert Annotation Group XML files to Excel, similar to the other migration utilities. It would be helpful to have such a converter…
  • ORD - Annotate superelevation in plan?

    Hi, is ther a way to annotate the superelevation in plan? mainly superelevation cross slope variation. We have the colored band but I would like to show the crossslope more preciseley. I know the superelevation section can have a linear feature definition…
  • ORD - Annotation of intersecting point in profile

    Is there a way to annotate automaticaly the intersecting point (crossing feature) in the profile? Idealy station, feature name, description. I know how to display a cell, I know the use of place label to do it manualy but I would like to do it through…
  • ORD U2/U3 Alignment Annotation Issues

    When annotating an alignment I'm getting three different text sizes. The curve anno is one size, the start coordinates anno is another size and the alignment bearing, distance and stationing is a third size. See video Example 1.mp4 ( https://youtu.be…
  • Wildcards for ORD Annotation Filters?

    Hi all, Does anyone know if wildcards are possible in the ORD Annotation Filter for properties like Feature definition, Feature name, etc? It seems that each feature name or definition needs to be explicitly defined and not even feature definition…