-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Save the current Cesium config as a link for sharing #1806
Comments
One use case for this came up in the PDG meeting today: the LEO Network would like to include links on their website that open up the PDG portal and specific locations and with specific layers visible |
This feature keeps getting requested for different use-cases, which is why I've added the high priority tag. For example, a researcher just asked whether we could create a link that displays the Details Panel for a particular layer by default. Here are details of the request:
|
Overall, there have been few requests to save map views as a collection, but many requests to get a link of the current map view to share between users. If we can get the link functionality implemented, then a user could at least create their own collection of views via browser bookmarks. We could also use the link functionality to create a "Gallery" view in the future. Map properties that should be shared via the link:
|
Add a feature to Cesium and MetacatUI where users can save their current data layer configuration to come back to later since the map will be reset anytime the browser window is closed. This Cesium config can be reloaded when the user logs in on their next visit.
These saved configs could also be shared with others. e.g. if you found an interesting combination of data layers/colors/filters/time, you could save and share that map with others. We could also allow users to publish their saved maps and create a "Gallery" of maps others have created. This could help a lot with community and cooperativeness around the PDG.
The text was updated successfully, but these errors were encountered: