Serve transit data through our own API about findsepta HOT 2 OPEN

I think we should have one process running that periodically (tbd how often) retrieves data from here, then does our cleaning, and stores it in an SQL database. Then the api will mostly just be sql queries – and as long as our database is designed to be pretty universal, we should be able to reimplement this for other cities without altering anything but the process that is pulling data from SEPTA/its counterpart.

Ideas for api endpoints:

• Get bus positions by route
• Get bus positions by stop
• Get bus timings by stop
• Get bus positions by long/lat (maybe unnecessary given the previous one but potentially useful)

from findsepta.

Agreed! I'd also like to serve fixed routelines as a separate API, too.

Our cleaning script will most likely be the biggest headache here, and might even warrant its own issue thread. For now, let's focus on setting up a mirror API on our server, and then work on cleaning the data after we've shifted our architecture. Here's my suggested task list:

• 1. Set up automatic querying of TransitViewAll
• 2. Build DB for storing the data on our server (Postgres?)
• 3. Build API in Flask, routing queries with SQLAlchemy
• 4. Switch our current app architecture to query from our own API instead of SEPTA's
• 5. Start on data cleaning script

from findsepta.