1 / 39

Easy Breezy Beautiful DTA: Modeling of the Geary Boulevard Bus Rapid Transit Project

Easy Breezy Beautiful DTA: Modeling of the Geary Boulevard Bus Rapid Transit Project. Elizabeth Sall, Michalis Xyntarakis, & Billy Charlton. TRB Planning Applications Conference – Reno, NV May 2011. BRT Segment. Project Background – Geary BRT. Downtown.

mai
Download Presentation

Easy Breezy Beautiful DTA: Modeling of the Geary Boulevard Bus Rapid Transit Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Easy Breezy Beautiful DTA:Modeling of the Geary Boulevard Bus Rapid Transit Project Elizabeth Sall, Michalis Xyntarakis, & Billy Charlton SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY TRB Planning Applications Conference – Reno, NV May 2011

  2. BRT Segment Project Background – Geary BRT Downtown 4 Muni Bus Lines: Local, Limited, 2 Zonal Express 54,000 Daily Muni Boardings (Fall 2010) + Golden Gate Transit Service SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  3. “What Questions Do You Want To Answer About the BRT ?” • How many people will ride it? • If we take a lane away, where does the traffic go? What is impacted? • How will travel time change for Autos and Transit Riders on: • Geary Boulevard? • The Corridor? TDM TDM TDM V TDM SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  4. Overall Modeling Flowchart -- Before Land Use Transportation Where Are The Diversions? CHAMP Transit Ridership Transit & Auto Travel Time In Corridor Auto Demand in Corridor MAGIC VOODOO Synchro Intersection Volumes Auto Demand on Geary Intersection LOS In Corridor VISSIM Geary Roadway & Transit Performance SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  5. Why DTA? • Avoid messiness, crazy spreadsheets, & lots of manual labor SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  6. Why DTA? • Avoid Subjectivity SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  7. Why DTA? • Avoid Answering questions with the wrong tool * * * * SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  8. Overall Modeling Flowchart – With DTA Land Use Transportation CHAMP Transit Ridership What Are The Diversions? Auto Demand in Corridor DTA Synchro Intersection Volumes Transit & Auto Travel Time In Corridor Auto Demand on Geary Intersection LOS In Corridor VISSIM Geary Roadway & Transit Performance SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  9. Overview of How We “Got” DTA for Geary BRT • Initial DTA Development • What did we actually do to calibrate? • Where did we end up on validation? • What does it take to make a scenario? • Do the results make sense? SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  10. SF DTA Development:Current San Francisco DTA Subarea Now: NW Quadrant Van Ness / Fulton 200 Internal Zones 60 External Zones 3,000 Nodes 7,000 Links 240 Signals 83 Transit Lines Future: Entire City North of Cesar Chavez SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  11. Code. Read in : SFMTA Signal Cards for signal Timing Synchro files for intersection geometry Read the city stop sign shapefile for unsignalized intersections Transit Lines and transit dwell from SF-CHAMP files Read Demand from SF-CHAMP trip tables Write it all to Dynameq ASCII Format SF DTA Development:How did we get all that data into the DTA? SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  12. Geary DTA Development – Calibration Steps • Becoming one with your model: • Checked and double-checked network on Geary and parallel routes • Analyzed vehicle paths at various iterations • Select links, select links, select links • Modified freeflow speeds where justified • Modified traffic flow parameters where justified SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  13. Geary DTA Development – Calibration Steps • Original MEH SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  14. Geary DTA Development – Calibration Steps • Digging through path selections revealed: • Freeflow speed on parallel routes too fast • Final: SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  15. DTA Development - Validation • Targets: • Volumes: • High daily volatility: pattern >> actual numbers • Segment speeds: • within 2 mph on Geary • within 2-4 mph on parallel routes SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  16. SF DTA Validation:Count Data • Counts Used • 74 Mainline Counts • 700+ Turn Counts SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  17. Count Parser -- countsXLS2Dynameq.py Attribute on DTA Network Started with R^2 = .89 Slope=0.59! SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  18. SF DTA Validation : Validation Results – 15 Min Mainline Counts SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  19. SF DTA Validation: Validation Results – 15 Min Movement Counts SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  20. corridorPlot.py SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  21. 29 routes 102 79 101 82 117 118 34 77 91 72 69 71 67 13 9 1 62 30 3 46 45 2 31 4 135 6 20 7 110 SF DTA Validation:Travel Time Data SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  22. SF DTA Validation:Travel Time Data Source: SFCTA Spring 2009 LOS Monitoring SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  23. RouteTravelTimes.py • Key to [less] painful calibration: easy access to data StartTime: 5:00PM EndTime : 6:00PM Scenario: 2008 DefinedRoutes = All OR Name = NewRoute OriginNode = 12345 DestinationNode = 54321 SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  24. SF DTA Validation:Travel Time Validation Results For this effort, Started with Slope: 0.90 R-2 = 0.88 SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  25. Making a Scenario • Three basic steps: • Demand • Highway Network • Transit Network SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  26. Getting From Cube Making a Scenario – Demand • …to Dynameq SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  27. importCubeDemand.py Parses Dynameq Network Parses Cube Matrix Punch Corrects Boundary Validates vs Network Assigns Intrazonals Applies Time Slices Dynameq Demand File SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  28. Making a Scenario – Highway Network SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  29. Getting From Cube Making a Scenario – Transit Network • …to Dynameq LINE NAME="MUN5I", FREQ[1]=4, FREQ[2]=8, FREQ[3]=5, FREQ[4]=15, MODE=2, N= 27980, 27978, DELAY=0.104, N=-27976 LINE *id "label" litype vtype stime level 13 "MUN5I" 0 Generic 15:31:00 0 *hway dep 00:05:00 36 SEGMENTS *id start end label tlane dwell stopside 1 27980 53342 label1 1 0.000000 0 2 53342 27978 label2 1 6.240000 0 3 27978 27976 label3 1 0.000000 0 SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  30. 27980, 27978, 27976 1 27980 53342 2 53342 27978 3 27978 27976 importCubeTransitRoutes.py Parses Dynameq Network Parses Cube Transit File Trims to Subarea Fixes Connectivity Randomizes Start stime 15:31:00 Calculates Departures *hway dep 00:05:00 36 Dynameq Transit File SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  31. Results – Corridor Volumes SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  32. Draft Results – Diversions Analysis SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  33. Draft Results –Speed Changes in Corridor -2% EB -3% WB SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  34. Exporting from DTA to Microsimulation Models • Two Options: • Subarea extraction (preferred) • Flexible time increments • Script output to format in VISSIM matrices ascii • Intersection Turn Movements • Flexible time increments • Specify node set or every node along route X • Exports to one CSV per intersection SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  35. Questions?Upcoming dta project website:http://code.google.com/p/dta/ • elizabeth@sfcta.org • Special Thanks: Zabe Bent, Dave Stanek, • Eric Wolmerdorff, David Parisi & Michelle Bina SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  36. Corridor flow plot 5 to 6PM, Geary Boulevard WB, San Francisco, CA Volume of vehicles getting on Geary Volume of vehicles getting off Geary 250 Flow on Geary Volume 450 Direction of movement SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  37. Select Link Analysis on Geary And 15 Ave WB, Flow from 5 to 6 PM Right Turn Flow Select Link Left Turn Flow SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  38. Getting From Cube Making a Scenario – Demand • …to Dynameq # importCubeDemand.py # input settings cubeFile= ..\subareaPM.csv outFile = ..\demandPM.txt DemandDuration = 3 hours TimeStepDemand = 15 minutes TimeSliceFactors= [0.08, 0.08, 0.08, 0.08, 0.08, 0.08, 0.09, 0.09, 0.09, 0.08, 0.07, 0.07] SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

  39. Getting From Cube Making a Scenario – Transit Network • …to Dynameq # importCubeTransitRoutes.py # input settings cubeFile= ..\transit.lin outFile = ..\dynameqTransit.txt Headway = ‘PM’ numSubareaNodes = 4 dynameqHwyNetworkFolder = ..\base08 SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY

More Related