Assignment and Description different types of service functions by its time dimension as designated by an authority. The period may be characterized when something changes from one state to another, for example, a specific fare cost may be assigned to a “peak” fare time period, while an fare time period may indicate a lower fare cost. Table 17: Time Period Requirements for Temporal Dimension Data Set Req’t # Req’t Name Requirement Description for Summary Data Set 1 Uniqueness and Name A time period is or assigned a unique index. A time period name may assume the purpose of the type of time period (see Requirement 7), for example, monthly ridership
Figure 15: Example of a Time Period Selection Tool The values that demonstrate the example above would look like the example in Table 23. 23: Example of Implementing a Hierarchical Recurring Time Interval Time Period Time Period Data Values - 1 timePeriodID 1001 timePeriodName Example timePeriodDescription Demonstrate hierarchical levels of time intervals authority MTA Long Island Bus effectiveDateBegin 20100101 effectiveDateEnd 20101231 Time Dimension Data Values - 1 Data Values - 2 Data Values - 3 Data Values – 4 timeDimID 1 2 3 4 timePeriodID 1001 1001 1001 1001 timeDimName Daily period and day type for example interval for example Monthly interval for example Quarterly interval for example timePeriodType recurring recurring recurring recurring customTimeInterval biw mnth qtr dayType weekday periodID 1 Period Data Values - 1 periodID 1 periodName AM Peak periodDescription Morning Peak periods for inbound trips inclusive true timeBegin 18000 timeEnd 36000 dayType weekday
29: Service Supplied Summary Data Set and Summary Data Concept Requirements Planning Concept / SDP Data Routes (by direction) Route Segments (transit path) Transit Facility (stops and transfer cluster) Mode List mode by route Not applicable Transit path by definition is assigned a mode. List mode by transit path. List modes that serve transit facility, stop or transfer cluster Running Time Not applicable List raw trip information, sorted by pattern; calculate average scheduled running from origin to destination. List trips that traverse route segment and average scheduled running time from route segment origin to destination Not applicable Headway (service and See Trips Service Headway List raw trip information Effective Headway List and order raw Effective Headway List and order trip
effective) / Frequency for each sorted by timeStart and pattern; calculate the average of the difference in time between one trip and the next; calculate the number of trips that are included in calculation (for Frequency). trip information for all the routes that traverse the route segment, and calculate service headway and then effective headway. information for all the routes that stop to board and alight passengers at that facility, and calculate service headway and then effective headway. Service type See Trips List service type by raw trip information for each route sorted by pattern, e.g. List service type by all trips for all the routes that traverse the route segment. List service information by all for all routes that stop to board and alight passengers
local or express. at that facility. Span of service See The timeBegin of the first trip to the timeEnd of the last trip in a Schedule Day. Maximum number of hours is 24. The timeBegin of the first trip to enter the route segment, and the timeEnd of the last trip to exit the route segment in a Schedule Day. Maximum number of hours is 24. The tripTimes of the and last trips to provide service to the transit facility in a Schedule Day. Maximum number of hours is 24. Capacity See Trips The total vehicle capacity (as defined by PTV_Type) for each Trip for a route (by direction The total vehicle capacity (as defined by PTV_Type) for trips for all routes that traverse The total vehicle capacity (as defined by PTV_Type) for trips for all routes that stop at
and sorted by pattern). the route segment. the transit facility. The platform or pad capacity for transit Transfers Not applicable A list of the raw data that describes Event Connection elements for specified trips. Not applicable A list of the raw data that describes Event Connection elements for specified transfers that occur at specified transit facilities (facility, stop, transfer cluster). This data also includes linear distance
between transfers. [Note: the parking facility data concept supports linear distance and passenger access components between the parking and transit facility.] Planned exceptions (temporary revisions to the schedule) List of all the temporary revisions to an original schedule as submitted to the SDP. For each temporary revision, the activation Not applicable Not applicable Not applicable
30: Data Description for Service Supply Data Sets Planning Concept / SDP Data Routes (by direction) Trips Route Segments (transit path) Transit Facility (stops and transfer cluster) Mode Data Set see Mode Data Set See Mode Data Set See Mode Data Set Running Time Data Set See Pattern Running Time See Corridor Running Time Headway Data Set for service and effective headways, and frequency See Service Headway And Frequency See Effective Headway See Effective Headway Service type Data Set See Service Type Data Set See Service Type Data Set See Service Type Data Set Span of service Data Set See Span of Service Data Set See Span of Service Data Set See Span of Service Data Set Capacity Data Set See Capacity Data Set See Capacity Data Set See Capacity Data Set Transfer Service Data Set See Transfer Service Data Set See Transfer Service Data Set Planned Exception Data Set See Planned Exception Data Set Mode Data Set Description The mode data set contains information on the mode of different routes that apply to the SDP domain elements (route, trip, corridor, or transit facility). The planning data set package contains the detailed
included more than once in the stopping pattern); Mandatory nextTripTime For each Trip use timeEnd element. From the related tripTimeList (in Trip), the tripTime that matches the nextLocation (and firstLocation if nextLocation is used more than once in the stopping pattern). 24720, 24300
Alightings The quantity of passengers exiting a transit vehicle in revenue service. Also called “offs” or “departed.” Passenger Load The quantity of transit patrons carried at a given time by a specified means such as a transit vehicle in revenue service. National Transit Database Definitions According to the NTD, “service consumed is “[t]he amount of service actually used by passengers and which is measured by unlinked passenger trips and passenger miles.” [4, S-10] 42: Service Consumed Related NTD Performance Measures Performance Measure NTD Definition [4, NTD Glossary] Passenger Miles Traveled (PMT) The cumulative sum of the distances ridden by each passenger. Unlinked Passenger Trips (UPT) The number of passengers who board public transportation vehicles. Passengers are counted each time they board vehicles no matter how many vehicles they use to travel from their origin to their destination. Average Trip Length The average distance ridden for an unlinked passenger trip (UPT) by time period (weekday, Saturday, Sunday) computed as passenger miles (PM) divided by unlinked passenger trips (UPT). NYMTC Best Practices Model Service Consumed Parameters The major service consumed measures needed by the NYMTC Best Practices Model (BPM) is defined by “capacity,” that is: “the average hourly capacity (persons/hour) for each pattern” [9, p., 15]. There are five capacity measures defined by the BPM. These are described in Table 43. Table 43: NYMTC BPM Service Consumed Measures Measure Description AM Capacity AM Peak Period Capacity (persons per hour) Mid Capacity Midday Period Capacity (persons per hour) PM Capacity PM Peak Period Capacity (persons per hour) Eve Capacity Evening Period Capacity (persons per hour) Night Capacity Night Period Capacity (persons per hour) Service Consumed Data Concept Requirements The service consumed data includes operational data for passenger counts (boarding/alighting) at each stop, by route segment and by trip as reported by each transit provider. Summary data sets are
technology testing data may be based on raw counts collected by automated or human collection procedures, or it may be corrected for bias and error. Different transit operators apply different types of correction procedures or criteria to accepting their automated technologies. They use different acceptance testing and periodic screening tests to measure its accuracy. Sometimes a scaling factor may be associated with correcting the load (cumulative ons) due to the counting technology. To this end, the scaling factor may be derived based on the technology and screening tests. 6 Load Constraints A load must be zero or greater. A load cannot be negative. 7 Through Load – for Loops and Interlining configurations that do not require all passengers to alight the vehicle at a trip terminus, such as a loop or interlining service should count the continuing passengers as a “through load.” In addition, for where only a few route segments are selected, the load prior to each stop’s boardings and
and / or restrict access by individuals with disabilities, including individuals who use wheelchairs. ADA Accessible Vehicles with Lifts Public transportation revenue vehicles, which do not restrict access, are usable, and provide allocated space and / or priority seating for individuals who use wheelchairs, and which are accessible using lifts. Refer to 49 CFR Part 38. Reporting manual reference: A-30, ADA Accessible Vehicles with Ramps/Low Floor Public transportation revenue vehicles, which do not restrict access, are usable, and provide allocated space and / or priority seating for individuals who use wheelchairs, and which are accessible using ramps. Refer to 49 CFR Part 38. Reporting manual reference: A-30, Common Wheelchair Those that do not exceed 30 inches in width by 48 inches in length measured 2 inches above the ground and not weighing (ADA 49 C.F.R. § 37.3). Common wheelchairs can include scooters.
Accessibility Requirements by Mode (vehicle type) The key objective of accessibility onboard a transit vehicle is for individuals with mobility limitations to board and alight a transit vehicle (with assistance if necessary) and to ride securely. This requires a ramp, bridge or lift between the transit vehicle and transit stop (platform or pad) for persons with mobility aids (e.g., wheelchair). For non-wheelchair bound persons, assistance may include railings or clearly marked, priority seating. For persons in wheelchairs, this may include a clearly marked location for situating themselves while riding. Based on Part 38 ADA Accessibility specifications for transportation vehicles (from 49 CFR Subtitle A Edition, pp., 502-539), requirements for different modes are listed in Table 51. The details of each requirement may be found in Part 38 as referenced by the paragraph number in the column (header called: Para). Although requirements are common across modes, sometimes they vary due to the vehicle configuration. A transit agency shall designate its fleet or vehicle (or vehicles that service a route) as “accessible” if these criteria are met. With respect to this data specification, accessibility related to the vehicle indicates that the requirements described in Part 38 and related regulations are met. The SDP data model assigns accessibility to route. Each route element includes a code that describes the ADA compliance with respect to mobility, visual and auditory access (see Section Most transit agencies also distinguish the type of ingress/egress equipment on board the vehicle, e.g., ramp (and low floor buses), lift, and platform bridge.
51: Part 38 ADA Accessibility specifications for transportation vehicle Para Buses, vans, systems Para Rapid Rail Vehicles Para LRT Systems Para Commuter Rail Cars and Systems Para Intercity rail cars and systems Para Over the road Buses and other modes General General General 38.91 General General General Mobility aid accessibility (a) General (b) Vehicle lift (c) Vehicle ramp (d) Securement devices Mobility aid accessibility General Vehicle lift Vehicle ramp or bridge 38.95 Mobility aid accessibility General Car lift Car ramp or bridge plate Mobility and seating location Mobility aid accessibility General Car lift Car ramp or bridge plate Seating Mobility aid accessibility (a) General (b) Vehicle lift (c) Vehicle ramp (d) Securement devices Doors, steps and thresholds Slip Door height Doorways width Signage Signals with boarding platform Doorways width Signage Signals with boarding platform 38.93 Doorways Clear width Signals with boarding platform Signage Doorways width Signals with boarding platform Signage Doors, steps and thresholds Priority seating Priority Seating Priority seating Priority seating Sleeping compartment Interior circulation, handrails and stanchions Interior circulation, handrails and stanchions Interior circulation, handrails and stanchions 38.97 Interior circulation, handrails and stanchions Interior circulation, handrails and stanchions Interior circulation, handrails and stanchions
Table 55: Summary of Levels and Testing Criteria (adapted from 2, Table 73) Level & Level Name Testing Areas Test Result Next Step Level 1: Registration-ready Syntactic Integrity Check correct syntax, values valid, and file complete. Checks described in [Reference 2, Section 6.1]. Ready to be registered and ready for logical consistency checks. In some cases, the files are now ready to be assembled into a complete set of [PDP result set] data User may register file; File is available to progress to Level 2 testing. Level 2: Semantic integrity and logical consistency Check logical consistency as described in [Reference 2, Section 6.2 and related checks listed below]. SDP documents are internally consistent and valid. The schedule data is ready to be used and included in the [TSIP]… as Level 2 qualified. Revised [PDP] document is to be shared with requesters (consumers) 3: Regional consistency Check [PDP] Level 2 documents against regional data policies and conventions. Ready to use in regional applications. Revised [PDP] document is ready to be used in a regional application that requires regional information consistency. Note: changes to [Reference 2, Table 73] are included in brackets. Transit Network Data Set Checks <<insert here>> Time Period Data Set Checks <<insert here>> Service Supplied Data Set Checks <<insert here>> Service Consumed Data Checks <<insert here>> Accessibility Data Checks <<insert here>> Identifiers <<insert here>>