1 / 25

The Downtown Seattle Bus Monitoring System

The Downtown Seattle Bus Monitoring System. Collecting and Analyzing Transit Travel Time Data. 2011 ITS Washington Annual Meeting. Owen Kehoe, PE, PTOE King County Metro Transit : Seattle, WA. Bus Monitoring?. Project Background Data Sources: AVL, APC & AVI Data Processing & Reporting

jefferson-tommy
Download Presentation

The Downtown Seattle Bus Monitoring System

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. The Downtown Seattle Bus Monitoring System Collecting and Analyzing Transit Travel Time Data 2011 ITS Washington Annual Meeting Owen Kehoe, PE, PTOE King County Metro Transit : Seattle, WA

  2. Bus Monitoring? • Project Background • Data Sources: AVL, APC & AVI • Data Processing & Reporting • System in Action • Lessons Learned

  3. Seattle Bus Monitoring System Background

  4. History • Enhanced Travel Time Monitoring Need • 2005-2007: Bus Tunnel Closure • 2009-2016: Alaskan Way Viaduct • Uses • Scheduling/Funding • Identifying Problem Areas • Planning for the Next Impact

  5. Current Focus AWV • Alaskan Way Viaduct • Long-term detours • Reduced capacity • Enhanced Transit Services Agreement • WSDOT provides funding for transit • Added trips • Schedule Maintenance • Expand Monitoring System Source: WSDOT

  6. Seattle Bus Monitoring System Data sources

  7. AVL System • AVL = Automatic Vehicle Location • Signpost/Odometer based system • Travel time between timepoints only! • Route specific • Off-route buses not tracked • Data available System-Wide AVL Data feeds OneBusAway

  8. APC System • APC= Automated Passenger Counter • Sampling Method • 20% of Fleet APC-Equipped • Data Available After Service Change • Other Data Collected • Travel Time between Bus Stops • Dwell Time APC Data used to Track Ridership Trends

  9. AVI System • AVI = Automatic Vehicle Identification • Roadside RFID tag readers • Legacy TSP tags • Tags logged regardless of Route/Schedule • Strategic Locations AVI Reader  TSP Tag

  10. AVI Reader Locations • Original AVI System • North CBD Screenline • Central CBD Screenline • South CBD Screenline Outer CBD Screenline • Expanded AVI System • Outer CBD Screenline • W Seattle Screenline • Other Key Locations Other Key Locations

  11. AVI Reader Communication Readers communicate using Spread-Spectrum Wireless Phone drops provide backhaul to KC server Outer CBD Screenline Each reader has unique Node # Other Key Locations

  12. Seattle Bus Monitoring System DATA PROCESSING & REPORTING

  13. Huge amount of data! • MS Access and SQL Server • Make AVL data more useful • Interpolate timepoint data into street segments • GIS and Bus Stop data  Estimate travel time share Travel Time = 5 min AVL Data GIS Data Length= 1000’ Speed= 20 mph Length= 2000’ Speed= 30 mph Length= 1000’ Speed= 25 mph A B C D Bus Stop Data Dwell = 30 sec Dwell = 20 sec Share 0.41 0.29 0.30 2.0 min 1.5 min 1.5 min Travel Time = 3 min

  14. Matching • Need to combine AVL & AVI Data • AVI  CBD and selected locations • AVL  Outlying points • Travel Times calculated by matching • Coach ID, Route, Run, Date, [Time] Start Point End Point Coach: 2345 Route/Run: 5/13 Date: 3/14/2010 Timestamp: 10:34:33 Coach: 2345 Route/Run: 5/13 Date: 3/14/2010 Timestamp: 10:42:56 Match! Travel Time=8:23

  15. Types of Reports • Regular Reporting • Specific Pathways • Defined by roadway infrastructure • Grouped by Market Coverage Area • 3x/Year Service Change • Ad-hoc Reporting • Special cases • As needed basis

  16. Pathway Report Two Directions, Two Charts Pathway Map Sample Size: Indication of Data Quality Scenario Info

  17. Pathway MOE’s • Slice data into hour intervals • Median Travel Times (Average) • 25th – 75th Percentile (Reliability) Compare scenarios side-by-side 25th & 75th Percentile { Median Travel Time One Bar represents one hour of data

  18. Seattle Bus Monitoring System System in Action

  19. Monitoring tells a Story 12-13 minute delay PM peak Mid-Day Train Blockages • Baseline Condition: Fall 2009 • Fall 2010: 1st & Spokane Ramp Closure • Lengthy & unreliable detour • Spring 2011: Lane Reduction on SR-99 • Routes moved to 3rd Ave • Traffic diversion to 1st Ave

  20. Ad-Hoc Reporting Alaskan Way Viaduct 8-Day Closure Results

  21. Experiments in Real-Time Real-Time Travel Time Tool

  22. Seattle Bus Monitoring System Lessons Learned

  23. AVI Equipment Challenges Power Connections RF Interference Tag Reads 900MHz Band Fixed Frequency Wireless Communication 900MHz Spread Spectrum Repeaters Read Rate Reliability

  24. Data Processing Challenges Return Trips Confound Matching No Trip ID in AVI data Use maximum travel time cap Same Endpoints, Different Pathway Filter with Schedule Data Development Effort Expanded territory added complexity Ongoing refinement

  25. The Downtown Seattle Bus Monitoring System Collecting and Analyzing Transit Travel Time Data Owen Kehoe, PE, PTOE owen.kehoe@kingcounty.gov King County Metro Transit Seattle, WA

More Related