Skip to content

Extensions defined in ENABLED_EXTENSIONS environment variable #348

Description

@underchemist

Hello! I'm trying clarify for my own understanding the behaviour of stac-fastapi-pgstac when using ENABLED_EXTENSIONS, specifically the pagination extension.

We're running stac-fastapi-pgstac==6.2.1 and pgstac==0.9.8

from #114 (comment) it seems that paging links are returned from pgstac directly. When we use ENABLED_EXTENSIONS=query,sort,filter,pagination,collection_search things work as expected with paging links e.g. GET /search?limit=1:

  • next link is included in response
  • requesting subsequent pages with next link href returns next page

When pagination is not included in ENABLED_EXTENSIONS I observe:

  • next link included in response
  • requesting subsequent pages with next link href returns first page only

As a caveat I also observe that when collection_search is not included in ENABLED_EXTENSIONS as in

if self.extension_is_enabled("CollectionSearchExtension"):
the client instead makes a query to all_collections instead of collection_search in pgstac which results in just a LIST response of collections and no next links as expected.

Let me know if this is a correct-ish interpretation? I'm wondering if it's necessary to have pagination extension as something you can enable/disable since it seems pagination is now on pgstac side, at least for /search and /collections/{collection id}/items model responses.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions