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

Stops and Lines should be related via route stop patterns #224

Open
tkimia opened this issue Mar 4, 2020 · 0 comments
Open

Stops and Lines should be related via route stop patterns #224

tkimia opened this issue Mar 4, 2020 · 0 comments

Comments

@tkimia
Copy link
Collaborator

tkimia commented Mar 4, 2020

Detailed Description

We have lines. We have stops. But the way they're related is totally random. Turns out there's an API endpoint on TransitLand that contains this information!

Possible Implementation

We have a rake task that pulls a bunch of data from TransitLand and uploads it into a database: that's called set_up_transitland. You can see that in that task we make a bunch of GET calls to transit land and create instances of the Stop and Line models.

The same way that we can reach out to

https://transit.land/api/v1/stops?served_by={AGENCY_ID} 

to get stops, we can also reach out to

https://transit.land/api/v1/route_stop_patterns?traversed_by=r-dp3w-brownline&per_page=false

to get a bunch of patterns of stops for a line.

This ticket should encompass the effort to simply import the infomation into our database such that we don't relate stops to Lines directly, but relate Lines to stop patterns.

More Info

You can use this website to see the information live:
https://mobility-explorer.interline.io/

What's more, you can use the built in dev console in your browser to see what calls are being made to transit land to get the data which will show on the screen.

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

No branches or pull requests

1 participant