Pgstac queryables

[bitner]

Related Issue(s):

• Partially fixes Queryables link relation and endpoint issues #469. This does not add the queryables link to / or /collections/{collection_id}/queryables to keep the scope of this fix to the pgstac backend. Currently there is no (at least that I am aware of) mechanism to inject extra links as part of an extension, so hardcoding the queryables links will result in bad links when the FilterExtension is not enabled.

Description:
Adds support to pgstac backend queryables functionality added in pgstac v0.6.8.

• Adds /queryables endpoint
• Adds /collections/{collection_id}/queryables endpoint

PR Checklist:

• Code is formatted and linted (run pre-commit run --all-files)
• Tests pass (run make test)
• Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
• Changes are added to the CHANGELOG.

[geospatial-jeff]

Currently there is no (at least that I am aware of) mechanism to inject extra links as part of an extension, so hardcoding the queryables links will result in bad links when the FilterExtension is not enabled.

You may currently do this with conformance classes but not links. This will be easier to add once #432 is resolved. #472 is part of that larger effort and moves in the direction of making links easier to customize but I hadn't thought of the case where an extension requires additional links so I created #475 to track that.

[geospatial-jeff]

LGTM 👍

[carderne]

Sorry for possibly misplaced question but:
Currently setting a bbox in the Collection Filter dialog in stac-browser doesn't work with stac-fastapi - it just calls /collections{collection_id}/items with bbox=1,2,3,4, which is ignored in the route.

Will this fix that? If not where should I go looking to get that to work? (Aside from monkey-patching in some code to use bbox in that route...)

[bitner]

Sorry for possibly misplaced question but: Currently setting a bbox in the Collection Filter dialog in stac-browser doesn't work with stac-fastapi - it just calls /collections{collection_id}/items with bbox=1,2,3,4, which is ignored in the route.

Will this fix that? If not where should I go looking to get that to work? (Aside from monkey-patching in some code to use bbox in that route...)

No, this does not add that capability. As far as i know, that is not part of the stac specification. You can bring things like this up by adding an issue rather than replying to unrelated pull requests.

[carderne]

I'm trying to figure out how filtering is "supposed" to work, and whether the issue is with stac-browser, stac-fastapi, or pgstac. There's been a lot of recent activity in all three projects around this, so I didn't want to open an issue if it was already in the process of being resolved. Sorry for wasting your time.

[bitner]

You are not wasting my time, it is totally OK to open up an issue for something like this. It is far better for us to be able to see questions like this there than buried in an unrelated thread. Stac FastAPI and PGStac try to stay as close as possible to the Stac specification at stacspec.org, there are instances where we may be behind in implementing new things in the spec and other times that we may add additional capabilities that are not part of the spec, but that is generally the source of how things are "supposed to work". In particular, the OpenAPI specs for the collections endpoint for the specification is at https://api.stacspec.org/v1.0.0-rc.1/collections/#tag/Core/operation/getLandingPage. As of now, the Stac API specification does not appear to support any filter operations. This is probably an instance of something that stac-browser has implemented that is not part of the specification and that there may be other stac servers that do support that anyway.

…

On Thu, Oct 6, 2022 at 9:19 AM Chris Arderne ***@***.***> wrote: I'm trying to figure out how filtering is "supposed" to work, and whether the issue is with stac-browser, stac-fastapi, or pgstac. There's been a lot of recent activity in all three projects around this, so I didn't want to open an issue if it was already in the process of being resolved. Sorry for wasting your time. — Reply to this email directly, view it on GitHub <#474 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABIHXGQHYFXW5IW65ACX43WB3NXJANCNFSM6AAAAAAQ3ZJ6VY> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

-- ************************************ David William Bitner dbSpatial LLC 612-578-9553

[carderne]

👍 #476