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
Max zoom level no longer working from 0.14.0 to 0.15.1 (defaults to 18) #1859
Comments
Can confirm. In the Also note how this works in tandem with We should fix this and improve documentation. |
So there is still a possibility to increase the zoom level? Or is it disabled in the newest updates? If you are working on a small scale (e.g. meters), this is almost a necessity. |
@Stephaneke The maximum zoom is defined by the tile provider. You can play around with different tile layers to see how that affects the max zoom level. E.g. Our documentation is off as the |
@Stephaneke I did a quick experiment with a different provider. This one goes to level 22, which is the best I could find. It does require an api key. Parts in angle brackets need to be replaced. See https://github.com/leaflet-extras/leaflet-providers/blob/master/leaflet-providers.js for other providers.
|
This probably broke when we adopted xyzservices. This probably needs more than just a documentation change. Ideally we restore the previous behavior as described in the rasterlayer docstring. But now the ‘max_native_zoom’ value comes from xyzservices? And ‘max_zoom’ allows further zooming? Something like that. |
I did a few tests. My feeling is that |
I made a PR to bring back the behavior we had before, while keeping the values we get from xyzservices: #1952 |
Describe the bug
Since the update from 0.14.0 to 0.15.1, the max zoom level function does no longer work and defaults to 18?
To Reproduce
Expected behavior
I expect the maximum zoom level to be 25 instead of 18
Environment (please complete the following information):
maps.zip
Possible solutions
List any solutions you may have come up with.
folium is maintained by volunteers. Can you help making a fix for this issue?
The text was updated successfully, but these errors were encountered: