Within the Copernicus Data Space Ecosystem there are two STAC catalogues available:
1. Production catalogue available here: https://radiantearth.github.io/stac-browser/#/external/catalogue.dataspace.copernicus.eu/stac
2. Development catalogue available here: https://radiantearth.github.io/stac-browser/#/external/pgstac.demo.cloudferro.com
CDSE querables attributes for Senitnel-2 L1C:
CDSE STAC development roadmap
0. Simplify the geofootprint which is the largest attribute in the STAC response and slows down spatial querying (especially relevant for S-3 and S5P) ← to be provided by the Bureau d'Etude
1. Add the 20m R,G,B,NIR Sentinel-2 bands to the STAC ← waiting from the feedback from STAC community how to correctly implement this (as a separate asset or an alternate-asset)
2. Disable the overview displaying on items/assets level for selected collectios e.g. Senitnel-3 where overviews generated in satellite projection is not displayed correctly.
3. Implement the CEOS-ARD extension for Level-2 and Level-3 products https://github.com/stac-extensions/ceos-ard First would be the Senitnel-2 L2A (stac item example https://github.com/stac-extensions/ceos-ard/blob/main/examples/optical-sr/item.json), then Sentinel-3 and Sentinel-5P products. There is no CEOS ARD for radar data yet. Currently it is only for CEOS ARD PFSes (so surface reflectance and temperature, and aquatic reflectance)
4. Populate the development catalogue with the Sentinel-2 L1C and L2A products and make the online version of the catalogue publicly available for testing
5. Add new collections based on the on the stac-tools for Sentinel-1 (https://github.com/stactools-packages/sentinel1), Sentinel-3 (https://github.com/stactools-packages/sentinel3), Sentinel-5P (https://github.com/stactools-packages/sentinel5p) These collections will conform to the new Sentinel's extensions: https://github.com/stac-extensions/sentinel-1 , https://github.com/stac-extensions/sentinel-3 , https://github.com/stac-extensions/sentinel-5p
6. Migrate some generic attributes from platform specific extension to more general extensions such as eo and sar. The rest of missions specific attributes (red crosses) should be maintained in the mission specific extensions not in the EOPF extension: https://github.com/CS-SI/eopf-stac-extension
7. Add to STAC Functionality of online/offline products. Add on demand product generation (url-s)
Missing STAC functionalities to be potentially implemented in new STAC extensions:
- Hiding entire extensions in the https://github.com/stac-api-extensions/fields This could mimic the Odata $expand option for advanced, ESA internal extensions.
- Hiding items and assets within a Collection by an AOI ← e.g. useful for hiding data over Ukraine
- User levels and permissions to filter the Json response for general & expert CDSE users.