Skip to content

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

@philvarner

Description

@philvarner
Collaborator

The Query Extension spec uses 'neq'.

Activity

geospatial-jeff

geospatial-jeff commented on Aug 4, 2022

@geospatial-jeff
Collaborator

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

philvarner

philvarner commented on Aug 4, 2022

@philvarner
CollaboratorAuthor

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

duckontheweb commented on Aug 6, 2022

@duckontheweb
Contributor

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

duckontheweb

duckontheweb commented on Aug 6, 2022

@duckontheweb
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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @philvarner@duckontheweb@geospatial-jeff

        Issue actions

          Query extension uses 'ne' for not equal operator instead of 'neq' · Issue #408 · stac-utils/stac-fastapi