Skip to main content

Oregon State Flag An official website of the State of Oregon »

Oregon.gov Homepage

QuickStart for OpenRoads Designer

This information is intended to provide OpenRoads Designer users with background about how the software is configured to provide ODOT standard symbologies.

Below, you will see ordered steps that are typically taken for design activities in a small project. When you expand each step, you will see links to documentation that explain the configuration and choices you may have when operating the software.

​When using Bentley CAD software, you'll want to ensure that the ProjectWise project you are working in is a CONNECT Design Platform and has a 9_WorkSet folder, or if not, you will need to launch Bentley CAD software from a desktop shortcut and select the OregonDOT WorkSpace and ODOT WorkSet from your C: drive.

- How to Open DGNs and Access ODOT Standards

Create New DGNs

​If your project is in ProjectWise - follow these instructions to use the ProjectWise Explorer to create new DGNs.

​If your work is on a mapped drive or on a network server share - follow these instructions to use your CADD application to create new DGNs.

"wrk" versus "pub" versus "bas_CF"

The recommended practice for naming and referencing civil design files is:
  • Begin your civil design in "pub" files - published files will contain the civil design that you will attach to container files for sharing with others and using for contract plans and quantity estimates.
  • As needed, use "wrk" or working files to hold civil data that should not be shared. Examples are options that were not used and draft notes. "wrk" files may be attached as references to a "pub" file.​
  • Use civil container files, "bas_CF", to share your civil design with others and with the contract plans production process. Do this by attaching "pub" files as references with No Nesting. When the hierarchy and referencing is performed this way, it does not allow access to the "wrk" files and prevents others from accessing your data that is not ready for prime time.

Preparing for Civil Work

The best practice for new civil DGN files is to begin with a 2D seed file for all civil work, except for terrains and survey fieldbook data begin with a 3D seed file.​

TERR

DGN files that will hold terrain models should be created from a 3D seed file. Terrains may be imported from a legacy-type file, created new from features, or created from fieldbook data.
​

GEOM, CORR, CIVL, FEAT, OPNP, XSEC, and Container Files

All civil data, except terrains, should be created by beginning with a 2D seed file. An important step to prepare a civil DGN file for 3D design and for use by others is to attach a terrain as a reference and set the terrain active.
Set as Active Terrain Model is a critical final step in the creation of civil container files.
Setting a terrain active in a 2D DGN file causes the following:
  • Creates an ORD/OSD-managed 3D model
  • Attaches 3D models in current references to the new 3D model
  • Self-references the new 3D model into the 2D model of the active file with live nesting, and
  • When you make reference attachments in the future, it attaches their 3D models to the 3D model in the active file automatically​

Create An OITL from the ODOT_ORD_seed.itl

A template library (.itl) is always loaded when you launch ORD/OSD. By default, the read-only ODOT_ORD_seed.itl is loaded from the WorkSpace in C:\ODOT\v2024\Organization-Civil\ODOT_Standards\Template Library. This makes it easy to use the example templates or standard components in a quick corridor. Changes cannot be made to the ODOT_ORD_seed.itl. If custom templates are needed for modeling, use a discipline-specific (.itl) or folow these instructions to create a project-specific (.itl) that auto-loads.​

​Work only in the Default model in any DGN file where you are creating civil data like geometries or corridors.

Do not create new models for civil things with different names. ORD needs to be able to create and manage the Default-3D model. Using models with names other than Default for civil stuff may interfere with ORD's ability to create the managed model and correctly attach it as a reference. Just don't go there.

Create other DGN FILES from seed (with their own Default model) when you need to separate your data. Then attach it as a reference - Default to Default. Use the sequential file naming like, GEOM_XXX_pub_01, GEOM_XXX_pub_02, etc. along with a good description. Use container files to reference together civil data by type.

​ODOT provides default preferences which include the Explorer and the Properties dialogs both docked and pinned open at the left. The Level Display dialog is open and shares a group with the Explorer. The Models dialog and References dialog share a group that is docked at the bottom and unpinned, so you only see tabs. The Feature Definition Toolbar and Civil Accudraw toolbox are open and docked at the bottom.

To make any changes to your Preferences, use the back stage: File>Settings>User - and you will see Preferences and much more.

​The behavior, appearance and annotation of civil elements are controlled by the feature definition assigned to it.​ Feature definitions have assigned feature symbologies and the symbologies are assigned to use element templates. The feature symbology can also be assigned to annotate the element.

- ODOT Alignment Feature Definitions​ and Annotations

- Alignment Stationing Best Practices PDF - (Webinar)​ ​

​Engineering Tips Webinar on 2/16/2022 used an older project that was completed using InRoads V8i to demonstrate the following tasks. The entire webinar is just over 56 minutes long. The links below will take you to specific times during the webinar.

- Setup, Process, and Create the 3D File for the Terrain

- Create a Terrain from a Fieldbook from a DTM

- Explore an Original Ground Terrain​

- Create Horizontal Geometry

- Display Profile of the Terrain

- Cut Stacked Cross Sections

- Cut Plan/Profile Sheets​

A more detailed explanation of these two design deliverables is located in the OpenRoads Designer User Guide:

Plans Production Process and Design Deliverables - Webinar 5/4/22

​OPNP File Creation

XSEC_bas File Creation

Using OpenRoads Designer and the ODOT Drawing Boundary Seeds

Civil Profile and Alternating Plan and Profile - Webinar 11/9/22, Slides​

Below is a series of four webinars that explore key concepts that every designer and CAD technician using the ODOT standards and Bentley CAD software should understand about the design deliverables and plans production process.

Foundations: Models, Container Files, Live Nesting and Design Deliverables (Slides) - (56:35 Webinar)

Drawing Boundaries for the Plans Production Process (Slides) - (54:22 Webinar)

Civil Profile and Alternating Plan & Profile (Slides) - (57:16 Webinar)

Design Deliverables and Plan Sheet Production (Slides) - (56:58 Webinar)