MUNI Map
Context
The map is the entrypoint to all of this web-app’s functionality.
I am enamored by the ability to see all of the buses all at once. It is refreshing to see the big picture and to only filter down to individual needs when necessary.
Filtering to individual needs will be done by the following three features
Each vehicle icon will be made clickable, upon which, details will display
- vehicle_id
- speed
- direction
- next_stop
- stated arrival time at next stop
- predicted arrival time at next stop
Each route-card in the sidebar will be made clickable, upon which it will expand and display
- It will filter the map to show only vehicles from that route, and will also make stops appear as markers display:
- route_id
- if it is a bus or a train line
- number of buses active
- hours of operation
There will be a “show stops” button that will display all of the stops corresponding to currently displayed routes. Upon clicking on a stop marker, it will display,
- stop name
- lat,lon
- whether or not it has a bench (?)
What about Gaussian fitting of buses spatial distribution based on occupancy at given times of day. How about mapping these Gaussians in a time-lapse? This would be a fun way of measuring population density in SF at given times.
I will also find room for two more interactive fields:
- origin & destination (as either lat,lon or as stop names/IDs) –> optimal route
- text field for semantic querying of the database and recieving LLM generated response