Even, I seems that ogrinfo "insists" that the /api path exists, since it throws an error 404 as reported above. So we had to implement a dummy /api in our minimal server implementation which returns "OK" to ogrinfo in order to bypass those 404 errors from ogrinfo.
I quickly skimmed the ogrinfo code [1] ff. and assumes that it lacks a catch for this 404 error. Should I create an issue? :Stefan [1] https://github.com/OSGeo/gdal/blob/master/gdal/ogr/ogrsf_frmts/wfs/ogroapifdriver.cpp#L509 ff. Am Di., 3. Dez. 2019 um 21:25 Uhr schrieb Stefan Keller <[email protected]>: > > Hi Even > > Awesome, thanks! Tu es le meilleur. > > :Stefan > > Am Di., 3. Dez. 2019 um 17:45 Uhr schrieb Even Rouault > <[email protected]>: > > > > 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 <ourlayer>" [2] obviously because some discovery > > > paths are not implemented at server side. > > > > > > Now, my question is: What are the endpoints really required by the OGR > > > reader driver? /api ? > > > > Source is there: > > https://github.com/OSGeo/gdal/blob/master/gdal/ogr/ogrsf_frmts/wfs/ogroapifdriver.cpp > > > > Master implements the final spec: > > http://docs.opengeospatial.org/is/17-069r3/17-069r3.html > > (there have been changes w.r.t earlier drafts) > > > > From my memories, the OGR driver needs: > > - Landing page: required > > - /collections: required > > - /collections/{collectioname}/items: required > > - /api (actually link provided in Landing page): optional > > - /conformance: not used > > > > You can enable --config CPL_DEBUG ON --config CPL_CURL_VERBOSE YES > > to see which network requests are attempted (some may be attempted and if > > the server doesn't implement them, execution can continue > > > > -- > > Spatialys - Geospatial professional services > > http://www.spatialys.com _______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
