Week 11 Challenge

Q1. Copy T-intersection civil cell DGNLIB

Aim & Introduction

Civil cells templates are used in order to connect the proposed road to match the existing junctions or to create special tie-in conditions with existing ground.

Procedure.

A detailed explanation of civil cell copy template has been detailed below.

Open ORD=> Browse 2D seed file =>Name the file as Civil cells=>blank page opens up=> Now go to model detailing=>Civil cells tab=> click place a civil cell=> small window opens up=> click on the ... civil cell name=>pick civil cells window opens up=> click on T-intersection dgnlib(default)=> click on Basic T(urban) and the template window opens up.

Note: Reference lines must be designed in the dgn file before placing any civil cells template into any file.

Now go to DGN library=> for this go to File(top left corner)=>settings=>configuration=>variable=>window opens up=>type civil cells=>select CIVIL_CIVILCELLDGNLIBLIST=>click edit =>Another window opens up which shows the path for the civil cells dgn library(copy or snapshot the reference for the future.

Note: Don't edit anything directly in the 'Edit configuration variable'.

Now close the window and go back to File=>Open=>Browse=>(before browsing the file make changes in the file type as DGN library files) and no files are visible

So browse C:program data/Bentley/openroads designer CE/configuration/Organization -Civil/Imperial/Dgnlib/civil cells

Now hit open , 2 new windows open up with T-intersection default view and T-intersection 3D view. Now go to explorer=>T-intersection dgnlib(default)=>civil cells=>T basic rural=>click on the plan C/l => flyout menu=>open the profile view=> a profile view opens up with a default level.

Now do the profile for edge of pavement from the plan => a profile opens up.

Note: Click on the visible civil handles on the civil cell, it can be seen that 2 template drops exist in a civil cell. Even though the civil cells look like a corridor, it doesn't have the properties of a real corridor and it has been divided into a linear component and a surface component.

Also, the angle of the civil cells can be modified with the help of civil rules on the base line.

In order to place the civil cells into a corridor=> Open ORD=>browse corridor basics.dgn ( before that change the file type from dgnlib to cad files)=>open=>new window opens up=>click on the corridor=>flyout menu=>click lock deactivate rule(just to avoid processing all the time).

To put the civil cells near the 1st intersection, it is necessary to have the CL and profile for the clipped area. Just hover the cursor on the CL, it can be noted that the Geom temp line has got an active profile. So go to File=>Open project mainline alignment latest.dgn and the file opens up with following attachments as shown below.

Now attach corridor basics.dgn to project mainline alignment latest.dgn and turn off the display of project mainline alignment latest, survey topo, eterrain file and corridor basics.dgn. Go ahead and design the CL for the junction .

For designing the CL, go to Geometry=>simply select both lines=>hit space key=>copy command=>snap to any nearby points=>keep it back =>come back horizontal=>complex geometry=>define by best fit=>small window opens up=>select complex by edges method and keep everything else default=> Now the CL has been created.

Now click on the CL=>flyout menu=>convert to horizontal rules=>now the CL has become a proper horizontal member. Go ahead and turn the display on for ROW existing and the topo and adjust the length of the CL and shorten it with civil rules. Now turn the display off for TOPO and design the profile for this line=>before that assign and FD to this line => go to geometry=>standard=>set FD=>Alignment=>Geom baseline Driveway=>name the element as 'Geom DW'. Now click on the element=>flyout menu=>open profile view.

Go to vertical=>draw a profile curve with vertical=>complex by PI=>set the FD active.

Note: Even though the Grade defence is more it can still work for minor intersections.

In order to design the intersection, the proposed level of the mainline alignment at the intersection must be known. So, go to vertical=>profile creation =>profile intersection point=> Select the small intersection line 1st and mainline alignment 2nd, reset to complete and magenta line appeared on the profile which is the correct level for the intersection and the profile needs to be redesigned and cross slope to be taken into account while designing

For that, go to references, turn display on for corridor basics=>go to geometry=>vertical=>profile creation=>profile intersection point=>select the CL of small intersection=>pick both EOPs of the main line alignment=>finally pick each CLs and reset to complete. Now 2 more magenta points have been appeared on the profile and the intersection must be designed based on the available data and shoulder details to be added later on.

Go to vertical and draw simple profile line to match 3 points and observe the slope of it and try to understand the mainline road characteristics of that location. Also, it can be seen that cursor moves equally in plan and profile window and draw simple limit of construction lines based on the location in the plan.

Also, it can be noted that length of each line is about 11' and 22 ' required as per the standards. So, extend line each side to make it 22' in each side and draw a smooth profile from the limit of construction to match pavement lane.

Now make it smooth by applying curves.

Make the profile active from flyout menu. Now in order to place the civil cell=> go to file =>open corridor basics.dgn=>attach Roadwayplan.dgn=>Open 3 views=>Go to geometry=>Horizontal=>Draw a line at the outer end of the junction section (on both sides). This is done in order to select the Entrance rural civil cell which is having 3 reference lines. Now go model detailing =>place a civil cell=>Entrances=>Entrance rural=>Ok=>Locate 3 reference lines( First active EOP of main corridor, next locate C/L of the junction part and finally locate the outer end line which drawn)=>a cyan colour civil cell appears over the corridor=> click on the brown arrow to arrange the direction and location of the civil cell =>locate the corridor to be clipped message appears but in this context the corridor has already clipped=> so, reset and accept.

Note: If the 3D created with errors( for eg: the EOP line which selected might not have a profile in it) or in order to adjust the outer line, then click on that specific line plan (EOP or EOS)view=> flyout menu=>open the profile view=>go to geometry=>vertical=> profile creation=>select=>project profile range to element=>locate the element to project (which is the same line )=>select the plan element to project on to (which is the line just outside of the clipping area and located in line with specific element without profile) , so select it=>project on to ( select the same line without profile)=>select range from start of the clipping area outer line(LHS) to end of the clipping area outer line (RHS). Again, the line created has no profile and the profile must be projected from the nearby inner line towards the outer line. For that click on the outer line (line drawn and projected at outside) => flyout menu=>open profile view. Now go to =>profile creation and project the line of the inner EOP or Eos towards the outer line.

Note: if there is EOS or EOP line, go to horizontal=>line=>draw a simple line with the same FD(overlapping or extending beyond the point of contact of existing EOS or EOP on both sides in order to understand the profile of road at end points). Go to vertical and open profile view for the line and do the same procedure described in the above paragraph.

Do the same process for both sides and place the civil cell in the opposite side too. Now the dgn file will look like as shown below.

In the above shown image, one lane from EOP to EOS is missing on both sides. In order to model the missing lane, go to corridor = Template=>Create template=>Skill Lync project=>Training 01=> ITL file opens up=> double click on the LHS shoulder=>component properties window=>Display rules=>edit=>delete Not Intersection Left=>Apply=>Ok. Now click on the Buffer component=>display rules=> currently there is no display rules=> so click edit=>select rule=> CL_INT_to left=>later add NOT ( make it NOT CL_INT_to Left)=> come back and check in the next window if it is giving '=true' value which is very important=>apply=> close . Now test the null point for LHS horizontally and make sure that LHS buffer is disappearing when testing. Now repeat the same process for RHS . Once done all the changes, unlock the deactivate rule from the flyout menu. Now select the template flyout menu=>synchronize with library and subsequent 3D model change will be visible as shown below.

Note: if the buffer is not disappearing, then Go to buffer and check if there is any mixing of R and L components. Also, the radius of the Civil cell curve can be modified by selecting the template and increasing or decreasing the radius using civil rules.

Results

Thus, civil cells can be placed into a corridor.

Q2 DGLLIB file list.

Aim & Introduction

The DGNLIB file contains a list civil cell templates which can be used to create specific junction conditions along the main corridor.

Procedure

The procedure for opening the DGNLIB will be explained below.

Open ORD=> Browse 2D seed file =>Name the file as Civil cells=>blank page opens up=> Now go to model detailing=>Civil cells tab=> click place a civil cell=> small window opens up=> click on the ... civil cell name=>pick civil cells window opens up=> click on T-intersection dgnlib(default)=> click on Basic T(urban) and the template window opens up.

Now go to DGN library=> for this go to File(top left corner)=>settings=>configuration=>variable=>window opens up=>type civil cells=>select CIVIL_CIVILCELLDGNLIBLIST=>click edit =>Another window opens up which shows the path for the civil cells dgn library(copy or snapshot the reference for the future.

Note: Don't edit anything directly in the 'Edit configuration variable'.

Now close the window and go back to File=>Open=>Browse=>(before browsing the file make changes in the file type as DGN library files) and no files are visible

So browse C:program data/Bentley/openroads designer CE/configuration/Organization -Civil/Imperial/Dgnlib/civil cells

Results

The civil cells template available in the DGNLIB is listed below.

1.Basin

2.Bridge Embankment

3.Connector

4.Cul-De-Sac

5.Curb Ramps

6.Entrances

7.Interchange

8.Medians

9.Roundabouts

10.T-intersections.

Q3. List out the References in the civil cell.

Aim & Introduction

Each civil cells are defined by different references, and this section will discuss the references of Civil cells based on which the template is designed.

Procedure

Open the civil cells.dgn file which created earlier=>Model detailing =>place a civil cell=> small window appears=>click on the radio button => new window opens up=>open each template listed in the window and the red lines in the window should be designed and placed it in the basic dgn file before placing any civil cells into it. Also, there should be a terrain file attached to it.

Results

Thus, the civil cells references can be seen in the file.

Q4. On any one civil cell, change the secondary alignment bearing, so that it is skewed by 10ᵒ. Confirm if the civil cell, transitions as per the alignment shift.

Aim & Introduction

The basic civil cells templates can be further edited based on the references and changing the skew angle is one of the methods to edit it.

Procedure

The procedure for changing the skew angle will be explained below.

Open ORD=> Browse 2D seed file =>Name the file as Civil cells=>blank page opens up=> Now go to model detailing=>Civil cells tab=> click place a civil cell=> small window opens up=> click on the ... civil cell name=>pick civil cells window opens up=> click on T-intersection dgnlib(default)=> click on Basic T(urban) and the template window opens up.

Now select any template (For example select the Rural =>new construction=> T intersection=> zoom in and check the existing angle with the civil rules.

Now change the angle using the civil rule by 10 degree and subsequent changes can be visible in the 3D too.

Note: During the design if an intersection driveway needs change in angle, then go to geometry file(eg: project mainline alignment file) make changes in the angle of the line with civil rules=>come back to the design file=>run process corridor command for the civil cells=>changes will be applied to the civil cells depends on the feasibility of the available site condition(or solutions determined by the ORD).

Results

Thus, the skew angle can be modified in the in civil cells DGNLIB.

Q5.Design 2 driveways alignment and profiles perpendicular to the INT_01 alignment.

This has been detailed in Q1.

Q6: Place appropriate civil cell on one driveway.

This has been explained in Q1.

Q7: Design the second driveway by manual method (using geometry, terrain, modelling tools)

Aim & Introduction

Some special cases instead of placing a civil cell template, customized intersection might be needed, and, in such cases, manual method can be used to design the intersection details.

Procedure

The detailed procedure for designing the second driveway will be explained below.

Open ORD=> browse corridor basics.dgn=>file opens up. In this file only the intersecting road C/L has got a profile and EOPs and EOSs doesn't have any profile. As a first step in the manual design, a profile needs to be created for all outer edges.

Select all the outer lines of the cross junction without the corridor =>hit space bar=>snap it to nearby point and place it back to the exact position.

Now go to references=>turn display off for roadwayplan.dgn=>go to geometry =>general tools=>design elements=>create civil rule feature=>FD=>Linear=>Road EOP=>pick all the edge lines=>right click.

Now select each element, it can be noted that the elements became civil ruled elements=> Now click on each element=>flyout menu=>open profile view of the first straight element

Now go to geometry=>vertical=>element properties=>profile by slope from the element=>No FD=>Locate the element=>locate the reference (which is the CL of the junction road) =>all other properties of the small window remain same=>profile appears on the window=>click on it and make it active by flyout menu. Select the opposite side and do the same.

For the below 2 straight line portions, select project profile range to element command to create a profile (use junction CL as projection reference). For the curve sections use profile intersection point command to create profile and make it active.

It can be observed that some of the EOP lines are not joined with the mainline EOPs. In order to make it correct, go to same 3D view and with element selection join all the microstation lines and it will be reflected in the plan as shown below.

Now go to terrain =>from elements=>pick elements=>pick elements=>pick elements at the edges of the intersection and reset to complete. The 3D triangulated model will be created as shown below.

Note: All the edges must have an active profile in order to generate an active surface.

Now click on the 3D intersection=> flyout menu=>properties=>turn off the triangles and turn on the contours.

Now go to model detailing=>apply surface template=>locate terrain boundary (edges of the newly created intersection) =>select contours=>now the thickness has been assigned to the template.

Now in order to fix the end condition errors=> go to linear template=>on the 3d select the element (straight portion edge where the problem) =>click Alt+down arrow key=>pick template window=>select EC combined cut and fill=>now select the curve portion and do the same=> it can be observed that most of the graphics are clear from errors. If there are small patches to be filled further, it can be done by first adding a key station. For that click on apply linear template=>window appears=>try to select the elements (curve junction radius area, it can be noted that selection is not happening ) so come out and right click=>Turn level off by elements=>click on the junction road=>now the thickness layer of the graphics has turned off=> now go to element selection=>expand element selection it can be observed that the element supposed to select is in default mode=>go to reference attachment level display of corridor basics.dgn=> right click =>select any other level=>jump to active (command) and turn off the default=>pick the element=>go to apply linear template =>do the same process as before=>Now the end condition graphics has been created.

If further errors exist, it can be resolved by Geometry edit =>edit terrain model=>edit by picking up the additional triangulation=> but it can't be directly selected from 3d because surface applied to it. So, to plan view and select additional triangulation points.

Results

Thus, second driveway design can be done manually.

8. Generate component quantities of the Corridor_INT_01.

Aim & Introduction

Component quantities function generates the quantities of each components which are defined and connected by feature definitions in the 3D design .

Procedure

The procedure for generating the component quantities will be described below.

Open ORD=>browse corridor INT_01.dgn=>go to corridor=>click on corridor reports=>click on component reports=>a table opens up with detailed report of all the components required to construct the road.

Note: Unit cost of the items can be changed in order to get the total cost of the work.

Now click on Reports in component quantities window it will generate a detailed quantity report in the xml format based on stations.

Now go to Review=>Design input reports=>it can be observed that all corridor details, key stations, Template drops, labelled constraints, point controls etc is listed out in the reports.

Similarly, Result Reports which is detailed report of the entire corridor, milling report and superelevation report can be generated with ORD.

Note: Element component quantities (under Model analysis and Reports=>Civil analysis) can calculate each component quantities together. For example, this command can add Main corridor +civil cells+ building pad etc and calculate component quantities together.

Results.

Thus, component quantities can be generated.

Q9.9. Generate cut-fill volumes and Mass Haul diagram and report for INT_01.

Aim & Introduction

End area volume report is the final report of the cut and fill volumes of a corridor, and it can be used for the final quantity calculation for the entire corridor.

Procedure

The procedure for generating the end area volume reports will be discussed below.

Open ORD=>Open corridor INT_01.dgn=>Model analysis & reporting. Now in order to create End area volume report, 'cut and fill volume ' must be created. For, that click on the 'cut and fill volume command'=>give everything default=>data point to accept it=>a graphics has been generated with red (fill area), blue (cut area).

As the cut and fill volume has been created, now go ahead and click on the Mass haul diagram=>window appears=> give method as Cross section method. But before that the 'Cross section named boundary' has to be created. For that go to 'Drawing Production'=>Named boundaries=>select 'place a named boundary cross section' and give inputs in the window as shown below.

No do a data point and go to plan=>right click view control=>open cross section view=>It can be seen that 'Named cross section boundaries have been created.

Now go back to Home=>Model analysis & Reporting=>Civil analysis=>Mass haul diagram=>window appears=>select method as cross section boundary and select the inputs as shown.

Results.

Thus, mass haul diagram has been created as shown below.

10. Generate corridor, legal, input, geometry, earth works XML reports. Save each report in PDF format in the project folder.

Aim & Introduction.

The report options in the ORD can accurately calculate each component required for the construction which can also be used for quantity calculation and cost analysis.

Procedure

The procedure for generating the legal, input, geometry and earthworks can be done from either going into

Home=>Model analysis and reporting or go to Corridor=>Review=>corridor reports which has been explained in Q9.

Results

Thus, all the reports can be generated and converted to xml.