Update filter conformance classes

[m-mohr]

The filter conformance classes seem to be completely wrong. They don't even match the (wrong) ones in rc.1.

See also radiantearth/stac-api-spec#312

I'm not sure which one of the constants if for ogcapi-features though, so the changes may need to be swapped.

Looking at this, the question also arises why for example https://api.stacspec.org/v1.0.0-rc.1/ogcapi-features#sort is not used anywhere in stac-fastapi?

[geospatial-jeff]

Looking at this, the question also arises why for example https://api.stacspec.org/v1.0.0-rc.1/ogcapi-features#sort is not used anywhere in stac-fastapi?

The sort extension currently uses https://api.stacspec.org/v1.0.0-rc.1/item-search#sort (see here), @m-mohr should it use the ogcapi-features href instead?

[m-mohr]

The sort extension currently uses https://api.stacspec.org/v1.0.0-rc.1/item-search#sort (see here), @m-mohr should it use the ogcapi-features href instead?

Depends on where it is supported, I think.
.../item-search#sort if it is supported for /search
.../ogcapi-features#sort if it is supported for /collections/...

Similarly for all the others... @geospatial-jeff

[philvarner]

Correct -- except for filter, where we re-use the OGC conformance class binding filter to OAFeat

[m-mohr]

But there are still separate conformance classes, only that there's no "new" one for STAC, right?

[philvarner]

But there are still separate conformance classes, only that there's no "new" one for STAC, right?

correct

[geospatial-jeff]

@philvarner How does it look now? I updated the item search and filter conformance classes, and added the features filter conformance class which was previously missing.