Download presentation
Presentation is loading. Please wait.
Published byBranden Whitacre Modified over 10 years ago
1
The Downtown Seattle Bus Monitoring System Collecting and Analyzing Transit Travel Time Data Owen Kehoe, PE, PTOE King County Metro Transit : Seattle, WA 2011 ITS Washington Annual Meeting
2
ITSWA 2011: Seattle Bus Monitoring Project Bus Monitoring? Project Background Data Sources: AVL, APC & AVI Data Processing & Reporting System in Action Lessons Learned
3
ITSWA 2011: Seattle Bus Monitoring Project BACKGROUND Seattle Bus Monitoring System
4
ITSWA 2011: Seattle Bus Monitoring Project 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
ITSWA 2011: Seattle Bus Monitoring Project 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
ITSWA 2011: Seattle Bus Monitoring Project DATA SOURCES Seattle Bus Monitoring System
7
ITSWA 2011: Seattle Bus Monitoring Project 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
ITSWA 2011: Seattle Bus Monitoring Project 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
ITSWA 2011: Seattle Bus Monitoring Project AVI System AVI = Automatic Vehicle Identification Roadside RFID tag readers Legacy TSP tags Tags logged regardless of Route/Schedule Strategic Locations TSP Tag AVI Reader
10
ITSWA 2011: Seattle Bus Monitoring Project AVI Reader Locations Outer CBD Screenline Other Key Locations Original AVI System North CBD Screenline Central CBD Screenline South CBD Screenline Expanded AVI System Outer CBD Screenline W Seattle Screenline Other Key Locations
11
ITSWA 2011: Seattle Bus Monitoring Project AVI Reader Communication Outer CBD Screenline Other Key Locations Readers communicate using Spread-Spectrum Wireless Phone drops provide backhaul to KC server Each reader has unique Node #
12
ITSWA 2011: Seattle Bus Monitoring Project DATA PROCESSING & REPORTING Seattle Bus Monitoring System
13
ITSWA 2011: Seattle Bus Monitoring Project 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 AD Travel Time = 5 min Length= 1000 Speed= 20 mph Length= 2000 Speed= 30 mph Length= 1000 Speed= 25 mph C Dwell = 20 sec B Dwell = 30 sec 0.410.290.30 Travel Time = 3 min AVL Data GIS Data Bus Stop Data Share 2.0 min1.5 min
14
ITSWA 2011: Seattle Bus Monitoring Project 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 Travel Time=8:23 Match!
15
ITSWA 2011: Seattle Bus Monitoring Project 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
ITSWA 2011: Seattle Bus Monitoring Project Pathway Report Two Directions, Two Charts Sample Size: Indication of Data Quality Pathway Map Scenario Info
17
ITSWA 2011: Seattle Bus Monitoring Project Pathway MOEs Slice data into hour intervals Median Travel Times (Average) 25 th – 75 th Percentile (Reliability) Median Travel Time 25 th & 75 th Percentile One Bar represents one hour of data Compare scenarios side-by-side {
18
ITSWA 2011: Seattle Bus Monitoring Project SYSTEM IN ACTION Seattle Bus Monitoring System
19
ITSWA 2011: Seattle Bus Monitoring Project Monitoring tells a Story Baseline Condition: Fall 2009 Fall 2010: 1 st & Spokane Ramp Closure Lengthy & unreliable detour Spring 2011: Lane Reduction on SR-99 Routes moved to 3 rd Ave Traffic diversion to 1 st Ave 12-13 minute delay PM peak Mid-Day Train Blockages
20
ITSWA 2011: Seattle Bus Monitoring Project Ad-Hoc Reporting Alaskan Way Viaduct 8-Day Closure Results
21
ITSWA 2011: Seattle Bus Monitoring Project Experiments in Real-Time Real-Time Travel Time Tool
22
ITSWA 2011: Seattle Bus Monitoring Project LESSONS LEARNED Seattle Bus Monitoring System
23
ITSWA 2011: Seattle Bus Monitoring Project AVI Equipment Challenges Power Connections RF Interference Tag Reads 900MHz Band Fixed Frequency Wireless Communication 900MHz Spread Spectrum Repeaters Read Rate Reliability
24
ITSWA 2011: Seattle Bus Monitoring Project 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
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.