1. General Information / links / how to start:


 

New STAC Catalogue: https://stac.dataspace.copernicus.eu/v1

New STAC Browser: https://browser.stac.dataspace.copernicus.eu

2. Friendly User Testing high level plan

TaskWhen
New STAC Catalogue Friendly user Testing03-13.12.2024
FUT testing review (STAC API Catchup meeting) and decision point16.12.2024


3. Testing feedback


WhoStatusComment

JM

Fixed

https://stac.dataspace.copernicus.eu/v1/api

returns 

{
  "code": "RuntimeError",
  "description": "Cannot update undefined schema for $ref=#/components/schemas/stac_fastapi__pgstac__extensions__query__Operator-Input__1"
}


Jan: Problem described here: https://github.com/stac-utils/stac-fastapi-pgstac/issues/173

JMMostly fixed. Still CQL-2 text seems to have issues. Is the product type necessary for all collections as some of them contain only one product type e.g. L2A
https://stac.dataspace.copernicus.eu/v1/queryables

are only the minimum cross collection search parameters: id, date, geometry
I would have expected an extended set (e.g. including product type)

JMLink removed as it will be obsolete once the Odata  is decomissioned.
From https://stac.dataspace.copernicus.eu/v1/collections/sentinel-1-grd/items/S1A_EW_GRDM_1SSH_20241130T001228_20241130T001333_056776_06F825_E84D_COG 

      "rel": "via",
      "href": "https://datahub.creodias.eu/odata/v1/Products?$filter=((Name%20eq%20%27%27))&$expand=Attributes&$expand=Assets"

I note this isn't available for Sentinel-2 items, if to be included I would have expected from something like

      "href": "https://catalogue.dataspace.copernicus.eu/odata/v1/Products?$filter=((Name%20eq%20%27S1A_EW_GRDM_1SSH_20241130T001228_20241130T001333_056776_06F825_E84D_COG%27))&$expand=Attributes&$expand=Assets"
JMfixed
From https://stac.dataspace.copernicus.eu/v1/collections/sentinel-1-grd/items/S1A_EW_GRDM_1SSH_20241130T001228_20241130T001333_056776_06F825_E84D_COG
 "assets": {
    "hh": {
      "href": "s3://DIAS/Sentinel-1/SAR/EW_GRDM_1S-COG/2024/11/30/S1A_EW_GRDM_1SSH_20241130T001228_20241130T001333_056776_06F825_E84D_COG.SAFE/measurement/s1a-ew-grd-hh-20241130t001228-20241130t001333-056776-06f825-001-cog.tiff"

I would have expected s3://eodata/ ...
JMTBD
From https://stac.dataspace.copernicus.eu/v1/collections/sentinel-1-grd/items/S1A_EW_GRDM_1SSH_20241130T001228_20241130T001333_056776_06F825_E84D_COG

   "eopf:origin_datetime": "2024-11-30T00:37:28.440834Z"

I would have expected the publication time of the non-COG version of the GRD