SCOPE: Different implementation options for Provider Map

[mrose914]

Given the new redesign of the Provider Map page, we would like to scope out implementation considerations and options for implementing the map, per convo in dev kickoff on 4/13.

[mrose914]

Goal is to see a couple of options, from low to high effort, so that we can align on a design and implementation plan that achieves the goals but does not introduce a ton of complexity or unnecessary effort.

[mrose914]

cc @segacy1

[segacy1]

@machikoyasuda @mrose914 I broke down the map functionality a little further here. The options included are:

1. (MVP) We keep the same functionality that exists today + the table
2. When a user clicks on a provider in the network list they'll see additional specs AND/OR
3. When a user clicks on a location on the map, the location is highlighted

[mrose914]

@segacy1 reviewing this now!

[mrose914]

I'm flexible on our options and willing to do what makes the most sense based on implementation considerations.

FWIW @thekaveman @machikoyasuda @angela-tran I did speak with @evansiroky today to follow up on how we might power this map with a new view. The great news is that there is recent alignment on the definition of an "agency." I am going to follow up with a couple folks to confirm the final set of fields we want to include on the new page next week but sounds like we will have the ability to create a view in Airtable and/or Metabase. More details here: https://dbt-docs.calitp.org/#!/model/model.calitp_warehouse.dim_organizations