Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JET Data #20

Open
reedacus25 opened this issue May 20, 2024 · 3 comments · May be fixed by #27
Open

JET Data #20

reedacus25 opened this issue May 20, 2024 · 3 comments · May be fixed by #27

Comments

@reedacus25
Copy link

I think it would be helpful to have JET bus routes included with the RTA data to have a more comprehensive transit status, since there is overlap between JET and RTA in certain parts of the metro, despite the lack of fare transfers. The map for their live status is here.

@naf419
Copy link

naf419 commented Nov 4, 2024

the static gtfs data (route geometries) are not available from jp transit directly, but they are available from ride (https://rideneworleans.org/opendata/gtfs/)

the live bus location data is available via some light reverse engineering and i have it coded up, but im pretty sure its not appropriate to contribute here... jp transit doesn't respond to my requests regarding either feed, so i dont know where that leaves us...

@reedacus25
Copy link
Author

Appreciate the response @naf419!

Glad to learn about a new open data format with GTFS.

That said, I'm assuming that the feeds advertised for JeT here would be functional, both RT and static, but I'm assuming (part of) the reluctance is that there is no license to access the data, as it appears there is for NORTA? As you said, the RT feeds look trivial, but the static feeds seem to be a magic link someone unearthed or published?

@naf419 naf419 linked a pull request Nov 5, 2024 that will close this issue
@naf419
Copy link

naf419 commented Nov 5, 2024

thanks for that link, dont know how i missed it. it does look a lot more legit than my reverse engineered version of their javascript app's "encrypted" api keys...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants