Planning Data Requirements and Profile
description
Transcript of Planning Data Requirements and Profile
![Page 1: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/1.jpg)
Planning Data Requirements and Profile
Planning RSTWG MeetingMay 24 10-12:30 pm
![Page 2: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/2.jpg)
Document Organization◦ Typology◦ Outline◦ Difference between Data Concepts & Data Summaries
Planning Data Concepts◦ Service Supplied◦ Service Consumed◦ Accessibility◦ Comparison
Cross Cutting Concepts◦ Transit Network◦ Time Period
Validity checking, metadata, conformance and more
Planning RSTWG Topics
![Page 3: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/3.jpg)
Document OrganizationPDP Data Requirements Document1st DraftPublished: April 30 (5 May) 2010
![Page 4: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/4.jpg)
1. Introduction2. Planning and Data Overview3. Cross-cutting Selection Concepts
◦ Transit Network: Query by geographic units ◦ Time Period: Query by temporal units
4. Detailed Planning Data Concepts◦ Service Supplied◦ Service Consumed◦ Accessibility◦ Dataset Comparison
PDP Requirements Document
![Page 5: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/5.jpg)
5. Validity Checking6. Metadata7. Conformance
◦ Schema, versioning, naming conventions, integration with other TSIP Data Profiles
Appendicesa. Data Dictionary (glossary and acronym list)b. References / Resourcesc. Parking Facility Data Modeld. Transit Vehicle Extensionse. Accessibility Extensionsf. NYMTC PDP “profile”g. List of Data Sets
PDP Requirements Document, cont.
![Page 6: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/6.jpg)
PDP Result Set
Spatial Dimension Query/Transit Network
(Section 3.1)
Temporal Dimension Query (Section 3.2)
Planning Data Set (Section 4)
Summary Data Set FormatSummary Data Set is the output (Result Set) of a query. The Query is included in the Result Set
![Page 7: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/7.jpg)
Service Supplied (Section 4.1) Service Consumed (Section 4.2) Accessibility (Section 4.3) Level of Service (TBD) Fares (part of Fare Collection Data
Requirements)
Service Information Categories
![Page 8: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/8.jpg)
Transit NetworkHow the query for location works…
![Page 9: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/9.jpg)
Query for Spatial Dimension
0-dimensional map feature
1-dimensional map feature
2-dimensional map feature
Query or select Transit Feature
0-D Transit Features
1-D Transit Features
2-D Transit Features
Use Transit Features for Query to find Service Information
Transit Network Dataset
Querying for Transit NetworkWhen you know the
features you are looking for, you can enter query here.
![Page 10: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/10.jpg)
Transit Features (in SDP) by Dimension
0-dimension (point) 1-dimension (polyline) 2-dimension (polygon)Location (key = locationID) TransitPath (key =
tranPathID)PolygonType (keys = locationID, polygonID)
Transit Facility [Amenity, Depot, Portal, PassengerAccessComponent, TransitStop, Transit Facility]
Transit Gazetteer [Timepoint, TransferCluster, ConnectionSegment]
add ParkingFacility add Transit Vehicle PTV
Location is referenced by the following transit service elements: Block (begin and end points) and
BlockTimes Trip (begin and end points) and
TripTimes Pattern and EventList
(transitPointEvent) Transfer Event (guaranteed) and
EventConnections
Block (blockPathEvent) Pattern (transitPathEvent) Track
Depot (includes text for ServiceArea description)
Location (geometry) (add ServiceArea)
![Page 11: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/11.jpg)
Service SuppliedPlanned service information includes schedule, route and schedule calendar information.
![Page 12: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/12.jpg)
Service Supplied ..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)
![Page 13: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/13.jpg)
Key Summary Data Sets:◦ Mode◦ Average Running Time (scheduled)◦ Headway / Frequency◦ Service Type◦ Span of Service◦ Capacity (vehicle and infrastructure)◦ Transfer Opportunities (coordinated service)◦ Planned Exceptions (revisions to original
schedule)
Create Data Sets to Calculate Planning Measures from Schedules
![Page 14: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/14.jpg)
(1) Service Type◦ Add to Trip
element.
(2) Public Transit Vehicle (PTV) -- Rail and Bus◦ to support vehicle
capacity measure.
Additional SDP Data Concepts
![Page 15: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/15.jpg)
Query for / Transit Network
Routes (by direction)
Trips Route Segments (transit path)
Transit Facility (stops and clusters)
Mode Mode DS -- Mode DS Mode DSRunning Time
-- Pattern Run Time DS
Corridor Run Time DS
--
Headway / Frequency
-- Service Hdwy
Frequency
Effective Hdwy DS
Effective Hdwy DS
Service Type -- Ser Type DS Ser Type DS Ser Type DSSpan of Service
-- SOS DS SOS DS SOS DS
Capacity -- Cap DS Cap DS Cap DSTransfers -- Trip Transfer
DS-- Facility
Transfer DSPlanned Exceptions
SDP (for Exceptions)
-- -- --
Service Supplied Data Set and Summary Concepts
![Page 16: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/16.jpg)
From SDP (derived from NTD), for example:
◦ CR = commuter rail◦ FB = ferry boat◦ HR = heavy rail or
subway◦ MB = bus (motor
bus)◦ CO = coach bus
(e.g., commuter bus)
Mode dataset
Count Route mode list
routeID mode agencyID
Result Set -- Mode for Route, Trips, Transit Facilities
![Page 17: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/17.jpg)
Average Running Time◦ The duration (in seconds) needed for a public
transportation vehicle in revenue service to travel between a known location to another over the same path. For example, for one or more trips (over the same path), the running time is the average time it takes to travel between each trip’s locationBegin to locationEnd, or between one TripTime to another.
Service Type [serviceType]◦ A classification for the level of service provided by a trip.◦ Regular, express, circular, jitney, limited, etc.
Running Time Data Concepts
![Page 18: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/18.jpg)
Average Running Time
Where “t” indicates the time in seconds at the starting and ending locations (origin and destination, respectively) and “n” indicates the number of trips included in the calculation.
![Page 19: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/19.jpg)
Result Set -- for Running Time on Trips (Pattern) or Route Segment
Running Time Dataset
Count (number of paths)
pathList
Avg Run Time
Number (“n”)
segmentID
firstLocation
nextLocation
pathRunTimeList
agencyID
routeID
routeDirection
tripID
firstTripTime
nextTripTime
segmentID indicates either a patternID or tranPathID
See Avg Running Time Equation
![Page 20: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/20.jpg)
Service Headway
![Page 21: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/21.jpg)
Result Set -- for Service Headway for Routes and Trips
Service Headway Dataset
Avg Service
Headway [min]
routeID routeDirection
patternID (opt)
locationID (Common TripTime)
numberTrips TripList
Trip (with tripTimeLi
st)
![Page 22: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/22.jpg)
Effective Headway Effective Headway: Composite headway of all bus, rail or other mode
service at a stop or in a corridor based on vehicle frequency, the number of vehicles per hour divided by 60 minutes.
In other words, the effective headway is the number of minutes between transit vehicles when all headways are combined. Effective Headway is typically calculated by an individual mode along a route, but a combination of modes may be used at a key stop.
Where “SH” refers to the service headway and “n” refers to the number of service headways that are included in the calculation for the effective headway.
![Page 23: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/23.jpg)
Effective Headway Example Example #1: two routes operating on a segment of roadway (or
track) each with ten minute headways, the effective headway is five minutes.
Effective headway = 60 / (60/10 +60/10) = 5 minutes
Example #2: when calculating effective headway for the stop at E 116 Street and 3rd Avenue where service is provided by the Routes 98, 101, and 103 with service headways of 10, 7 and 5 minutes (respectively), then the effective headway would be:
Effective headway = 60 /[(60 minutes / 10 minute headway) + (60 minutes / 7 minute headway) + (60 minutes / 5 minute headway)]
= 60 minutes / 26.6 buses hour = 2.25 minutes
![Page 24: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/24.jpg)
Result Set -- for Eff. Headway for Rte Segments and Transit Facilities
Effective Headway dataset
Effective Headway [min]
Number (“n” service
headway records)
Service Headway list
[1..n]
![Page 25: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/25.jpg)
Result Set -- for Frequency for Trips
Frequency Dataset
Veh per time period Trip list
Trip (without tripTimeList)
![Page 26: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/26.jpg)
Service Type Dataset
count
Trip List
tripID
routeID
routeDirection
agencyID (opt)
serviceType
Service type examples:◦ Regular◦ Express◦ Limited◦ Circular◦ Jitney
Should BRT be Mode or ServiceType?
Result Set -- for Service Type for Trips, Rte Seg, Facilities
![Page 27: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/27.jpg)
Duration of service for an agency, along a corridor, on a particular route, or at a transit facility
Span DS
serviceSpan [min]
firstTrip Trip Defn
lastTrip Trip Defn
Result set for Request for Span of Service for Trips, Rte Seg, Facility
Example: serviceSpan = 5:58 pm to 10:32 am = 990 min
![Page 28: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/28.jpg)
Capacity is the measure of total number of passengers (that can be supplied by a transit vehicle) per hour by pattern, corridor, or through a transit passenger facility.
The Capacity Data Set is the summation of vehicle passenger capacity assigned to each trip that traverses the geographic dimension over a time period (e.g., 1 hour). The capacity data set includes capacity measures for:
◦ Total (seating+standing)◦ Seating◦ Standing◦ Wheel chair
Vehicle Passenger Capacity (supply side measure)
Needed to augment the Transit Vehicle Definition to support vehicle capacity measures including rail cars in each consist.
![Page 29: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/29.jpg)
Capacity Dataset
Sum Total Cap
Sum Seating Cap
Sum Standing Cap
Sum Wc Cap
Trip Count
Trip List
Result set for Request for Capacity for Trips, Rte Segment, Facility
Trip List
tripID
routeID
patternID
agencyID (opt)
carCount (opt)
Total Cap
Seating cap
Standing cap
Wc cap
![Page 30: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/30.jpg)
Coordination between trips within an agency Coordination between trips between two agencies
Related SDP Data Concepts◦ “Places and times when connections may be made…
These concepts differ from geographically and temporally calculated trip connections in that they are recommended transfer locations and times.” [SDP Guidance Part 2, 10-1]
◦ Event Connection [connection types include protected, recommended, scheduled]
◦ Transfer Cluster [may include Connection Segment]
Result Set for Request for Transfer Service for Trips
![Page 31: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/31.jpg)
Transfer Concepts in SDPSDP
Sched Version
Agency Registration
Agency
Route (route directions)
Schedule Revision
Service
Trip (trip time)
Event Connection (trip transfers)
Transit Network
Pattern (transit pt events)
Transit Gazetteer
Location
Timepoint
Transfer Cluster (locations)
Transit Facility
Facilities (plant components)
Transit Stop (platform)
Portal, Amenities, etc.
Abridged Version
![Page 32: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/32.jpg)
Trip Transfer DS
Trip Transfer Count
Event Connection
ListAgency Data
[1..n]
agencyID Trip List Location List
Transfer Cluster List
Result Set for Request for Transfer Service for Trips
![Page 33: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/33.jpg)
Facilities Transfer DS
Facility Transfer Count
Transfer Cluster List
Master Location List
Agency Data [1..n]
agencyID Location List Facilities List
Result Set for Request for Transfer Service for Transit Facilities
![Page 34: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/34.jpg)
Planned Exception data set includes revisions to an original schedule.
Request scheduleVersionID◦ Example LI Bus: 210,
110, 409, 309, 209
PE DS
count Sched List
Schedule version ID
Activation date
Deactivation date Exceptions
Schedule Revision
Result Set -- for Planned Exception data
![Page 35: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/35.jpg)
Service Consumed Data Concept and Data Set Requirements
![Page 36: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/36.jpg)
Service Consumed 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 (locationID)◦ Passenger Load by route segment
Key Summary Data Sets◦ Average Load◦ Average Ridership (at stop)
![Page 37: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/37.jpg)
Passenger Load and Ridership ◦ Calculated from CountList Structure
Boardings (onCount) and Alightings (offCount).
thruCount* ◦ Used to capture the number of passengers
who stay on an interlining vehicle.
wcOnCount, wcOffCount and wcThruCount ◦ Used to capture wheelchair ridership.
cumulativeOn / Off ◦ Captures the boarding and alighting from
the start of each trip.◦ A simple load may be calculated for a route
segment by the difference bet. the cumulative Ons and Offs.
Passenger Count Data Concept
* “thru” count idea from TCRP Report 113: Using Archived AVL-APC Data…
![Page 38: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/38.jpg)
PC List
date
tripID
routeID
dayType
scheduleVersionID
Passenger Count
scaleFactor
metadata
Passenger Count List Dataset Passenger Count
tripTime
locationID
onCount
offCount
thruCount
wcOnCountwcThruCountcumulativeO
ncumulativeO
ff
![Page 39: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/39.jpg)
Passenger Ridership Calculations
Algorithms for average alightings, wheel chair boardings, and alightings are similarly calculated by substituting offCount, wcOnCount, and wcOffCount for onCount.
![Page 40: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/40.jpg)
Avg Ridership
pcCount
locationID
Public Loc DescAvg
BoardingsAvg
AlightingsAvg WC
BoardingsAvg WC
AlightingsPassenger Count List
Passenger Count
Average Ridership Data Set
![Page 41: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/41.jpg)
Passenger Load Calculations
Average Load Calculation for Multiple Trips
Average Load Calculation for Multiple Route Segments in a Corridor
![Page 42: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/42.jpg)
Average Load Data Set
Avg Load Data Set
PC Count (=n)
Avg Load
Passenger Count List
Passenger Count [1]
Passenger Count [i]
Passenger Count [n]
Load is calculated differently for Routes (trips) vs. Corridors (route segments)
![Page 43: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/43.jpg)
Stops / Trip*
1 [b / a] cum [on/off]
2 3 Average Load by Route SegStop (fr-to)
Stop #1
[12 / 0] Cum [12/0]On 12
[10 / 0] Cum [10/0]On 10
[14 / 0] Cum [14/0]On 14
Stop #2
[2 / 4] Cum [14/4]On 10
[8 / 4] Cum [18/4]On 14
[2 / 5] Cum [16/5]On 11
Seg (1-2)Avg Load 12
Stop #3
[4 / 10]Cum [18/14]On 4
[1 / 10]Cum [19/14]On 5
[0 / 10]Cum [16/15]On 1
Seg (2-3)Avg Load 11.7
Stop #4
[0 / 4]Cum [18/18]
[0 / 5]Cum [19/19]
[0 / 1]Cum [16/16]
Seg (3-4)Avg Load 3.3Avg Trip Load 17.7
Average Load Example
* Trips are of the same Route and Pattern
![Page 44: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/44.jpg)
Accessibility
![Page 45: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/45.jpg)
“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.”
Refined defn for SDP – adaCompliance_cd◦ notCompliant◦ fullyCompliant◦ mobilityChallengedAccess◦ visuallyChallengedAcess◦ …
Accessibility Defn & Data Req’ts
![Page 46: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/46.jpg)
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)
Accessibility
![Page 47: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/47.jpg)
Extension to Connection Segment
partMobility: “may include curbs, escalators, and other small obstructions..”
partAccessible: “may not include announcements and signs..”
Added connectionType to Connection Segment.
Values include:◦ fullMobility◦ partMobility◦ fullAccessibility◦ partAccessible◦ notAccessible
![Page 48: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/48.jpg)
Designates Amenity (shelter, bench, TVM) as “access-enabled” through adaCompliance.
Add PAC_Characteristics with attributes associated with one or more PACs.
Extension to Amenity Passenger Access Component and Amenity
![Page 49: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/49.jpg)
Added adaCompliance & accessEquipment
Added AccessibilityStatus (description of accessibility for each rail car, bus and other PTV)
Extension to Transit Vehicle with Access Attributes
![Page 50: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/50.jpg)
Incorporate Changes and Updates Add more examples
◦ Assignments/Selection: Running Time for Trips on a Pattern Running Time for Corridor Service Headway Frequency Effective Headway for Transit Facility Service Type (need raw data…) Span of Service Transfer Service (Metro North for Trips) Planned Exceptions (need raw data…) Ridership / Load (need raw passenger count data…) Accessibility (need attribute data on vehicles, stations, connection
paths)
Next Steps
![Page 51: Planning Data Requirements and Profile](https://reader035.fdocuments.us/reader035/viewer/2022062218/56816688550346895dda3ee5/html5/thumbnails/51.jpg)
Use T-Best Need SDP data which includes:
◦ Transit Stops◦ Transit Facilities◦ Amenities, (Portals, Passenger Access
Components)◦ (Transfer Cluster and Connection Segments)◦ (Transit Path)
Planning Demonstration