Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query extension uses 'ne' for not equal operator instead of 'neq' #408

Open
philvarner opened this issue Jun 2, 2022 · 4 comments
Open
Labels
api layer pgstac spec Compliance with STAC/OGC specifications sqlalchemy

Comments

@philvarner
Copy link
Collaborator

The Query Extension spec uses 'neq'.

@geospatial-jeff
Copy link
Collaborator

In addition it would be great to standardize on these operators in the API layer instead of backends defining their own.

@philvarner
Copy link
Collaborator Author

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
Copy link
Contributor

For the PgSTAC backend, this is being tracked by stac-utils/stac-fastapi-pgstac#9

@duckontheweb
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api layer pgstac spec Compliance with STAC/OGC specifications sqlalchemy
Projects
None yet
Development

No branches or pull requests

3 participants