Hi Jukka,
One workaround is to use -skipfailures and compare afterwards which IDs in
the source data are not present in the target table. Skipfailures is forcing
the transaction size into one row and it may be deadly slow if the output is
GeoPackage because initializing/committing a transaction
Hi,
One workaround is to use -skipfailures and compare afterwards which IDs in
the source data are not present in the target table. Skipfailures is forcing
the transaction size into one row and it may be deadly slow if the output is
GeoPackage because initializing/committing a transaction in SQLit
Hi,
I was mainly curious without any exact need at the moment. I just noticed that
gdal2xyz.py can create xyz files with more bands than just one for z but I also
had a feeling that GDAL cannot read such files directly back, which appeared to
be true.
Generally speaking there might be some use
Hi all and happy new year!
as suggested some days ago [0] I've set up a vrt file that I use to
export many tables from a gpkg to a PG.
In the PG DB there are some constraints and with the vrt files all works
as expected: if an error (like a wrong value caught by the constraint) a
total rollb
