Endpoint for routes

[jaronheard]

It should return an array with
route:
description:
to enable a dropdown like this one

https://trimet.org/#tracker/line/100+0

[bhgrant8]

@znmeb @code-farmhouse do you know if this info exists in the database somewhere currently? If not the info appears to be in the GTFS schedules and info download in a txt/csv:

https://developer.trimet.org/schedule/gtfs.zip

[bhgrant8]

I believe this is getting pulled into our next db update, @znmeb is this correct?

[znmeb]

The current state of things is

SELECT * FROM trimet_gis.tm_route_stops

That will correspond to the congestion data.

For the ridership data there is an equivalent table in the GTFS archives, or one can be made from that with a little work. I don't think the MAX or Streetcar line numbers have changed, so you can probably just assume that anything that isn't currently MAX or Streetcar is a bus.

P.S.: The MAX lines are easy to spot from the stop names - the one that has a segment from Hillsboro to Beaverton Transit Center is MAX Blue Line, etc. Same for the streetcar - nothing else stops at quite a few of the stops.

[bhgrant8]

I just might hardcode this in as a static json or python dict from the gtfs. we can change later if needed

[alankessler]

https://trimet.org/ws/int/v1/routeConfig

[znmeb]

It's in the database, but

a) it's static - it describes the routes as of when I inserted the shapefile into the database.
b) the shapefiles and their contents are not licensed for re-distribution via an API.

So ... if we want to expose current route information we need to get it from GTFS. I have links to GTFS-to-PostGIS repositories - I'm considering making a Docker image thereof. It's four bash scripts and should work with the PostGIS image in the data-science-pet-containers, although there's a lot in that image that isn't needed.

If I can get @code-farmhouse code for processing the historical GTFS data I can probably add that to the image. I have the code @jbeyer16 wrote for downloading the historical GTFS data.