Changing to an unsupported tile provider zoom level removes all tiles and reports a load of errors

[thomaslindstrom]

Would be nice to have an option to cap tile layer url zoom without screwing up the coordinates and still see the CSS3 zooming while pinching and animating. Will also result in fewer requests if I can specify that no tiles have decimal zoom levels.

EDIT: This is a really bad description, refer to the one below: #1934 (comment)

[mourner]

This was addressed by adding maxNativeZoom option to TileLayer. If you specify it, it will use that last zoom on other zoom levels by scaling tiles. Try it out.

[thomaslindstrom]

I can't see maxNativeZoom anywhere in the docs, but I'll try it - thanks!

[mourner]

It's in the master version. See changelog.

[thomaslindstrom]

Oh, sorry. Thanks again.

[mourner]

No problem, let me know if it worked for you. :)

[thomaslindstrom]

Sorry, no, it doesn't work. My explanation was really bad, though, so I can see what caused the confusion. Let me try again.

What I'm requesting is something to floor or round the zoom level, so that Leaflet doesn't make tile requests for zoom levels with decimals (like 12.462 and 13.5), zoom levels that I know won't work with my tile provider (see image).

Even with maxNativeZoom set on my tileLayer, Leaflet still sent bad requests when I changed the zoom level using map.setZoom(12.5).

Sometimes I also get this error: No value provided for variable {s} when doing map.setZoom(12.5), too, and the tile layer disappears (image children are still there, but very small for some reason).

I tried manually (just to see if it was that easy) to visit getTileUrl and floor the zoom value, but then the coordinates went bananas.

Something like stripZoomURLDecimal: boolean or similar in L.tileLayer would be great.

[thomaslindstrom]

Here, I prepared a test case for you.

http://jsfiddle.net/982Nj/1/

Remember to open the console, too!

[denimboy]

mourner,

the problem is applications are setting fractional zoom levels map.setZoom(12.3456), the tile layer accepts it and makes requests for tiles with floating point zooms /tile/12.3456/0/0/0.png. Most tile servers 404 on those fractional zooms so the map fails.

It seems reasonable to me to have a boolean option like @thomaslindstrm suggests to int or round zooms to make sure only requests for integer zooms are made.

[denimboy]

also happens frequently on phones and tablets when people pinch to zoom

[danzel]

So you want to setZoom to 12.5, but we request the 12 (or 13) tiles and show those stretched or shrunk?

[thomaslindstrom]

Preferably yes. That would eliminate faulty requests and prevent the tiles from disappearing when pinch zooming.

EDIT: Not only setZoom, but all requests for tiles. I'd like an option to turn off decimal zoom levels.

[danzel]

Hang on, is pinch zooming causing the zoom level to end up a fractional value? Because that would be a bug.
Is this simple to reproduce, or is there something special to it?

[thomaslindstrom]

Yes it is, and I don't think it's hard to reproduce - you'll only need a tile layer that doesn't provide floating point zoom tiles.

I'll try this real quick on my iPhone using the test case I provided earlier and get back to you in two.

EDIT: It looks like once the map has hit a fractional zoom level, the tiles disappear and are hard to get back when pinch zooming as you'd have to go to the maximum or minimum zoom level for it to cap.

EDIT2: I'm seeing this in without setting a fractional zoom level before pinch zooming in Leaflet 0.6, but it might have been fixed in later versions.

[thomaslindstrom]

Any updates on this issue? @mourner @danzel