Preliminary Review of the PDP Requirements

Transcription

1 Preliminary Review of the PDP Requirements Planning RSTWG Meeting March 22, 2010 Prepared by Paula Okunieff

2 Objectives, Clarifications, Assumptions Planning Data Typology and Classification Document Organization Cross Cutting / Selection concepts Geography and Time Planning Data Set Description Next Steps and schedule Demonstration Approach Topics

3 Does this make sense? Are there better ways of defining a term? Are data concepts missing? Do we really need these data concepts to calculate the performance measures? Do we need these data sets? Are the equations correct? In the ballpark without refinements that you may include. Objectives to answer these questions

4 This document does not assume that the performance measure is defined for your study like we define it in here. That is why the raw service information is detailed! This document does not provide guidance on how to generate policy measures for Federal and State reporting. This is a preliminary draft. Clarifications

5 PDP data sets can only be provided to planners when Operators submit the data. Assumptions

6 Planning Typology / Classification

7 Spatial Dimension (custom & transit) Transit Network patterns, facilities, transit paths, places, locations Cross Cutting Spatial Dimension

8 Temporal Dimension (custom & transit) Transit and Planning Time Periods Spatial Dimension Transit Network) Cross Cutting Temporal Dimension

9 Select by Geography or transit network Time period or recurring time period Agency Drives a Query-Response Approach Requirements document focus is on Data descriptions Functionality is not part of this Requirements Document What is a dimension?

10 PDP Query Spatial Selection Params Temporal Selection Params Agency List PDP Data Set Package Includes selection criteria (time and geography) and service information. PDP Result Set Spatial Feature Set Time Period Data Concept Planning Data Set

11 Requirement Document Organization

12 1. Introduction 2. Planning Data Overview Summary of ConOps and relationship to Portal Planning Data Typology & Classification Data Profile Format (Query Result Set) 3. Detailed Requirements Cross Cutting 4. Detailed Requirements Planning Data Concepts and Data Sets 5. Validity Checking 6. Metadata 7. Conformance PDP Requirements Sections

13 Definitions Describes scope Includes some policy level definitions Data Concepts Planning Data Sets Requirements for new and extended data concepts to add to SDP Extended descriptions are included in an appendix Requirements / description for planning data concepts and service data that are used to generate a planning data concept. Examples For each Planning Data Set Volunteers needed for more and better examples. Detailed Requirements Sections

14 Transit Network Data Concept The Spatial Dimension Data Set Description

15 Transit Features are identified in the SDP Point [0-D] Key Feature set Polyline [1-D] Key Feature set Polygon [2-D] Key Feature set Point Key is locationid Point Features, e.g., Amenity Depot Passenger access component Portal Timepoint Transfer Cluster Transit Facility Transit Stop Page 25 for table of Transit Features Spatial Data Concept

16 Polygon Type (extension) Use KML to extend the polygon type Use to describe following: Service Area Fare Zone Parking facility Model described in Appendix C (based and extended WDMS parking data model) Additional Spatial Features or Feature Format

17 Transit features Selection Criteria Attributes assoc. with data set Point Features Transit places, events By Polygon By Circle By Corridor By Transit features Count Polyline Features Transit network segments (path, alignments) Same criteria as point features (but may be defined differently) Count Linear distance (without duplication) Summary Data Set Selection Criteria Polygon Features Transit features represented as a polygon Same criteria as point features (but may be defined differently) Count Circumference Area

18 Transit Network Selection Parameter Feature Set List Location Basic Transit Network Data Set Format

19 p. 42 Example of a Tool to Select Spatial Dimension Elements

20 Time Period Data Concept The Temporal Dimension Data Set Description

21 Effective Period Type of Period Day type General time intervals (continuous & recurring) Custom recurring intervals Custom continuous periods Type of Clock Schedule vs. 24 hour Time Period Temporal Dimensions

22 Temporal Data Model Model accommodates multiple time dimensions. Currently limited at three (3). Blue highlighted entities refer to SDP and transit temporal dimensions like Schedule version Day type Daily period (peak fare) Yellow highlighted entities refer to user-defined temporal dimensions May includes BPM AM/PM Peak NTD monthly (for ridership), etc.

23 Example of a tool to Select Time Period p., 56

24 Temporal Data Set Top level includes Effective Period TimeDimension includes up to 3 custom and agency defined time periods.

25 Service Supplied Data Concept and Data Set Requirements

26 ..describes service provided to meet needs of current and future customers, and used to measure effectiveness of service plans that are translated into deliverable service. Uses schedule and other planned service data (defined in SDP) Service Supplied

