au09 speakerhandout cv122-31

7/24/2019 AU09 SpeakerHandout CV122-31

http://slidepdf.com/reader/full/au09-speakerhandout-cv122-31 1/19

A Simplified Process for Dynamic Complex Urban

Corridor Design Arthur Miller, PE – JR Engineering

CV122-3 In this class we will look at a real world arterial corridor design. This design has been

completed or a client and has man! o the challenges aced with arterial design"superele#ation, medians that cross the centerline o the roadwa!, right$turn ba!s, andtransition regions. I !ou ha#e tried to model these situations in Auto%A&' %i#il (&' andbecame rustrated because there were )* dierent assemblies and onl! +od knows howman! regions that were de#eloped to model the corridor and !ou inall! threw up !ourarms in disgust, this class is or !ou -e will introduce the concept o design corridors, as!stematic naming con#ention to keep track o where !ou are in the corridor, and designthe corridor using onl! si #er! simple assemblies To top it o, design changes are eas!and d!namic, which allows the designer to ocus on optimi/ing the design.

About te Spea!er"

Arthur is a senior technical specialist or JR Engineering in %entennial %olorado. -ith o#er 0) !ears o eperience, heis an epert in transportation engineering, speciali/ing in comple urban arterial corridors, roundabouts, signali/ation,and intersection design. 1e is a skilled pro2ect manager who de#elops inno#ati#e sotware design worklows thatspeed up the design process while pro#iding 3ualit! control that is inherent to the process.amiller42rengineering.com



CV122-3 A Simplified Process for Dynamic Complex Urban Corridor Design

Cursory #nformation

File Structure and Shortcut Considerations

#ssue

A well thought out ile structure is imperati#e to successul data management using %i#il (&'. 5ince data

is not stored in a centrali/ed data base but rather in each indi#idual drawing and these drawings are

linked using data shortcuts it is eas! to see how without a deined standard o ile management ma!hem

would soon reign within the design team. I e#er!one does what 6seems right in their own e!es7, soon no

one will be able to igure out where data is stored, let alone how the design was accomplished Each

design member must know what iles to create, what those iles are to be named and stored, what data

shortcuts should be attached to each drawing, and what inormation is stored in the drawings.

$ile Structure Used #n %is Class 8or this class we will use the ollowing ile structure. The abbre#iation is the name o the ile. -e will

use the pro2ect number irst ollowed b! the abbre#iation 9e. The eisting surace would be named

