Not quite sure if this is an issue with GeoServer or QGIS or just my own incompetence but thought I would report it: Our users noticed that when using an OGC API Features interface provided by GeoServer (2.27.4) in QGIS, they were unable to filter the features in the requests. QGIS requested all the features without a filter and then performed filtering afterwards (apparently, haven’t tested myself). With large datasets this obviously isn’t good. Similar usage on other OGC API Features interfaces (not provided by GeoServer) resulted in requests that did contain the correct CQL-filter.
After some research it seems that the problem has to do with the conformance response GeoServer gives (../ogc/features/v1/conformance). This has a line
http://www.opengis.net/spec/cql2/1.0/req/cql2-text
when QGIS is expecting
http://www.opengis.net/spec/cql2/1.0/conf/cql2-text
i.e. instead of “req” there should be “conf”. When I experimented by forcing the conformance reply to use “conf”, QGIS was able to use the interface correctly.
Kind regards,
Samuli Neuvonen, Finnish Environment Institute