OPEN ROADS

Hello Chetan,

Main Difference between MXRoad and Open Roads is, In MXRoad if you want to edit some alignment after completing your road design then you need to redo everything from start. In open roads, you can easily edit it while doing road or corridor design and move further. Also in MXRoad take you through designing a road, including; creating an alignment and carriageways, applying superelevation, widening the road, designing a junction, adding shoulders, verges and footways, and adding pavement layers but In Open Roads Technology, there is a option called Corridor Modelling which includes carriageway, shoulder design etc.
 
Regards,
Purva Lakde

Hello Chetan,

Main Difference between MXRoad and Open Roads is, In MXRoad if you want to edit some alignment after completing your road design then you need to redo everything from start. In open roads, you can easily edit it while doing road or corridor design and move further. Also in MXRoad take you through designing a road, including; creating an alignment and carriageways, applying superelevation, widening the road, designing a junction, adding shoulders, verges and footways, and adding pavement layers but In Open Roads Technology, there is a option called Corridor Modelling which includes carriageway, shoulder design etc.
 
Regards,
Purva Lakde

Thank you, Is there any link or tutorial for starting open roads.

Hello Chetan,

Thank you for your response.

If you are on learning period of Open Roads Technology then I would suggest you Learn server link. Please refer the following link for your reference. This link help you how to start Open Roads i.e Introduction of Open Roads.

http://learn.bentley.com/app/Public/ViewLearningPathWithMasterCourseExpanded?lpId=106057&mcId=101656

The below link is related to Bentley Communities which includes all the topic of Open Roads including videos as well.

http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/7021.openroads-video-clips-technotes-faqs

Regards,

Purva Lakde

Ok

Well, I've just stumbled upon this post and I'd like just to briefly mention some other differences I've noticed, in case somebody doesn't make it to training videos below ; ). I'd definitely supplement the above with some other crucial facts like:

- string based design (MX) vs. cross-section and corridor based design (OR) (which means you 'extend' pre-programmed cross-section along your centerline - useful for long sections of roads),
- Civil Cells introduced as a solution for a repetitive geometric solutions based on reference strings and geometrical dependencies (it's like copying chunk of MX code / macro and applying it in different locations, just without using code but with pointing reference strings - useful for introducing a change to a corridor, like intersection or layby or a merge / diverge),
- design intent which was 'easy' to track in MX input files is now rally easy to track in OR as it's 'live data' in CAD file (no more 'just let me find this input file responsible for that string' type of problems - you just click it and see how it was created),
- no input files in OR,
- design data is stored in a .dgn file, there's no 'project' like in MX,
- you can reference .dgn files which contain live design data, e.g. you can store terrain model in one .dgn and design in other,
- triangulation, contours are just 'display modes' of a terrain entity (no separate models like in MX),
- elements produced using OR are BIM ready as they can be loaded with information, unlike MX strings, as I've read... (haven't seen it live though),
- and there's entire universe of other aspects like how to make models live, how to provide annotated cross-sections where you like it, how you like them, how to include components (3D entities, not strings) you create in clash analysis, but it's just supposed to be a brief note...

Concerning geometry design mentioned in the other comment, I cannot agree with "In MX, you need to create alignments using PI's", as I've been using only element method in MX so far : )

Hope it makes it somewhat clearer.

Regards, T.