GTFS RT LIRR and MNR feed access

583 views
Skip to first unread message

John Larsen

unread,
Feb 7, 2015, 4:02:17 PM2/7/15
to mtadevelop...@googlegroups.com
As part of the AppQuest 3.0, it was posted how to use and how to get access to the feeds.

Here is it on a separate thread for your convenience

In order to get access to the LIRR and MNR feeds, please shoot me a direct message or email lars...@gmail.com with your MTA API Key and I will get your key processed to access the feed.

PLEASE DO NOT POST YOUR KEY ON THIS OPEN FORUM!!!


Long Island Rail Road GTFS RT feed information

Endpoints

There are three endpoints provided

1.       The Protocol Buffer feed is at

https://mnorth.prod.acquia-sites.com/wse/LIRR/gtfsrt/realtime/[PutAPIKeyHere]/proto

2.       The JSON data feed is at

https://mnorth.prod.acquia-sites.com/wse/LIRR/gtfsrt/realtime/[PutAPIKeyHere]/json

3.       The XML data feed

https://mnorth.prod.acquia-sites.com/wse/LIRR/gtfsrt/realtime/[PutAPIKeyHere]/xml

Dataset

All of the datasets conform to the GTFS RT specification located at

https://developers.google.com/transit/gtfs-realtime/

This feed implements Trip Update.

Use the TripUpdate.TripDescriptor.Id to match the GTFS schedule Trip.trip_id to join to the schedule information.

Metro-North Railroad GTFS RT feed information

Endpoints

There are three endpoints provide

The endpoint address is the same for all of the feeds. It is at

https://mnorth.prod.acquia-sites.com/wse/gtfsrtwebapi/v1/gtfsrt/[PutAPIKeyHere]/getfeed

To access the protocol buffer feed, add an http header GET request

Accept:  application/x-protobuf

To access the JSON feed, add an http header to the GET request

                Accept: application/json

To access the XML feed, add an http header to the GET request

                Accept: application/xml

Dataset

All of the datasets conform to the GTFS RT specification located at

https://developers.google.com/transit/gtfs-realtime/

This feed implements the Trip Updates portion of the specification.

Within the TripUpdate.VehicleDescriptor, the label refers to the train number represented in the GTFS schedule Trip.trip_short_name. This is how you would link the train status from the GTFS RT to the GTFS schedule.

Alex Perlyuk

unread,
Nov 19, 2015, 5:06:35 PM11/19/15
to mtadeveloperresources
In the current Metro North GTFS-RT feed, there are IDs in the TripUpdate.VehicleDescriptor label that do not match with any GTFS schedule Trip.trip_short_name

ID I am encountering is TripUpdate.VehicleDescriptor.label=137

Could you please clarify how to get trip info for this scenario?

thanks.

Alex Perlyuk

unread,
Nov 19, 2015, 5:12:39 PM11/19/15
to mtadeveloperresources
It also includes a route ID 17 that is not in the DB

Here's the payload for that node:
{"id":"137","trip_update":{"trip":{"start_time":"1658","start_date":"11192015","schedule_relationship":0,"route_id":"17"},"vehicle":{"label":"137"},"stop_time_update":[{"departure":{"delay":480,"time":1447970280},"stop_id":"124"},{"departure":{"delay":480,"time":1447971540},"stop_id":"108"},{"departure":{"delay":480,"time":1447975560},"stop_id":"15001"},{"departure":{"delay":480,"time":1447976460},"stop_id":"17016"},{"departure":{"delay":480,"time":1447977540},"stop_id":"17015"},{"departure":{"delay":480,"time":1447978800},"stop_id":"17012"},{"departure":{"delay":480,"time":1447980420},"stop_id":"17010"},{"departure":{"delay":480,"time":1447981800},"stop_id":"17009"},{"departure":{"delay":480,"time":1447984500},"stop_id":"17006"},{"departure":{"delay":480,"time":1447985220},"stop_id":"17005"},{"departure":{"delay":480,"time":1447986120},"stop_id":"17004"},{"departure":{"delay":480,"time":1447987200},"stop_id":"17003"}]}}

John L

unread,
Nov 19, 2015, 5:50:04 PM11/19/15
to mtadeveloperresources

That is an Amtrak train that does not belong there so I would ignore it.

Thanks for pointing it out!


--
You received this message because you are subscribed to the Google Groups "mtadeveloperresources" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mtadeveloperreso...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Burag Cetinkaya

unread,
Jul 27, 2019, 4:24:00 PM7/27/19
to mtadeveloperresources
The API url above with my key seems to consistently return an access denied message. Did the URL structure change? 


To unsubscribe from this group and stop receiving emails from it, send an email to mtadeveloperresources+unsub...@googlegroups.com.

Michael Dannenbring

unread,
Jul 28, 2019, 10:42:59 PM7/28/19
to mtadevelop...@googlegroups.com
Email me michael.d...@mtahq.org with your API key and I will double check to make sure you are setup with the proper access.

To unsubscribe from this group and stop receiving emails from it, send an email to mtadeveloperreso...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "mtadeveloperresources" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mtadeveloperreso...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mtadeveloperresources/21e83c9c-16db-494d-8eda-e16e4b28d117%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages