memorandum #2015 -97 to: hampton roads transportation ... hrto subcommittee-fu… · memorandum...

McKinley Price, Chair, Linda T. Johnson, Vice Chair

The Regional Building 723 Woodlake Drive Chesapeake, Virginia 23320 757-420-8300

Robert A. Crum, Jr., Executive Director

August 4, 2015 MEMORANDUM #2015-97 TO: Hampton Roads Transportation Operations (HRTO) Members & Guests BY: Robert B. Case, PE, PTOE, PhD – Principal Transportation Engineer RE: HRTO Subcommittee Meeting – August 11, 2015 An HRTO Subcommittee meeting will be held 9:30 a.m. – 11:30 a.m. on Tuesday, August 11, 2015, Regional Board Room, 723 Woodlake Dr., Chesapeake. The meeting will be conducted by Mr. Brian Fowler (Norfolk), HRTO Co-Chair. 1. Public Comment Period

2. Summary Minutes of June 9, 2015 Meeting

Minutes of the previous HRTO meeting are attached.

Attachment 2

Recommended Action: Approval

3. Local Evacuation Plans 9:30 a.m. – 10:15 a.m.

As a follow-up to VDEM’s review of evacuation plans last summer, VDOT is helping localities update their local plans. Mr. Larry Trachy (VDOT, Operations, Central Office) will lead a discussion of that effort.

4. Operations Strategy Update

10:15 a.m. – 10:30 a.m.

Background: • In January 2014, the HRTPO Board allocated $400,000 RSTP funds for an

Operations Strategy (UPC 105492). • At the June 2014 HRTO meeting, Co-chair Mike Corwin (VDOT) offered to

manage this project using one of VDOT’s four on-call consultants.

On July 8, 2015 the Project Steering Team (PST) gave its approval to the scope of the first task to be completed by VDOT consultant Kimley Horn.

HRTO Co-Chair Mike Corwin (VDOT) will provide an update and next steps.

August 4, 2015 Page 2

5. Potential for Intersection Congestion Alleviation (PICA) 10:30 a.m. – 11:15 a.m.

In the recent CMP master document, HRTPO staff identified arterial roadway segments with high potential for intersection congestion alleviation (called “PICA” for short), i.e. segments that have more delay than one would expect given their volume per lane and location/type (e.g. rural, high design speed vs. urban, low design speed). HRTPO staff recently examined each high-PICA segment in the CMP master document, identified the promising ones—those likely to receive major benefit from minor improvement—and recommended further analysis to estimate that benefit. Dr. Robert Case (HRTPO) will provide an overview of the PICA analysis, present informal survey results, and look for feedback from the subcommittee. Attachment 5

6. HRTPO Update 11:15 a.m. – 11:30 a.m.

Rob Case and Keith Nichols (HRTPO) will update the HRTO on operations-related HRTPO actions:

• Recent actions of HRTO’s parent committee – the Transportation Technical Advisory Committee (TTAC)

• Recent actions of VDOT’s RCTO-TIM (Traffic Incident Management) committee.

7. Next Meeting Schedule, Location, and Agenda Items

The next HRTO meeting is scheduled for Tuesday, October 13, 2015 at 9:30 a.m. (location TBD).

RBC/kg Attachments

August 4, 2015 Page 3 HRTO Subcommittee: Darin Bracy, WATA Alesia Cain, HRT Kamlesh Chowdhary, HRT Ken Coody, VDOT Randy Cooper, NN Michael A. Corwin, VDOT Kevin Eppley, CH Jeffrey Florin, VPA Brian C. Fowler, NO Steven Froncillo, CH Franklin Hickman, VB Jacqueline M. Kassel, NN

Stephen P. Kopczynski, YK Robert E. Lewis, SU Ric Lowman, VB Oliver Rose, VDOT Daniel A. Rydzewski, NO W. Leon Sisco, WATA Eric Stringfield, VDOT Danny Williams, PO Martin Willson, HA James Wright, PO John Yorks, HA

August 4, 2015 Page 4 HRTO Invited Guests: Joel Acree Susan Baldwin, HRT Jocelyn K. Bauer R. Stephen Best, CH Tim Breslin, CH Chad Brooks David Brown, VSP Robert Buckham, VSP Leah Bush, VDH A. Call, HA Jimmy Carter Mecit Cetin, ODU Jonathan Clark, Open Roads Dwayne Cook, VDOT Marc Copeland Steven Cover, VB Scott Cowherd, VDOT Barbara Creel, WATA Kevin Crum, SNJB William P. Dent, WM Fire Leon Dextradeur, VB Thelma Drake, NO Doug Draper, CH Martha Morecock Eddy, Timmons Michael Felix, NO Rusty Fitzhugh, VDOT Eric Fly, Seamcorp Robert K. Gey, VB George Glazner, NN James Gray, HA Cynthia Hall, NO John Hendrickson, PBQ&D Steve Hetrick, AG Jeffrey B. Holland, CBBTC

