(not sure if this is the best place to report this, so feel free to refer to a better place)
"bbox":[-179.9999999,-79.97868240000001,179.9999999,80.0233214],
"geometry": {
"type": "MultiPolygon",
"coordinates": [
[
[
[-1e-8, 80.0233214],
[-1e-8, 80.0223214],
[-0.0111564000000044, 80.0223214],
[-179.9999999, 80.0223214],
[-179.9999999, 80.0233214],
[-1e-8, 80.0233214]
]
],
[
[
[-179.9999999, -79.97868240000001],
[-179.9999999, -79.9776824],
[-0.0111564000000044, -79.9776824],
[-1e-8, -79.9776824],
[-1e-8, -79.97868240000001],
[-179.9999999, -79.97868240000001]
]
],
[
[
[179.9999999, 80.0233214],
[179.9999999, -79.97868240000001],
[1e-8, -79.97868240000001],
[1e-8, -79.9776824],
[179.9776872, -79.9776824],
[179.9776872, 80.0223214],
[1e-8, 80.0223214],
[1e-8, 80.0233214],
[179.9999999, 80.0233214]
]
]
]
}
(not sure if this is the best place to report this, so feel free to refer to a better place)
The STAC items from https://stac.dataspace.copernicus.eu/v1/collections/clms_lst-tci_global_3km_10daily_v3_cog seem to have degenerate geoemetries, causing broken spatial filtering in STAC API requests.
for example, STAC API request with a simple bbox around lon=3,lat=50:
https://stac.dataspace.copernicus.eu/v1/search?limit=100&bbox=3.0%2C50.0%2C3.1%2C50.1&datetime=2025-09-01T00%3A00%3A00Z%2F2025-09-09T23%3A59%3A59.999000Z&collections=clms_lst-tci_global_3km_10daily_v3_cog
returns 0 matches
removing the
bboxparameter returns 1 match: https://stac.dataspace.copernicus.eu/v1/search?limit=100&datetime=2025-09-01T00%3A00%3A00Z%2F2025-09-09T23%3A59%3A59.999000Z&collections=clms_lst-tci_global_3km_10daily_v3_cogwhich contains item https://stac.dataspace.copernicus.eu/v1/collections/clms_lst-tci_global_3km_10daily_v3_cog/items/c_gls_LST10-TCI_202509010000_GLOBE_GEO_V3.0.1_cog
which has this bbox and geometry:
which looks like this (a multipolygon of three razor-thin polygons):