search

eurodatacube / eodash

Software behind the RACE dashboard by ESA and the European Commission (https://race.esa.int), the Green Transition Information Factory - GTIF (https://gtif.esa.int), as well as the Earth Observing Dashboard by NASA, ESA, and JAXA (https://eodashboard.org)
https://race.esa.int
MIT License
89 stars 43 forks source link

Global Coherence Sentinel-1 #2580

Open aapopescu opened 1 month ago

aapopescu commented 1 month ago

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

lubojr commented 1 month ago

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

AlessandroScremin commented 1 month ago

@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 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 commented 3 weeks ago
lubojr commented 3 weeks ago

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 commented 2 weeks ago

@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