Skip to content

Finalize the UI for the visualization #1007

Description

@emmambd

Describe the problem

Incorporate feedback from user interviews

Proposed solution

  • Generate sample file for parsing (backend + frontend pairing)

  • Load the PMTiles from the feed's dataset bucket

  • Add a feature flag and deploy to PROD

  • Test when route colors don't exist that it defaults to black and white

  • Modify route name logic so if route_short_name doesn't exist, display route_long name, if route_long_name doesn't exist, display route_short name)

  • Display: (short name) Long Name


  • No longer have a route availabiliy tab
  • On map
    • Add scale bar (compass*)
    • Side panel with all routes -> ability to filter
    • Ability to toggle stops
    • [bonus] filter by route type
    • Click on a route -> highlight all the stops for that given route
      • If many, will highlight the stops for all
      • Will select these routes for filter (will be able to clear)
    • Stop hover
      • Add stop location

Include timestamp of map update

If you click on another route, would that clear all route filters? -> yes

We would no longer display service dates of a route

To think about

  • How to access the detailed map
  • How the heat map fits in with this (bounding box is a fallback)
  • Look into OSM vs CartoDB

If shapes exist -> show detailed map
If no shapes data -> heat map default
If no heat map -> bounding box

V2

  • Select a date and see routes for that date / time****

Alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions