Following the previous announcement about the release of the new Data Catalogue we would like to inform about additional changes in CREODIAS that will be introduced due to migration to new data sources and further adjustments of metadata. On 20th of February the following changes will be introduced:
- Product paths for some new Sentinel products will be changed according to the attached table. Historical data will not be migrated, it will stay under the current paths, therefore it is recommended to use the Data Catalogue to search for products and retrieve product paths from the response generated by the API.
Example of changed path in the repository for Sentinel-1 GRD IW products:
PRODUCT LOCATION FOR ALL DATA INGESTED BEFORE FEBRUARY 20th: /eodata/Sentinel-1/SAR/GRD/2023/02/19/S1A_IW_GRDH_1SDV_20230119Txxxxxx_20230119Txxxxxx_yyyyyy_zzzzzz_wwww.SAFE
PRODUCT LOCATION FOR ALL DATA INGESTED AFTER FEBRUARY 20th: /eodata/Sentinel-1/SAR/IW_GRDH_1S/2023/02/20/S1A_IW_GRDH_1SDV_20230220Txxxxxx_20230220Txxxxxx_yyyyyy_zzzzzz_wwww.SAFE
- As already announced the product types (value of productType field in the metadata) in the new Data Catalogue will change for multiple collections. The most significant change concerns the Sentinel-1 where the legacy RAW, GRD, SLC and OCN types will be changed to more detailed as described in the attached table.
To allow the users to smoothly migrate from the legacy product types to more detailed product types both new and old values for Sentinels 1,2,3 will be usable in the catalogue search until the end of the migration process to the new Copernicus Data Access Service in June 2023 (https://scihub.copernicus.eu/news/News01130). After the migration only the new product types will be available.
This temporary feature will only be applicable for inclusive search (using =/eq in the OData filter). Mapping will not be present for exclusive search (not/not eq).
Example of changes required for the RESTO API query for Sentinel-2 L1C:LEGACY RESTO API
&status=all&dataset=ESA-DATASETNEW RESTO API
The best performance and flexibility can be achieved when using OData query:
We strongly recommend adopting OData as a replacement for the legacy RESTO API to unlock the full potential of the new CREODIAS data catalogue: https://creodias.eu/eo-data-catalogue-api-manual
Please be advised that if you experience problems or errors while implementing changes or testing your applications using the new catalogue or after the changes introduced on February 20, please contact our Customer Support department at firstname.lastname@example.org