Global Coherence Sentinel-1

[aapopescu]

Please integrate this dataset
https://asf.alaska.edu/datasets/daac/global-seasonal-sentinel-1-interferometric-coherence-and-backscatter-dataset/

[lubojr]

There does not seem to be a viewing API.
Data would need to be ingested to SH. @AlessandroScremin

[AlessandroScremin]

@lubojr and @aapopescu

we should agree on the approach for defining the sensing time and season definition that is required in SH when ingesting datasets.

Those dataset are Split as single global tif per type of analyses for the season, or tiles tif for the season. Spring, Summer, Fall, Winter. So no sensing time indication. The provider said the season is considered: """in the dataset filenames seasons were referred to as northern hemisphere winter (DJF), spring (MAM), summer (JJA), and fall (SON)"""

this make me think to definitions of spring periods: So what sensing time could we assign to the season? the middle value of which "season definition"?

Astronomical season 21 March – 21 June Meteorological season 1 March – 31 May Solar (Celtic) season 1 February – 30 April [Southern temperate zone](https://en.wikipedia.org/wiki/Southern_temperate_zone) Astronomical season 23 September – 22 December Meteorological season 1 September – 30 November Solar (Celtic) season 1 August – 31 Octobe).

Furthermore, looking at the the datasets, the images are split by metrics (AMP, COHxx, rho, tau, rmse) with different information/parameters...do we have one in particular already defined?

Global__100ppd.tif
SEASON = winter, spring, summer, or fall (referring to Northern hemisphere seasons)
POLARIZATION = vv, vh, hh, or hv
METRIC = AMP, COHxx, rho, tau, rmse
xx = 06, 12, 18, 24, 36, 48

[lubojr]

• review interval of start/end from SH STAC to our STAC catalog - for seasonal data (should be there), just to double check @lubojr

[lubojr]

As for seasons: Update: I have checked our catalog generator implementation and if there is just a single datetime in the STAC response for an Item, we take that as a single date, alternatively if a datetime is not set, but start_datetime and end_datetime are, then we take those two and compose an interval out of them for a WMS query. (start/end).

I have checked an example from N1_NO2 dataset and only datetime is present in the STAC Item, so that is what we will show, a single date. I would therefore suggest mid of the season for sensing date.

[aapopescu]

@AlessandroScremin let us start with this product:
Global mosaicked tiles as cloud optimized GeoTIFFs at 0.01-degree pixel spacing for eachof the computed metrics
Seasons: winter, spring, summer, fall
Polarisation: hv
Metri: AMP
xx: 12

So we should have 4 products ingested to start with

[aapopescu]

Hi, @dmoglioni, can you please help with this one?

[AlessandroScremin]

@aapopescu

cc @dmoglioni @FedericoRondoni

with @dmoglioni we ingested the 4 season dataset for the metric AMP hv and the COH12 hh (for COH12 we have only hh or vv) for this test we used the COH12 hh.

Here two screenshot of how they look like in the greyscale

this is the AMP hv

and this one is the COH12 hh

we ingested already the 4 seasons for each of the metric, so if they are ok for you as well we can create the YAML and MD file to add the collection to the stac catalogue

[FedericoRondoni]

YAML files created here eurodatacube/eodash-catalog#183

The assets need to be added @dmoglioni

[FedericoRondoni]

@AparicioSF currently working on the description

[FedericoRondoni]

@aapopescu I think that this is issue can be closed since everything is online now

[aapopescu]

@dmoglioni , I cannot see this dataset online, please test

[dmoglioni]

@AparicioSF please verify if .yaml and .md were created

[AparicioSF]

Hi. Yes @dmoglioni , they were created in the past.
Markdown is here:
https://github.com/eurodatacube/eodash-assets/blob/main/collections/SSLC2_Seasonal_S1_COH12_hh_interferometric_coherence/SSLC2_Seasonal_S1_COH12_hh_interferometric_coherence.md

For the yaml, I made (just now) a change/update on the name inside of the yaml, that could have been the reason for not showing up?:
eurodatacube/eodash-catalog#203

[dmoglioni]

@AparicioSF thank you!
@santilland could you try retrieving the data now?

[santilland]

Strangely some of the indicators from the original pull request were no longer configured in the eodashboard catalog, i created a pull request to re-add them, can be seen here:
https://eodash-trilateral-staging.eox.at/explore?catalog=collections_missing
Will merge this later into production again to make sure they are there, once done i would close the issue.

[santilland]

Data is available, closing the issue