Things that need to change:
Things that are already customized by page (using properties):
- Sensors displayed
|Sensors||Filtered Sensors||All Sensors||All Sensors and Filtered Sensors||Currently handled through properties|
|Drawing shapes||Based on the draw filter location option||Never||Based on a radio button|
Draw shapes functionality could be in a different component specifically for drawing shapes and it extends the map.
It will contain the html for the buttons and all the event listeners for draw functionality.
It will need to take as input the functions that are currently used for search vs explore like updating the global state and the rules for enabling/disabling.
|Shapes feature / Clustering|
Style to match v2 if single feature
|Never - Check what happens when two different sources on the same location track the same parameter.|
A style function to be sent in from the 'parent' maps to the Map.
Clustering functionality could also be a different component/extension for the Map. And enabled through properties.
It will take the styling function as input.
It will define the generatePointsCircle and displayOverlappingMarkers
|On Click feature / popup contents||Similar contents||Needs to reflect the trend on button click|
To have a component with the html contents of the popup.
The component could have a way of being extended with additional details (the different parts between search and exploratory analysis)
The component is sent as a property to the Map.
|External Listeners||On click on a feature in the left, the popup needs to show up.||An extension/event listener defined within ExploreMap Component.|
|Feature Attributes||10 attributes||10 attributes||10 + 4 attributes||Some way of extending/appending the extra parameters not considered common or necessary (for trends)|
|Additional Layers||Defined Regions|
|Shape for the icons/features||SVG's with colors per source|
SVG's with colors per source
Change to triangles on update
|Send a style function as input within the properties.|