.@mines-paris.org
> > > > To: gdal-dev@lists.osgeo.org
> > > > Subject: Re: [gdal-dev] Default GeoTransform for MEM driver
> > > > Date: Mon, 9 Dec 2013 20:54:35 +0100
> > > > CC: lucena_i...@hotmail.com; tke...@utexas.edu;
> >
> > jukka.rahk
On Tue, Dec 10, 2013 at 12:44 PM, Even Rouault wrote:
> Le mardi 10 décembre 2013 16:48:31, Ivan Lucena a écrit :
> > Hi Even,
> >
> > > From: even.roua...@mines-paris.org
> > > To: gdal-dev@lists.osgeo.org
> > > Subject: Re: [gdal-dev] Default GeoTrans
Le mardi 10 décembre 2013 16:48:31, Ivan Lucena a écrit :
> Hi Even,
>
> > From: even.roua...@mines-paris.org
> > To: gdal-dev@lists.osgeo.org
> > Subject: Re: [gdal-dev] Default GeoTransform for MEM driver
> > Date: Mon, 9 Dec 2013 20:54:35 +0100
> &
On Mon, Dec 9, 2013 at 1:54 PM, Even Rouault
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 beh
Hi Even,
> From: even.roua...@mines-paris.org
> To: gdal-dev@lists.osgeo.org
> Subject: Re: [gdal-dev] Default GeoTransform for MEM driver
> Date: Mon, 9 Dec 2013 20:54:35 +0100
> CC: lucena_i...@hotmail.com; tke...@utexas.edu; jukka.rahko...@mmmtike.fi
>
> Le lundi 09 d
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
seem
[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
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
Tim Keitt 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 corn
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?
THK
--
Timothy H. Keitt
http://www.keittlab.org/
__
10 matches
Mail list logo
