We could allow filtering and aggregating with more options. I propose replacing type + muni with three filters:
- types
- source
- last updated
At the cluster level, we have to be less granular, since it's inefficient to have quadtree bins for every date or source. Let's design a separate UI for cluster level filtering - last updated dates aggregated to a year, source aggregated to just three main values (user submitted, community map, tree inventory), maybe we can even flatten the list of types.
Related to #1063 (show locations from one source, with no filtering), and #378 (variable clustering).
We could allow filtering and aggregating with more options. I propose replacing type + muni with three filters:
At the cluster level, we have to be less granular, since it's inefficient to have quadtree bins for every date or source. Let's design a separate UI for cluster level filtering - last updated dates aggregated to a year, source aggregated to just three main values (user submitted, community map, tree inventory), maybe we can even flatten the list of types.
Related to #1063 (show locations from one source, with no filtering), and #378 (variable clustering).