You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a plan for the STAC Filtering Extension to support (or allow) the equivalent of the OGC API - Features - Part 3: Filtering queryables-query-parameters conformance class allowing to use more HTTP query parameters directly for filtering ? This would be very useful as it avoids having to implement CQL2 capabilities in the server.
The text was updated successfully, but these errors were encountered:
This behavior is similar to what the (old) STAC API Query extension does for Search, just slightly different and (so far) without mentioning the queryables endoint (there's an issue for it though).
Is that an elegant way to deprecate the Query extension? ;-)
Is there a plan for the STAC Filtering Extension to support (or allow) the equivalent of the OGC API - Features - Part 3: Filtering queryables-query-parameters conformance class allowing to use more HTTP query parameters directly for filtering ? This would be very useful as it avoids having to implement CQL2 capabilities in the server.
The text was updated successfully, but these errors were encountered: