-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TilesXYZ ignores selected layer CRS #43904
Comments
@frafra can you attach it? |
@gioman I am sorry, it contains sensible information I cannot share. It contains some areas near Oslo, Norway, but when I generate the tiles it produces images located in northern France. I have the same problem when I use Python and I use a simple |
@frafra it is just needed a rectangle with the bbox of your layer. |
Sure, that should work as well :)
|
@frafra what QGIS version are you using? and on what operating system? |
I think the problem is that mbtiles are (by design) always generated in 3857, and the tool do not reprojects the chosen extent if this is not in 3857 and the project is (because if the project and extent are both the same and not in 3857 it seems to work ok). |
I'd say this is a won't fix, as MBTiles is always in EPSG:3857. |
I have two layers: a vector layer (EPSG:25833) and a OpenStreetMap silly map raster tile (EPSG:3857). QGIS project CRS is set to match the raster tile (EPSG:3857).
When I run "Generate XYZ tiles (MBTiles)" from the graphical user interface, I can select the map canvas extent to generate the tiles, which works as expected, or the vector tile, which produces tiles in the wrong position.
I see the extent as
xmin,xmax,ymin,ymax [EPSG:3857]
if I use the map canvas extent, while I see the extent asxmin,xmax,ymin,ymax [EPSG:3857]
if I select the vector layer. CRSs are then correctly specified, but TilesXYZ does not convert the coordinates into the project coordinates, producing incorrect results sometimes.Setting the project CRS to match the vector layer CRS works.
The text was updated successfully, but these errors were encountered: