You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All tiles should be displayed properly forming whole map instead of repeated fragments
Current behavior
There is no problem when tiles width is greater than height (for example 2048 width and 1024 height), but with the opposite configuration tiles are displayed incorrectly.
After some debugging session I recognized that there is a problem with wrapping X coords of tiles. CRS that we are using there have wrapLng (-180, 180) so we are setting _wrapX in GridLayer.js:
I don't understand why it's using y value of tileSize to calculate max range of X, shouldn't it use only tileSize.x for _wrapX, and tileSize.y for _wrapY?
After changing it locally to:
Checklist
Steps to reproduce
I'm trying to get custom sized tiles from http://www.ign.es/wms-inspire/ign-base and display them in our app, with wrap option enabled.
Expected behavior
All tiles should be displayed properly forming whole map instead of repeated fragments
Current behavior
There is no problem when tiles width is greater than height (for example 2048 width and 1024 height), but with the opposite configuration tiles are displayed incorrectly.
After some debugging session I recognized that there is a problem with wrapping X coords of tiles. CRS that we are using there have wrapLng (-180, 180) so we are setting _wrapX in GridLayer.js:
I don't understand why it's using y value of tileSize to calculate max range of X, shouldn't it use only tileSize.x for _wrapX, and tileSize.y for _wrapY?
After changing it locally to:
everything is working properly.
Minimal example reproducing the issue
No response
Environment
The text was updated successfully, but these errors were encountered: