Ticket #3628 (new bug)

Opened 2 years ago

Last modified 2 years ago

Web Mercator overlays broken with "maxResolution: 156543.0339"

Reported by: nrenner Owned by:
Priority: major Milestone: 2.13 Release
Component: Layer.XYZ Version: SVN
Keywords: Cc:
State:

Description

Maps with option "maxResolution: 156543.0339" calculate wrong tile URLs for overlays, at least when using Google as base layer and OSM as overlay, see:

 http://jsfiddle.net/nrenner/N3DSB/

This probably has been introduced by  #219.

Simply not setting maxResolution or setting "maxResolution: 156543.03390625" does work, but many existing maps probably still use "maxResolution: 156543.0339" and might get broken.

Change History

Changed 2 years ago by erilem

Thanks for reporting this mrenner.

Andreas, I'm not yet familiar with the new code. Do you think that's a regression?

Changed 2 years ago by ahocevar

@erilem: not a regression. We have this behavior since r11118 (i.e. pre 2.11), and 156543.0339 was an incorrect maxResolution.

Changed 2 years ago by erilem

Hmm the same example works for me with 2.11.

Changed 2 years ago by erilem

It probably works with 2.11 because the layer has a maxResolution so that of the map has no effect at all.

Changed 2 years ago by erilem

If we don't want to fix that because users should use correct values then we may want to add something in the 2.12 release notes.

Note: See TracTickets for help on using tickets.