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
When searching tiles, it seems like we need to swap x and y to get the correct tile (We get AF instead of EU otherwise).
Further, when searching, we can specify CRS while the bbox for tiles is given in ?? metres??? or something ?
Is this a bug or should I use some other function to get the tile bbox in e.g EPSG:3006 ?
Output from the experiment with and without swapped x-y for EPSG3006 and EPSG4326:
As this is covered by the CI's test_search_tiles_lon_lat_extent(), I'm curious:
a) which plattform are you working on?
b) have you followed the installation in README.rst?
c) can you run the test, e.g. via python setup.py test ?
Last year, there was one issue with GDAL2 vs GDAL3, when the order of axis has changed. I assume this issue is connected.
When searching tiles, it seems like we need to swap x and y to get the correct tile (We get AF instead of EU otherwise).
Further, when searching, we can specify CRS while the bbox for tiles is given in ?? metres??? or something ?
Is this a bug or should I use some other function to get the tile bbox in e.g EPSG:3006 ?
Output from the experiment with and without swapped x-y for EPSG3006 and EPSG4326:
The text was updated successfully, but these errors were encountered: