stac-fastapi
stac-fastapi copied to clipboard
Query extension uses 'ne' for not equal operator instead of 'neq'
https://github.com/stac-utils/stac-fastapi/blob/162a1a2c324b4c2bfe3451f7ae19d7840a0e0452/stac_fastapi/pgstac/stac_fastapi/pgstac/extensions/query.py#L18
The Query Extension spec uses 'neq'.
In addition it would be great to standardize on these operators in the API layer instead of backends defining their own.
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
For the PgSTAC backend, this is being tracked by stac-utils/stac-fastapi-pgstac#9
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?