Chapter 4 - Developing Electronic Data - Revision history

BergK1 at 16:01, 24 January 2025

2025-01-24T16:01:10Z

BergK1 at 17:04, 24 April 2024

2024-04-24T17:04:43Z

BergK1 at 17:03, 24 April 2024

2024-04-24T17:03:31Z

BergK1: Replaced content with "{{Navbox DSR|Chapter 3 - Standard Naming Conventions|Chapter 5 - RID Process}} ==4.1 Milestone Submittals== The Development Guide has moved..."

2024-04-24T17:03:23Z

Replaced content with "{{Navbox DSR|Chapter 3 - Standard Naming Conventions|Chapter 5 - RID Process}} ==4.1 Milestone Submittals== The Development Guide has moved..."

BergK1: /* 4.1.2 Preliminary Plan Proposed 3D Model Requirements */

2024-03-08T13:29:42Z

4.1.2 Preliminary Plan Proposed 3D Model Requirements

BergK1: /* 4.3 3D Modeling Recommendations */

2024-03-08T13:22:39Z

4.3 3D Modeling Recommendations

BergK1: /* 4.2 3D Model Submittal Requirements */

2024-03-08T13:21:29Z

4.2 3D Model Submittal Requirements

BergK1: /* 4.1.3 FPC and Final Plan Proposed 3D Model Requirements */

2024-03-08T13:20:08Z

4.1.3 FPC and Final Plan Proposed 3D Model Requirements

BergK1: /* 4.1.3 FPC and Final Plan Proposed 3D Model Requirements */

2024-03-08T13:19:57Z

4.1.3 FPC and Final Plan Proposed 3D Model Requirements

BergK1: /* 4.1.3 FPC and Final Plan Proposed 3D Model Requirements */

2024-03-08T13:19:37Z

4.1.3 FPC and Final Plan Proposed 3D Model Requirements