0:(;<=E+.dwg>.

Dra&ing

'ame

Dra&ing

Abbr(

Dra&ing Contains Sort Cuts

#n

Sort Cuts

)ut

&esign

Eisting

E? Eisting hori/ontal linework @one @one

Eisting

5urace

E+ All data used to create the

eisting surace. Ma!

contain contour data, point

data, eature line data, etc.

@one Eisting 5urace to

the &5I and

8%B drawings.

&esign

1ori/ontal

&1 Proposed hori/ontal

linework

@one @one

&esign

%orridor

&%B • : %orridors

• ( Assemblies

• @ormal %rown

%orridor and5urace

• Median Cet o

%enterline %orridor

and 5urace

• Eisting 5urace

rom E+ &rawing

• Proposed

%enterline

Alignment rom&5I

• Proposed

%enterline Proile

rom &5I

Two suraces to the

&5I drawing.

&esign

ertical or

&5I %ontains all roadwa! • Eisting 5urace Proposed

%enterline

:




Dra&ing

'ame

Dra&ing

Abbr(

Dra&ing Contains Sort Cuts

#n

Sort Cuts

)ut

5treet

&esign

proposed"

• Alignments

• Bset Alignments

• Proiles

rom E?

• Two 5uraces

rom the &%B

Alignment to the

&%B and 8%B

Proposed

%enterline Proile to

the &%B and

8%B

Bset Alignments

and Proiles to the

8%B

8inished%orridor

8%B 5i Assemblies

8inished %orridor

8inished %orridor 5urace

9called 8+>

Eisting 5urace rom theE+ &rawing

Proposed %enterline

Alignment and Proile

rom the &5I

Bset Alignments and

Proiles rom the &5I

@one

Corridor Design #ssues

Determining Regions

Ater the hori/ontal geometr! has been established it is time to deine the regions in the &esign 1ori/ontal

9&1> drawing. A region is deined the same as a corridor region. This means we are being proacti#e and

determining the regions ahead o time and naming those regions so that we can later use these names in

our alignment names, base line names and region names. D! starting out proacti#el! we will alle#iate

man! headaches later on b! starting to de#elop a s!stematic naming con#ention at the #er! start.

&etermining a region boundar! is eas!. Just locate region boundaries b! appl!ing these three rules"

(




0. Place a boundar! at the start o intersection curb returns.

:. Place a boundar! at the end o

intersection curb returns.

(. Place a boundar! at the lip o the

median pan where the median

alignment crosses to the

opposite side o the roadwa!

centerline alignment.

The region boundaries should be drawn

in the &1 drawing on a working, no plot

la!er and then the name o each region

should also be written in the &1 drawing

on the same no plot la!er. This

inormation ma! sta! in the &1 drawing

or i !ou are a neat person and dont like

the clutter in the drawing make a region

block and block out this inormation so

that !ou or someone else ma! insert the

inormation when designing so the! can

reerence these regions to the naming

con#ention.

Defining Offset Alignments

%e 'e& )ffset Alignment $eatureBset alignments is a cool new eature in %i#il (&' :*0* that allows one to deine an alignment that is

oset rom another alignment 9i.e. centerline alignment> and then when the centerline alignment is mo#ed

the oset alignment also mo#es. Bnce the oset alignment is created then one can create transition

regions where one transitions rom one oset distance to another.

There are se#eral limiting actors in this irst release that limits the useulness o using oset alignments

or comple urban corridor design. The limitations that I ha#e seen to date are"

• -hen a transition region is established the sotware re3uires a transition region back to the

normal deined oset. 5o i part o !our roadwa! is at :; and then a lane is added to make it (=

and !ou use a transition region it will ha#e a second transition region that !ou do not want to take!ou back to :;.

• The transition regions ha#e se#eral geometric t!pes that can be used, but the! are all based upon

criteria or a turn ba! and not on a <*"0 transition taper to widen a roadwa! or a dual let turn ba!.

Although in certain instances the tools the! ha#e will work to deine this situation, oten times

9especiall! in roadwa!s with lots o hori/ontal cur#es> these transition st!les will ail and not be

able to gi#e the desired results.

;




• Median transition regions ail when re3uired to cross the centerline o the roadwa!. I#e tried this

doing se#eral dierent methods and it either will not accept the negati#e oset input or the

sotware crashes.

The power o using the oset alignment coupled with the inherent limitations o the transition oset

alignment has led me to the conclusion that where !ou are able to use the oset alignment do and then

use regular alignments in those transition regions where oset alignments are not up to the task. This will

limit the areas where one will ha#e to manuall! go and grip edit the alignment to mo#e it to the new

correct location.

-hen creating an oset alignment that cannot be created using the Bset Alignment command, I create

these alignments b! using the Create Alignment from Polyline command. The reasons or doing this is

that it is eas! to do, i I need to ad2ust it in the uture Ill snap the alignment to the new hori/ontal geometr!

and not all transitions on the oset alignments maintain tangenc!.

Alignment 'aming Con*entionPlease note tat from no& on &en # use te term offset alignment it refers to an alignment tat is

offset from te centerline and does not infer as to being created by using te offset alignment

command(

Cabeling o oset alignments is critical. A clear and concise naming o each alignment will allow easier

targeting to the appropriate subassemblies during corridor creation. The ollowing naming con#ention is

recommended"

• Cabel the region or regions that the alignment goes through irst.

o 0 i the alignment goes onl! through region 0F or

o 0$: i the alignment goes through regions 0 and :F or

o 0$< i the alignment goes through regions 0 through <. etc.

• Cabel the side o the roadwa! the alignment is on 9based on the roadwa! centerline looking in the

direction o increasing stations>. RT or right or CT or let.

o RT or rightF or

o CT or let.

• Cabel i it is median edge o pa#ement or outside edge o pa#ement

o ME or Median edge o pa#ementF or

o BE or Butside roadwa! edge o pa#ement.

A complete alignment name would be something like this" 0$:$RT$BE. This eample would show that this

alignment goes through regions 0 and : and is the right outside edge o pa#ement.

<




Cip o pan alignments can go through dierent regions in one alignment. Geep the regions marked on a

working la!er in plan #iew so i someone else needs to complete what !ou ha#e started the! will be able

to ollow the naming con#ention. Bnce the alignments are completed the un actuall! begins

Creating )ffset Alignments

%e Design Corridor -hen one reads 6&esign %orridor in the title to this section the irst thought is this sounds reasonable.

That is, until I start describing what this design corridor stu is all about and then the deer in the headlight

look comes o#er !our ace as !ou wonder how in the world this is considered design. 5o beore going

into the process, lets take a ew minutes to gi#e an o#er#iew so that !ou will understand wh! I call this

the &E5I+@ assemblies, corridors, and suraces.

-hen I irst started using %i#il (&' man! !ears ago I irst tried to design in the same manner as I did in

C&T. I created a #er! complicated assembl! that I hoped would work. The assembl! would work or 2ust

a small section and then I would run into a problem. 5o I would create another complicated assembl!

that would address the new problem and it would work or that small area and then I would run into

another ma2or problem. D! time I had e#er! situation addressed I had se#eral do/en assemblies

designed that onl! worked or #er! small areas o the corridor design. Also, ha#ing so man! assemblies it

caused the sotware to get conused on how to connect up the dots and the corridor ended up ha#ing

man! other issues that were not design related but rather sotware related. Bne thing that is certain in

urban arterial design is that there is no such thing as a t!pical cross$section

5o the corridor then was a stack o cards with man! regions and man!, man! dierent assemblies that

addressed e#er! situation that was happening on each side o the centerline. Then a design changecomes along and the stack o cards comes tumbling down. In act, it was so complicated that it was

easier to start o#er rom scratch than to tr! to igure out how this change in alignment or geometr!

aected dierent regions and caused new regions and assemblies to be needed. There had to be an

easier wa! to accomplish the design task.

I set out on a 3uest to ind a method to design a comple corridor and be able to ha#e it simple to design

and utili/e the incredible power that %i#il (&' should ha#e during design changes. I architects are able

to ha#e a DIM process, transportation engineers should ha#e the same abilit!. This 3uest has led to the

use o design assemblies, corridors and suraces.

What is a Design Corridor?

5o what is all this design corridor stu an!wa!H 5impl! put, it is two corridors that use the same

centerline alignment and proile o the roadwa! being designed. Doth design corridors use onl! one

simple subassembl!, which deines the top surace o the roadwa!. The irst corridor is designed using

the normal crown o the roadwa!. This corridor will deine superele#ation transition regions and an! other

cross$slope transitions using onl! a single link or each side o the roadwa!.

The other subassembl! is onl! used where the median crosses centerline to orm a let turnba!

approaching an intersection. This small area re3uires special attention because one usuall! does not

=




want a crown break in the turn lane so the roadwa! cross$slope is carried up past the centerline to

maintain positi#e drainage to the outside curb and gutter. 5o the second subassembl! carries the normal

crown slope up past the centerline.

5uraces are made or each corridor. Then surace proiles are made or each o the our edges o

pa#ement alignments that reerence these two suraces. -e will use these design suraces, alignments

and proiles to attach all the lanes, curbs etc. in a inal corridor that shows the actual roadwa! eatures.

Then, to change all the eatures, one onl! has to modi! the design corridors and e#er!thing else updates

automaticall!. 5ound coolH It is cool and it works Read on and we will look at how to create the design

assemblies, corridors and suraces.

Defining the Three Design Assemblies and Corridor Scenarios and

Surfaces

'ormal Cro&n Corridor The irst assembl! is used or !our normal crown section and or the la!out o !our superele#ation

sections. The assembl! is named Normal Crown and uses the +in!,idtAndSlope subassembl!. This

subassembl! is attached twice or each side o the roadwa! and has the ollowing parameter #alues"

Bmit Cink @o

5ide 9Bne link is Right and the other link is Cet>

se 5uperele#ation 5lope Butside lane slope

5lope This should be !our normal crown slope which is usuall! $:.**

-idth 5hould be much larger than !our roadwa! corridor section. I use :**

Point %odes P: 9This is the deault>

Cink %odes Top, &atum 9This is the deault>

The use o this simple assembl! is to design the roadwa! trans#erse slopes. I e#er!thing sta!s at normal

crown that is great, but i !ou need to design transitions or intersections or superele#ations these

changes in cross$slope can be easil! achie#ed as well b! using this corridor. Bnce this corridor is

completed it represents the inished roadwa! surace. %reate a corridor surace.

')%" 5ince the corridor surace will be used to control the inished corridor the surace needs to be tightand accurate. 5o set the $re.uency in the Corridor Properties to a suicientl! small increment to

accuratel! portra! the surace and an! transition regions. I usuall! set the re3uenc! to two eet inter#als.

Shrink wrap surface tip

Kou ma! notice that when !ou tr! to shrink wrap a surace with onl! one baseline that !ou do not ha#e the

option to shrink$wrap the surace a#ailable. There is an eas! work around to this issue. Just create a

L




new baseline and dont deine an!thing to that baseline Then when !ou go to shrink wrap the surace the

option will be a#ailable to !ou.

/edian +eft of CenterlineThe second assembl! is used to deine the trans#erse slope or right and let sides o the roadwa! let

turn lanes where the median crosses centerline. This assembl! will work onl! in areas where there are

no cross$slope transitions or superele#ation. The assembl! is named Median T of C and uses the

+in!,idtAndSlope subassembl!. This subassembl! is attached twice or each side o the roadwa!.

The assembl! parameter #alues are the same as or the normal crown assembl! ecept the

superele#ation parameter is switched to none and the side link slope is set to :.** or both links.

%reate a corridor surace.

/edian +eft of Centerline )ption for use &it 0Superele*ations

The third assembl! is an optional one that ma! be used to deine the trans#erse slope or right and let

sides o the roadwa! let turn lanes where the median crosses centerline and the crossing happens withina superele#ation region. This assembl! is more complicated to understand and will not be dynamic.

The assembl! is named !Median T of C " and uses the +in!,idtAndSlope subassembl!. This

subassembl! is attached twice or each side o the roadwa!. The assembl! parameter #alues are the

same as or the normal crown assembl! ecept the width or each side is set to –:** eet and the side

link slope is set to :.** or both links. The link slope reall! is not that important because we will ha#e

superele#ation parameter is switched to )utside lane slope so the alignment superele#ation data will be

used to set the cross slope o#erriding the subassembl! parameter. @ow to understanding wh! we used –

:** eet

8rom the image abo#e we see that what we actuall! need when a median crosses o#er the centerline is

to ha#e the cross slope transer to the opposite side and then re#erse signs. 5o i the cross slope is –

0.L< on the right hand side then on the let hand side we would want a 0.L< cross slope. 5o we trick

the sotware. -e place a negati#e width on our subassembl! so the right side is on the let and the let

side is on the right Then we turn on the superele#ation parameters on the subassemblies and we get the

cross slope number or the cross slope on the side that we want. The ca#eat here is that we do not get

the right sign. -e actuall! get the wrong sign, which is a bummer. That is wh! this assembl! is not

d!namic, because we need to ind the station ranges that this subassembl! will be used and then

manuall! thorough the cross$section editor change the signs in those areas and then turn o the

)




superele#ation parameter.

)ffset Alignment ProfilesBset alignment proiles that will control the inished #ertical corridor are simpl! using surace proiles

rom the two design corridor suraces 9@ormal %rown, Median CT o %C>. It is eas! to get going ast and

then create proiles in the wrong ile Remember that proiles are kept with the alignments in the &5I

drawing.

Creating Offset Alignment #rofiles

Data Sortcuts of Design Corridor Surfaces

Bnce the design corridors ha#e been created along with the design suraces, it is time to create datashortcuts to !our pro2ects shortcut ile. I recommend creating a data short cut ile or each pro2ect and

ha#ing a speciic location or this ile in !our pro2ect director! structure. This structure works much like the

C&T database ecept drawings are not attached to the database so no warnings come up i !ou create a

shortcut to the wrong location. The drawback 9ob#iousl!>, to this method is one ma! easil! create a

shortcut to the wrong pro2ect. 5o make sure beore creating shortcuts that !ou are attached to the right

data shortcut pro2ect

Creating )ffset Profiles Using Design Corridor Surfaces

@ow the roadwa! design is complete. -e 2ust need to connect the dots The irst part o this is creating

the surace proiles or our edge o pa#ement oset alignments that we created earlier. -e will not need

to create a proposed proile because we will be reerencing our design suraces rom our design corridors. All we need to do here is reerence the correct surace with the correct oset alignment. Ill chart out

which suraces to sample with which alignment"

Alignment Surfaces

Right N Cet Butside Edge o Pa#ement Top @ormal %rown &esign 5urace

Median Edge o Pa#ement on the RT Top @ormal %rown &esign 5urace

O




side o %C 9looking in direction tra#el, not

stationing>

Median Edge o Pa#ement on the CT

side o %C 9looking in direction tra#el, not

stationing>

Median CT o %C &esign 5urace

Ater these proiles ha#e been created we ha#e completed the roadwa! #ertical design. -hene#er we

need to ad2ust the centerline proile or alignment, the corridors and suraces will automaticall! ad2ust as

well. D! using oset alignments, the alignments will ad2ust as well when centerline alignment is mo#ed so

the alignments and the proiles will automaticall! ad2ust as well because the! are reerencing the corridor

suraces which are attached to the centerline alignment and proile 5o we drag and drop the centerline

alignment, ad2ust the centerline proile and Doom, Dang, &one Prett! cool stu.

To inish up create data shortcuts or e#er!thing we ha#e done so ar. -e will now mo#e to a newdrawing to create a corridor that has the actual lanes, curbs, sidewalks, da!light lines, etc.

%e $inised Vertical Corridor @ow that all the roadwa! design work is completed we need to start looking at the assemblies needed to

complete the inished corridor. In this tutorial, we are looking 2ust at the corridor. 1opeull! I will ha#e an

intersection design class read! or A :*0*. -hen we look at the corridor and we see intersections,

right in right out intersections, right turn ba!s, and single and dual let turn ba!s, we rapidl! become aware

that in urban arterial design the t!pical cross$section is a m!th. In order to show a t!pical cross$section

we ha#e to water e#er!thing down with so man! varies from 0 to 200 feet that the t!pical cross$section we

are re3uired to show on the plans is meaningless to an!one. 5o how do we design our 6t!pical7 cross$

section 9Assembl! and 5ubassemblies> without ha#ing (,*** dierent sections or dierent areas alongthe roadwa!H The answer to that is eas!. &ont use the sotware like the programmers think !ou should

use the sotware Instead, think o the sotware as a bunch o tools in a toolbo. A designer designed a

screwdri#er to turn screws. Dut what i !ou cant get the seal on !our oil pan to come apartH Man, that

screwdri#er 2ust made a great tin! pr! bar In the same wa!, with a little ingenuit!, we will create a #er!

comple corridor with #er! ew assemblies. %ome on, lets check it out

-e will do all o this design using onl! si assemblies. I did sa! si. -ith si assemblies we will model

the entire arterial corridor including superele#ation regions, lane widening sections, right and let turn ba!s

and e#en let turn ba!s that cross the centerline o the roadwa!. These si assemblies also are not nearl!

as comple as the ones Im sure we all ha#e tried to create in the past with minimal success. Deing less

comple also means that the sotware has less opportunit! to get conused

Are !ou read! to see how this all comes togetherH -ell then, lets get started b! looking at these si

assemblies

Creating Si$ Assemblies

Deore we get started on the assemblies we will need to create a new drawing or our inished corridor

98%B>. Bnce sa#ed, bring in all the data shortcuts we created in the design phase or use in the

completion o the inished corridor.

0*




Instead o designing assemblies that do both sides o the roadwa! at once, tr!ing to complete all design

tasks with 2ust one assembl!, we are going to break the assembl! apart into our dierent segments. 8irst

o we are going to break the assemblies into the right side o the roadwa! and the let side o the

roadwa!. -e will then break each side down into two more components. The irst component will be themedian curb. Kes, it entails 2ust the median curb. Its a prett! simple assembl!. The second component

will be the lanes, outside curb and gutter, tree lawn, sidewalk, da!light components. @ot 3uite as simple,

but still prett! eas! to track the targets when we get into the corridor. Bne thing I will admit up ront with

this design is that I ha#e not igured out how to add in the median co#er material without making the

process wa! to complicated. The inished corridor surace will connect directl! across or median top

back o curb to median top back o curb. This should not drasticall! aect earthwork 3uantities either.

This is a small price to pa! or the ease and power inherent to this design method. I will describe how to

design the three right side assemblies with the knowledge that all one has to do is change the side to

create the ( let side assemblies. Cets get started

Creating /edian Curb Assemblies

Right Median Curb and Gutter Assembly

8or the right median curb and gutter section we will need two assemblies. The irst assembl! will be

when the lip o pan or right median alignment 9where we attach to the oset alignment> is right o the

centerline. The second assembl! will be designed or when the right median alignment or lip o median

pan is located let o the centerline. Cets create the irst assembl!.

0. %reate an assembl! and name the assembl! RT Median C&G.

:. %reate an assembl! oset and select a location to the right o the assembl!.

(. Attach subassembl! UrbanCurbuttereneral to the oset.

;. @ame the subassembl! RT Median C&G.

<. Bn the Parameters tab, ill in the parameters or the 2urisdictions median curb t!pical section.

=. 8or the side, select Cet.

The most common curb and gutter st!le or m! region o the countr! is listed below"

00




1ere is what the inished assembl! looks like"

Right Median Curb and Gutter Assembly that is Left of Centerline

0. %reate an assembl! and name the assembl! RT Median C&G LT of CL.

:. %reate an assembl! oset and select a location to the let o the assembl!.

(. Attach subassembl! UrbanCurbuttereneral to the oset.

;. @ame the subassembl! RT Median C&G 2 .

<. 8or the side select Cet.

=. 5ame Parameters as shown abo#e.

The second o the three Assemblies are created 1ere is what

the second assembl! will look like"

-e are two thirds o the wa! there Bnl! one more assembl! to

create and we will be done. The two eas! ones are complete

and now to a more diicult assembl!. Are !ou read!H Cets go

Creating )utside +ane Assemblies

0. %reate an assembl! and name the assembl! RT C&G with Lanes.

0:




:. %reate an assembl! oset and select a location wa! to the right.

(. Attach subassembl! +in!)ffsetAndSlope to the subassembl! to the assembl!.

;. @ame the subassembl! RT Link to RT ME .

<. Bn the Parameters tab set the ollowing Parameters"

Value 'ame Default #nput Value

5ide Cet

Bmit Cink Kes

se 5uperele#ation 5lope @one

Bset rom Daseline T!pical distance rom %C to Cip o

median pan. se a negati#e #alue or

let o the assembl!.

5lope @ormal %rown 5lope suall! $:.**

Point %odes P: 9&eault alue>

Cink %odes Top, &atum 9&eault alue>

This link will not be shown, but will allow the space where the median is located to the edge o

pa#ement.

@ow lets create the net piece o this assembl!.

=. Attach subassembl! +ane#nsideSuper to the subassembl! link named RT Link to RT ME.

L. @ame the subassembl! Right Lane.

). Bn the Parameters tab, set the ollowing Parameters"


%rown Point on Inside @o

5ide Right

Dase &epth 8rom +eotech Report

&eault 5lope @ormal %rown 5lope suall! $:.**

Pa#e0 &epth suall! *.0L, but could #ar!.

Pa#e: &epth Total Pa#ement &epth rom +eotech

Report

5ub$base &epth 8rom +eotech Report

-idth -idth o the thru lanes.

Reall! the width and slope dont mean much here. -e will control the width o the lanes and the cross$

slope o the lanes using our lip o pan alignments and proiles. The second subassembl! part is attached

and deined. @ow to the third part

O. 5elect the subassembl! UrbanCurbuttereneral rom the #mperial Structures tab on the

%ool Palettes.

0*. Attach subassembl! UrbanCurbuttereneral to the oset assembl!.

0(




00. @ame the subassembl! Right C&G.

0:. Bn the Parameters tab, set the ollowing Parameters 9This will #ar! depending on the

2urisdiction>"


Insertion Point +utter Edge

5ide Right

+utter 5lope Method se &epth

se 5E se Butside lane superele#ation or

subbase

&imension A 9mmQin> *.<*

&imension D 9mmQin> :.**

&imension % 9mmQin> *.0L

&imension & 9mmQin> *.<*

&imension E 9mmQin> *.<*

&imension 8 9mmQin> *.((&imension + 9mmQin> 0.**

+utter 5lope $:.** 9not used in the depth method>

5ubbase &epth 0.<*

5ubbase Etension 0.**

5ubbase 5lope $:.**

Bnl! two more parts to go, so dont 3uit on me now. -e are almost done.

0(. Attach the subassembl! UrbanSide&al! to the top back o curb named Right C&G.

0;. @ame the subassembl! Right Tree Lawn and Walk .

0<. Bn the Parameters tab, set the ollowing Parameters 9This will #ar! depending on the 2urisdiction>"


5ide Right

&epth *.((

Inside Doule#ard -idth <.**

Butside Doule#ard -idth 0<.**

5idewalk -idth 0*.**

5lope :.**

The inal 5ubassembl! is the da!light subassembl!. -e could ha#e a whole class on what t!pes o

da!light subassemblies are out there and how the! work. I might tackle that one in the uture. Gnowing

that there are man! special circumstances when we da!light Im going to keep this simple. I like simple

suall!, in an urban corridor we ha#e positi#e drainage rom the tree lawn area to the gutter. 5o when we

are in cut area we onl! need to da!light. In a ill situation we ma! ha#e the eisting ground going awa!

rom us, which is great, but sometimes it is draining towards the roadwa!. -hen it drains toward the

roadwa! we can oten 2ust use the ill slope da!light point as the bottom o the ditch without deining a

t!pical ditch. This works unless there is a low point somewhere where the water ponds up. 5o in this

class Im 2ust going to use a simple link that will da!light to the surace in cut or ill. This works in most

situations.

0;




0=. 5elect the subassembl! +in!Slope%oSurface rom the #mperial eneric tab on the %ool

Palettes.

0L. Attach the subassembl! +in!Slope%oSurface to the back o tree lawn subassembl! named

Right Tree Lawn and Walk .

0). @ame the subassembl! RT Dalight .

0O. Bn the Parameters tab, set the ollowing Parameters"


Add Cink in %ut and 8ill

Bmit Cink @o

5ide Right

se 5uperele#ation 5lope @one

5lope :<.** 9#aries per 2urisdiction>

Point %odes P: 9deault #alue>Cink %odes Top, &atum 9deault #alue>

The assembl! is done That reall! was not too bad, was itH 1ere is what the completed assembl!

looks like.

@ow that this is completed, !ou get to do it or the let side o the roadwa!

#utting it all together to create the Finished %ertical Corridor

Creating te finised corridor @ow that all the roadwa! design work is completed and the assemblies are created, we 2ust need to

assemble all the parts together in a inished corridor. The inal corridor will use the same centerline

alignment and proile but will target the design oset alignments and design proiles. 5ound a little

conusingH It is, but since we used a s!stematic naming con#ention on our alignments and ha#e alread!

broken the corridor out into logical regions it is simpl! connecting the right subassemblies to the right

alignments and proiles.

0<




Using /ultiple 4aselines

Remember in the last chapter how I talked about our tool bo and that we do not alwa!s use a tool as it

was designed to be usedH The inished corridor will be done in a wa! that is outside o the programmers

design worklow. In order to make e#er!thing simple and eas! to ollow and allow simple basic

assemblies to design the whole corridor we are going to make liberal use o Daselines so that we will be

able to run multiple assemblies down the same station ranges attaching the dierent assemblies to

dierent targets. Cets take a closer look at how to connect the dots and put e#er!thing together.

To demonstrate this process we need geometr! or all o us to use as a guide so that we understand what

the regions are and how the corridor is working 9see below>. In Region 0 we ha#e our$lane arterial with a

0= wide raised median 9measured lip o pan to lip o pan>. The cur#e re3uires a ; superele#ation and

as we approach the intersection there is lane widening to accommodate a dual let turn ba! or the

northbound traic. Region : starts where the lip o the median pan crosses the centerline o the roadwa!

and continues to the start o the intersections curb returns. 8or our eample we will create the inished

corridor or regions 0 and :.

+in!ing it all togeter

-e will use our baselines to put e#er!thing together in s!stematic wa! utili/ing our oset alignment

naming con#ention. 5o baselines will ha#e names RT$BE, CT$BE, RT$ME and CT$ME. -e will continue to

use the abo#e eample in the la!out below, 2ust remember the region numbers and side will #ar!depending on !our particular design. @ow lets look at each part and how things go together.

Defining te +anes and )utside Curb and utter

-hen deining the lanes and outside curb and gutter it is 2ust a matter o making sure the right alignment

and proile are attached to the right part o the subassembl!. Cets use our eample problem to look at

how this connects together.

0=




Connecting the dots on the Outside Curb and Gutter

%reate a baseline and name it RT!"E

%reate a region and name it R#!2!RT!"E

se assembl! RT C&G with Lanes

5elect R#!2!RT!"E or the oset alignment

5elect R#!2!RT!"E!$ormal Crown %rfa'e or the oset proile

5et the targets or the RT C&G with Lanes assem(l as shown

%arget )b5ect 'ame Subassembly

Target 5urace Eisting +rade 5urace RT &a!light

Bset Alignment R0$RT$ME and R:$RT$ME RT Cink to RT ME

-idth Alignment R0$:$RT$ME Right Cane

5lope Proile R0$RT$ME$@ormal %rown

5urace and R:$RT$ME$ME$CT o

%C 5urace

RT Cink to RT ME

Butside Ele#ation Proile R0$:RT$BE$R0$:RT$BE$@ormal

%rown 5urace

Right Cane

@otice that we can take care o the median being on the right or let side o centerline all in one step here

because when one alignment and proile ends the target will switch to the net one down the line. uick

and eas! to create

Defining te /edian Curb and utter -hen we deine the median curb and gutter we will need a new baseline. This new baseline will use the

centerline alignment and proile as the last baseline. @ame this baseline RT!ME . 5ince we are not

pro2ecting to the median using a Target we will ha#e to treat the same regions 0 and : separatel! b! using

two regions in our %orridor. This is due to the act that we will ha#e two dierent alignments and proiles

that we will need to use.

0L




Right Median Curb on Right Side of Centerline

@ow that the baseline is created we will want to create a region or the baseline RT$ME. @ame the region

R$0$RT$ME to deine the irst region, that o the median that is right o centerline.

Assign the assembl! RT Median %N+ to this region

8or this assemblies osets select alignment R#!2!RT!ME and Proile R#!2!RT!ME!$ormal Crown

%rfa'e.

There are no targets with this assembl! so we are done.

Right Median Curb on Left Side of Centerline

%reate another region or baseline RT!ME and name the region R!2!RT!ME .

8or this region we will use the Assembl! RT Median C&G LT of CL.

5et the assembl! osets select alignment R#!2!RT!ME and Proile R#!2!RT!ME!LT of CL %rfa'e.

There are no targets with this assembl! so we are done.

+oo!ing at te Corridor Properties

I#e described the process or the right side o a corridor or regions 0 and :. The process is the same or

an! region !ou are in. D! using a s!stematic naming con#ention it is 2ust a matter o naming things

correctl! and when we look at the %orridor Properties dialog bo !ou will see how organi/ed and eas! it is

to ollow the data. -hen we look at the %orridor Properties we see each baseline reerences the

centerline alignment and the centerline design proile. Each baseline deines onl! one side o the

roadwa! and one o the two edges o pa#ements BE or ME. This approach allows an eas! wa! to locateand e#aluate manageable portions o the roadwa! design.

#ssue Using /ultiple 4aselines

There is onl! one small problem with this method. I !ou want to #iew the cross$sections using the

Vie&6dit Corridor Section7 !ou will be disappointed because !ou can onl! #iew one baseline at a

time. Ma!be when Autodesk #iews m! class and sees how eas! this method is to use the! will add the

capabilit! to the sotware to #iew multiple baselines at once. This issue is easil! sol#ed or #iewing and

making sure e#er!thing looks correct b! creating cross$section #iews in the 5I drawing. Bnce e#er!thing

is good to go one can 3uickl! delete the section #iews. @ot 3uite as slick as using the Vie&6dit

Corridor Section tool, but it will let !ou know where !ou ha#e issues that need to be taken care o in !our

design.

Conclusions

#redefined File and Data Shortcut Structure

Deore doing a ma2or roadwa! pro2ect, spend some time and look at !our compan!s current standard ile

structure and ile naming con#ention. Then igure out how to best implement the new worklow re3uired

b! %i#il (&'. Then think where data should be stored or each design element and what other drawing

0)




iles will re3uire access to that inormation. Then show how the iles are linked together using data

shortcuts. This initial eort will allow a standard to be adhered to during the design process. It is #er!

eas! in %i#il (&' to get slopp! and put good inormation in the wrong location making design changes

diicult to accomplish. A ew hours o thoughtul brainstorming will go a long wa! to pre#ent man! designheadaches down the line that will not be eas! to correct.

&se of Consistent Naming Con'entions

I dont care i !ou do not like the naming con#ention that I came up with and presented in this class. The

important thing is that !ou ha#e a consistent naming con#ention that is used or naming alignments,

proiles, assemblies, subassemblies, baselines and regions. This naming con#ention needs to be in !our

companies %A& 5tandards so that an!one who touches the pro2ect will be able to 3uickl! get up to speed

on what was done and how it was done. Also, de#eloping a consistent worklow that matches the naming

con#ention is critical. As an eample, i we de#elop a naming con#ention that uses regions like I described

in this handout and then !ou design the corridor tr!ing to use onl! one region with perect assembl! then

the naming con#ention does not match the worklow. The naming con#ention and the worklow should gohand in hand so it is eas! or the designer to use the naming con#ention and the desired worklow.

Thin( Outside the )o$*

The most important aspect o this class is to encourage !ou to think outside the bo There are man!

wa!s to design using %i#il (&'. %i#il (&' has a #er! powerul set o d!namic tools that allows incredible

things to happen i one gets outside o the normal design paradigm. -hen looking at a design process

alwa!s think i I ha#e to change this will e#er!thing be d!namicH I not how can I make it d!namic so it is

eas! to updateH The other 3uestions to ask is how long will it take to design this wa! and will it ha#e

3ualit! assurances built into the processH I !ou can answer !es to these 3uestions then the process is a

good one I !ou come up with a great process or something I would lo#e to hear about it. Please do not

hesitate to email me !our great ideas

0O

au09 speakerhandout cv122-31

Documents