Unavailable Route IDs

[Tyler Palsulich]

Hi,

I'm having an issue with the OpenAPI routes call. Not all of the route IDs identified in the stops file exist in the routes file.

For example, for agency 72 (NYU), stop 4119814 (80 Lafayette Street) claims to have routes 4003338 and 4003430 in stops.json. But, neither of those exist in routes.json. So, the name of the route, its segments, and the order of its stops are unavailable. The missing routes are all currently inactive right now, but they should still be in routes.json, right? See here for a list of routes that should be present. I believe the segments that correspond to the missing routes are still available, but I'm not sure. Is this a known issue?

Thank you for any help!

Sincerely,

Tyler Palsulich

[Stu Zhao]

Which version of the API are you using?

--

Yanglei (Stu) Zhao

TransLōc, Inc.

Email: stu....@transloc.com

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

[Tyler Palsulich]

I've been using version 1.2.

Best,
Tyler

[Stu Zhao]

Hi Tyler,

We will look into this issue.

Thanks,

--

Yanglei (Stu) Zhao

TransLōc, Inc.

Email: stu....@transloc.com

[Tyler Palsulich]

Hi Stu,

Thank you so much!

Best,
Tyler