Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Future consideration
Created by Guest
Created on Apr 14, 2026

Provide the same Leica translator in OpenRoads Designer that was present as a Survey Add-in to InRoads V8i

Provide the same Leica translator in OpenRoads Designer that was present as a Survey Add-in to InRoads V8i, such that a choice of formats when exporting geometry is to export to the Leica DBX format.

There is a gap issue in the process to export OpenRoads geometry - OpenRoads Designer is missing the tool to Export alignments and surface features directly to Leica DBX format.
Using InRoads V8i, one could use a Leica Translator to export both surfaces and alignments to DBX format. In the Leica Captivate or Infinity software, the DBX input automatically generates a "road" by selecting the longest horizontal alignment as the parent, and assigns the other alignments and surface features that were created by the modeler as children, thus allowing the field instrument to stake out a toe of slope catch line from the centerline alignment, for example.
The gap is that the Leica Translator cannot be found in the OpenRoads Designer v2024 software.

Civil Product Used OpenRoads Designer, OpenRail Designer
  • Guest
    May 12, 2026

    An additional suggestion related to this idea is for the Civil Report Browser to retain the raw data generated from a geometry report in a separate location than raw data generated from a corridor report, which could allow XSL style sheets to be assembled from raw data with different civil sources, i.e raw-geometry-xml.xsl, raw-corridor-xml.xsl. Also provide a Terrain Features report about the source features that produces raw-terrain-xml.xsl. Then style sheets could be developed that combine information from different types of raw data. One function of the Leica Translator was it allowed a LandXML export that combined surface data with alignment data.