add query/sort/fields extension support for item_collection

[vincentsarago]

This is not yet ready but will love some feedback @hrodmn @m-mohr

This PR does:

• add fields, sort and query extension for item_collection endpoint

[vincentsarago]

register /collections/{col}/queryables endpoint for item_collection

[hrodmn]

@vincentsarago I am sure you have already thought of this but would it make sense to define SearchFilterExtension, ItemCollectionFilterExtension and CollectionSearchFilterExtension in stac-fastapi rather than in this package? Those seem like classes that will be useful for any backend that attempts to support this web of extensions.

[hrodmn]

I am struggling to find the problem that the refactor solves 😅
The reason the existing FilterExtension class could use some refactoring is that a user could decide to not add filter to the list of extensions for the item collection endpoint but the conformance class would still be present because it is automatically included in the conformance classes if you register the extension for item search.

[vincentsarago]

well it seems I broke something 🙈

Not sure what's going on! The /queryables endpoint should return application/schema+json but right now application/json

from stac_fastapi.extensions.core import FilterExtension, SearchFilterExtension

FilterExtension().response_class
>>> stac_fastapi.api.models.JSONSchemaResponse

SearchFilterExtension().response_class
>>> stac_fastapi.api.models.JSONSchemaResponse

maybe it's something else 😬

Edit: fixed in stac-utils/stac-fastapi#796

[vincentsarago]

we now have a pystac issue https://github.com/stac-utils/stac-fastapi-pgstac/actions/runs/13055953384/job/36438949990?pr=192

[m-mohr]

The issue looks unrelated (bands). Weird. Is that maybe an issue with the recently released upgrade of pystac to v1.1.0?

[vincentsarago]

@m-mohr yeah pretty sure this is related

[m-mohr]

Pinning pystac to the latest 1.0.0 version probably helps until the tests are migrated to 1.1.0.

[vincentsarago]

this is the error we are getting

            # The way bands were declared in assets changed.
            # In 1.0.0-beta.1 they are inlined into assets as
            # opposed to having indices back into a property-level array.
            if "eo:bands" in obj["properties"]:
                bands = obj["properties"]["eo:bands"]
                for asset in obj["assets"].values():
                    if "eo:bands" in asset:
                        new_bands: list[dict[str, Any]] = []
                        for band_index in asset["eo:bands"]:
>                           new_bands.append(bands[band_index])
E                           TypeError: list indices must be integers or slices, not dict

maybe we have to update our items

stac-fastapi-pgstac/tests/data/test_item.json

Lines 154 to 162 in df4c12a

	"eo:bands": [
	{
	"gsd": 30,
	"name": "SR_B1",
	"common_name": "coastal",
	"center_wavelength": 0.44,
	"full_width_half_max": 0.02
	}
	],

cc @gadomski @emmanuelmathot

[vincentsarago]

I think we're good, I just tried locally with migrate=False (the behaviour was changed in https://github.com/stac-utils/pystac/compare/v1.12.0..v1.12.1)

[gadomski]

Yeah, I second-guessed switching migrate after we did it b/c I knew it'd break tests. Might have been a mistake ...

[vincentsarago]

@gadomski it's fine 👍