1 / 21

What is iTSIP ?

What is iTSIP ?. Integrated TSIP Data Set Exchange Profile. Regional Data Sets. From TSDEA Functional Requirements Document [2006] What needs to be added to meet regional integration requirements? Spatial Location Connection Seg Code Lists OperatorID (in RTDP AgencyList )

shona
Download Presentation

What is iTSIP ?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. What is iTSIP? Integrated TSIP Data Set Exchange Profile

  2. Regional Data Sets From TSDEA Functional Requirements Document [2006] What needs to be added to meet regional integration requirements? Spatial Location Connection Seg Code Lists OperatorID (in RTDP AgencyList) Feature Type (in PDP) Regional Transit Facilities List (rename from Transit Stop Inventory) All nested elements Add Parking Facilities (PDP) Event Connection Location Parking

  3. iTSIP Scope

  4. Agency List Use format from Real Time Data profile (RTDP)

  5. AgencyList Use format from Real Time Data Profile (RTDP)

  6. <?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> Example AgencyListResultSet

  7. Regional Location and Facility Create a shared Facility List and associated Location Table

  8. Transit Facility – Location Relationship isGeneralized = “true” generalizedLocation = locationID isPartOf= “true” partOfFacID= transitFacilityID Transit Facility Location 1:1 Plant Component

  9. Location Table in SDP A unique set of all locations

  10. SDP Transit Facility ModelFor a single agency

  11. Regional Transit Facility isGeneralized = “true” generalizedLocation = locationID isPartOf= “true” partOfFacID= transitFacilityID 1:1 Regional Transit Facility Regional Location Plant Component Parking Facility SDP Transit Facility, Portal, Transit Stop, Passenger Access Component, Amenity

  12. iTSIP Regional Facilities Model

  13. Parking Facility Model

  14. Migrating Location element to Support Multiple Agencies Segment each SDP by agency and schedule version Create regional location table for shared / regional transit facilities entity Link regional locations through an association table (in TSIP)

  15. Modeling TSIP Location for Multiple Agencies Regional Association Table regional_ID, agencyID, locationID [R5000, 101, 232084] [R5000, 200, 891] [R5000, 400, 15] <sdp> Agency 101 locationID = 232084 <sdp> Agency 200 locationID = 891 locationID = R5000 Jamaica Station isGeneralized = “true” generalizedLocation = R5000 <sdp> Agency 400 locationID = 15

  16. Regional Event Connections Event Connection And Transfer Cluster / Connection Segment

  17. Event Connection Currently set up to add constraint related from and to agency. Add: fromAgency toAgency Related to Facilities/Location Model

  18. Transfer Cluster and Connection Segment Use Location from Regional Location table: clusterLocations connectionList fromStop, toStop locationID

  19. Regional Transfers Connection Segments And Fare Transfers

  20. 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)

  21. Transfer Data Model Includes 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

More Related