CDOT MicroStation and InRoads Transition NH 1191-016 SH 119 & SH 52 Presented By: Dan Marcucci Bob...

CDOT MicroStation and InRoads TransitionNH 1191-016

SH 119 & SH 52

Presented By:

Dan Marcucci

Bob Hays

Helen Peiker

CDOT MicroStation and InRoads TransitionNH 1191-016, NH 119 & SH 52

Location Map

• BNSF Railroad

BNSF Rai

lroad

IBM

SH11

9

SH 52

Office Park

Future Hotel

City of BoulderOpen Space

SH 119

SH 52

IBM


• General Project Information:– Located in Boulder County at the intersection of

SH119 and SH 52.– Requested and supported by the local agencies of

Boulder County, City of Boulder, and City of Longmont.

– City of Boulder Open Space is located in the south-east corner of the project.

– BNSF Railroad runs through the project.– IBM located on the West side of the project.– Black tailed prairie dogs are located throughout the

project.


• Engineering Project Information:– Surveyed 3 different times (1992, 2001, 2003-2004) over the course of 12 years

and each survey had additional surveys within the time periods they were done. Translated survey into InRoads Survey via CDOT translator program. It took approximately 200 hours to translate the survey into MicroStation. The survey was translated for graphics uses only (approximately 95% complete) because there were to many unresolved issues, due to different types of data involved in the different surveys. (conventional - coordinated base, conventional - azimuth based, RTK etc..). As a result no dtm was generated so the existing terrain was converted into InRoads from the original AutoCAD PICS files.

– Consultant designed project to FIR using AutoCAD and MX.– CDOT translated project to AutoCAD and InRoads

• Each team member created their own levels and features so there was little consistency.

• Team members learning InRoads.• No training or support available.

– Became a First Adopter project and translated project to MicroStation and InRoads.

• Team members started using standard levels and features.• Each time the configuration was updated team members had to update levels and

features.


• Roadway Engineering Design Team:– Varied from 2 to five people for differing lengths of time and

include: Bob Hays, Dan Marcucci, Helen Peiker, Gerald Fielding, and Megan Christensen (student intern).

– With a team of people coming and going the project was broken into parts where each person could easily work on their area while allowing others to work on theirs (SH119, Ramps A, B, C, D, SH 52, local roads, and bike paths). All team members were located in one office so constant communication and updating of team members and files could take place.

• Survey Team:– Varied over the years and include: Mark Guerrero, Ed Warwick,

Charlie Northrup, Bill Aldorfer, Helen Peiker, Lee Groves, Jerry Johnson, Art Lacombe


• Roadway Engineering Programming Challenges:– Complicated typical sections which included pavement, curb & gutter, sidewalks,

concrete or metal beam guardrail, drainage ditches, and walls all starting, stopping, and varying in width at different locations.

– Multiple walls and levels of walls due to tight right-of-way.– Raised medians crossing back and forth across centerline with varying widths.– Curb and Gutter transitions from catch to spill type.– Mainline super elevation rotating one direction while an auxiliary lane is

developed that super elevates the other direction. Or gores that have several break points (edge of travel for mainline and ramp).

– Toes that needed to tie into existing ground at a certain locations.– Tying together mainlines, ramps, bike paths, gores, local roads, structures, and

walls into one dtm.– Connecting ramp and mainline features at intersections.– Modeling Subgrade Features for Cross Sections and Volumes where various

alignments converge and diverge (mainlines, ramps, and bike paths).– Creating the variable slope and width depressed median.


• Complicated Typical Sections• Typical Section SH 119 Mainline

• Typical Section Ramp


• Roadway Engineering Programming Challenges:– Complicated typical sections which included pavement, curb &

gutter, sidewalks, concrete or metal beam guardrail, drainage ditches, and walls all starting, stopping, and varying in width at different locations.

• Used a variety of InRoads options:– Creating an alignment from template segments using Import Geometry

from Graphics to tie into. (daylight slopes, gores, supers going different directions)

– Created an alignment for the template segments to go and intersectd on a certain slope. (RE Walls)

– Station offset command in the modeler. (widening of a segment)– Transition between templates (spill to catch curb & gutter, segment

widening)– Created one surface and had another surface interface into it.

(depressed medians)


– Multiple walls and levels of walls


– Multiple walls and levels of walls• Created separate wall alignments (horizontal and

vertical) for top of walls. • Developed a decision table to create the bottom of

the walls. • Tied segments from Ramps and mainlines by

horizontal and vertical controls to the walls.


– Modeling Subgrade Features for Cross Sections and Volumes where various alignments converge and diverge (mainlines, ramps, and bike paths).


– Modeling Subgrade Features for Cross Sections and Volumes where various alignments converge and diverge (mainlines, ramps, and bike paths)

• Shoulder feature of the ramp would be copied into the bike path surface using “copy portion of surface”.

• Bike path surface the feature would be “partially deleted”, giving only the area desired.

• Use the “generate longitudinal feature” tool to offset both vertically and horizontally to obtain a subgrade surface that

ties into the ramp subgrade surface.


• Toes that needed to tie into existing ground at a certain locations.


– Toes that needed to tie into existing ground at a certain locations.

• Identified feature in original survey that the roadway needed to tie into.

• Used a decision table to have roadway template tie into that survey dtm Features X, Y, Z coordinates.


– Raised medians crossing back and forth across centerline with varying widths.


– Raised medians crossing back and forth across centerline with varying widths.

• Created horizontal alignments (left and right) of median edge of oil using MicroStation.

• Created horizontal alignment of medians by using the Import Geometry from Graphics command.

• Ran a “dummy” template with super elevation along CL of roadway with dummy segments following median alignments with fixity being variable width, resulting with the feature having the correct elevations.

• Import the resulting feature as the main horizontal and vertical alignments by using the Import Geometry from Graphics command.

• Created templates (left, right, catch and spill curb & gutter, travel lanes, and shoulders) and ran them along the new edge of oil alignments creating top of template.


• Curb and Gutter transitions from catch to spill type• Catch Type

• Spill Type


– Curb and Gutter transitions from catch to spill type.

• Created two median typical sections (catch and spill) and had InRoads transition between them over 50 feet.


• Mainline super elevation rotating one direction while an auxiliary lane is developed that super elevates the other direction. Or gores that have several break points (edge of travel for mainline and ramp).


– Mainline super elevation rotating one direction while an auxiliary lane is developed that super elevates the other direction. Or gores that have several break points (edge of travel for mainline and ramp).

• Took the feature that was created from the mainline template and created an alignment using the Import Geometry from Graphics command.

• Ran template along new alignment with proposed super elevation and roadway library to create the auxiliary lane with the correct widths and elevations.


– Connecting ramp and mainline features at intersections.

• Before

• After


– Connecting ramp and mainline features at intersections.

• To create feature between edge of oils of adjoining roadways used Fillet Feature command

• Used the Partial Delete Command to trim out the middle.

• Created decision table to run along that feature to create curb and gutter, sidewalk and slopes. Note: This does not work for toes on small radius curves. For those toes used the Fillet Feature command.


• Tying together mainlines, ramps, bike paths, gores, local roads, structures, and walls into one dtm.


– Tying together mainlines, ramps, bike paths, gores, local roads, structures, and walls into one dtm.

• Used the Copy Portion of Surface command and copies the source surface (surface to be added) into the destination surface (combination of all surfaces) to combine all the surfaces.

• Trimmed overlapping features using the Partial Delete and Delete Duplicate Features command. Note: fillet returns before adding to combined surface.


• Creating the variable slope and width depressed median.


– Creating the variable slope and width depressed median.

• Created a “dummy” south bound surface with all the varying median slopes. The side slopes were developed several hundred feet wide so the north bound surface would interface into it developing a feature in the correct location with the elevations.

• Using the Import Geometry from Graphics command made the feature into an alignment and had side slopes of both north and south bound tie into it creating the depressed median of varying width and side slopes.


• Intersection example


• Gore Example

CDOT MicroStation and InRoads Transition NH 1191-016 SH 119 & SH 52 Presented By: Dan Marcucci Bob...

Documents

Transcript of CDOT MicroStation and InRoads Transition NH 1191-016 SH 119 & SH 52 Presented By: Dan Marcucci Bob...