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

[Even Rouault]

Stefan,

> I seems that ogrinfo "insists" that the /api path exists, since it
> throws an error 404 as reported above.

I think it should still go on despite emitting the error. The error is
probably emitted on the /api/ (with trailing slash) at 
https://github.com/OSGeo/gdal/blob/master/gdal/ogr/ogrsf_frmts/wfs/
ogroapifdriver.cpp#L521
that isn't surrounded by error quieting.

Anyway, all this fallback logic is mostly historic material from the earlier
stages of the specification. Conformant servers should implement a API page,
not necessarily under the /api endpoint, but at the endpoint they declare in
the landing page

See http://docs.opengeospatial.org/is/17-069r3/17-069r3.html#_api_landing_page

I don't remember the exact details of the QGIS OAPIF client, but it's 
certainly
less forgiving than the OGR one, and wouldn't likely like the API to be 
missing.

> Should I create an issue?

In your implementation yes 

Even


-- 
Spatialys - Geospatial professional services
http://www.spatialys.com