ODOT Consultant Meeting, July 13, 2015

ODOT Consultant Meeting, July 13, 2015
ODOTcadd Standards for Bentley’s OpenRoads Technology Eric Thomas, CADD Consultant On behalf of the Office of CADD and Mapping Services ODOT Consultant Meeting, July 13, 2015

Presentation Overview
Take a detailed look at the ODOTcadd Standards and configuration for OpenRoads Cover the following topics: MicroStation Configuration Folder Structure and File Names Design File Settings Feature Definitions and Element Templates ODOTcadd Standards for OpenRoads

Presentation Overview
Cover the following topics: Survey Processing Horizontal Geometry Vertical Geometry Corridor Modeling SUDA/SUE/StormCAD Cross Sections Plan Production ODOTcadd Standards for OpenRoads

MicroStation Configuration
ODOT will use desktop shortcuts to access PowerGEOPAK or MicroStaion Shortcuts to open with the Legacy V8iSTD standards or the new ODOTcadd Standards Workspace switches defined as follows: -wsODOTV8istd=1 -wsODOTcadd=1 ODOTcadd Standards for OpenRoads

Upon access, MicroStation runs all CFG files found in: C:\ProgramData\Bentley\PowerGEOPAK V8i (SELECTseries 4)\WorkSpace\Standards ODOT copies a “redirect” configuration file to this folder z_ODOT_Redirect_Local.cfg z_ODOT_Redirect_Network.cfg ODOTcadd Standards for OpenRoads

The Redirect files are located here: \ODOTcadd\Standards\config\Standards\redirect Edit the paths as necessary for your site installation The Redirect file calls the appropriate standards ODOTcadd Standards for OpenRoads

The Redirect file calls the appropriate standards based on the workspace switch defined in the Shortcut %if defined(ODOTcadd) --- Variable Definitions for ODOTcadd--- %elif defined(ODOTv8istd) --- Variable Definitions for V8iSTD --- %endif ODOTcadd Standards for OpenRoads

The redirect file defines the following: The location for the ODOTcadd Standards The location for the User Configuration and User Preference files The location for MicroStation Project Configuration Files (PCF) The Temp folder for temporary resources Calls the Site Configuration File (CFG) ODOTcadd Standards for OpenRoads

Site specific standards for ODOTcadd are defined in the Site Configuration file: \CADDServices\ODOTcadd\Standards\config\Standards\ODOT_Site_V8iSS3.cfg This file is called by the Redirect file This file defines all the standards for ODOTcadd and OpenRoads ODOTcadd Standards for OpenRoads

Project Specific variables are defined in a MicroStation PCF file The location of the PCF files is defined in the Redirect file When MicroStation is opened, the PCF must be selected before opening a design file ODOTcadd Standards for OpenRoads

The PCF defines only variables specific to the project The Project Start Location (\design folder) Project Specific Seed Files Geographic Coordinate System Libraries OpenRoads Template Library ODOTcadd Standards for OpenRoads

Using shortcuts to access ODOT CADD Standards allows ODOT users to open MicroStation/PowerGEOPAK using the Bentley configuration Useful to access Bentley delivered workspaced for Bentley Learn Useful for consultants who need to open MicroStation with multiple agency standards ODOTcadd Standards for OpenRoads

Folder Structure and Design File Names
ODOT’s Folder Structure has been updated for projects using the ODOTcadd Standards Design File Names have been modified to include an underscore character between the PID number and the two character file type code. Example: _BP001.dgn ODOTcadd Standards for OpenRoads

Changes detailed in the Draft ODOTcadd version of the ODOT CADD Engineering Standards Manual ODOTcadd Standards for OpenRoads

These changes impacted multiple VBA applications Affected applications have been updated for ODOTcadd These changes are not backwards compatible with projects currently under development using the legacy V8iSTD CADD Standards ODOTcadd Standards for OpenRoads

Now projects are housed in a new the following folder: i:\ProjectData The project location is defined in a Project Configuration File (PCF) for each project ODOTcadd Standards for OpenRoads

Project Configuration Files are located in the following folder: i:\ProjectPCF The PCF location is defined in the Redirect File ODOTcadd Standards for OpenRoads

ODOTcadd Standards for OpenRoads
Design File Settings Settings specific to OpenRoads defined in the ODOT Seed Files Design File Settings > Civil Formatting ODOTcadd Standards for OpenRoads

Features and Element Temlplates
What is a Feature? Anything in the design representing a Real World entity Curb and Gutter Manhole Ditch Fill Slope Etc… ODOTcadd Standards for OpenRoads

Features and Element Templates
Feature Definitions define properties that determine how a design element is displayed in multiple contexts: Survey Profile Plan Cross Section 3D Model ODOTcadd Standards for OpenRoads

Three types of features: Point Features Catch Basin, Tree, Telephone Pole, etc… Linear Features Edge of Pavement, Wall, Ditch line, etc… Surface Features Existing Ground, Pavement Layers ODOTcadd Standards for OpenRoads

Depending on the type, the feature definition will have different properties --- add graphic --- ODOTcadd Standards for OpenRoads

Feature Definitions can refer to a “Native” standard (D&C Manager, Survey Manager) or a MicroStation Element Template ODOTcadd Standards for OpenRoads

Feature Definitions are defined in DGN Libraries When the feature is used, it is copied into the design file (just like a level, line style, font, etc..) If the Feature uses an Element Template, the ET is also copied to the active file ODOTcadd Standards for OpenRoads

The local Feature definition is always used first If the DGNLIB definition of the Feature or the Element Template is changed, the local definition is used unless the feature and element template are manually deleted and the element redrawn Note: Element Templates can be updated from the library, features cannot ODOTcadd Standards for OpenRoads

Feature Definitions are created, modified, and reviewed using the Civil Standards tab in Project Explorer Two categories listed, the current DGN file, and all libraries ODOTcadd Standards for OpenRoads

ODOT’s Feature Definitions use Element Templates with the following exceptions: Horizontal Geometry features use the Design and Computation Manager Survey Features use the Survey Manager Database ODOTcadd Standards for OpenRoads

Survey Processing Process in a 3D design file The choice of whether to use a grid or ground Geographic Coordinate System (GCS) is made at this stage ODOTcadd Standards for OpenRoads

Survey Processing The purpose of a GCS is to establish the location of the data on the Earth’s surface Once set, it should not be changed The GPK file is NOT Georeferenced Changing the GCS in the DGN file does not change the GPK file But what about Auto Persist? ODOTcadd Standards for OpenRoads

Survey Processing Field Codes are defined as OpenRoads Features Survey Features are defined in ODOT_Features_Survey.dgnlib Attached by configuration variable defined in ODOT_Site_V8iSS3.cfg Features can be reviewed in Project Explorer Civil Standards > Libraries > Feature Definitions ODOTcadd Standards for OpenRoads

Survey Processing Survey Features are defined to use the “Native Style” which associates the Feature with the legacy Survey Manager Database (SMD) definition The SMD file is specified by a configuration variable in ODOT_Site_V8iSS3.cfg CIVIL_SURVEY_STYLEFILE = $(ODOT_STD)geopak/Survey/ODOT_SMD.xml ODOTcadd Standards for OpenRoads

Survey Processing Office Use field codes Additional field codes that are not defined in ODOT’s data collectors Can be used to change the code on an item in the office Includes features for Drainage, Lighting, Pavement Marking, and a few other miscellaneous items Add to your data collector code list if desired ODOTcadd Standards for OpenRoads

Survey Processing Survey processing parameters are defined in the Survey Settings, which can be reviewed and edited using Project Explorer Project Settings > Survey These settings are copied to the active file when the survey data is processed ODOTcadd Standards for OpenRoads

Survey Processing It may be desirable to copy the settings to the file before processing in order to make changes The Link Code Position is set to Before Point Feature Definition Create Terrain Model for All Field Books is set to “True” ODOTcadd Standards for OpenRoads

Survey Processing Terrain Models Stored in the Survey DGN file Not recommended to edit the terrain models – edit the source data which is edits the terrain Accessed by other users via reference attachment ODOTcadd Standards for OpenRoads

Survey Processing Terrain Model Display is defined by choosing an OpenRoads Feature The Feature points to a MicroStation Element Template for the actual parameters Terrain Model Element Templates are defined in ODOT_Features_Design.dgnlib ODOTcadd Standards for OpenRoads

