Re: [gdal-dev] OGR C API PostGIS geometry with wrong field entries

Thanks for your feedback! I think I figured it out. The GRASS module v.in.ogr goes through the input features twice, but only for polygons. This is needed to properly convert non-topological polygons to topological areas in GRASS. The order of features can be different between the first and second

Re: [gdal-dev] Minimal requirements of a service for reader driver OGC API - Features?

Hi Even Awesome, thanks! Tu es le meilleur. :Stefan Am Di., 3. Dez. 2019 um 17:45 Uhr schrieb Even Rouault : > > On mardi 3 décembre 2019 17:25:20 CET Stefan Keller wrote: > > Hi, > > We're implementing a minimal server of an "OGC API - Features" service > > and test it with a reader driver of "

Re: [gdal-dev] Minimal requirements of a service for reader driver OGC API - Features?

On mardi 3 décembre 2019 17:25:20 CET Stefan Keller wrote: > Hi, > We're implementing a minimal server of an "OGC API - Features" service > and test it with a reader driver of "OGC API - Features" [1] (ogrinfo, > ogr2ogr, QGIS). We're getting ERROR 404 with "ogrinfo > WFS3:127.0.0.1:8000 " [2] obvi

[gdal-dev] Minimal requirements of a service for reader driver OGC API - Features?

Hi, We're implementing a minimal server of an "OGC API - Features" service and test it with a reader driver of "OGC API - Features" [1] (ogrinfo, ogr2ogr, QGIS). We're getting ERROR 404 with "ogrinfo WFS3:127.0.0.1:8000 " [2] obviously because some discovery paths are not implemented at server side