On mercredi 29 novembre 2017 13:33:17 CET Victor Chernetsky wrote:
> Thanks, this worked!
>
> I have a followup question: how does gdal/ogr2ogr knows that my
destination
> dataset/layer exists?
For the dataset, it tries to GDALOpen() it.
For the layer, by iterating over layers with GetLayer() a
Thanks, this worked!
I have a followup question: how does gdal/ogr2ogr knows that my destination
dataset/layer exists?
For instance, -append option suppose to do different things if layer
exists, or not. I don't see any isExists() APIs that would check it.
Thanks,
*Victor Chernetsky*
+1 (408) 3
On mercredi 29 novembre 2017 12:00:17 CET Victor Chernetsky wrote:
> Hey Even,
>
> How do I set OVERWRITE option?
With -lco OVERWRITE=YES since this is a layer creation option
> I tried all these:
> ogr2ogr -overwrite -f AmigoCloud "AmigoCloud:15276 datasets=100322"
This will trigger the logic
Hey Even,
How do I set OVERWRITE option?
I tried all these:
ogr2ogr -overwrite -f AmigoCloud "AmigoCloud:15276 datasets=100322"
~/Downloads/Visits.geojson
ogr2ogr --config OVERWRITE YES -f AmigoCloud "AmigoCloud:15276
datasets=100322" ~/Downloads/Visits.geojson
ogr2ogr -oo OVERWRITE=YES -f AmigoCl
+1 to what Howard said.
Two thoughts... (and I'm not saying CMake is any worse than autoconf)
Alternative build systems:
I co-maintain (mostly just me) a bazel build of GDAL (including autotest2,
expat, geos, hdf4, hdf5, hdfeos, kakadu, libgeotiff, libgif, libpng,
libtiff, netcdf, jpeg, proj, sq
Larry,
I agree that CMake brings some nice and useful features to the table. We
use it for PDAL, but we started out with CMake so there was no migration
that needed to be made.
CMake for GDAL is a project sustainment issue much more than a
technology switch and a patch. A person or a group of per
