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

Reports

Showing 43 of 1282

Add elevation ranges when measuring volume between terrains.

In Geopak, there was a tool under DTM Tools > Analysis > Volumes, where you could specify elevation ranges to calculate the volumes, while also taking into account the volumes between two TINs. You were able to specify multiple contour inter...
10 months ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Reports 1 Future consideration

Import data from reports to Item Types

Currently, is possible to create and personalice reports (Analise)using Item Types data, however,there is no relation back. It would be very benifecial if data added or even changed into the reports could be imported back into the model and Item T...
11 months ago in Item Types / OpenRail Designer / OpenRoads Designer / OpenSite Designer / Reports 0 Future consideration

horizontal reports for multiple alignments

Currently when only one rail alignment can be selected to output a horizontal report. Would be great if the ability to select multiple alignments and output a horizontal report at the same time. Reason: Currently have projects which contain multip...
12 months ago in Reports 0 Planned

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...
12 months ago in Geometry / OpenRail Designer / OpenRoads Designer / OpenSite Designer / Reports / Survey 1 Planned

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

Standard Report Formatting

We use reports generated in the Civil Reports Browser to export reports that go to contractors in the field. We often run into issues with the formatting of the report not being set correctly. This problem is compounded by the fact that formatting...
about 1 year ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Reports 0 Future consideration

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...
about 1 year ago in OpenRoads Designer / Reports 1 Future consideration

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...

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...
about 1 year ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Reports 0 Future consideration

Remove the Volume Exception Stations from End Area Volumes Report

If we add the Volume Exception stations (Cross Section Named Boundaries) for which we don not want to generate the End Area Volumes, The generated report still reports the Stations with the 0 Volume and its area. Kindly add an option to remove the...
about 1 year ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Reports 0 Future consideration