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.
From: [email protected] Date: Mon, 9 Dec 2013 10:55:34 -0600 To: [email protected] CC: [email protected] Subject: Re: [gdal-dev] Default GeoTransform for MEM driver Right. Thanks for checking into it. I guess I was thrown by http://www.gdal.org/classGDALDataset.html#af9593cc241e7d140f5f3c4798a43a668 which gives the default as {0, 1, 0, 0, 0, +1}. Is there a library wide convention on this? I can update the docs if so. (I assume its a simple pull and send a diff type setup.) THK On Sun, Dec 8, 2013 at 11:27 PM, Jukka Rahkonen <[email protected]> wrote: Tim Keitt <tkeitt <at> gmail.com> writes: > > I notice that the "MEM" driver returns {0, 1, 0, 0, 0, -1} by default. Is this a bug or do some formats flip the vertical axis? If so, what is the convention for detecting and handling "south up" formats in code? I guess that anchor point is at the top left corner and therefore the north coordinate is decreasing step by step when you walk downwards. Document http://www.gdal.org/gdal_tutorial.html supports my thoughts. -Jukka Rahkonen- _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev -- http://www.keittlab.org/ _______________________________________________ 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
