I have just noticed that destination nodata value is not set when
-dstnodata option is not used in gdalwarp.
This can be problematic when warping a dataset with no data values, as the
result can be different from expected, if -dstnodata is not set.
gdalwarp does use source nodata pixels if
Friends,
I am using GDAL to read NITF (rsets / overviews) and in this particular
dataset the rsets (r0, r1, r2) have different corner points (slightly).
Problem is that when I use these rsets and when I zoom in on these images,
GDAL compute some appropriate overview but since the corners are
Etienne, Frank,
The original idea was to save space with the byte type, although I admit
bools are a rather unusual case. If we represent them as ints it might be
more straightforward just to use the int form of ValuesIO instead. How
about removing the bool form of ValuesIO and should a future
On Wed, May 15, 2013 at 2:58 PM, Sam Gillingham gillingham@gmail.comwrote:
Etienne, Frank,
The original idea was to save space with the byte type, although I admit
bools are a rather unusual case. If we represent them as ints it might be
more straightforward just to use the int form of
I have built GDAL, and was experimenting on a project.
I have external zlib 1.2.5
The external libraries are generally statically linked.
When trying the same thing with gdal, I got a link error:
error LNK2005: _deflate_copyright already defined in gdal.lib(deflate.obj)
I tried to find where
Hi Frank,
I've updated the RFC.
Sam.
On 16 May 2013 10:26, Frank Warmerdam warmer...@pobox.com wrote:
On Wed, May 15, 2013 at 2:58 PM, Sam Gillingham
gillingham@gmail.comwrote:
Etienne, Frank,
The original idea was to save space with the byte type, although I admit
bools are a
Mihaela,
The -DFRMT_ZLIB item in gdal/frmts/makefile.vc is triggering use of the
local copy of zlib if OGDI is *not* configured as it includes a copy of
zlib. It should in theory be practical to generalize that in some way so
the decision isn't based on OGDI but clearly it isn't common to build
Thank you Frank,
I'm afraid I don't understand this.
I looked now at the list EXTERNAL_LIBS in nmake.opt, and zlib is not
included.
If in Linux it is possible (common?) to build with the system zlib, why
can't I do that in Windows, with the external zlib ?
And if I can't... then how can I avoid
Folks,
I'm starting work on an OGR driver for Google Maps Engine (GME), focused on
it's use as a feature store. This should be somewhat similar to the Fusion
Tables driver. GME API docs are at:
https://developers.google.com/maps-engine/documentation/before-you-begin
It will have (I think)