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
In addition it would be great to standardize on these operators in the API layer instead of backends defining their own.
@geospatial-jeff You're referring here to standardizing this within stac-fastapi.extensions to enforce a consistent list on the backends and not looking for clarification from the spec, yes?
Activity
neq
operator? stac-utils/pgstac#120geospatial-jeff commentedon Aug 4, 2022
In addition it would be great to standardize on these operators in the API layer instead of backends defining their own.
philvarner commentedon Aug 4, 2022
they are standardized
https://github.com/stac-api-extensions/query
<operator> can be one of: eq, neq, lt, lte, gt, gte, startsWith, endsWith, contains, in
duckontheweb commentedon Aug 6, 2022
For the PgSTAC backend, this is being tracked by stac-utils/stac-fastapi-pgstac#9
duckontheweb commentedon Aug 6, 2022
@geospatial-jeff You're referring here to standardizing this within
stac-fastapi.extensions
to enforce a consistent list on the backends and not looking for clarification from the spec, yes?