Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
ADD A NEW IDEA

My ideas: Reports

Showing 48

Add an end element in xml file

To make it easier to select and report the end station of an alignment it would be good to have an "Alignment End point" or "Alignment end element" in plan and profile. Also in cant!
5 days ago in Reports 0 Needs review

ORD Seeding Reports Like GEOPAK

Ohio DOT would like the ability to create Seeding Reports like those that could be generated within GEOPAK from the cross section candidate elements (or components) with their end width (slope lengths) including similar options that GEOPAK offered...
over 1 year ago in OpenRoads Designer / Reports 1 Future consideration

Add option to HorizontalAlignmentCheckIntegrity.xsl report to ignore angular differences for PIs with no curves.

In the InRoads Check Integrity command, the command would report "OK" for any PIs that did not have curves. We would like the ORD check integrity reports to not report issues at a PI if there are no curves present.
about 1 year ago in OpenRoads Designer / Reports 0 Future consideration

Add Input Reports for LARS CONNECT Edition

An input report should be made available to LARS files similar to the input report generated in LEAP Steel. This allows for a more efficient process for QA/QC of load rating files. This ability was present in LARS v10, but removed in the modernize...
5 months ago in OpenBridge Designer / Reports 0 Future consideration

Add option to save result as a "Report" when performing a Terrain to Terrain (or pane) Volume analysis.

Currently when performing a Terrain to Terrain (or pane) Volume Analysis, the only option for saving the result is to save it as a text string and place in a .dgn. It would be very helpful if there was an option so save this result as a report (id...
3 months ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Reports 0 Future consideration

Need a report (XSL) that combines Horizontal, Vertical, and cant information

Need a report (xsl) that combines Horizontal, Vertical, and cant information in it. Currently when the cant report (XML) is generated it also included horizontal geometry info (XSL). Similarly, when the horizontal report (XML) is generated it cont...
about 2 years ago in OpenRail Designer / Reports 2 Planned

XSLT 2.0 Support - Civil Reports

Who would like to have more capable Civil Reports? Currently, OpenRoads Designer relies on the XSLT 1.0 Transformation Language for generating Civil Reports. This language was published in 1999, now 24 years ago. In 2009, a much more full-featured...
over 1 year ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Reports 0 Future consideration

Clearance Report

Rail industry needs to measure clearance of many elements relative to the track: linear and point. Not all can be done using 3D clash. Some exact value are sometime required by the standards. Typically measurement of a platform edge from the CL bu...
about 2 years ago in OpenRail Designer / Reports 2 Planned

Upgrading from XSLT 1.0 to XSLT 3.0

XSLT 3.0 introduces several new features and improvements that can enhance the development process, increase efficiency, and provide better results. Performance Improvements: XSLT 3.0 includes optimizations that can significantly improve the perfo...

List Points in Numerical Order When Generating Horizontal Point Report

Currently when generating a Horizontal point report, ORD does not list the points in numerical order. Say we have the points P1 through to P100, they should not be listed as P1, P10, P11, P12......P19, P2, P21 etc. seems it sorts by alphabetical o...
about 1 year ago in Geometry / OpenRail Designer / OpenRoads Designer / OpenSite Designer / Reports / Survey 1 Planned