[gdal-dev] Wrong resolution info from multitable rasterlite

[Jukka Rahkonen]

Hi,

See what happened when I took two tiffs with different resolutions

This one
suomi45m_tm35fin.tif
Origin = (-70042.000000000000000,7903802.000000000000000)
Pixel Size = (200.000000000000000,-200.000000000000000)

and another
gdalinfo suomi1m_tm35fin.tif
Origin = (19970.000000000000000,7785300.000000000000000)
Pixel Size = (100.000000000000000,-100.000000000000000)

I converted them into the same rasterlite DB with these four commands:

gdal_translate -of rasterlite -a_srs epsg:3067 suomi45m_tm35fin.tif
rasterlite:multitable.sqlite,table=suomi45m

gdal_translate -of rasterlite -a_srs epsg:3067 suomi1m_tm35fin.tif
rasterlite:multitable.sqlite,table=suomi1m

gdaladdo rasterlite:multitable.sqlite,table=suomi45m 2 4 8 16

gdaladdo rasterlite:multitable.sqlite,table=suomi1m 2 4 8 16


Now gdalinfo reports that both of these rasterlite tables have 
a pixel size of 200 m

gdalinfo rasterlite:mmlrasterit_2011.sqlite,table=suomi45m
Origin = (-70042.000000000000000,7903802.000000000000000)
Pixel Size = (200.000000000000000,-200.000000000000000)

gdalinfo rasterlite:mmlrasterit_2011.sqlite,table=suomi1m
Origin = (19970.000000000000000,7785300.000000000000000)
Pixel Size = (200.000000000000000,-200.000000000000000)


Quantum GIS is placing the map that actually has 100 m pixels in a 
wrong scale into a project. However, I am not sure if this pure
GDAL error because Spatialite-gis seems to make the same
error. I can see correct values in the pixel_x_size x and 
pixel_y_size columns in the corresponding raster metadata tables.

Everything works as expected if I convert images separately into
two single-table databases.

-Jukka Rahkonen-