Closed jdries closed 8 months ago
Example STAC reveals that it's not very helpfull: https://catalogue.dataspace.copernicus.eu/stac/collections/SENTINEL-1-RTC/items/N02E040_2020_12_27_02F5EA
Inspection on disk shows that it should be possible to implement logic that finds the right files:
bash-4.4$ ls /eodata/Sentinel-1-RTC/SAR/RTC/2020/12/27/N02E040_2020_12_27_02F5EA
s1_rtc_02F5EA_N02E040_2020_12_27_ANGLE.tif s1_rtc_02F5EA_N02E040_2020_12_27_MASK.tif s1_rtc_02F5EA_N02E040_2020_12_27_VV.tif s1_rtc_02F5EA_N02E040_2020_12_27_metadata.xml
s1_rtc_02F5EA_N02E040_2020_12_27_AREA.tif s1_rtc_02F5EA_N02E040_2020_12_27_VH.tif s1_rtc_02F5EA_N02E040_2020_12_27_metadata.json s1_rtc_02F5EA_N02E040_2020_12_27_userdata.json
it's working, but need to blacklist it on prod so we can do proper testing
excluded from prod
This collection provides sentinel1 gamma0, so very promising. https://catalogue.dataspace.copernicus.eu/resto/api/collections/SENTINEL-1-RTC/search.json?
It even has stac metadata files, maybe this is a good one to implement on top of CDSE stac as well.