Incorrect LIRR track number from gtfs-rt

[Zahidur R]

1. I have implemented gtfs-rt API for my client (Clever Commute). Here gtfs-rt shows LIRR leaving NY Penn from tracks such as 4, 5, 6, 7 or 8.
   But actually LIRR trains never leave NYP on low-numbered tracks. Rather, they use approx tracks 14-22
   Is this issue with gtfs-rt?
2. On the other hand, LIRR gtfs-rt returns no data sometimes.
   Is  gtfs-rt  still is beta version?

[Fisher, Will]

What URL are you pulling from?

 

Will

--
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/2a0c9b93-6c4c-41f8-b790-26fdaeabe6ban%40googlegroups.com.

Confidentiality Note: This e-mail, and any attachment to it, may contain privileged and confidential information and is intended for the use of the individual(s) or entity named on the e-mail. Unauthorized disclosure of this message is prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and destroy this message and all copies thereof, including all attachments.

[Zahidur R]

From this URL

https://api-endpoint.mta.info/Dataservice/mtagtfsfeeds/lirr%2Fgtfs-lirr

[Fisher, Will]

Can you try backend.mylirr.org/gtfs and see if that’s any better?

To view this discussion on the web visit https://groups.google.com/d/msgid/mtadeveloperresources/c57cf047-c2c4-429f-a64e-26872fe5847an%40googlegroups.com.

[clevercommute]

I work with OP. I am the publisher of the app using that data. 

Thanks for the efforts here. But I need MTA to provide more clarity. 

I know everyone is doing their best and trying to help. 

If you need alpha/beta testers for this "backend" API, then we can consider participating if it makes sense for all parties. 

But for now, I am looking for feedback on the bugs reported in this thread. 

1. Are both of these APIs in GA status? 
2. Are you aware of what we see as an API defect? (LIRR trains on low-number tracks)
3. How can we file bug reports so that MTA can look into this and give us traceability

Thanks, 

--Josh 

[Fisher, Will]

Hi,

 

1. Yes, both are
2. Haven’t looked because my team doesn’t work on the feed you’re currently using. The feed I gave you runs the app and has many more eyeballs on it.
3. You can report directly to me (wfi...@mtahq.org) – should work for now

 

Best,

Will

To view this discussion on the web visit https://groups.google.com/d/msgid/mtadeveloperresources/c1f0d5af-fba6-41af-aadb-923bfbdbcc78n%40googlegroups.com.

[clevercommute]

Thanks. 

I don't think app owners should be asked to refactor their code as an experiment when (as far as they know) they are using a GA prod API. 

If your team does not work on that original production feed, then how does the dev community engage the team that does? 

We think there is a bug and as an app owner, I simply look to the API provider to own and operate the API with some kind of SLA.

An honest question for you: Any feedback for me on how we got to a point where my app is using an API that appears be #2 in terms of support and monitoring? 

Was there some kind of public announcement that MTA is doing a structured migration from one to the other? 

I know you are doing your best to help, but my board and my advisors are certainly going to grill me on this, and I can see their point of view. 

[Fisher, Will]

You can email me offline to discuss.

To view this discussion on the web visit https://groups.google.com/d/msgid/mtadeveloperresources/f175e285-dfe0-4d50-915e-c5e10ab160b0n%40googlegroups.com.

[Zahidur R]

http://backend.mylirr.org/gtfs is down now and no longer working. 

Do you have new API URL.?

[Fisher, Will]

Hi, please try this instead:

 

backend-unified.mylirr.org/gtfs and make sure the API version is set to 3.0 in the headers

 

Best,
Will

To view this discussion on the web visit https://groups.google.com/d/msgid/mtadeveloperresources/a95f7ea2-2855-410d-b12e-31093776a5c3n%40googlegroups.com.

[clevercommute]

Thanks for this. 

The ongoing concern is that MTA will make an unannounced change to a non-GA API which will break my code...and that appears to be exactly what happened here. 

(I'd welcome being wrong)

When/where was the deprecation of backend.mylirr.org/gtfs announced?

Where is the doc for backend-unified.mylirr.org?

[Nicholas Boccio]

Hi,

The backend-unified.mylirr.org API is now returning a CORS access error and I can't retrieve data from it. From the standard feed, I can't parse carriage details or track postings. Is there a way to fix this?

[Fisher, Will]

Hi,

 

Can you set the CORS headers correctly? Or at least copy the CORS headers that traintime.mta.info is sending (use Chrome Inspector).

 

Best,

Will

To view this discussion on the web visit https://groups.google.com/d/msgid/mtadeveloperresources/c2909798-0d1f-4381-876f-27ce89f3e9b5n%40googlegroups.com.

[Nicholas Boccio]

These are the response headers:

HTTP/1.1 403 Forbidden Date: Tue, 06 Jun 2023 15:18:34 GMT Transfer-Encoding: chunked Connection: keep-alive Server: nginx/1.20.0 Vary: Origin Vary: Access-Control-Request-Method Vary: Access-Control-Request-Headers X-Content-Type-Options: nosniff X-XSS-Protection: 0 Cache-Control: no-cache, no-store, max-age=0, must-revalidate Pragma: no-cache Expires: 0 X-Frame-Options: DENY

[Fisher, Will]

Oh you need the Accept-Version header…

You can copy again from the website request.

---

From: mtadevelop...@googlegroups.com <mtadevelop...@googlegroups.com> on behalf of Nicholas Boccio <njbo...@gmail.com>

Sent: Tuesday, June 6, 2023 11:26:22 AM

To view this discussion on the web visit https://groups.google.com/d/msgid/mtadeveloperresources/95ad8373-c4de-407b-b0b7-6787f3345c5bn%40googlegroups.com.

[Nicholas Boccio]

Here's the request headers from my site (local server test). I added the accept-version header but it didn't help:

OPTIONS /gtfs HTTP/1.1 Accept: */* Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.9,es;q=0.8,it;q=0.7 Access-Control-Request-Headers: accept-version,access-control-allow-origin,x-api-key Access-Control-Request-Method: GET Connection: keep-alive Host: backend-unified.mylirr.org Origin: http://127.0.0.1:5500 Referer: http://127.0.0.1:5500/ Sec-Fetch-Mode: cors User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36

[clevercommute]

The app I publish has been adversely affected. 

Four questions: 

1. What changed? 

2. When?

3. Where/how was it announced? 

4. When will discrete fix/guidance from MTA be published? 

[Zahidur R]

I added the header but it is actually problem with API URL. Because https://backend-unified.mylirr.org/gtfs is no longer valid and it's returning 404 status.

As you suggested I also checked traintime.mta.info and found that it's using different end-point e.g. https://backend-unified.mylirr.org/arrivals/NYK

I need a valid API end-point for GTFS data.

[Fisher, Will]

Hi, can you try /gtfs/mnr or /gtfs/lirr? These feeds are the most accurate but are more likely to change than the API portal.

 

If you want something completely stable, I’d suggest using the API portal: https://new.mta.info/developers

 

To view this discussion on the web visit https://groups.google.com/d/msgid/mtadeveloperresources/1bb454b1-1865-49b3-9e9c-581031cee2een%40googlegroups.com.

[Nicholas Boccio]

Thank you, this worked. Thank you for also providing the MNR API.

My issue with the API portal is that I can't seem to parse all the data I need. For MNR I can't get carriage details and for LIRR I can't get track number either (which is what this thread was started for in the first place I think?). If there's something in the proto configuration that needs to change to parse it correctly, please let me know.

Nick