`/search` with `bbox` crossing antimeridian does not work as expected

[mcucchi9]

The description for the bbox query parameter in the item-search STAC API documentation states that

For WGS 84 longitude/latitude the values are in most cases the sequence of minimum longitude, minimum latitude, maximum longitude and maximum latitude. However, in cases where the box spans the antimeridian the first value (west-most box edge) is larger than the third value (east-most box edge).

From what I understand, I would say that a STAC compliant /search endpoint should allow specifying antimeridian-crossing bounding boxes simply by setting the first value greater than the third value, such as

/search?bbox=178,-45,-178,45

Anyway I see that such a request does not work as expected, behaving instead in the same way as

/search?bbox=-178,-45,178,45

How am I suppose (if that is possible at all) to submit antimeridian-crossing bbox query parameter?
And, if that is not possible with the current implementation of stac-fastapi-pgstac, wouldn't this make it not fully compliant with the STAC API specification?

System setting

• stac-fastapi-pgstac: 6.1.0
• pgstac: 0.9.8

[vincentsarago]

stac-fastapi-pgstac doesn't change the bbox parameter. I think this should be raised at pgstac level https://github.com/stac-utils/pgstac