How can we keep this running smoothly with service changes? Ideally this would run hand in hand with the updates to Heroku.
-
Get the new GTFS This usually happens through e-mail and then we post it to the open data portal, although it does get posted to detroitmi.gov as well.
-
Bring the new GTFS into Postgres. We can use https://github.com/fitnr/gtfs-sql-importer
-
Clean up the data:
- copy stop names and location over from Tiffany's good file
- routes: route name, route number, custom meta stuff
- trip headsigns
- timepoints (still manual)
- route shapes? (AGO? Mapbox style/tileset?)
- Apply functions that we don't get for free with the sql-importer.
- nearby transfers
- stops-to-routes
-
Run
gatsby build
-
Redeploy
Download the example or clone the repo:
curl https://codeload.github.com/mui-org/material-ui/tar.gz/master | tar -xz --strip=2 material-ui-master/examples/gatsby
cd gatsby
Install it and run:
npm install
npm run develop
Gatsby is a static site generator for React.