1. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY 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

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

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

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

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

6. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY6 Why DTA? Avoid Subjectivity

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

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

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

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

11. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY11 SF DTA Development: How did we get all that data into the DTA? 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

12. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY12 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

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

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

15. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY15 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

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

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

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

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

20. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY20 corridorPlot.py

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

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

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

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

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

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

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

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

29. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY29 Making a Scenario – Transit Network LINE *id"label"litypevtypestime level 13"MUN5I"0 Generic15:31:000 *hwaydep 00:05:0036 SEGMENTS *idstart endlabel 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 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 Getting From Cube…to Dynameq

30. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY30 importCubeTransitRoutes.py Parses Dynameq Network Parses Cube Transit File Trims to Subarea Fixes Connectivity Randomizes Start Calculates Departures Dynameq Transit File stime15:31:00 1 27980 53342 2 53342 27978 3 27978 27976 27980, 27978, 27976 *hwaydep 00:05:0036

31. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY31 Results – Corridor Volumes

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

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

34. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY34 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

35. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY 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

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

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

38. SAN FRANCISCO COUNTY TRANSPORTATION AUTHORITY38 Making a Scenario – Demand Getting From Cube…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]

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