-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persist viewer type in the map configuration #8334
Comments
As discussed with @allyoucanmap It seems that there are (at least) two possible ways to persist matype (viewer) on map configuration. One would be by storing the active map viewer type when the user saves the map; that is if the viewer is doing updates to the map and has the 3d (Cesium) viewer activated that would be the maptype stored in the config and hence the one that will be active next time the user opens the map. This implementation would be somehow implicit in the sense that there's no explicit action from the user to set the maptype and it is given by the last viewer in which changes have been stored. Another way would be to have a section on the map settings for the user to set the default maptype (viewer) that would be used when the map loads. This option would be more explicit since the user would need to trigger a specific action in order to define this attribute of the map. |
@weberjavi moving in blocked column for now, waiting for a decision from the core team. |
Co-authored-by: Lorenzo Natali <[email protected]>
@allyoucanmap some notes after my tests: 1_ On dashboard, the zoom of the 2D map and 3D map is different if the two map are connected. Use this example. 2_ On dashboard, if a map is connected to a 3D map, it is no longer possible to zoom in/out the map independently. Expected Result ex.movCurrent Result current.mov3_ In the Geocarousel section of Geostory it is not possible to add a marker if the map is in 3D. Use this example. mark.mov4_ On dashboard and geostory, MS crashes if user tries to change style of 3D tiles or WFS layer. crash.mov |
@ElenaGallo thank you so much for reporting the above. Please create a dedicated issue for each point. @allyoucanmap I think at least some them should be fixed. Let's review together, in the meantime @ElenaGallo you can proceed with the creation of issues using the same project label and assigning issues to me and @allyoucanmap. |
@ElenaGallo is this tested/accepted? Please mention about newly created issues with links as requested above in a new comment. |
Description
Use Case
Some map could contain layer only visible in a specific viewer, for example the 3D tiles layers that could be available only in a 3D scene (Cesium). In this specific case it would be nice to be able to save the map with the information related to the current map type in use to visualize the map in 3D at the next reload.
The switch mechanism between 2D/3D in the map viewer is related to the mapType path inside the viewer url and stored in the redux state. This information is not persisted in the map config.
- [ ] Evaluate if it makes sense to deprecate the /viewer/:mapType/:mapId in favor of /viewer/:mapId where the mapType is managed only via config or internal state- [ ] Review if query params needs some adjustment based on previous improvement. In particular if we need to be explicit with a map_type param or guess the map type based on the query contentWhat kind of improvement you want to add? (check one with "x", remove the others)
Other useful information
see #8320 (review)
The text was updated successfully, but these errors were encountered: