[pygeoapi] Clarification on Features Core Part 1 1.0 Conformance

Tom Christian thomaschristian at gmail.com
Thu Apr 1 09:39:04 PDT 2021


I'm attempting to resolve a question I raised in
https://github.com/geopython/pygeoapi/issues/672 that was subsequently
closed, with me being redirected to this mailing list.

Initially my question was how pygeoapi is conformant with Features Core
Part 1 1.0 when several "providers" do not support bbox or datetime
filters. I was informed that the providers have varying levels of support
and this is OK. However, I am trying to determine how or where the OGC spec
permits different levels of conformance based on source data type. From my
reading of the documentation I did not think that this was an option.

Tom Kralidis stated "this is irrelevant from the OGC viewpoint", but I
don't understand how this is true - OGC should expect all collections to
support bbox and datetime filtering because it doesn't care about how the
data was accessed. If the spec says an implementation SHALL support bbox
and datetime filtering then presumably all providers need to support that
behaviour? Otherwise an API client who is unaware of each collection's data
source will see varying levels of spec compliance with no indication as to
why.

Any clarification much appreciated, thanks.
Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pygeoapi/attachments/20210401/eb8ef7d0/attachment.html>


More information about the pygeoapi mailing list