I'm getting two different pixel size values, does anyone know what is the reason for this issue?

From gdalinfo:

From gdalinfo

From gdal2tiles.py:

From gdal2tiles

GDAL version: 3.20

  • Two stabs in the dark. Is the initial raster in a different CRS than 3857, leading to a scale/resolution difference after reprojection on the fly during tiling? Alternately, is there any rotation involved? The parameters of the geotransform are the exact x and y resolutions only if there is no rotation - see gis.stackexchange.com/questions/281132/…
    – Houska
    Feb 17 at 19:21
  • What do you do for for getting the pixel size from gdal2tiles?
    – user30184
    Feb 17 at 19:24
  • @Houska It's the same file which was projected to UTM. No rotation. Feb 17 at 19:31
  • @user30184 i just edited the code in order to log it. Feb 17 at 19:31
  • What did you edit here github.com/OSGeo/gdal/blob/master/gdal/swig/python/scripts/… and what is your exact gdal2tiles command? Have you considered if it is possible to keep the same extent and pixel size when the image must be split into some amount of full 256x256 sized tiles?
    – user30184
    Feb 17 at 19:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.