Hi,
The actual error seems to be that you try to write some geometry that is not a
linestring into a GeoPackage table that has created with a constraint that
makes it accept only linestrings. You do that by using "-nlt linestring".
You have two options. The fast one is to use "-nlt geometry" tha
I have not even gotten to see that anything is being ignored because I have not
yet added any options. My first attempt was with adding skipfailures, but I
can’t add any of the options I have listed because I have no idea how to. I
thought it would be gdal_tools.config_options() but I get pyli
Hi,
No experience with pytest-benchmark, but I maintain an unrelated project that
runs some benchmarks on CI, and here are some things worth mentioning:
- we store the results as a newline-delimited JSON file in a different GitHub
repository
(https://raw.githubusercontent.com/rust-analyzer/me
-nln is being ignored because the data layer you're -updating -appending
to exists. You can't rename a layer if it has a name. Remove -nln option
Next you are trying to write a collection as a linestring. Use
-explodecollections (if exists in your install) and/or use -nlt
PROMOTE_TO_MULTI
Tr
I am running simple code to convert dxf to gpkg and I get the error below. -am
an trying to figure out how to add a bunch of options ( -f GPKG -append -update
--config DXF_ENCODING CP1252 --config DXF_INCLUDE_RAW_CODE_VALUES TRUE --config
DXF_TRANSLATE_ESCAPE_SEQUENCES FALSE --config DXF_MERGE_
Hi Even,
> With virtualization, it is hard to guarantee that other things happening
on the host running the VM might not interfer. Even locally on my own
machine, I initially saw strong variations in timings
The advice I've come across for benchmarking is to use the minimum time
from the set of r
Hi,
I'm experimenting with adding performance regression testing in our CI.
Currently our CI has quite extensive functional coverage, but totally
lacks performance testing. Given that we use pytest, I've spotted
pytest-benchmark (https://pytest-benchmark.readthedocs.io/en/latest/) as
a likely
Hi Jukka,
The documentation in
https://gdal.org/drivers/vector/oapif.html#layer-schema is wrong when
it claims this:
OGR needs a fixed schema per layer, but OGC API - Features Core
doesn't impose fixed schema. So the driver will retrieve the first
page of features (10 features) and establi
On Mon, Oct 9, 2023 at 10:05 PM Even Rouault via gdal-dev
wrote:
>
> Michael,
>
> you won't find much support for that in GDAL itself. You'd better have a
> look at Spatialite topology, PostGIS topology or GRASS topology.
Concerning the latter, here some overview Wiki pages:
- https://grasswiki.o
Hi,
The documentation in https://gdal.org/drivers/vector/oapif.html#layer-schema is
wrong when it claims this:
OGR needs a fixed schema per layer, but OGC API - Features Core doesn't impose
fixed schema. So the driver will retrieve the first page of features (10
features) and establish a schema
10 matches
Mail list logo
