-
Notifications
You must be signed in to change notification settings - Fork 55
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
Sharemap zoom to feature #1948
Comments
What seems to be the problem? Does the map not open at the expected location and zoom level or is the feature not selected? (Or are you missing a zoom/pan animation?) I tried sharing an origo-cities geojson feature via the default share method and opening the shared map it was set to the zoom level and extent saved with the feature selected including an overlay. Same for a wfs feature. This is what I would expect. Edit. It was broken in the near past: #1900 |
Problem is that the zoom to feature not trigger when open sharemap-url. Here are two live-examples, first latest master, second from around march 2023. |
Thanks @Grammostola for the info, that solves our use case right now. For example, a Sharemap config opt-in |
Center and zoom would still work as a fallback right? The change in #1904 obeys all parameters:
What it doesn't do is to zoom to the feature itself, which I admit it did before. But that would ignore center and zoom which effectively made the link not reflect how the map was composed when the link was made. The way it is now is that the link recreates how the map looked when the link was created. #1899 proposes to select which arguments are part of the sharemap link, which would make it possible to omit center and zoom and have the map zoom to the selected feature. |
@Owemyr As I understand it, this is no longer an actual issue that needs to be fixed, correct? |
Thats correct @tonnyandersson |
Describe the bug
Sharemap zoom to feature not working.
To Reproduce
Expected behavior
The map should zoom to feature when open sharemap-url. We have also tested on WFS source with same result.
Worked before, but not sure when and which PR the issue occured.
The text was updated successfully, but these errors were encountered: