We now have a user activity page with filters by type and place. Filtering map by source would still be interesting! We would need new query parameters like user_id and import_id from the API. I think this shouldn't be combined with the other filters, and the UI design should reflect it.
On mobile, add a header over map and list, with a 'back' that goes back to the user / import page.
On desktop, we can show the user/import in the side pane, no filtering or summary counts by type.
We can keep tree inventories out of scope, or maybe set a threshold number of locations for which this feature is out of scope: then we don't need to provide cluster counts.
Originally posted by @wbazant in #424
We now have a user activity page with filters by type and place. Filtering map by source would still be interesting! We would need new query parameters like user_id and import_id from the API. I think this shouldn't be combined with the other filters, and the UI design should reflect it.
On mobile, add a header over map and list, with a 'back' that goes back to the user / import page.
On desktop, we can show the user/import in the side pane, no filtering or summary counts by type.
We can keep tree inventories out of scope, or maybe set a threshold number of locations for which this feature is out of scope: then we don't need to provide cluster counts.
Originally posted by @wbazant in #424