Sometimes it feels totally frustrating to work with annotations in ORD. The problem stems from the dynamic nature of ORD files. Say we have a track where we have done annotations and we took our time to specify their position and adjust them. We h...

Text Favorites are great. This is the primary way we transfer information from the model into intelligent annotations. Their functionality needs to be expanded to cover, quite literally, anything. If a property is discoverable anywhere in the desi...

Similar to the new Station/Offset Expressions, it would be great to query a terrain in an item type on an element and return the elevation. It would be used primarily for point cells, but I could also see it being useful for linework.

A SWITCH/CASE function would be easier to use than having to nest multiple IF functions.

RM BRIDGE, increase the naming character limits for load cases and load sets to more than 16 characters.

When creating cut and fill meshes in ORD it creates the meshes for the entire design file. This applies a feature definition for both the cut and fill meshes that only allow for one applied shrink/swell rate. It would be helpful to be able to appl...

There used to be a tool in InRoads (I think it was part of the Generate Longitudinal Feature) where you could project the slope between 2 elements onto a third element. The is no such tool in ORD. The only way I can figure to do it now is to creat...

Please allow the use of guidelines of a deck template to be used for barrier placement. Right now it's limited to regular decks only. WIth advanced deck, only the Alignment can be used.

NR60 Mk2 turnouts to be included by default in the standard OpenRail definitions.

Currently Item Types with Expressions update whenever properties are displayed. etc and are always "live" even via referencing, etc. This causes many issues where the original Excel lookup spreadsheet or Civil data is not present (when viewed in M...