Difference between revisions of "OpenRoads Designer"

From MediaWiki
Jump to navigation Jump to search
(Replaced content with "{{Navbox CAD Training}} The Development Guide has moved to a Sharepoint site. If you haven't visited the new site yet contact MDOT-EngineeringSupportTraining@michigan.g...")
Tag: Replaced
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Navbox CAD Training}}
 
{{Navbox CAD Training}}
  
==[[#OpenRoads Designer Learning Path | OpenRoads Designer Learning Path]]==
+
The Development Guide has moved to a Sharepoint site.
  
 
+
If you haven't visited the new site yet contact MDOT-EngineeringSupportTraining@michigan.gov to request access to the Development Guide.
    <gallery widths = 200px heights = 270px>
 
 
 
        File:LearnPath_Microstation1.png | [[https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=114506&callFrom=MyLp Bentley Learn]] | [[https://web.microsoftstream.com/video/e1ef3017-cf82-498e-a8ae-d91507329597?list=studio Configuring the Workspace]]
 
 
 
        File:LearnPath_ORD1.png | [[https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=114465&callFrom=MyLp Bentley Learn]]
 
 
 
        File:LearnPath_ORD2.png | [[https://web.microsoftstream.com/channel/64c81192-6095-4138-ab7c-584ec452e6d0 Stream]] | <span style="color: red"> -Dataset Coming Soon- </span>
 
 
 
        File:LearnPath_ORD3.png | [[https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=114467&callFrom=MyLp Bentley Learn]]
 
 
 
        File:LearnPath_ORD4.png | [[https://web.microsoftstream.com/channel/e58f6a3e-d591-4fcc-8360-58f9c7908490 Stream]] | <span style="color: red"> -Dataset Coming Soon- </span>
 
 
 
    </gallery>
 
 
 
==[[#Course Overviews | Course Overviews]]==
 
 
 
 
 
{{LearnPath_MicrostationPart1}}
 
 
 
 
 
{{LearnPath_ORDPart1}}
 
 
 
 
 
{{LearnPath_ORDPart2}}
 
 
 
 
 
{{LearnPath_ORDPart3}}
 
 
 
 
 
{{LearnPath_ORDPart4}}
 
 
 
 
 
==[[#OpenRoads Designer Best Practices | OpenRoads Designer Best Practices]]==
 
 
 
===[[#File Federation | File Federation]]===
 
 
 
It is extremely important to protect the data that we are designing. All CONNECT edition data lives in a DGN and can no longer be recovered from an external source such as a GPK file. Federating files allow allows for maximum efficiency when working with a large design team since there is less risk of two designers needing to access the same file.
 
 
 
'''In General'''
 
 
 
*Each alignment should have it's own DGN
 
*Each alignment should have it's own Superelevation DGN (if required)
 
*Each corridor should have it's own DGN
 
*Each designer should work in their own template library
 
 
 
While this does create a lot of DGN files on a large project, container files can be created for each type of file to make accessing or reviewing other data more streamlined.
 
 
 
===[[#Corridor Processing Order | Corridor Processing Order]]===
 
 
 
Understanding what a corridor is doing it is processing is important because the techniques that are used to create the corridor can have a large impact on processing speed. In general, the corridor is processed if the following order:
 
 
 
 
 
# The template is dropped, and points are placed in their default location as they are currently saved in the template library
 
# Parametric constraints are applied; Points are recalculated
 
# Horizontal Feature Constraints are applied; Points are recalculated
 
# Point Controls are applied; Points are recalculated
 
# Display rules are computed
 
# End conditions are solved
 
 
 
 
 
'''Some important notes on the above processing order'''
 
 
 
* You can think of the order of processing as a priority for that specific constraint. For example, if a point control and a parametric constraint are placed on the same point over the same station range, the point control will win. This is because point controls are calculated after parametric constraints.
 
 
 
* The locations of the points are calculated and updated multiple times. Display rules are not calculated until after the location of the points have been established. A complex template with many display rules will process much slower than a simple template because the locations of template points are calculated multiple times even if the component is not visible.
 
 
 
===[[#Corridor Modeling Techniques | Corridor Modeling Techniques]]===
 
 
 
There are many different effective approaches to corridor modeling. In general, the modeling approach will fall into one of three categories
 
 
 
# Super Template: One template is used for each corridor. The corridor is manipulated and changed using a series of complex display rules.
 
# Simple Templates:  Multiple full width templates are created for each typical cross section.
 
# Multi-Corridor: Each major component of the corridor is broken into separate corridors. For example, a backbone corridor for the lanes and pavement section, and left and right side corridors for shoulders, curb and gutter, side slopes, and ditches.
 
 
 
It is important to decide the method that will be used to model the project early in the modeling process, as it can be difficult to change gears after a substantial part of the modeling has been completed. The table below has been created to compare the different modeling approaches
 
 
 
{| class="wikitable"
 
|-
 
! Criteria !! Super Template !! Simple Templates !! Multi-Corridor
 
|-
 
| Number of Design Files || style="color: green;"|Least  || style="color: green;"|Least || style="color: red;"|Most
 
|-
 
| Number of Templates || style="color: green;"|Least || style="color: red;"|Most|| style="color: orange;"|Middle
 
|-
 
| Ease of Modifying Templates|| style="color: red;"|Difficult || style="color: green;"|Easy || style="color: orange;"|Moderate
 
|-
 
| Corridor Processing|| style="color: red;"|Slowest || style="color: orange;"|Middle || style="color: green;"|Fastest
 
|-
 
| Supports Multiple Modelers|| style="color: red;"|No || style="color: red;"|No || style="color: green;"|Yes
 
|}
 
 
 
 
 
Items to take into consideration are:
 
 
 
* How many designers will be working on modeling related tasks
 
* How important is corridor processing speed
 
** On a small project, processing speed may not be a consideration as all of the above methods will process fast
 
* Skill level of the design team
 
** While super templates can be difficult to modify, an experienced user may find this easier than managing many templates and corridors
 
** How comfortable is the design team with managing many files
 

Latest revision as of 12:06, 24 January 2025

The Development Guide has moved to a Sharepoint site.

If you haven't visited the new site yet contact MDOT-EngineeringSupportTraining@michigan.gov to request access to the Development Guide.