mikeucfl wrote
> So if anyone sees a similar issue, it's something internally with GEOS but
> I
> didn't have enough time to track it down. Re-projecting to something using
> meters does help though.
Hi,
If you could share couple of problematic geometries for example as WKT then
somebody else
Just to update with what I've figured out so far.
1. The issue surrounds an OGRMultiGeometry that has intersecting interior
rings.
2. The projection of the geometries are in EPSG 4326 (lat/long).
3. Internally in GEOS when the difference operator runs, there is a call to
check if the geometry is
Hi,
That was the case, once I updated into recent trunk the error message
disappeared.
-Jukka-
Lähettäjä: Even Rouault [mailto:even.roua...@spatialys.com]
Lähetetty: 6. helmikuuta 2018 14:54
Vastaanottaja: gdal-dev@lists.osgeo.org
Kopio: Rahkonen Jukka (MML)
Jukka,
Which version do you use ? If it is a trunk version before Jan 23,
you may run into the bug fixed by https://trac.osgeo.org/gdal/
changeset/41325
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev
Hi,
Title says most of it. Running "ogr2ogr -f gpkg -update -overwrite" for a
vector table in GeoPackage gives an error:
ERROR 1: Spatial index already existing
I wonder if the overwrite mode still does the right thing. Is the R-Tree table
truncated automatically by the triggers together with
