Hi Jukka,
Thanks for the note about row by row inserts - this would explain the large
performance difference.
I'd agree it is best to filter out features explicitly. Sometimes -skipfeatures
is just handy for having a quick look at the data though in a different format.
The main issue was the
Hi Seth,
Even if the creation of spatial index with -skipfeatures is now fixed,
generally that is a thing that should not really be used with GeoPackage and
SQLite/Spatialite. That leads to single-row transactions and very poor
performance.
There are usually other ways to avoid the problems and s
Excellent - thanks for the incredibly fast fix Even - wasn't expecting that!
Seth
--
web:http://geographika.co.uk
twitter: @geographika
On Thu, Nov 29, 2018, at 11:57 AM, Even Rouault wrote:
> On jeudi 29 novembre 2018 09:56:28 CET Seth G wrote:
> > Hi all,
> >
> > When running a command simila
On jeudi 29 novembre 2018 09:56:28 CET Seth G wrote:
> Hi all,
>
> When running a command similar to below (GDAL 2.3.1 on Windows):
>
> ogr2ogr -f "SQLite" test.db test.shp -skipfailures -dsco SPATIALITE=YES -lco
> SPATIAL_INDEX=YES
>
> If there are any errors (e.g. a MULTILINESTRING in a LINEST
Hi all,
When running a command similar to below (GDAL 2.3.1 on Windows):
ogr2ogr -f "SQLite" test.db test.shp -skipfailures -dsco SPATIALITE=YES -lco
SPATIAL_INDEX=YES
If there are any errors (e.g. a MULTILINESTRING in a LINESTRING dataset),
ogr2ogr skips the errors, but also skips creating th
