R3 Urban dashboard requires some additional features for data exploration and organization. Based on the discussion with @slesaad today, the extra features we need are
Ability to display custom layers (likely a geojson layer) on top of the existing layers
1-1. Ability to display (more than a pop-up length) static contents based on the interaction with the custom layer.
A specific scenario: There will be a geojson with a list of cities. When a user clicks on a city, a panel showing its static contents (including facts, table, charts..) will open.
1-2. Ability to organize static contents of custom layers through MDX : We can foresee how complicated the workflow will be if the static content should be input as a part of a GeoJSON file. Can we make static contents for these custom layers to live somewhere else in static files like MDX?
1-3. Where is this 'embedded environment' going to live? in GHG instance? or somewhere else?
Additional note: Can we use some parts of Map components from VEDA-UI and add the additional layers on top of them?
Ability not to display stories on the dashboard: There will be small stories that will be linked from somewhere, but won't be displayed on the stories hub page. We need some kinds of flags not to show the stories. (It might make sense to implement the same thing for the datasets, since there has been a request to hide some datasets from the hub page before.)
Acceptance Criteria
[ ] Given when then the feasibility, strategy and LOE of each feature is clear
Context
R3 Urban dashboard requires some additional features for data exploration and organization. Based on the discussion with @slesaad today, the extra features we need are
Additional note: Can we use some parts of Map components from VEDA-UI and add the additional layers on top of them?
Acceptance Criteria
Related Tickets