Survey Processing The terrain boundary is displayed using the General Settings for the Element Template The General Settings define the existing ground line symbology for cross sections. That is why it is set to XS_X_Ground_Line Occasionally the boundary will not display with the expected symbology ODOTcadd Standards for OpenRoads

Survey Processing Drainage Attributes/VBA Apps ODOT looking to move away from the legacy VBA apps New process needed to import existing drainage information into StormCAD John Drsek developing 3D drainage components for StormCAD ODOTcadd Standards for OpenRoads

Survey Processing Suggested field collection process: Shot on top of the grate Shot at the bottom of the drainage structure Shot at the invert of each pipe at both ends Would like to solicit input from Surveyors on this process ODOTcadd Standards for OpenRoads

Survey Processing Survey provides the following to Design: 3D DGN file with the topo and the Terrain Model Design accesses this information through reference file attachments Ground Coordinate System DTY file (if applicable) Customized Seed Files with the GCS ODOTcadd Standards for OpenRoads

Horizontal Geometry Stored in the DGN Which DGN file? \design\geopak\basemaps\nnnnnn_BK###.dgn All Geometry in one DGN? One DGN for each alignment? 2D or 3D? Work in 2D, the 3D Model is generated automatically by OpenRoads ODOTcadd Standards for OpenRoads

Horizontal Geometry Do I still need a GPK file? Yes. Geometry is also stored in the GPK file for use with legacy GEOPAK tools Create GPK before defining alignments Set Working Directory Manually – The GEOPAK Project Manager is optional Disable Visualization ODOTcadd Standards for OpenRoads

Horizontal Geometry Several Feature Definitions are available for Horizontal Geometry Auto Persist is set to “True” Auto Annotate is set to “True” ODOTcadd Standards for OpenRoads

Horizontal Geometry Auto Persist Automatically exports the alignment to the GPK with it is created or modified Does not recognize the GPK Redefine setting Auto Annotate Annotates the alignment when created or modified Auto Persist must be active Annotation Scale must be set to match Feature ODOTcadd Standards for OpenRoads

Horizontal Geometry Recommended Alignment Creation Workflow: Set the working Directory Create the GPK file Turn off Visualization in the GPK ODOTcadd Standards for OpenRoads

Horizontal Geometry Recommended Alignment Creation Workflow: Create all geometry using the feature “Scratch Alignment” Auto Persist and Auto Annotate are set to False Used for laying out your design without Auto Exporting ODOTcadd Standards for OpenRoads

Horizontal Geometry Recommended Alignment Creation Workflow: Change the alignment to the desired feature after the design is complete Set the Annotation Scale to match the desired feature Set the Feature Name before assigning the Feature to the element When the feature is assigned, Auto Annotate and Auto Persist are processed ODOTcadd Standards for OpenRoads

Horizontal Geometry Notes on Auto Persist Only one scale can be annotated/associated with the alignment Use D&C to annotate additional scales in the BK file ODOTcadd Standards for OpenRoads

Horizontal Geometry Users access the alignments via reference attachments ODOTcadd Standards for OpenRoads

Vertical Geometry Vertical Alignment stored in the DGN Which DGN file? The same design file as the alignment \design\geopak\basemaps\nnnnnn_BK###.dgn ODOTcadd Standards for OpenRoads

Vertical Geometry Workflow: Reference the Terrain and set it active before extracting the Existing Ground profile Vertical Alignments are displayed and defined in a Profile Window Select Open Profile Window from the pop-up menu when the horizontal alignment is selected When the profile window is opened, the existing ground profile is extracted from the active terrain model ODOTcadd Standards for OpenRoads

Vertical Geometry The profile window is used as a temporary display of the profile graphics The profile is not written to the file The existing ground line symbology is defined by the Terrain Model Feature/Element Template Proposed profiles inherit the symbology from the Alignment Feature Definition ODOTcadd Standards for OpenRoads

Vertical Geometry Multiple vertical alignment can be stored for a single horizontal alignment Only one profile can be set as the “Active Profile” ODOTcadd Standards for OpenRoads

Vertical Geometry Profiles must be exported to the GPK and plotted with D&C Manager for plan production The Proposed Profile feature definition is set to Auto Persist Existing Profiles must be manually exported (General Geometry Task Group) ODOTcadd Standards for OpenRoads

Corridor Modeling Which Design File? \design\geopak\basemaps\nnnnnn_KM###.dgn One corridor per DGN Use 2D files the 3D graphics are generated automatically ODOTcadd Standards for OpenRoads

Corridor Modeling Template Library \ODOTcadd\Standards\Geopak\Road\templates\ ODOT_Templates.itl Provided as a starting point for modification Based on old Roadway Designer ideals Uses complex method to automate shoulder break on the high side of superelevation Will be revisited this fall/winter ODOTcadd Standards for OpenRoads

Corridor Modeling ODOT Template Library Usage Copy to: \design\geopak\nnnnnn_Templates.itl Defined in the PCF file: CIVIL_ROADWAY_TEMPLATE_LIBRARY = $(_USTN_PROJECTDATA)Geopak/123456_Templates.itl Use the Project Templates folder to create your templates ODOTcadd Standards for OpenRoads

Corridor Modeling Template Library Names and Features are very important Features are assigned to Points and Components Template Point Features Use plan view equivalents for surface points Use the “Template” features for subsurface points ODOTcadd Standards for OpenRoads

Corridor Modeling Template Library Point Names must be consistent from Template to Template to ensure connectivity Point Name Overrides can be used for multiple end condition points Standard Point Names? Nothing published at this time Looking for suggestions/additional input on this ODOTcadd Standards for OpenRoads

Corridor Modeling Template Library Affixes Recommend using prefixes “L-” and “R-” ODOTcadd Standards for OpenRoads

Corridor Modeling Template Library The Subgrade is not defined in the templates Add the subgrade manually to your templates ODOTcadd Standards for OpenRoads

Corridor Modeling Template Library Why is there an XGL point in the templates? Used for Cross Section annotation of the existing ground profile elevation ODOTcadd Standards for OpenRoads

Corridor Modeling Generating Corridors: Select the Create Corridor command from the pop-up menu when an alignment is selected Named according to the Horizontal Alignment Design Stages Define commonly used settings for a corridor ODOTcadd Standards for OpenRoads

Corridor Modeling Generating Corridors: Design Stages Defined in ODOT_DesignProjectSettings.dgnlib Defines the meshes created (top mesh, bottom) and whether 3D linear features are created Copied to the Active Model when used Reviewed in Project Manager Civil Standards > Project Settings > Corridor Design Stages Template Drop Interval Multiplier defined for each available stage ODOTcadd Standards for OpenRoads

Corridor Modeling Generating Corridors: Template Drop Interval Recommend using 5’ 2D lines are drawn using the Feature assigned to the point The 3D Model is automatically referenced to the 2D model I normally turn this off ODOTcadd Standards for OpenRoads

Corridor Modeling Generating Corridors: Template Range Graphics CM_Corridor_Template_Range_Graphics Corridor Graphics CM_Corridor_Graphics Handles used to select the corridor ODOTcadd Standards for OpenRoads

Corridor Modeling Superelevation Superelevation shapes normally defined in the Corridor DGN file Shape Display: Workspace > Preferences > View Options – Civil > Superelevation Settings Turn on/off Shape display View Preferences Fill can also turn off Shape display ODOTcadd Standards for OpenRoads

Corridor Modeling Superelevation: The Superelevation process uses the legacy GEOPAK .SEP files After computing Superelevation, use the Assign to Corridor command ODOTcadd Standards for OpenRoads

Corridor Modeling Superelevation: Points in the template with Superelevation Flag toggled on are considered as superelevation points The shoulder break on the high side of superelevation is automatically applied when using the ODOT templates ODOTcadd Standards for OpenRoads

Corridor Modeling SUE/SUDA/StormCAD John Drsek overseeing development of standards Survey Data to StormCADD workflow under evaluation As previously stated, a new data collection procedure will be recommended ODOTcadd Standards for OpenRoads

Cross Sections Draw cross sections in a separate dgn file nnnnnn_XC###.dgn nnnnnn_XS###.dgn ODOTcadd Standards for OpenRoads

Cross Sections Cross Sections are cut from the 3D model To show up on the cross section, it must be in the model Before cutting sections, attach all the models that you want to use as for the cross sections as references in the XC or XS design file’s Design model. ODOTcadd Standards for OpenRoads

Cross Sections Cross sections are drawn into their own design model The software creates the model The model is named according to the selected horizontal alignment ODOTcadd Standards for OpenRoads

Cross Sections Cross Section preferences are defined in the following file: \CADDServices\ODOTcadd\Standards\Geopak\Road\xin\ODOT.xin Assigned by a configuration variable in ODOT_Site_V8iSS3.cfg CIVIL_XIN_FILE = $(ODOT_STD)geopak/road/xin/ODOT.xin ODOTcadd Standards for OpenRoads

Cross Sections ODOT provides 3 cross section preferences: Sheet: CROSS 10 Scale Sheet: CROSS 5 Scale Stacked: GEOPAK Format The GEOPAK Format preference draws pattern lines and GEOPAK control cells Useful if you plan to run GEOPAK Criteria or earthwork computations ODOTcadd Standards for OpenRoads

Cross Sections GEOPAK Pattern Lines and Control Cells are not drawn with the CROSS formats Cross Section sheets can also be generated using the legacy GEOPAK Tools if you use the Stacked: GEOPAK Format option ODOTcadd Standards for OpenRoads

Cross Sections The Cross sections are not dynamically linked to the model To recut cross sections, delete the cross section model first ODOTcadd Standards for OpenRoads

Cross Sections Annotation: Cross sections are not annotated automatically Annotation must be done manually ODOT has not configured the preferences for this option ODOTcadd Standards for OpenRoads

Cross Sections Annotation: Feature Definitions assigned to the Template Points control how the intersected feature line appears in the cross section Surface Features use the following Element Template: Cross Sections\XS Intersection Location ODOTcadd Standards for OpenRoads

Cross Sections Annotation: Cross Section Annotation uses these crossing features for annotation purposes The XGL Point in the Templates was included for annotating the existing ground elevation ODOTcadd Standards for OpenRoads

Plan Production Plan Production tools are provided by the legacy software functions GEOPAK Functions: D&C Mannger Plan/Profile/XS Labelers Plan and Profile Clip Etc… ODOTcadd Standards for OpenRoads

Questions? ODOT: Consulting: ODOTcadd Standards for OpenRoads

Subsurface Utility Design and Analysis
(SUDA) Subsurface Utility Engineering License StormCAD License (100 Inlets Included) SUDA is built from Bentleys leading and proven H&H (Haestad) technology. Civil users get integration and data fidelity with SewerCAD, SewerGEMS, StormCAD, and CivilStorm. With this integration, civil users can easily move into more advanced analysis such as time dependent flows available with products like CivilStorm. NEXT SLIDE Conflict Management SUE Attribution 3D Modeling of all underground Integrated with OpenRoads Storm/Sanitary Hydraulic Analysis and Design Hydrology

SUDA Known Limitations
-Text labels in Node Cells (drop text elements into linear elements) -Global Origin Shift -MicroStation Modify Commands -Morph Utility Types Can change feature (gas type to water type) but underlying intelligence is not changed -Node Rotation Rule –relative rotation angle ruled to a linear element will be added in next release -Multi Select Pipe Size Edits -Point Cloud Clash Detection

ODOT Standards/Progress Update
Focus on Drainage All Catch Basins (2-2A, 2-2B, 2-3, 2-4, 2-5, 2-6, 3, 3A, 4, 4A, 5, 5A, 6, 7 and 8) have 3D cells and features created. Working on Manholes(Types 1, 2, and 3 have 3D cells and features created) Inlets and Headwalls next. Start on setting up the analysis (StormCAD) with SS4 Update

ODOT Consultant Meeting, July 13, 2015

Similar presentations

Presentation on theme: "ODOT Consultant Meeting, July 13, 2015"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

ODOT Consultant Meeting, July 13, 2015

Similar presentations

Presentation on theme: "ODOT Consultant Meeting, July 13, 2015"— Presentation transcript:

Similar presentations

About project

Feedback