Chapter 4 - Developing Electronic Data

From MediaWiki
Revision as of 11:08, 1 April 2021 by HightB (talk | contribs) (→‎4.1.3 OEC and Final Plan Proposed 3D Model Requirements: Updated to include MDOT CONNECT workspace and cleanup of data glitch on apostrophes)
Jump to navigation Jump to search

4.1 Milestone Submittals

Format, contents and file naming convention at the milestone submittals shall be in accordance with Chapter 3. Also see Joint RID Review Checklist and Index.xlsm which is outlined in Section 6.1.

These files must be turned in at all submittals. They can be referenced to the other files specified in this section for milestone submittals if necessary and merged into the final RID files as indicated in Chapter 5. The files listed below not specifically defined in Chapter 3, should use the Miscellaneous (Z) designation.

  • Alignment File(s):
    • Option 1: Can contain all the project alignments. Only one scale is allowed for this file. In the MDOT_02 workspace all alignments must be created with Civil Geometry and utilize a geometry feature style that auto exports to the GPK. It is referenced to the corridor file(s) for use with modeling.
    • Option 2: The RID required geometry can be annotated from the COGO horizontal alignment chains using the Design and Computation Manager (DDB). These can have multiple DGN models for various scales as needed for the plans during design. When using the MDOT_02 workspace actual Civil Geometry alignments auto exported to COGO would be stored in the corridor files or referenced from another design alignment (base) DGN file which must be submitted with the corridor files.
  • Superelevation File(s) – (MDOT_02 only) Can contain all superelevation sections and lanes or can be broken out to match the corridor file limits. Typically referenced to the corridor file.
  • Civil Cell File(s)- (MDOT_02 only) Can contain all civil cells for an entire project, broken out by roadway, type or whatever is need to accommodate the project needs. Civil cells should not be placed in the Corridor files, the exception could be intersections when ditches are needed to flow around a quadrant and continue beyond the civil cell limits.
  • Component File(s) – (MDOT_01 only) Contain the 3D components from Roadway Designer for the entire project or broken out by roadway.

[top of page]

4.1.1 Base Plan or Bridge Study Proposed 3D Model Requirements

3D Models are not required at Base Plan or Bridge Study submittal.

[top of page]

4.1.2 Preliminary Plan Proposed 3D Model Requirements

The RID files submitted with the Preliminary Plans shall include the DGN for the alignment, base files, model files, and Cross Sections that were used to develop the Preliminary Plans. Proposed 3D models submitted at the Preliminary Plan turn-in are expected to include the following elements if applicable to the project:

MDOT_01 Elements

  • All roadways and roadway features including superelevation, pavement transitions and gores
  • Intersections (enough to verify slopes)
  • Driveways (enough to verify the slopes)
  • Crossovers (enough to verify the slopes)
  • Side Slopes
  • Shoulders\flares and any widening
  • Barriers\curb and gutter
  • Ditches (rough locations and slopes only)

MDOT_02 and MDOT_CONNECT Elements

  • All roadways and roadway features including superelevation, pavement transitions and gores
  • Intersections (designed with Civil Cells or enough to verify the slopes)
  • Driveways (designed with Civil Cells or enough to verify the slopes)
  • Crossovers (designed with Civil Cells or enough to verify the slopes)
  • Side Slopes
  • Shoulders\flares and any widening
  • Barriers\curb and gutter
  • Ditches (rough locations and slopes only)


All design models created in the MDOT_02 and MDOT_CONNECT workspace shall be submitted in the Corridor Design Stage: 3 - Review (1x). 3D models should be processed at a maximum template drop interval of 5 feet on roadways for the entire project or maintaining the default Civil Cell settings. In the MDOT_01 workspace long sections of roadway (1000 feet or greater) in both a horizontal and vertical tangent can be processed at a 25 foot template drop interval. It is recommended that the models are processed at an interval which is a multiple of the required plotted cross sections for the best results.


Example: If plotted cross sections at an interval of 25 feet are desired, the model should be processed at 5 feet, 1 foot or in long tangent areas at 25 feet.


Models should also be processed at all critical stations including superelevation transitions, horizontal and vertical cardinal points, the beginning and ending of tapers, gore 2 foot and 22 feet points, the centerline of each driveway, crossovers, intersections, and any other critical area necessary to accurately represent the proposed roadway surface for review.

(The date suffix is not required at the milestones, but will be required for the final posted RID.)

[top of page]

4.1.3 OEC and Final Plan Proposed 3D Model Requirements

OEC and Final Plan 3D model submittal requirements include all RID required for the project as noted in the Project Data Requirements Table. Proposed 3D models will be submitted at the OEC and Final Plan turn-in and are expected to include the following elements if applicable to the project:

MDOT_01 Elements
  • All roadways and roadway features including superelevation, pavement transitions and gores
  • Pavement cross section
  • Intersections
  • Driveways (enough to verify the slopes)
  • Crossovers (enough to verify the drainage and slopes)
  • Medians\Islands (enough to verify drainage)
  • Subgrade and\or subbase surface including day lighting if applicable
  • Side Slopes
  • Shoulders\flares and widenings
  • Retaining walls\barriers\curb and gutter
  • Ditches\Detention Basins
  • Proposed paths (not including ADA ramp facilities, paths within the radii limits at intersections or if intermittent within the project limits at intervals of less than 100 feet in length)
  • Proposed sidewalk (not including ADA ramp facilities, sidewalk within the radii limits at intersections or if intermittent within project limits at intervals of less than 100 feet in length)
 MDOT_02 and MDOT_CONNECT Elements
  • All roadways and roadway features including superelevation, pavement transitions and gores
  • Pavement cross section
  • Intersections
  • Driveways
  • Crossovers
  • Medians\Islands
  • Subgrade and\or subbase surface including day lighting if applicable
  • Side Slopes
  • Shoulders\flares and widenings
  • Retaining walls\barriers\curb and gutter
  • Ditches\Detention Basins
  • Proposed paths (ADA ramp facilities within the limits of any intersection radii are only required when the appropriate MDOT Civil Cells are available)
  • Proposed sidewalk (ADA ramp facilities within the limits of the intersection radii are only required when the appropriate MDOT Civil Cells are available)


All design models created in the MDOT_02 and MDOT_CONNECT workspace shall be submitted in the Corridor Design Stage: 3 - Review (1x). 3D models should be processed at a maximum template drop interval of 5 feet. In the MDOT_01 workspace 3D models should be processed at a maximum template drop interval of 5 feet on roadways and 1 foot at intersections, gores and other transitions and 25 feet in long sections of roadway (100 feet or greater) in both a horizontal and vertical tangent. It is recommended that the models are processed at an interval which is a multiple of the required plotted cross sections for the best results.


Models should also be processed at all critical stations including superelevation transitions, horizontal and vertical cardinal points, low points, the beginning and ending of tapers, radii, and ditches, gore 2 feet and 22 feet points, the centerline of each driveway, crossover and intersection and any other critical area necessary to accurately model the proposed roadway surface.

(The date suffix is not required at the milestones, but will be required for the final posted RID.)

[top of page]

4.2 3D Model Submittal Requirements

This section outlines the 3D Model requirements.

For an outline regarding the data that is required at each milestone turn in see Section 4.1. The section defines when a 3D model is required and the level of detail that is required at each milestone.

At this time MDOT is in the transition phase between the MDOT_01 and MDOT_02 workspaces. Because of this transition we have created multiple versions of the 3D Model Submittal Preparation form.

For an outline regarding how to prepare the 3D model for submittal using the MDOT_01 workspace please refer to 3D Model RID Preparation SS2.pdf. This document is an overview of how to create the required 3D model surfaces and files.

For an outline regarding how to prepare the 3D model for submittal using the MDOT_02 workspace please refer to 3D Model RID Preparation SS3.pdf. This document is an overview of how to create the required 3D model surfaces and files.

To see the 3D model surface feature list for the MDOT_01 workspace please refer to 3D Model Surface Feature List SS2.pdf and for the 3D model surface feature list for the MDOT_02 workspace refer to 3D Model Surface Feature List SS3.pdf.

4.3 3D Modeling Recommendations

Roadway

This section is to assist users in the development of 3D models for roadways.

3D Modeling

See the Roadway 3D Modeling Recommendations.pdf.

Data Management

Designing in MDOT_02 and Plans Production in MDOT_01

Best Practices for use when modeling roadways in the MDOT_02 Workspace but completing plans production with in the MDOT_01 Workspace:

  • MDOT_02 Files in a separate folder from MDOT_01 files
  • 1 GPK for the project stored in the MDOT_02 file folder (MDOT_01 can also read this GPK file)
  • No editing of GPK with Classic COGO tools in either version of the software
  • MDOT_02 3D model lines can be referenced to MDOT_01 drawings for plans production (some level inconsistencies exist between the 2 workspaces that must be resolved at RID turn in when the 3D line work is merged into the MDOT_01 DGN proposed DGN file)
  • MDOT_01 DGN’s cannot be opened in MDOT_02 and MDOT_02 DGN’s can only be referenced to MDOT_01


Required DGN Files
  • 2D DGN File of the TOPO in MDOT_01 format (Source of existing line work for plans production).
    • This file should become the Design_Files: D-XXXXXX_Topo_20YY-MM-DD.dgn
  • GEOPAK TIN File of the in MDOT_01 format (source of existing surface data for plan production of profiles and label tools).
    • This file should not be included in the RID.
  • 3D DGN File containing a Terrain Model in MDOT_02 format (Source of the existing 3D surface model for proposed 3D modeling purposes).
    • This should be the same file as the Survey: S-XXXXXX_Survey_3D_20YY-MM-DD.dgn that is posted to the RID by the Surveyor.
  • GEOPAK TIN file of the proposed 3D surface in MDOT_02 format (Created as part of the modeling process, necessary if plan labeling tools are required for labeling proposed elevations on the plans)
    • This file should be used to create the Models: M-XXXXXX_PrTriangle_20YY-MM-DD.dgn and M-XXXXXX_LandXML_PrTriangle_20YY-MM-DD.xml.


[top of page]

Retrieved from "https://mdotwiki.state.mi.us/design/index.php?title=Chapter_4_-_Developing_Electronic_Data&oldid=3280"