27 Key Summary Data Sets to Measure: Mode Average Running Time (scheduled) Headway / Frequency Service Type Span of Service Capacity (vehicle and infrastructure) Transfer Opportunities (coordinated service) Planned exceptions Create Data Sets to Calculate Performance Measures based on Schedules

28 Additional SDP Data Concepts (1) Service Type Add to Trip element. (2) Public Transit Vehicle (PTV) -- Rail and Bus to support vehicle capacity measure.

29 Planning / SDP Mode Running Time (ART) Capacity Trips Not applicable (see Route) List raw trip info, sorted by patterns; calculate ART from origin to destination The total capacity (as defined by PTV_Type) for each trip for a route (by direction and sorted by pattern). Planning Data Set Requirements The table (on page 68-70) shows the data sets that can be requested based on the selected Spatial Dimensions. 1. route by direction 2. trips (patterns) 3. route segments (part of patterns or multiple patterns) 4. transit facility, stops, and transfer cluster The table describes business rules related to how the data is summarized.

30 Avg Running time Running time data set count pathlist number segmentid First Location agencyid routeid segmentid is a patternid for a Trip request or tranpathid for a Route Segment request Next Location Path Running Time List Route Direction tripid First Trip Time Next Trip Time Average Running Time Data Set

31 Service Consumed Data Concept and Data Set Requirements

32 Service Consumed are those transit provisions -- related to services and facilities -- that are used by transit passengers as part of revenue service. Key Data Concepts Boardings / Alightings at stops Passenger Load by route segment Key Summary Data Sets Average Load Average Ridership (at stop) Service Consumed

33 Passenger Count New Data Concepts and their relationship to the SDP data concepts. Passenger Load is calculated from CountList Structure Boardings (oncount) and Alightings (offcount). thrucount* is used to capture the number of passengers who stay on an interlining vehicle. wconcount, wcoffcount and wcthrucount is used to capture wheelchair ridership. cumulativeon / Off captures the boarding and alighting from the start of each trip. * thru count idea from TCRP Report 113: Using Archived AVL-APC Data

34 Avg Load Data Set Load is calculated differently for Routes (trips) vs. Corridors (route segments) PC Count (=n) Avg Load Passenger Count List Passenger Count_1 Passenger Count_... Passenger Count_n Average Load Data Set

35 Accessibility Data Concept and Data Set Requirements

36 The ease of mobility and maneuverability (e.g., time, distance and transfers required) for a person to get from point A to point B using transit. Accessibility

37 Key Data Concepts Vehicle Equipment Wheelchair lifts, ramps, signs, announcements, other equipment for rail, subway and bus Station Platform Access (gap, drop); equipment to bridge gap Announcement and Signs Frequency, Volume/Brightness, type, location of Braille signs Accessible paths Transfers Access to stations/stops (incl. entrances, pads, and bet parking and stop/platform) Accessible Data Concepts

38 What are the Data Sets? Fleet by vehicle equipment type Queries related to specific stations, routes and trips with high (wheelchair) ridership that have certain (vehicle-station-stop) characteristics (e.g, gap, equipment, pad type, etc.) Accessible path for a specified station -- with estimated distance (time) to travel from origin to destination. Accessible Data Sets

39 Service Information Comparison Data Set Requirements

40 Create packages of Period and Data Create references to link Period and Data Agency List Agency List Spatial Dimension Spatial Dimension Differences Differences Result set Planning Set 1 Time Dimension Result Set Time Dimension 1 Planning Set Time Dimension n Planning Set n Time Dimension Planning Set Planning Set 1 Planning Dimension n Result Set Alternatives

41 13 April -- Complete 1 st Draft of PDP Requirements Revised Transit Network section Include summary table that relates spatial dimension result set to planning data sets Completed sections on Accessibility and Comparison Data Sets Initial ideas for Chapters 5-7 (checking, metadata, and conformance) Preliminary Schema (and data model related to SDP) Incorporate changes based on today s discussion Interface for NYMTC BPM and TBEST Next Steps

42 13 April 1 st Draft Due 1 April Solicit demonstrations for TBEST May Comments and review meeting Results from demonstration 3 June 2 nd Draft Due 16 June Final comments due 30 June Final PDP due Next Steps

43 Solicit 1 or 2 Transit Planning Organizations to participate Propose 3 Alternative Simple Planning Studies Work with organization to select and refine study. Validate and verify data from SDP Implement study Draft two reports Planning Study Lessons learned and improvements to PDP Demonstration Approach

44 Thank You