[gdal-dev] Default GeoTransform for MEM driver
Tim Keitt
tkeitt at utexas.edu
Tue Dec 10 08:58:47 PST 2013
On Mon, Dec 9, 2013 at 1:54 PM, Even Rouault
<even.rouault at mines-paris.org>wrote:
> Le lundi 09 décembre 2013 18:08:19, Ivan Lucena a écrit :
> > The other problem with that documentation is the return code. CE_Failue
> > means that the driver does not support it and/or that the dataset doesn't
> > have it.
>
> The current behaviour of the MEM driver doesn't particularly shock me. It
> seems OK to return CE_Failure if SetGeoTransform() hasn't been explicitely
> called to define it. And as far as the default geotransform, it is a
> matter of
> taste. [ 0, 1, 0, 0, 0, 1] would be indeed a bit more classical for a
> ungeoreferenced image, but one can consider that if GetGeoTransform()
> returns
> CE_Failure, the returned geotransform is to be ignored.
>
> To answere Tim's initial question {0, 1, 0, 0, 0, -1} is a north-up image :
> (0,0) is the coordinate of the upper left of the top left pixel, and y
> values
> are decreasing with image rows.
>
That makes sense. It just a matter of always checking the transform and not
assuming as I was that there is one default arrangement.
THK
>
> Even
>
> --
> Geospatial professional services
> http://even.rouault.free.fr/services.html
>
--
http://www.keittlab.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20131210/380b1f9f/attachment.html>
More information about the gdal-dev
mailing list