Transcript Planning Data Requirements and Profile

Planning RSTWG Meeting
May 24 10-12:30 pm

Document Organization

Planning Data Concepts

Cross Cutting Concepts

Validity checking, metadata, conformance and
more
◦ Typology
◦ Outline
◦ Difference between Data Concepts & Data Summaries
◦
◦
◦
◦
Service Supplied
Service Consumed
Accessibility
Comparison
◦ Transit Network
◦ Time Period
PDP Data Requirements
Document
1st Draft
Published: April 30 (5 May) 2010
Introduction
Planning and Data Overview
Cross-cutting Selection Concepts
1.
2.
3.
◦ Transit Network: Query by geographic units
◦ Time Period: Query by temporal units
Detailed Planning Data Concepts
4.
◦
◦
◦
◦
Service Supplied
Service Consumed
Accessibility
Dataset Comparison
5.
6.
7.
Validity Checking
Metadata
Conformance
◦ Schema, versioning, naming conventions, integration
with other TSIP Data Profiles

Appendices
a.
b.
c.
d.
e.
f.
g.
Data Dictionary (glossary and acronym list)
References / Resources
Parking Facility Data Model
Transit Vehicle Extensions
Accessibility Extensions
NYMTC PDP “profile”
List of Data Sets
Summary Data Set is the
output (Result Set) of a
query. The Query is
included in the Result Set
PDP
Result Set
Spatial Dimension
Query/Transit Network
(Section 3.1)
Temporal Dimension
Query (Section 3.2)
Planning Data Set
(Section 4)





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)
How the query for location
works…
When you know the
features you are
looking for, you can
enter query here.
Query for Spatial Dimension
Query or select Transit Feature
Use Transit Features for Query
to find Service Information
0-dimensional map
feature
0-D Transit Features
Transit Network Dataset
1-dimensional map
feature
1-D Transit Features
2-dimensional map
feature
2-D Transit Features
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)
Planned service information
includes schedule, route and
schedule calendar
information.


..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)

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)

(1) Service Type
◦ Add to Trip
element.

(2) Public Transit
Vehicle (PTV) -Rail and Bus
◦ to support vehicle
capacity measure.
Query for /
Transit
Network
Mode
Routes (by
direction)
Trips
Route
Segments
(transit path)
Transit Facility
(stops and
clusters)
Mode DS
--
Mode DS
Mode DS
Running
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 DS
Span of
Service
--
SOS DS
SOS DS
SOS DS
Capacity
--
Cap DS
Cap DS
Cap DS
Transfers
--
Trip Transfer
DS
--
Facility
Transfer DS
SDP (for
Exceptions)
--
--
--
Planned
Exceptions

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

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.

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.
Avg Run Time
See Avg Running
Time Equation
Number (“n”)
Running Time
Dataset
Count (number
of paths)
segmentID
pathList
agencyID
firstLocation
routeID
nextLocation
segmentID indicates either
a patternID or tranPathID
routeDirection
pathRunTimeList
tripID
firstTripTime
nextTripTime
Service
Headway
Dataset
Avg
Service
Headway
[min]
routeID
routeDirec
tion
patternID
(opt)
locationID
(Common
TripTime)
numberTri
ps
TripList
Trip (with
tripTimeLi
st)



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.

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
Effective
Headway
dataset
Effective
Headway [min]
Number (“n”
service headway
records)
Service Headway
list [1..n]
Frequency
Dataset
Veh per time
period
Trip list
Trip (without
tripTimeList)

tripID
count
routeID
Trip List
routeDirection
Service Type
Dataset
agencyID (opt)

serviceType
Service type examples:
◦ Regular
◦ Express
◦ Limited
◦ Circular
◦ Jitney
Should BRT be
Mode or
ServiceType?

Duration of service for an agency, along
a corridor, on a particular route, or at a
transit facility
serviceSpan
[min]
Span DS
firstTrip
Trip Defn
lastTrip
Trip Defn
Example: serviceSpan = 5:58 pm to 10:32 am = 990 min


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
Needed to augment the
Transit Vehicle Definition to
support vehicle capacity
measures including rail cars
in each consist.
Sum Total Cap
Trip List
tripID
Sum Seating Cap
Capacity
Dataset
Sum Standing Cap
routeID
patternID
agencyID (opt)
Sum Wc Cap
Trip Count
carCount (opt)
Total Cap
Seating cap
Trip List
Standing cap
Wc cap

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]
SDP
Sched Version
Agency
Registration
Service
Transit Network
Agency
Trip (trip time)
Route (route
directions)
Event Connection
(trip transfers)
Pattern (transit pt
events)
Transit Gazetteer
Location
Facilities (plant
components)
Timepoint
Transit Stop
(platform)
Transfer Cluster
(locations)
Schedule Revision
Abridged Version
Transit Facility
Portal, Amenities,
etc.
Trip Transfer
DS
Trip Transfer
Count
Event
Connection List
Agency Data
[1..n]
Transfer
Cluster List
agencyID
Trip List
Location List
Facilities
Transfer DS
Facility
Transfer Count
Transfer
Cluster List
Master
Location List
Agency Data
[1..n]
agencyID
Location List
Facilities List

Planned Exception
data set includes
revisions to an
original schedule.
Schedule
version ID

Request
scheduleVersionID
◦ Example LI Bus:
210, 110, 409, 309,
209
PE DS
count
Sched List
Activation
date
Deactivation
date
Exceptions
Schedule
Revision


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)

Passenger Load and Ridership

thruCount*

wcOnCount, wcOffCount and
wcThruCount
◦ Calculated from CountList Structure
Boardings (onCount) and Alightings
(offCount).
◦ Used to capture the number of
passengers who stay on an interlining
vehicle.
◦ 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.
* “thru” count idea from TCRP Report
113: Using Archived AVL-APC Data…
date
tripID
routeID
Passenger Count
tripTime
locationID
onCount
dayType
offCount
scheduleVersionID
thruCount
Passenger Count
wcOnCount
PC List
scaleFactor
metadata
wcThruCount
cumulativeOn
cumulativeOff
 Algorithms for average alightings, wheel chair
boardings, and alightings are similarly calculated by
substituting offCount, wcOnCount, and wcOffCount
for onCount.
pcCount
locationID
Public Loc
Desc
Avg
Ridership
Avg
Boardings
Avg
Alightings
Avg WC
Boardings
Avg WC
Alightings
Passenger
Count List
Passenger
Count
 Average Load Calculation for Multiple Trips
 Average Load Calculation for Multiple Route Segments in a Corridor
PC Count
(=n)
Avg Load
Data Set
Load is calculated
differently for
Routes (trips) vs.
Corridors (route
segments)
Avg Load
Passenger
Count [1]
Passenger
Count List
Passenger
Count [i]
Passenger
Count [n]
Stops /
Trip*
1
[b / a]
cum [on/off]
2
3
Average Load by
Route Seg
Stop (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.3
Avg Trip Load
17.7
* Trips are of the same Route and Pattern


“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
…

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)


Added connectionType
to Connection
Segment.
Values include:
◦
◦
◦
◦
◦
fullMobility
partMobility
fullAccessibility
partAccessible
notAccessible
partMobility: “may include
curbs, escalators, and other
small obstructions..”
partAccessible: “may not
include announcements
and signs..”


Designates Amenity
(shelter, bench,
TVM) as “accessenabled” through
adaCompliance.
Add
PAC_Characteristics
with attributes
associated with one
or more PACs.


Added adaCompliance & accessEquipment
Added AccessibilityStatus (description of
accessibility for each rail car, bus and
other PTV)


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)


Use T-Best
Need SDP data which includes:
◦
◦
◦
◦
◦
Transit Stops
Transit Facilities
Amenities, (Portals, Passenger Access Components)
(Transfer Cluster and Connection Segments)
(Transit Path)