INTEGRATED TSIP DATA SET EXCHANGE PROFILE

What is iTSIP?

Regional Data SetsFrom TSDEA Functional Requirements Document [2006]

What needs to be added to meet regional integration requirements?Spatial

LocationConnection Seg

Code Lists

OperatorID (in RTDP AgencyList)

Feature Type (in PDP)

Regional Transit Facilities List (rename from Transit Stop Inventory)

All nested elementsAdd Parking Facilities (PDP)

Key

TSDEA

Operator Registration Spatial Code Lists/

ConventionsTransit Stop

Inventory

Map Patches

Landmarks

Place Names

Connection Seg

OperatorID

StopType

FeatureType

TSDEA Demo

Transit Facilities

Coordinated Transfer

Transfer Cluster

Portals

Amenities

Agency registration

Consistency Checks

Address Conventions

Other NYSDOT

TBD

Quality Checks

Version Control

SDP

This architecture describes the persistent data sets needed in the TSDEA portal to ensure regional consistency.

Pass. AccessComp

Location

Event Connecti

on

Parking

iTSIP Scope

iTSIP

AgencyList (RTDP)

RegionalTransitFacList (iTSIP)•Including Parking Facilities•(as cited in RTDP)

RegionalEventConnection (iTSIP)

RegionalTransfers (iTSIP)•Including Transfer Clusters and Connection Segments•Including Fare Collection

Regional Locations (iTSIP)

USE FORMAT FROM REAL TIME DATA PROFILE (RTDP)

Agency List

AgencyList

Use format from Real Time Data Profile (RTDP)

ExampleAgencyListResultSet

<?xml version="1.0" encoding="UTF-8"?><n1:AgencyListResultSet …. [header info] s-time="2001-12-

17T09:30:47.0Z" rtdpVersion="002"><AgencyList>

<agencyName>MTA New York City - Subway</agencyName>

<agencyAcronym>NYCT</agencyAcronym><agencyID>100</agencyID>

</AgencyList><AgencyList>

<agencyName>MTA New York City Transit-Bus</agencyName>

<agencyAcronym>NYCT</agencyAcronym><agencyID>101</agencyID>

</AgencyList><AgencyList>

<agencyName>MTA Long Island Bus</agencyName><agencyAcronym>LIB</agencyAcronym><agencyID>200</agencyID>

</AgencyList><AgencyList>

<agencyName>MTA Long Island Rail Road</agencyName>

<agencyAcronym>LIRR</agencyAcronym><agencyID>500</agencyID>

</AgencyList></n1:AgencyListResultSet>

CREATE A SHARED FACILITY LIST AND ASSOCIATED LOCATION TABLE

Regional Location and Facility

Transit Facility – Location Relationship

Transit Facility

Plant Componen

t

Location

isGeneralized = “true”generalizedLocation = locationID

isPartOf= “true”partOfFacID= transitFacilityID

1:1

Location Table in SDPA unique set of all locations

SDP Transit Facility ModelFor a single agency

Regional Transit Facility

Regional Transit Facility

Plant Componen

t

Regional Location

isGeneralized = “true”generalizedLocation = locationID

isPartOf= “true”partOfFacID= transitFacilityID

1:1

SDP Transit Facility, Portal, Transit

Stop, Passenger Access Component, Amenity

Parking Facility

iTSIP Regional Facilities Model

Parking Facility Model

Migrating Location element to Support Multiple Agencies

1. Segment each SDP by agency and schedule version

2. Create regional location table for shared / regional transit facilities entity

3. Link regional locations through an association table (in TSIP)

Modeling TSIP Location for Multiple Agencies

<sdp>Agency 101

<sdp>Agency 200

<sdp>Agency 400

locationID = R5000Jamaica Station

locationID = 232084

locationID = 891

locationID = 15

Regional Association Tableregional_ID, agencyID,

locationID[R5000, 101, 232084]

[R5000, 200, 891][R5000, 400, 15]

isGeneralized = “true”generalizedLocation = R5000

EVENT CONNECTIONAND

TRANSFER CLUSTER / CONNECTION SEGMENT

Regional Event Connections

Event ConnectionCurrently set up to add constraint related from and to agency. Add:

fromAgency

toAgency

Related to Facilities/Locati

on Model

Transfer Cluster and Connection SegmentUse Location from Regional Location table:

•clusterLocations

•connectionList• fromStop, toStop

•locationID

CONNECTION SEGMENTSAND

FARE TRANSFERS

Regional Transfers

What is a Transfer?

A patron’s movement from one transit vehicle to another to get from an origin to destination

A TRANSFER_RULE describes rules for transferring from one service (LEG) to another (LEG).  The transfer rule may be associated with the service (TRIP to TRIP, ROUTE to ROUTE, SERVICE TYPE to SERVICE TYPE, MODE to MODE, AGENCY to AGENCY), location (TRANSFER CLUSTER, TRANSIT FACILITY) of transfer, fare media used, additional fare characteristics (e.g., charging method).

  Rules for Transfer fall into one or more of these categories:

Origin and/or destination of trip plan (includes legs traveled and direction of travel) Transfer location Specific trip transfers (at event connection) Media product used From service type (and/or mode) to service type (and/or mode)

Transfer Data ModelIncludes Rules for:

Origin and/or destination of trip plan (includes legs traveled and direction of travel)

Transfer location

Specific trip transfers (at event connection) – including time duration bet. transfers

Media product used

From service type /mode to service type /mode