Thanks for the various ideas everyone, I've now found that the utility
gdallocationinfo gets the right answer for co-ordinates, so I'm just
checking to see how it does it and will incorporate this into my pixel
position calculations.
for example:
gdallocationinfo -xml -wgs84 /mnt/svrstuff/srtmda
That might be the answer - or at least part of it, I still get brain fade
trying to work through projections and projection conversion.
I'll try and think this bit through again!
Here's the gdalinfo from the input file :
Driver: GTiff/GeoTIFF
Files: brw.tif
Size is 48243, 78372
Coordinate Syste
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...
I'm building a set of 'tiles' that actually just contain dem data to drive a
3d geograpic tool on android (using opengl es2.0)
primarily for the uk (cos that's where I am) but hopefully in a way that
works anywhere.
I've picked up the srtm data and used gdal translate and gdawarp as
described in
