> I don't think this comes from GDALPam, but rather from the lower level
> machinery of GDALRasterBand & GDALRasterBlock. As I said before, multi-
> threaded writing has never properly worked and I'm not sure if the issue
> you see is just an implementation bug or a design bug.
OK, after
So it seems I have to do a bit more testing then.
Perhaps it's the server I'm accessing which is buggy then.
I'll have a go with the testserver you're using, and compare.
Thanks for the answer.
>Odd-Ragnar<
-Opprinnelig melding-
Fra: Even Rouault [mailto:even.roua...@spatialys.com]
Hi Jukka,
>
> I wonder if it could be possible to do something like "DROP CASCADING" in
> GeoPackage and delete the spatial index by the same.
I will work in a short term on this (as well as renaming columns)
The "usual" syntax "ogrinfo -sql 'DELLAYER:bar' foo.gpkg" will be available,
and
Hi,
I wonder if it could be possible to do something like "DROP CASCADING" in
GeoPackage and delete the spatial index by the same. It will for sure be
unusable once the table is dropped. I feel that SQLite does not support that
because cascading drop seems to require that parent and child
Le jeudi 29 septembre 2016 10:06:12, Odd Ragnar Lydersen a écrit :
> So I have tried to dig a bit more into this, and I have noticed a few
> things.
>
>
> 1) I set MAXFEATURES=60 in the url
>
> 2) I select the layer I want to work with, let's call it MyLayer.
>
> 3) I call
So I have tried to dig a bit more into this, and I have noticed a few things.
1) I set MAXFEATURES=60 in the url
2) I select the layer I want to work with, let's call it MyLayer.
3) I call SetSpatialFilterRect() on the MyLayer and set it to a small area
containing 11 points.