Robert T. Holloway, Jr., PQ John Horner, Open Roads Chuck Houck, NO Amanda Jacobs, JC Daniel E. Jenkins, FHWA Alan Jensen, P.E., NAVY John Kaoudis, NN Raymond Khoury, VDOT Charles Lavene, Norfolk Airport Stephen D. Little, Transdyn Glenn McBride, VDH Jake McCoury, VSP Ryan McLane, ERC Mike Miller, VDOT Joe Moore, NN Jessie Neal, VDOT Mark Outlaw, SU Earnest Poole, VSP Matthew Riethmiller Iris Rodriguez, FHWA Safety Officer, NN Mark Sawyers Mark Solesky, CH James Stanek, VDOT Gregory S. Staylor, CH Chris Swartz, HA Charles E. Vidrine, NAVY Keith Whitley, VSP Scott S. Williams, NN Jeff Wise, NO Nick Wooten, HA Kevin Wyne, PQ

Copy: Sam Belfield Keith Nichols Seth Schipinski Camelia Ravanbakht

DRAFTMinutesoftheJune9,2015HRTOSubcommitteeMeetingSandy Bottom Nature Park, 1255 Big Bethel Road, Hampton, VA 9:30am Attendees:GregBilyeu VDOTC/ORobCase HRTPOJonChambers Kimley‐HornMichaelClements VDOTC/OMikeCorwin VDOTScottCowherd VDOTC/OBrianFowler NorfolkSteveFroncillo ChesapeakeCarlinHebert Kimley‐HornSteveHetrick Albeck‐Gerken,Inc.FranklinHickman VirginiaBeachRobertLewis SuffolkMikeMiller VDOTWalterNein ChesapeakeKeithNichols HRPTOIrisRodriguez FHWAMartinWillson Hampton1. PublicCommentPeriod

Nocomments.2. MinutesfromApril14,2015Meeting

Nomodificationsoftheminutes–Approved.3. VDOT Statewide Signal Update

Mr.MichaelClementsSignal&ArterialSystemsProgramManager,VDOT,CentralOffice

A. ArterialOperationsPlan

a. Purpose:TopresenthighlevelframeworkthatwillsetthedirectionfortheintegrationofmoreeffectiveandrealtimemanagementoftrafficonarterialhighwaysfromwithinVDOTTOCs

b. Vision i. StatusofSignalSystemsii. PerformanceonSignal&ArterialSystemsiii. RealTimeResponse

c. Goals:i. Managesignalsbasedonrealtimeconditions

Attachment 2

ii. Realtimeinformationiii. Promotecoordinationofsignals

d. Highpriorityneeds/focusesi. Communication‐HighSpeedbandwidthii. Automatedmonitoringsystemsforproactivemaintenanceiii. Developandimplementmonitoringiv. Establishsystemforsignaltimingpracticestoprovidestatewide

consistencye. AOPOngoingStrategies&Initiatives

i. Statewidesignalcontrollerprogramii. Statewidecentralsignalsystemiii. VDOTTransportationCommunicationMasterPlan

1. Comp20142. Developplans

iv. AutoSignalPerformanceMetricsv. ASCTvi. ICM(IntegratedCorridorManagement)vii. DevelopStandardAgreementswithlocalitiesfor

1. EVP‐EmergencyVehiclePreemp.2. TSP‐TransitSignalPriority

viii. Connectedvehicletestbedsix. Developmentofincidentmanagementandtimingplansx. UpgradingtoIPaddressablesignalequipment

f. AOPFuturePlansi. RTSOP(Reg.TrafficSignOpsProgram)ii. ATM(ArterialActiveTrafficManagement)iii. DynamicLaneAssessment

B. Statewidesignalcontrollerplatform

a. 3000Signalsi. EasternRegion

1. VDOT‐1732. Local‐1635

b. 6typesofcontrollersc. Variouscommunicationlinksd. SignalSystemGaps

i. TOCFacilitySpaceii. CommunicationNetworkiii. IPAddressableFieldEquipmentiv. MaintenanceManagementSystemsv. FreewayIncidentManagementandSpecialEventPlansvi. Performance

C. Statewidecentralsignalsystem

a. SystemevaluationandselectionofastatewidecentralsystemforVDOTb. June2015initiatedc. Conceptofoperations

Attachment 2

d. Systemrequirementsi. Compevaluationii. Verificationandvalidationofplansiii. Procurementplaniv. AnticipatedcompletionDecember2015

D.CommunicationsMasterPlan—ongoingprojectwithKimleyHorn.

4. OperationsStrategyUpdate

A. Background

a. InJanuary2014,theHRTPOBoardallocated$400,000RSTPfundsforanOperationsStrategy(UPC105492).

b. AttheJune2014HRTOmeeting,Co‐chairMikeCorwin(VDOT)offeredtomanagethisprojectusingoneofVDOT’sfouron‐callconsultants.

B. Updateandnextstepsa. MetwithKimleyHornimmediatelyfollowingHRTOmeeting.b. Resultsofmeetingwillbesharedsoon.

5. HRTPOUpdate

Dr.RobertCaseHRTPO

A. RecentactionsofHRTO’sparentcommittee–theTransportationTechnical

AdvisoryCommittee(TTAC)a. May6Meeting

i. ApprovedHRT’sTIPamendmentwhichincludes:1. Added$104KforSurvey/SROEquipment2. $501KaddedforADABusStopUpgrades3. AddednewprojectforBusTechnologyupgrades

b. June3Meetingi. ApprovedDRPT’samendment

1. Transferred$826KtoBusTechnologyupgrades

B. VDOT’sRCTO‐TIM(TrafficIncidentManagement)Committee‐April21Meeting:a. Tunnels‐atleastonelaneopenduringincidentsb. Crashreconstructionteamsworkingtospeedupprocessesinregion

i. Proposal:AtotalstationlaserunitinHamptonRoadswithacostofapproximately$60‐$100K

c. Mr.StanekshowedVDOT’sIncidentDetourPlansforI‐64

C. HighBang‐for‐Buckimprovement‐20intersectionshavebeenidentifiedwithhighpotentialforlow‐costimprovementinthefollowingcities:Hampton,VirginiaBeach,Chesapeake,Norfolk,Williamsburg.

a. IntroductionofHRTPOdevelopmenttoolidentifyingPotentialIntersectionCongestionAlleviation(PICA)tobediscussedindetailatAugustHRTOmeeting.

Attachment 2

6. Next Meeting Schedule, Location, and Agenda Items

ThenextHRTOmeetingisscheduledforTuesday,August11,2015at9:30a.m.(locationTBD).

HRTPOtoolidentifyingPotentialIntersectionCongestionAlleviation(PICA)tobe

discussed.

Attachment 2

1

ExaminingArterialSegmentsIdentifiedinthe2014CMPMasterDocumentashavingHighPotentialforIntersectionCongestionAlleviation(PICA)toIdentifyPromisingIntersectionsforHigh‐BenefitMinorImprovements

RobertB.Case,HRTPOStaffDRAFTJuly2015TableofContents(coloredbycity)

PromisingIntersections(only)

AMAnalysis Locality PagePembroke/LaSalle Hampton 7Independence/Baxter Va.Beach 8Northampton/DiamondSprings Va.Beach 10Aberdeen/Todds Hampton 12Witchduck/VBBlvd Va.Beach 13Mercury/PowerPlant Hampton 15Kempsville/Battlefield Chesapeake 16PrincessAnne/Colley Norfolk 19GW/Shell/Galberry Chesapeake 20

PMAnalysis Locality PageNewtown/VBBlvd Norfolk 24Newtown/VBBlvd Va.Beach 24IndianRiver/Providence Va.Beach 25Rte199/JamestownRd Wlmsbg 26Battlefield/Cedar Chesapeake 27Greenbrier/Volvo Chesapeake 28Witchduck/Cleveland Va.Beach 29Chesapeake/LittleCreek Norfolk 30IndianRiver/Reon Va.Beach 32Newtown/Kempsville/PA Norfolk 33Newtown/Kempsville/PA Va.Beach 33PICAanalysistable.xlsx

DRAFT

Attachment 5

2

OverviewIntherecentCMPmasterdocument1,HRTPOstaffidentifiedarterialroadwaysegmentswithhighpotentialforintersectioncongestionalleviation(called“PICA”forshort),i.e.segmentsthathavemoredelaythanonewouldexpectgiventheirvolumeperlaneandlocation/type(e.g.rural,highdesignspeedvs.urban,lowdesignspeed)2.Theroadwaysegmentswiththehighestpotentialforintersectioncongestionalleviation(i.e.highestPICAsegments)arereproducedinTable9(AM)andTable10(PM)below.

1HRCongestionManagementProcess,SystemPerformanceandMitigationReport,HRTPO,Oct.2014,pg.402ForfurtherexplanationofthedevelopmentandcalculationofPICA,seepage39oftheCMPmasterdocumentmentionedabove.

Attachment 5

3

Inthisanalysis,staffexamineseachhigh‐PICAsegmentintheCMPmasterdocument,identifiesthepromisingones—thoselikelytoreceivemajorbenefitfromminorimprovement—andrecommendsfurtheranalysistoestimatethatbenefit.

Attachment 5

4

MethodologyInordertoidentifypromisingintersections—thosewhichmayreceivehighbenefitfromlowcostintersectionimprovements—staffperformedthefollowinganalysisforeachhigh‐PICAarterialsegmentlistedinthe2014CMPmasterdocument:

