MDT OPENROADS

TECHNOLOGY

INFORMATIONAL SESSION

NOVEMBER 14, 2017

MEGAN CAIL, P.E.

CE SPECIALIST

MDT ROAD DESIGN

GOALS

� ATTENDEES SHOULD BE ABLE TO:

� DEFINE WHAT SITUATIONS TO USE THE ENHANCED AND LEGACY

WORKSPACES

� UNDERSTAND DESIGN FILE SETUP FOR AN OPENROADS

MODELING PROJECT USING THE NEW MDT FILE STRUCTURE

2

TOPICS

� SOFTWARE VERSIONS

� CADD STANDARDS

� WORKSPACE

� SEED FILES

� FILE STRUCTURE

� REFERENCING RELATIONSHIPS

3

SOFTWARE VERSIONS

� MICROSTATION OPENROADS DESIGNER - CONNECT EDITIONCANNOT BE USED.

� FILES ARE NEITHER FORWARD OR BACKWARD COMPATIBLE AT THIS TIME

4

*For purposes of this session, please

consider ‘OpenRoads’ to be

synonymous with ‘GEOPAK SS4 with OpenRoads Technology’ and not

‘OpenRoads Designer CONNECT

Edition’.

CURRENT MDT SOFTWARE VERSIONS

CADD STANDARDS

� CURRENT CADD STANDARDS AVAILABLE ON THE FTP SITE.

5

WORKSPACE

6

ENHANCED WORKSPACE SETUP

LEGACY WORKSPACE SETUP

WORKSPACE

� 2 SEPARATE UPF (USER PREFERENCE FILES)

� INDIVIDUAL USER WORKSPACE PREFERENCES WILL HAVE TO BE SET FOR

EACH WORKSPACE SEPARATELY.

� 2 SEPARATE UCF (USER CONFIGURATION FILES) STORED ON THE CADD STANDARDS SERVERS. THIS FILE LOADS WHEN MICROSTATION IS OPENED VIA THE PRECONSTRUCTION STARTUP MENU.

� UCFS INCLUDE CONFIGURATION VARIABLES THAT ARE COMMON TO ALL

WORKGROUPS IN EACH WORKSPACE, SUCH AS, PLOTTING SETUP AND

LINESTYLE LIBRARIES.

7

WORKSPACE

� LEGACY WORKSPACE

� PROJECTS CURRENTLY BEING DESIGNED WITH GEOPAK CRITERIA

� ENHANCED WORKSPACE

� PROJECTS NOT PAST ALIGNMENT AND GRADE BY APRIL 2017

� PROJECTS WITH A SCHEDULED LETTING DATE AFTER FFY 2022

� ALL 3-D MODELING PROJECTS

� PROJECTS NOT REQUIRING ADVANCED DESIGN TOOLS (PAVE PRES.)

8

SEED FILES

� LEGACY WORKSPACE

� 1000 UPF

� ENHANCED WORKSPACE

� 10,000 UPF

� ALL PROJECT DGNs MUST BE CREATED

FROM THE SAME SEED

� REFERENCING ISSUES DUE TO DIFFERENT

FILE ORIGINS

� MDT PLOTTING SOFTWARE WILL NOT

ACCEPT .CPBs REFERENCING MULTIPLE SEED FILES

9

FILE STRUCTURE

NEW MODELING FILE NAMING CONVENSION

RDMAP - 2D STRIP MAP FILE• ALL COGO VISUALIZATION OF ALIGNMENTS AND

PROFILES, LINE WORK FOR EDGE OF PAVEMENT,

SIDEWALK, CURB, ETC.

RDCMA – 3D CONTOUR MAP FILE• FOR CRITERIA ONLY

RDETR – EXISTING TERRAIN MODEL FILE• EXISTING GROUND TERRAIN MODEL

• CREATED FROM SURVEY-PROVIDED 3D ELEMENTS,

TIN, OR DTM FILE(S)

RDEFF – EXISTING FEATURES FILE• ROAD DESIGN COPY OF SURVEY FILES

• ELEMENTS ARE FEATURIZED

10

FILE STRUCTURE

RDPTR – PROPOSED TERRAIN FILE• CREATED FROM 3-DIMENSIONAL BREAK LINES CREATED

BY THE CORRIDOR TEMPLATE(S)

RDUMA – UTILITIES MAP FILE

• 3-DIMENSIONAL VISUALIZATION OF UTILITIES WITH

KNOWN DEPTHS AND CLEARANCES

• UTILITIES MODELED IN THE 3-D ENVIRONMENT

• PROPOSED AND EXISTING CULVERTS

RDALN – ALIGNMENT FILE• CONTAINS ALL CIVIL ALIGNMENTS AND PROFILES

• CONTAINS CORRIDOR LINEAR REFERENCE ELEMENTS

(FOR POINT CONTROLS)

RDSUP – SUPERELEVATION FILE• CONTAINS SUPERELEVATION SECTIONS AND LANES

RDCRR – CORRIDOR FILE• CONTAINS 3-DIMENSIONAL ROADWAY MODEL

• CORRIDOR LENGTH: BASED ON COMPLEXITY AND

TEMPLATE DROPS

• SUGGESTED CORRIDOR LENGTH: 1-3 MILES PER FILE

• CREATE SEPARATE CRR FILES FOR CROSSROADS

AND APPROACHES

• NO MORE THAN 25 APPROACH CORRIDORS PER FILE

11

REFERENCING RELATIONSHIPS

� RDETR

� RDEFF – only if the

existing terrain model is created from 3D

elements

� RDALN

� RDETR

� RDEFF

� RDSUP

� RDALN

� RDXSF

� RDETR

� RDEFF

� RDALN

� RDCRR

� RDUMA

� RDCRR

� RDETR

� RDEFF

� RDALN

� RDSUP

� RDCRR

� RDPTR

� RDALN (3D)

� RDCRR (3D)

12

QUESTIONS?

13