[gdal-dev] Re: Using a gdal generated tiff to generate DEM tiles - losing registration

[Iain]

http://osgeo-org.1803224.n2.nabble.com/file/n6947649/tilersrc.tar.gz
tilersrc.tar.gz 

Here's the source. It's a bit of lashup, but the principle bits that must
underly the problem are the tile and boundingbox classes (both pretty small)
and the pixoffsets and readtile functions in the gdshelper class.

The input file I'm using starts from srtm files through this chain:

gdal_fillnodata.py   #just to get cleaner data 

gdal_merge.py     # to generate 1 big file

gdal_translate -of GTiff -co "TILED=YES" -a_srs "+proj=latlong" brisles.tif
brislestrans.tif

gdalwarp -of GTiff -co "TILED=YES" -srcnodata 32767 -t_srs "+proj=merc
+ellps=sphere +R=6378137 +a=6378137 +units=m" -rcs -order 3 -tr 30 30 -multi
brislestrans.tif brisleswarped.tif

The output from this comes out correctly registered from hillshade, but
wrong from my program...

Iain


--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Using-a-gdal-generated-tiff-to-generate-DEM-tiles-losing-registration-tp6946188p6947649.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.