1. IdentifytheindividualintersectionalongthesubjectarterialsegmentwhichislikelycausingthehighPICAvalue(“controllingintersection”)

GiventhatstaffhadmeasuredPICAintheCMPmasterdocumentforarterialsegmentsbydirection(fromcrossingarterialtocrossingarterial),thecontrollingintersectionisusuallytheintersectionattheendofthesegment.

2. Determinewhetherornotaprojectimprovingtheintersectionisimminent

Ifsuchaprojectisimminent,norecommendationwasmade.

3. Determinewhetherornotdelayatthesubjectintersectionislikelytobereducedbyaddingapproachlanes(thru,left,orright)

Delaycanlikelybereducedatintersectionsbyaddingapproachlanesformovementsthata)haveahighvolume,andb)currentlylackthemaximumnumberofapproachlanes3.Thevolumeofamovementcanberoughlyestimated(lowvs.high)byexaminingthegeographiccontextoftheintersection.Forexample,giventhetriangleformedbyWitchduckRd,IndependenceBlvd,andVBBlvd,itislikelythattheSBWitchduckleftturnvolumeatVBBlvdislow.

4. Recommendnextsteps

IftheintersectionappearsNOTtobeagoodcandidateforlaneaddition,staffrecommendedusingsoftware(e.g.Synchro)tocomparethedelaysassociatedwithexistingtimingandoptimaltiming,andtherebydeterminewhetherornotsignalre‐timingwouldbeeffective.IftheintersectionISagoodcandidateforlaneaddition,staffrecommendedusingsoftware(e.g.Synchro)toestimatethedelayeffectofcandidateimprovements.

3Thenumberoflanesapproachinganintersectioninagivendirectionislimitedbythenumberoflanesexitingtheintersectionalongtheotherintersectionlegs.Forexample,fora4‐wayintersectionoftwo4‐laneroads,eachapproachislimitedtoamaximumof2thrulanes,2leftturnlanes,and2rightturnlanes.

Attachment 5

5

AnalysisofAMHigh‐PICASegmentsSegmentswithhighPICAintheAMareshowninTable9below.

Onthefollowingpages,staffexamineseachAMhigh‐PICAsegmentlistedabove4usingtheabovemethodologytorecommendanalysisofthedelaybenefitofminorimprovementsforpromisingintersections.

4ignoringthosesegmentswithcongestioncauseddownstream[markedwithbullet]

Attachment 5

6

IndianRiverRd(FerrellPkwytoKempsvilleRd)WBControllingIntersection:IndianRiver/KempsvilleIntersectionTheCityofVBiscurrentlyexecutingaprojecttoconvertthistraditionalintersectiontoaninnovativeone(“indirectleftturnstothenorthandsouthonKempsvilleRoadandmedianU‐turnleftstotheeastandwestonIndianRiverRoad”).Recommendation:N.A.(Thecompletionofthisprojectwilllikelyalleviatecongestionatthisintersection.)

Attachment 5

7

PembrokeAve(SettlersLandingRdtoLaSalleAve)EBControllingIntersection:Pembroke/LaSalleIntersection

PembrokeAve(runningSW/NE)andLaSalleAve(runningnorth/south)[source:Google]Givenintersectionacuteangleandlocation,therearelikelyhighleft‐turnvolumesfromEBPembrokeontoNBLaSalle.Thismovementcurrentlyhasonlyoneleftturnlane.Recommendation:Test(e.g.w/Synchro)improvementscenarios#2thru#4against#1:

1.ExistingLaneConfigurationandExistingTiming2.ExistingLaneConfigurationandOptimizedTiming3.EBPembrokeAveLaneConversion:convertonethrulaneintoaleftturnlane(orthru‐left),resultingindualleftturnlanesonEBPembrokeAve4.PembrokeAveLaneAdditions:addaleftturnlanetoEBPembroke,resultingindualleftturnlanes;forlanealignment,alsoaddleftturnlanetoWBPembroke

Attachment 5

8

IndependenceBlvd(I‐264toBaxterRd)SBControllingIntersection:Independence/BaxterIntersection

Source:GoogleMapsGiventhatalargenumberofturnlanes(includingatriple‐leftset)havebeenprovidedatthisintersection(2SB,4EB,2.5NB,and2WB‐total10.5),andthatthemaximumnumberofthrulaneshavebeenprovided5,itisunlikelythatadditionalturnlanesorlaneconversion(i.e.convertingathrulaneintoaturnlane)wouldbefruitful.Recommendation:GiventhehighPICAvalue,checkingthesignaltimingwithSoftware(e.g.Synchro)maybefruitful.[NotethattheNBIndependencesegment(HollandRdtoBaxterRd)alsohasahighPICAscore(seebelow),givenmorecredencetotimingproblemsatthisintersection.]

5giventhenumberoflanesdownstreamofintersection

Attachment 5

9

Route35(Rte671toRte673)NBControllingIntersection:MeherrinRd/GraysShopRdIntersection

Source:GoogleMapsThisintersectionbeingun‐signalized,itappearsthattheintersectionisnotthecauseofthehighPICAscoreforthesubjecthighwaysegment.(Thescorecouldbetheresultofbaddata.)Recommendation:N.A.

Attachment 5

10

NorthamptonBlvd(WesleyanDrtoDiamondSpringsRd)EBControllingIntersection:Northampton/DiamondSpringsInterchange

Northampton(runningSW/NE)andDiamondSprings(runningNW/SE)[Source:Google]Giventhatalargenumberofturnlaneshavebeenprovidedatthisintersection,andthatthemaximumnumberofthrulaneshavebeenprovided6,itisunlikelythatadditionalturnlanesorlaneconversion(i.e.convertingathrulaneintoaturnlane)wouldbefruitful.Recommendation:GiventhehighPICAvalue,checkingthesignaltimingwithSoftware(e.g.Synchro)maybefruitful.

6giventhenumberoflanesdownstreamofintersection

Attachment 5

11

IndependenceBlvd(HollandRdtoBaxterRd)NBControllingIntersection:Independence/BaxterIntersectionDuetoahighPICAscorefortheSBIndependencesegmentapproachingthissameintersection,thisintersectionwasanalyzedaboveandcheckingsignaltimingwasrecommended.(Note:Iftheexistingtimingisclosetooptimal,thehighPICAvalueforthisNBsegmentmaybecausedbyspillbackfromcongestiondownstream.)NorthamptonBlvd(I‐64toWesleyanDr)EBControllingIntersection:Northampton/WesleyanIntersection

NorthamptonBlvd(runningSW/NE)andWesleyanDr(runningNW/SE)[Source:Google]After2013whenINRIXcollectedthedataHRTPOstaffusedtocalculatePICAvalues,NorfolkandVBcompletedaprojectimprovingWesleyanDr,includingconstructionoftriple‐leftturnlanes,likelyloweringtheneedforcongestionalleviationatthisintersection.Recommendation:N.A.

Attachment 5

12

AberdeenRd(MercuryBlvdtoToddsLn)NBControllingIntersection:Aberdeen/ToddsIntersection

AberdeenRd(runningnorth‐south)andToddsLn(runningeast‐west)[Source:Google]Givenintersectionlocation,thereislikelyahighleft‐turnvolumefromWBToddsontoSBAberdeen.Currently,onlyoneleftturnlaneservesthismovement.Recommendation:Test(e.g.w/Synchro)improvementscenarios#2and#3against#1:

1.ExistingLaneConfigurationandExistingTiming2.ExistingLaneConfigurationandOptimizedTiming3.WBToddsLn.LaneAddition:addaleftturnlane,resultingindualleftturnlanesonWBToddsLane;forlanealignment,alsoaddleftturnlanetoEBToddsLane

Attachment 5

13

WitchduckRd(I‐264toVa.BeachBlvd)NBControllingIntersection:Witchduck/VBBlvdIntersection(Seealsoanalysisofanotherpotentiallycontrollingintersectiononthissegment[Witchduck/Clevelandintersection]inthePMsectionbelow.)

WitchduckRd(runningnorth‐south)andVBBlvd(runningeast‐west)[Source:Google]Althougha$32mwideningofWitchduckRd(fromI‐264toVBBlvd)isplanned(2034Long‐RangeTransportationPlan,HRTPO,Jan.2012,pg.18‐9),alow‐costintersectionimprovementexecutedintheshort‐termatthisintersectionmaybevaluable.Eachapproachhasright‐turnlanes,andtheapproacheswithhighleft‐turnvolumeshavedualleft‐turnlanes.Recommendation:GiventhehighPICAvalue,checkingsignaltimingwithSoftware(e.g.Synchro)maybefruitful.(Note:Ifexistingtimingisclosetooptimal,thehighPICAvalueforthissegmentmaybecausedbytheleftturnaccessingI‐264WBortheschoolzone.)

Attachment 5

14

KempsvilleRd(ProvidenceRdtoPrincessAnneRd)NBControllingIntersection:Kempsville/Witchduck/PrincessAnneIntersection

PARd(east‐west),KempsvilleRd(runningsouth),WitchduckRd(runningnorth)[Source:GoogleMaps]Amassiveintersectionprojectisunderwayforthisintersection,thecompletionofwhichwilllikelyalleviatecongestionatthisintersection.Recommendation:N.A.

Attachment 5

15

MercuryBlvd(I‐64toPowerPlantPkwy)WBControllingIntersection:Mercury/PowerPlant

MercuryBlvd(runningeast‐west),ToddsLn(runningNW),andPowerPlantPkwy(runningtowardSE)[Source:GoogleMaps]Eachapproachhasright‐turnlanes,andtheapproacheswithhighleft‐turnvolumeshavedualleft‐turnlanes.Recommendation:GiventhehighPICAvalue,checkingthesignaltimingwithSoftware(e.g.Synchro)maybefruitful.

Attachment 5

16

KempsvilleRd(GreenbrierPkwytoChesapeakeExpressway)WBControllingIntersection:KempsvilleRd/BattlefieldBlvd/GreatBridgeBlvd

BattlefieldBlvd(runningN‐S),KempsvilleRd(runningeast),GBBlvd(runningwest)[Source:GoogleMaps]Althougheachapproachhasadedicatedright‐turnlane,onlytheKempsvilleRdapproachhasdualleft‐turnlanes.(WBGBBlvdcannotreceivedualLTL’sfromNBBattlefield.)Recommendation:Test(e.g.w/Synchro)improvementscenarios#2thru#4against#1:

1.ExistingLaneConfigurationandExistingTiming2.ExistingLaneConfigurationandOptimizedTiming3.EBGreatBridgeBlvdLaneAddition:addaleftturnlane,and/oraddathrulane4.SBBattlefieldBlvdLaneAddition:addaleftturnlane,resultingindualLTLs

Attachment 5

17

ChesapeakeBlvd(CromwellDrtoLafayetteBlvd)SBControllingIntersection:SBChesapeake/LafayetteGiventhattheintersectionofSBChesapeakeBlvdandLafayetteBlvdisnotsignalized,thehighPICAvalueonTable9maynotreflectaneededimprovement.Recommendation:N.A.MilitaryHwy(CanalDrtoBainbridgeBlvd)EBControllingIntersection:Military/BainbridgeGiventhatthisintersectionisnotsignalized,thehighPICAvalueonTable9mayreflecttheGilmertonBridgereplacementproject.Recommendation:N.A.

Attachment 5

18

PrincessAnneRd(LlewellynAvetoColleyAve)WBControllingIntersection:ThedelayonthissegmentmaybecontrolledbythePA/ColonialIntersectionand/orthePA/ColleyIntersection,bothanalyzedbelow.PA/ColonialIntersection

PrincessAnneRd(runningeast‐west)andColonialAve(runningnorth‐south)[Source:GoogleEarth]GiventhattheaboveGoogleEarthshotshowsleftturnlanesonColonial,andyettheGoogleMaps45˚shot(notshown)didnot,restripinghasapparentlyoccurredrecentlyatthisintersection,perhapsfollowingthegatheringoftheINRIXdataonwhichthePICAscoreisbased.Recommendation:N.A.

Attachment 5

19

PA/ColleyIntersection

PrincessAnneRd(runningeast‐west)andColleyAve(runningnorth‐south)[Source:GoogleMaps]Recommendation:Giventhattheheavily‐travelledNBColleyAveapproachtothisintersectioniscurrentlylimitedtoonelane(i.e.noleftorrightturnlanes)duetothethreeon‐streetparkingspotsattheintersection,checkingtheefficacy(viaSoftware(e.g.Synchro))ofreplacingthosethreespotswithatwo‐laneapproach(i.e.eitherathru/leftlaneandrightturnlane,oraleftturnlaneandthru/rightlane)maybefruitful.

Attachment 5

20

GWHwy(MillCreekPkwytoI‐64)NBControllingIntersection:GWHwy/Shell/Galberry

Source:GoogleMapsRecommendation:Testthebenefitofaddinglanesatthisintersection(e.g.usingSynchro),e.g.addinganotherNBleft‐turnlane.

Attachment 5

21

AnalysisofPMHigh‐PICASegments

SegmentswithhighPICAinthePMareshowninTable10below.

Onthefollowingpages,staffexamineseachPMhigh‐PICAsegmentlistedabove7usingtheabovemethodology(outlinedatthebeginningofthisreport)torecommendanalysisofthedelaybenefitofminorimprovementsforpromisingintersections.

7ignoringthosesegmentswithcongestioncauseddownstream[markedwithbullet]

Attachment 5

22

IndianRiverRd(I‐64toCentervilleRd)EB,ControllingIntersection:IndianRiver/CentervilleIntersection

Source:GoogleMapsAlthoughdemandatthisintersectionmayexceeditscurrentcapacity,basedontravelingthisrouteeachweekdayPMpeak,itappearsthatEBtrafficapproachingthisintersectionatthattimeishamperedbydownstreamintersections(e.g.IndianRiver/Kempsville).(NotethatthedownstreamsegmentisalsoonTable10asaPMhigh‐PICAsegment,andthereforeaddressedbelow.)Recommendation:FollowingthecompletionofthecurrentLynnhavenPkwyproject(betweenIndianRiverRdandCentervilleTnpk)—whichwillremovevehiclesfromtheIndianRiver/KempsvilleIntersection—andthecurrentIndianRiver/KempsvilleIntersectionproject—whichwillreducedelayatthatintersection—re‐calculatePICAatthis(IndianRiver/Centerville)intersection.

