Closed RickyC0626 closed 1 year ago
Status update: Trying different methods and gauging on cost and speed to MVP
Option | Pros | Cons |
---|---|---|
Manually generating tiles from MBTiles dataset | Free, flexible | Takes a long time to set up, need to self host, large directory size (> 2GB), takes a long time to build custom features (directions, search, geospatial analysis) |
Mapbox | Free tier, has APIs for features like tiles, directions, search | Requires card for registration, no budget cap, expenses can balloon if unexpected spike in traffic |
Google Maps API | Not sure | No free plan, cost more than Mapbox (per request) |
Will probably go with Mapbox. Putting off building UI for now until backend API is built to process and cache MTA data properly.
Edit: Mapbox doesn't support transit routes, only driving. Can look into something like OpenTripPlanner for transit data, but even that is extremely memory-hungry.
Edit 2: Sticking with Mapbox, but pivoting to different idea. Could display weather overlay (clouds, heat, wind) on top of map.
Center of map should start in NYC.