This chapter covers directory locations, descriptions, and naming conventions for data files used by the InRoads design software. These binary files contain all engineering design data created during a project and instructions on the format of output data from InRoads, whether to a MicroStation graphic format or to a text report format.
InRoads requires multiple file types to perform various functions for the creation of a engineering design project. These files can be generally segregated into two categories. The first group controls the graphic display, text reporting, and precision of data out of InRoads. The second group contains the data files created in the process of designing a roadway project.
The following four file types control the export of data from InRoads into graphic or text format. Each of these files are standard in the CDOT Workspace and CDOT policy does not allow independent user modifications to these files. If adjustments or additions are required, users are encouraged to submit a change request to CDOT CADD Manager. The request will be reviewed and incorporated into future configuration releases upon approval.
The CDOT InRoads Preference file contains information necessary for InRoads to display design data accurately as MicroStation graphics. All named symbologies, feature style information, and preference symbology is contained within the preference files and is configured to exactly match the CDOT Workspace and its by-level symbology standards. This file also controls the precision readout, command settings, grid spacing, and a multitude of other settings required for InRoads to perform correctly.
The CDOT InRoads Style file controls symbology for the display of horizontal and vertical geometry data into the MicroStation Model file. Points, Lines, Arcs, and Spirals from the InRoads alignment file are displayed consistent with CDOT by-level symbology.
This file contains InRoads intelligent drafting notes that access engineering data from the geometry file and digital terrain model files. The drafting notes file sets the graphic parameters for displaying notes that contain data such as station, offset, or elevation.
This file specifies what information is used from the XML Data files and how the information will be displayed to create a report. The standard CDOT Style Sheets are located under C:\Program Files\Workspace-CDOT\Standards-Global\InRoads\XML Style Sheets\ folder.
InRoads data files contain all pertinent engineering-generated data assembled during the project. These files are user-created, progressed during the evolution of a project, and saved in the Project Specific/Specialty Group specific/InRoads folder.
Digital Terrain Models are mathematical representations of the surface of the earth. InRoads uses DTM data to produce contours, display the existing and proposed groundlines in profile and cross section grids, and in the calculation of cut and fill quantities. DTM are created with a combination of surface points identified as spot points, breaklines, contour lines, or other point types used to define the surface.
Existing CDOT Digital Terrain Models represent existing ground conditions at the time that surveying data was collected. Existing DTMs may be assembled from traditional survey, terrestrial LiDAR, aerial LiDAR, aerial orthophotography, or a combination of these methods. The standard existing ground surface naming convention is JPC#SURVSurface##.dtm and is stored in the \\Projects\JPC#\ROW_Survey\InRoads\DTM\ folder. For example: 14942SURVSurface01.dtm.
Proposed CDOT Digital Terrain Models represent the project design as generated by InRoads using the horizontal alignments, vertical alignments, templates, and roadway definitions. Proposed DTM's can also be generated and/or modified manually. The proposed ground surface is stored under the Specialty Group's folder structure under InRoads. For example \\Projects\JPC#\Design\InRoads\. Proposed DTMs are named with the Job Project Code (JPC). Most projects will contain multiple DTMs that define various portions of the projects, such as the mainline, ramps, and detours. Where mulitple DTMs are required, additional descriptors can be used in the file name, such as 14942C470Mainline.dtm or 14942C470Detour.dtm to distinguish stored surfaces.
CDOT Geometry Project files contain horizontal alignment, vertical alignment, and superelevation information. These files are saved under the Specialty Group's project folder under InRoads. The naming convention for Geometry Project files consists of the Job Project Code (JPC) with the .alg file extension.
The Existing Geometry Project contains the centerline of survey as acquired by the Survey department. The standard existing Geometry Project file naming convention is JPC#SURVGeometry##.alg and is stored in \\Projects\JPC#\ROW_Survey\InRoads\Geometry\ folder. For example; 14942SURVGeometry01.alg.
The Proposed Geometry Project contains geometry relating to proposed horizontal, vertical, and superelevation data added. The proposed geometry file will contain all alignments for the roadway design including ramps, detours, cross streets, and the associated vertical profiles. Also included in the geometry file are the superelevation assignments that control how the templates and roadway library control superelevation.
Important note: There are a number of settings in the alignment file that must be evaluated by the design engineer. Many of the settings have been addressed in the CDOT configuration; however care must be taken to assign proper values for the modeling of the design surface as required by the project.
One example of these settings is the Rounding Linear Transitions variable for superelevation which is on by default in the CDOT configuration. With this setting on, superelevation transitions will be rounded to the nearest 30 feet. With this setting off, InRoads will calculate the transitions exactly. Ensure that the Rounding Linear Transitions option is off under the Build Superelevation Transitions > Controls.
The standard Proposed Geometry Project file naming convention is JPC###.alg and is stored under the Specialties Group folder structure under InRoads. For example; \\Projects\14942\Design\InRoads\14942.alg.
The Typical Section Library contains templates, decision tables, cut and fill tables, material tables, and transition control names used to model the proposed roadway surface. The standard CDOT Typical Section Library file contains standard templates and tables that can be copied and modified for each specific project requirement. This library is located under C:\Program Files\Workspace-CDOT\Standards-Global\InRoads\Templates\CDOT-Typical Sections.tml. A copy of this file should be placed under the Specialty Group’s project folder under InRoads. The naming convention for the Typical Section Library consists of the Job Project Code (JPC) with the .tml file extension. For example; \\Projects\14942\Design\InRoads\14942.tml.
A template is a cross sectional representation of the driving surface structure. It is made up of layers, with each layer representing a different material used in the pavement or road bed. Each layer creates a design surface using the layer name as the surface name. Template layers are made up of line segments defined by the width and slope from the point closest to the template center to the point furthest from the template center. The segment point furthest from the template center is assigned a TC Name (Transition Control Name). This TC Name can be used to modify the template during processing
A Cut And Fill Table defines a series of possible solutions used to connect the template to the existing surface. Each entry defines a segment that is attached to the end of the template (the POSS). It extends out from that point, at the defined slope and width until one is found that intercepts the existing surface. The first entry that intercepts the existing surface is used. Entries are processed in ascending order of the Height (for Fill) or Depth (for Cut).
A material table works in the same way as a cut and fill table with the addition of a sub-strata. A solution will only be accepted if it intercepts the specified material (sub-strata). The use of a material table requires the various materials to be specified in the existing (target) surface.
A Decision Table is used to connect the template to the existing surface. The table defines segments, much like the templates, except that the information is presented in text format. Each record of a decision table specifies a Start TC Name, End TC Name, Width, Slope, and a Target if it is to intercept a target. The decision table records are processed from the top-down until a solution (target) is found.
Transition Control Names are attached to the ends of segments defined in Templates, Cut And Fill Tables, Material Tables, and Decision Tables. These are also used for the names of corresponding features in the design surface created by roadway modeler. Transition Control Names also supply the Feature Style for the feature. The Feature Style determines the display characteristics and pay item code of the feature.
The Roadway Library contains roadway definitions and independent template controls. CDOT Roadway Library files are saved under the Specialty Group’s project folder under InRoads. The naming convention for the Roadway Library consists of the Job Project Code (JPC) with the .rwl file extension. For example; \\Projects\14942\Design\InRoads\14942.rwl.
The Project File contains the directory location of all the InRoads data files used for a particular project and is used to load all necessary files for an InRoads session. This file is an ASCII file that can be edited using Notepad or Wordpad. Each individual running InRoads will need a personal copy of the .rwk file because the drive letter changes when computers are mapped across the network. The naming convention for the Project file consists of the Job Project Code (JPC) with the .rwk file extension. For example; \\Projects\14942\Design\InRoads\14942.rwk.
This file contains the geometry project, cogo points and surface data that is used to create XML reports. The naming convention for the XML Data file consists of the Job Project Code (JPC) with the .xml file extension. For example; \\Projects\14942\Design\InRoads\14942.xml.
InRoads Survey requires similar files to InRoads for the control of the assembly and display of survey data.
This file specifies survey field coding, survey control codes, and code properties for planimetrics, DTMs, and geometry symbology. This file is standard in the CDOT Workspace and CDOT policy does not allow independent user modifications to this file. If adjustments or additions are required, users are encouraged to submit a change request to CDOT CADD Manager. The request will be reviewed and incorporated into future configuration releases upon approval.
This file contains information unique to the InRoads Survey application such as unit information, text symbology, file options, view options, and planimetrics settings.
For more information concerning Survey Standards see the Survey Manual Web Page