Attachment 5

23

IndianRiverRd(CentervilleRdtoKempsvilleRd)EB,ControllingIntersection:IndianRiver/KempsvilleIntersectionThecompletionofthecurrentLynnhavenPkwyproject(betweenIndianRiverRdandCentervilleTnpk)—whichwillremovevehiclesfromtheIndianRiver/KempsvilleIntersection—andthecurrentIndianRiver/CentervilleintersectionprojectwilllikelyamelioratetheproblemidentifiedbythecurrenthighPICAofthissegment.Recommendation:N.A.WitchduckRd(I‐264toPrincessAnneRd)SB,ControllingIntersection:Witchduck/PA/KempsvilleIntersectionThecompletionofthecurrentWitchduck/PA/KempsvilleintersectionprojectwilllikelyamelioratetheproblemidentifiedbythecurrenthighPICAofthissegment.Recommendation:N.A.

Attachment 5

24

NewtownRd(I‐264toVBBlvd)NB,ControllingIntersection:NewtownRd/VBBlvdIntersection

Source:GoogleEarthItislikelythatthisintersectioncausesmoredelaythanexpectedinthePMduetotheitslackofdualleft‐turnlanes,particularlyontheNBandSBNewtownRdapproaches.Althoughthisintersection(atleasttheSBapproach)wouldbeupgradedwiththeplanned$24mNewtownRdproject(2034LRTP,HRTPO,Jan.2012,pg.18‐5),significantcongestionreliefcouldbeprovidedsoonerandmuchmorecheaplybyaddingtheseturnlanes.Recommendation:EstimatethedelayofthefollowingscenariosusingSoftware(e.g.Synchro):

1. Existingintersectionconfigurationandexistingtiming.2. Existingintersectionconfigurationandoptimizedtiming.3. Additionofleft‐turnlanesontheNBandSBNewtownRdapproaches.4. Additionofaboveleft‐turnlanesplustheEBandWBthrulanesassociatedwith

wideningofVBBlvdfromJanafShoppingCentertoNewtownRd.

Attachment 5

25

IndianRiverRd(I‐64toProvidenceRd)WB,ControllingIntersection:IndianRiver/ProvidenceIntersection

Source:GoogleMapsEventhoughProvidenceisafour‐laneroad,itonlyhasonethrulaneineachdirectionatthisintersection.Therefore,itislikelythatthisintersectioncausesmoredelaythanexpectedduetothelackofdualthrulanesontheEBandWBProvidenceRdapproaches.ProvidenceRdbeingfourlanes,thisimprovementcouldbemadeattheintersectionalone,requiringnowideningofProvidenceRdupstreamordownstreamoftheintersection.Recommendation:Testthefollowingscenariosusingsoftware(e.g.Synchro):

1. Existingintersectionconfigurationandexistingtiming.2. Existingintersectionconfigurationandoptimizedtiming.3. AdditionofthrulanesonEBandWBProvidenceRdapproaches.4. AdditionofthrulanesonEBandWBIndianRiverRdapproaches.

IndependenceBlvd(I‐264toBaxterRd)SBControllingIntersection:Independence/BaxterIntersectionRecommendation:SeerecommendationforthisintersectionintheAMsectionabove.

Attachment 5

26

Rte199(JohnTylerHwytoJamestownRd)EBControllingIntersection:Rte199/JamestownRdIntersection

Rte199(East‐West)&JamestownRd(North‐South)[Source:GoogleMaps]16yearsago,HRTPOstaffstudiedtheoperationofthisintersection(Route199TransportationStudy,HRPDC,April1999)undervariousimprovementalternatives.StafffoundthataddingaleftturnlanetotheWBRte199approach(andaddingrightturnlanesatthreeapproaches)wouldprovideLOSDintheforecastyear2015.Followingthestudy,therightturnlaneswereadded,allowingthethru‐rightlanestobeconvertedtothrulanes.Theproposedleftturnlane,however,wasnotconstructed.Thisintersectioncurrentlyhasmaximumthrulanesatitsapproaches,singleleftturnlanes,andsinglerightturnlanesateachapproach.Therefore,toimprovethisintersectionwouldrequireoneormoreadditionalleft‐turnlanes.Recommendation:Usesoftware(e.g.Synchro)toestimatethedelayimprovementexpectedfromadditionalleftturnlanesontheSB,EB,andNBapproaches8.

8SBJamestownRdsouthofthisintersectionhavingonlyonethrulane,dualWBleftturnlanesarenotrecommended.

Attachment 5

27

BattlefieldBlvd(KempsvilleRdtoCedarRd)SBControllingIntersection:Battlefield/CedarIntersection

