-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Missing maxNativeZoom for vector tiles in iOS lib #2761
Comments
This behavior is not expected -- it should display the z16 level tiles. In short, since vector tiles are highly amenable to overscaling, it's always assumed that |
Ah, sounds like a bug then. There is no property for maxZoom in the iOS lib though. If I put
|
Thanks for fixing this! Just integrated 3.0 and works like a charm. |
Great! We didn't knowingly do anything to fix this for 3.0, but it's possible it got fixed as a side effect of something else. |
I'm sorry, I was a bit fast there, it still tries to load tiles for zoom levels that doesn't exist. So please reopen! Did some work on the map parts in the app today and it doesn't work. I was just being lucky before, i.e. I had zoom set at 10 and our tiles were loaded, than when zoomed to > 16, it (probably) interpolated those tiles. Maybe I'm doing something wrong here. In the style I set add our layer this way:
and I expect it to only load tiles for zoom level 16 and lower, but still get 2015-12-15 15:13:09.964 Mapillary[734:114998] [ERROR] {Map}[Style]: Failed to load [https://SOMEURL/tiles/17/70274/41071.mapbox]: |
It seems it has gotten worse in later releases. I hope this video will help illustrate the problem better. |
Perhaps the original post is a bit off and should create a new one? |
@millenbop Yes, can you please create a new issue if this is still occurring? |
Yeah seems like it still exists. I have created #4969 |
We serve vector tiles up to zoom level 16, but sometimes we need to go up to zoom level 18. If the tiles are loaded at a lower zoom level and the map is zoomed in, it seems to interpolate the vector tiles it already has, but if the map starts loading at zoom level > 16, they are not displayed.
It's not a very clean solution and is prone to errors.
It would be very useful to have
maxNativeZoom
in this lib (for iOS) as well, similar to https://www.mapbox.com/mapbox.js/api/v2.2.2/l-tilelayer/The text was updated successfully, but these errors were encountered: