Currently, we can set default values for item types and then change them once they are drawn into the file. However, if the values that we need to input into the item type are coming from a source outside of ORD, there's no way to import that info...
We have a label that we need to include 2 offsets from the centerline in the same label. However, when I use the Data Point selection method, it only lets me select one point. There's no way to create the label to include 2 offsets. The only worka...
It is known that processing slows when using nested IIF statements. In order to simplify the expressions functions for Roundup and Increments for Ceiling.Math with are needed. Roundup function with a precision Roundup(100.03,1) = 100.1 math functi...
DU RIM Elevation calculated from Ground Elevation offset
The RIM Elevation is a stagnant number once you enter an elevation it does not update in relation to any surface changes. RIM Elevation would be better suited for use if it can be defined with an offset. Another field would be needed: RIM Depressi...
It would be amazing if we could utilize our own grate spacing for calculating the head on inlets. KYTC has several grates that don't quite match with what is in the delivered system, and this may affect the depth of the head on the inlet.
Users often make changes to the different fit options in the Dynamic XS view that are not persisted when the file is closed or a section via datapoint is issued (Fit Section / Center Backbone / Center on Current Offsets). It defaults back to the F...
At KYTC we like to show the vaults of drainage structures, in order to do that S&S drew them for us. ORD does that in 3D, however, we turn the 3D off when producing plans. It would help in the case that we could point to two cells (one that ma...
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.