Source:GoogleMapsCurrently,thelackofadedicatedSBrightturnlanefortheheavyrightturnmovementforcesboththruandright‐turningtraffictousetwolanes,providingsub‐optimalperformanceatthisintersection.AddingalanetotheSBBattlefieldBlvdapproachatCedarRdwouldprovidetwothrulanesandadedicatedrightturnlane,reducingdelaysatthisintersectioninthePM.Recommendation:Usesoftware(e.g.Synchro)toestimatethedelayimprovementexpectedfromanadditionalSBapproachlane.

Attachment 5

28

GreenbrierPkwy(EdenWaytoVolvoPkwy)SBControllingIntersection:Greenbrier/VolvoIntersection

Source:GoogleMapsAthirdlanewasrecentlyaddedforvehiclesleavingthisintersectionintheNBdirection.Giventhenumberoflanescurrentlyexitingthisintersection(3NB,2WB,2SB,2EB),additionalleftturnlanescouldbeaddedtotheEB,NB,andWBapproaches,and—mostimportantly—anadditionalthrulanecouldbeaddedtotheNBapproach.Recommendation:Usesoftware(e.g.Synchro)toestimatethedelayeffectofaddingapproachlanesatthisintersection.

Attachment 5

29

WitchduckRd(I‐264toVBBlvd)NBControllingIntersection:Giventhe23totallanesapproachingtheWitchduck/VBBlvdintersection,theunexpecteddelayonthissegmentofWitchduckRdmaycomefromtheWitchduck/ClevelandIntersection.(SeealsothephotoandanalysisoftheWitchduck/VBBlvdintersectionintheAMsectionabove.)

Source:GoogleMapsAlthougha$32mwideningofWitchduckRd(fromI‐264toVBBlvd)isplanned(2034Long‐RangeTransportationPlan,HRTPO,Jan.2012,pg.18‐9),alow‐costintersectionimprovementexecutedintheshort‐termatClevelandStmaybevaluable.Giventhenumberofexistinglanesexitingthisintersection,additionalapproachlanescouldbeaddedtotheWB,NB,andEBapproaches.Recommendation:Usesoftware(e.g.Synchro)totestthedelayeffectofaddingapproachlanesatthisintersection.

Attachment 5

30

ChesapeakeBlvd(I‐64toLittleCreekRd)NBControllingIntersection:Chesapeake/LittleCreekIntersection

Source:GoogleMapsGiventhatonlytwoapproacheshavededicatedrightturnlanes,andonlyoneapproachhasdualleftturnlanes,theadditionofleft‐turnandright‐turnlanestothisintersectionoftwo4‐laneroadwaysmaysignificantlyreducedelay.Recommendation:Usesoftware(e.g.Synchro)toestimatethedelayeffectofaddingturnlanesatthisintersection.

Attachment 5

31

IndianRiverRd(FerrellPkwytoKempsvilleRd)WBControllingIntersection:IndianRiver/KempsvilleIntersectionForanalysisofthisintersection,seeAMsectionabove.[documentcontinuesonfollowingpage]

Attachment 5

32

IndianRiverRd(ProvidenceRdtoI‐64)EBControllingIntersection9:IndianRiver/ReonIntersection

Source:GoogleMapsGiventheheavycongestiononEBIndianRivereastofI‐64inthePM,thecongestiononthissegmentofIndianRiver(westofI‐64)maybecausedoff‐site,i.e.byspillbackfromtheover‐capacityintersectionsontheeasternsegment.Given,however,theheavyleftturnvolumeonSBReonDr(towardtheinterstate)—anditssingleleft‐turnlane—itappearsthatdelayatthisintersectionmaybesignificantlyreduced(atleastfortravelersapproachingonReon)byanadditionalleftturnlaneonSBReon.Notethat—giventhetriangularconfigurationofReon,Providence,andIndianRiver—rightturnsfromSBReonarelikelylowinvolume.Likewise,thrumovementsfromSBReonintoPinewoodVillagearelikelylow.Recommendation:Usesoftware(e.g.Synchro)toestimatethedelayeffectofanadditionalReonDrleftturnlane.Thislanecouldbeaddedeitherbya)buildinganewlane,orb)convertingtheexistingrightturnlaneintoaleft‐thru‐rightlane.

9Seeidentificationofcontrollingintersection/segmentbelowpicture.

Attachment 5

33

NewtownRd(I‐264toKempsville/PARd)SBControllingIntersection:Newtown/Kempsville/PAIntersection

Source:GoogleMapsGiventhatonlyoneapproachhasdualleftturnlanes,theadditionoflanestothisintersection(particularlyanadditionalleftturnlaneonEBKempsvilleRdforinterstate‐boundtraffic)maysignificantlyreducedelay.Recommendation:Usesoftware(e.g.Synchro)toestimatethedelayeffectofaddinglanesatthisintersection.

Attachment 5