Thanks for the replies so far. Unfortunately, adding a 3rd calibration point to the .map file has not helped. Of course I'm assuming that the added calibration point is valid (eg, I tried the one suggested below, which looks like it should be OK).
Does anybody have any other suggestions as to why this .map file cannot be interpreted correctly by GDAL? Is it a bug, or an incomplete .map parsing implementation, or am I doing something wrong? Cheers, Nik. On 12/11/2012, at 11:38 PM, Jukka Rahkonen <[email protected]> wrote: > Nik Sands <nixanz <at> nixanz.com> writes: > >> >> I appreciate that (hence pasting the content of the file in my original > email). However, I don't know how to >> be certain that the text I put into the file represents something that makes > sense. >> >> However, as I said I will give it a shot (when I get back to my computer). > > This is my guess: > Point01,xy, 0, 0,in, deg, , ,, , ,, grid, > 55,219999.09067205,5570000.7412442,S > Point02,xy, 1000, 1000,in, deg, , ,, , ,, grid, > 55,223259.16350298,5566740.6684133,S > Point03,xy, 0, 1000,in, deg, , ,, , ,, grid, > 55,219999.09067205,5566740.6684133,S > > Having two calibration points in OziExplorer .map files is not at all uncommon > and with digital maps and orthophotos in some projected coordinate system > there > is no need to have more. Same situation basically than with ESRI world file > georeferencing when just one anchor point and pixel size is given. > http://www.oziexplorer3.com/eng/features/features_moreinfo3.html > > -Jukka Rahkonen- > > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