@@ Line 3: / Line 3: @@
 ==[[#4.1 Milestone Submittals|4.1 Milestone Submittals]]==
-The Development Guide has moved to a Sharepoint site. [https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/ New Development Guide]
+The Development Guide has moved to a Sharepoint site.
-If you haven't visited the new site yet, click the link, then click Request Access. You will be added to the Sharepoint Visitors group, and will receive an email with a link to the Development Guide. If you still have access issues, contact MDOT-EngineeringSupportTraining@michigan.gov
+If you haven't visited the new site yet contact MDOT-EngineeringSupportTraining@michigan.gov to request access to the Development Guide.

@@ Line 3: / Line 3: @@
 ==[[#4.1 Milestone Submittals|4.1 Milestone Submittals]]==
-The Development Guide has moved to a Sharepoint site. New Development Guide
+The Development Guide has moved to a Sharepoint site. [https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/ New Development Guide]
 If you haven't visited the new site yet, click the link, then click Request Access. You will be added to the Sharepoint Visitors group, and will receive an email with a link to the Development Guide. If you still have access issues, contact MDOT-EngineeringSupportTraining@michigan.gov

← Older revision		Revision as of 17:03, 24 April 2024
Line 6:		Line 6:

	If you haven't visited the new site yet, click the link, then click Request Access. You will be added to the Sharepoint Visitors group, and will receive an email with a link to the Development Guide. If you still have access issues, contact MDOT-EngineeringSupportTraining@michigan.gov		If you haven't visited the new site yet, click the link, then click Request Access. You will be added to the Sharepoint Visitors group, and will receive an email with a link to the Development Guide. If you still have access issues, contact MDOT-EngineeringSupportTraining@michigan.gov
−
−	~~Categories: Design Submittal RequirementsRID~~

@@ Line 3: / Line 3: @@
 ==[[#4.1 Milestone Submittals|4.1 Milestone Submittals]]==
-Format, contents and file naming convention at the milestone submittals shall be in accordance with [[Chapter_3_-_Standard_Naming_Conventions|Chapter 3]].  Also see [https://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=71536ffa-6a51-4e45-b38b-da310526378b&fileName=%22 Joint RID Review Checklist and Index.xlsm] which is outlined in [[Chapter_6_-_3D_Model_QA/QC#6.1_Design_Model_Quality_Control|Section 6.1]].
+The Development Guide has moved to a Sharepoint site. New Development Guide
-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_-_RID_Process|Chapter 5]]. The files listed below not specifically defined in [[Chapter_3_-_Standard_Naming_Conventions|Chapter 3]], should use the Miscellaneous (Z) designation.
+If you haven't visited the new site yet, click the link, then click Request Access. You will be added to the Sharepoint Visitors group, and will receive an email with a link to the Development Guide. If you still have access issues, contact MDOT-EngineeringSupportTraining@michigan.gov
-* Alignment File(s):
+Categories: Design Submittal RequirementsRID

@@ Line 26: / Line 26: @@
 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:
-{|
-|style="width:30%"|
+'''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)
@@ Line 47: / Line 36: @@
 *Barriers\curb and gutter
 *Ditches (rough locations and slopes only)
-All design models created in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|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.  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.

← Older revision		Revision as of 13:22, 8 March 2024
Line 107:		Line 107:

	====[[#Data Management\|Data Management]]====		====[[#Data Management\|Data Management]]====
−	=====Designing in [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_02]] and Plans Production in [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_01]]=====
−
−	Best Practices for use when modeling roadways in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_02]] Workspace but completing plans production with in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_01]] Workspace:
−
−	* [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_02]] Files in a separate folder from [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_01]] files
−	* 1 GPK for the project stored in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_02]] file folder ([[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_01]] can also read this GPK file)
−	* No editing of GPK with Classic COGO tools in either version of the software
−	* [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_02]] 3D model lines can be referenced to [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|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 [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_01]] DGN proposed DGN file)
−	* [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_01]] DGN's cannot be opened in [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_02]] and [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_02]] DGN's can only be referenced to [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_01]]
−
−
−	~~: '''Required DGN Files'''~~
−	~~:* 2D DGN File of the TOPO in [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_01]] format (Source of existing line work for plans production).~~
−	~~:**This file should become the [[Chapter_3_-_Standard_Naming_Conventions#Design_Files:\|Design_Files:]] D-XXXXXX_Topo_20YY-MM-DD.dgn~~
−	:* GEOPAK TIN File of the in [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|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 [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_02]] format (Source of the existing 3D surface model for proposed 3D modeling purposes).
−	~~:**This should be the same file as the [[Chapter_3_-_Standard_Naming_Conventions#Survey:\|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 [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|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 [[Chapter_3_-_Standard_Naming_Conventions#Models:\|Models:]] M-XXXXXX_PrTriangle_20YY-MM-DD.dgn and M-XXXXXX_LandXML_PrTriangle_20YY-MM-DD.xml.~~
−

@@ Line 95: / Line 95: @@
 For an outline regarding the data that is required at each milestone turn in see [[Chapter_4_-_Developing_3D_Models#4.1_Milestone_Submittals|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 [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] and [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|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 please refer to [http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=48d94203-fb47-4920-b9f5-bd6786e5f96e&fileName=%223D%20Model%20RID%20Preparation%20SS3.pdf%22 3D Model RID Preparation SS3.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 [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace please refer to [http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=73958c98-d6cc-473c-ba9b-07043ac49ae9&fileName=%223D%20Model%20RID%20Preparation%20SS2.pdf%22 3D Model RID Preparation SS2.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 3D model surface feature list refer to [http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=33572229-baca-4b5c-8303-34a465677aa3&fileName=%223D%20Model%20Surface%20Feature%20List%20SS3.pdf%22 3D Model Surface Feature List SS3.pdf].
 ==[[#4.3 3D Modeling Recommendations|4.3 3D Modeling Recommendations]]==

← Older revision		Revision as of 13:20, 8 March 2024
Line 80:		Line 80:
	*Proposed paths (ADA ramp facilities within the limits of any intersection radii are only required when the appropriate MDOT Civil Cells are available)		*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)		*Proposed sidewalk (ADA ramp facilities within the limits of the intersection radii are only required when the appropriate MDOT Civil Cells are available)
−	\|}

@@ Line 66: / Line 66: @@
-'''[[MDOT_CONNECT]] Elements'''
+'''MDOT_CONNECT Elements'''
 *All roadways and roadway features including superelevation, pavement transitions and gores
 *Pavement cross section