1 / 32

Model Validation of Transit Ridership at the Corridor and Transit Route Level

Model Validation of Transit Ridership at the Corridor and Transit Route Level. by Mark Charnews October 19, 2006. Reasons for a Validation of the Regional Travel Demand Model at the Corridor and Transit Route Level. Validate Travel Demand Model Transit Component to a greater level of detail.

kaelem
Download Presentation

Model Validation of Transit Ridership at the Corridor and Transit Route Level

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. Model Validation of Transit Ridership at the Corridor and Transit Route Level by Mark Charnews October 19, 2006

  2. Reasons for a Validation of the Regional Travel Demand Model at the Corridor and Transit Route Level • Validate Travel Demand Model Transit Component to a greater level of detail. • Use the Regional Model for Transit Corridor Analysis by the Regional Council • Determine if Regional Model can be used by local transit agencies, who may not have the resources to develop, maintain and run their own models, to do their own corridor analysis. • Provide a model for consistent transit studies for all local transit agencies.

  3. The Model Area and Transit Agencies’ Service Areas

  4. Regional Transit Monthly Ridership • Ridership has been reasonably stable from 1999 to 2005 with a slight decline between the start of 2001 and the end of 2003 that coincided with a small economic downturn in the region. Current ridership near or at 2000 levels.

  5. King County Metro (MetroKC) • MetroKC is the largest transit agency, with over 70 percent of total transit ridership in the area.

  6. Other Transit Agencies’ Monthly Ridership • A small decline in ridership occurred for each agency due to an economic turndown and current ridership has mostly recovered to year 2000 levels. • New Sound Transit Service took ridership away from MetroKC, Pierce and Community Transit.

  7. Bus Travel Times • AM Peak Service ttfs: Local Bus Service ft11 = 1.5708 * timau .min. (length * 12) Express Service ft12 = 1.53615 * timau .min. (length * 12) Park and Ride Service ft13 = 1.5125 * timau .min. (length * 12) Closed Door Service ft14 = timau • Transit times are related to congested highway times.

  8. Bus Travel Times • Mid-day Service ttf: Local bus Service ft11 = 1.72431 * timau .min. (length * 12) Express Service ft12 = 1.60597 * timau .min. (length * 12) Park and Ride Service ft13 = 1.4375 * timau .min. (length * 12) Closed Door Service ft14 = timau

  9. Comparison of Average Modeled Transit Times and Average Scheduled Times • Times are shorter than observed, transit speeds are faster.

  10. Comparison of Average Modeled Transit Times and Average Scheduled Times

  11. Comparison of Modeled and Observed Bus Route Times • Some outliers, many routes with different times depending upon which branch of the route is measured. Needs a careful manual match up for better accuracy.

  12. Comparison of Modeled and Observed Bus Route Times • Better fit for mid-day service.

  13. Modeled Daily Ridership Equation • Model only assigns a three hour AM peak and a six hour Mid-day period. Daily Ridership = 2.2327 * AM Ridership + 1.5643 MD Ridership • Based on Time of Day proportions from MetroKC data.

  14. Daily Ridership by Company • MetroKC - Modeled 392,919 boardings, Observed 358,806 boardings.

  15. Daily Ridership by Company • Pierce Transit - Modeled 40,733 boardings, 32,978 observed.

  16. Daily Ridership by Company • Kitsap Transit - Modeled 15,277 boardings, Observed 11,712 boardings.

  17. Daily Ridership by Company • Kitsap Transit – special case, each bus makes one trip in AM, one in PM passengers assigned to route for Bremerton Naval Yard. Modeled 2,025 boardings, Observed 529 boadings.

  18. Daily Ridership by Company • Everett Transit - very small service area, highway and transit network too coarse, TAZs too large. Modeled 4,031 boardings, Observed 2,550 boardings.

  19. Daily Ridership by Company • Community Transit - very poor fit, but total modeled ridership 19,844 boardings, observed 18,091 boardings is close.

  20. Daily Ridership by Company • Community Transit did a major redesign of service. • Using Fall 2000 ridership, a much better fit is obtained. • Modeled: 14,681 boardings, Observed 12,392 boardings.

  21. MetroKC Ridership by Service Type • Modeled 274,003 boardings, Observed 245,745 boardings.

  22. MetroKC Ridership by Service Type • Modeled 100,609 boardings, Observed 95,166 boardings.

  23. MetroKC Ridership by Service Type • Note R squared near to Community Transit (which has a lot of P&R service) R squared figure. • Modeled 18,307 boardings, Observed 17,894 boardings.

  24. MetroKC Ridership by Route Distance • The difference between Modeled and Observed boardings was plotted against one way route time. • Low R squared suggests no bias in boarding estimation by route distance.

  25. Transit Route Boardings within 35% of Observed

  26. Transit Route Boardings below 35% of Observed

  27. Transit Route Boardings above 35% of Observed

  28. Conclusions • Overall a reasonably consistent fit between modeled and observed boardings by route. • Bus travel time estimation needs to be refined. • Higher resolution TAZ system and highway/transit network needed for entire region to truly capture all transit routes.

  29. Future • Set dwell times as a function of boardings. • Examine path building parameters to see if better fit can be obtained. • Review these findings with local transit agencies. • Develop new zone system and higher resolution road network. • Suggestions?

  30. Questions Mark Charnews PhD. Mcharnews@psrc.org Puget Sound Regional Council 1011 Western Avenue, Suite 500 Seattle, Washington 98104-1035

More Related