Add some YAML

[FedericoRondoni]

CDS7_windu_ERA5-SingleLevel_100m_GLOBAL CDS8_windv_ERA5-SingleLevel_100m_GLOBAL Modis_SNPP_2023 SSLC1_Seasonal_S1_AMP_hv_interferometric_coherence SSLC2_Seasonal_S1_COH12_hh_interferometric_coherence OHC300_Ocean_Heat_Content_upper_300m ENSST_by_GCOM-W-AMSR_JAXA SLSTR1_Sentinel-3-SLSTR-L2-LST SLSTR2_Sentinel-3-SLSTR-L2-WST NELST_ECOSTRESS_LST

[dmoglioni]

@lubojr / @santilland

• we changed theme of Land Surface Temperature (Sentinel-3 SLSTR L2) to "extreme events" und updated the corresponding layer id. You should be able to visualize the data correctly now. We checked it on the dashboard environment and it works even though the data loading is slow (not sure if the bottleneck is on SH or on the dashboard side).
  cc @aapopescu

[lubojr]

It is in this case the sentinel hub being slower.

@aapopescu We have added a legend and evalscript definition for the OHC300_Ocean_Heat_Content_upper_300m dataset.

For the rest which are available already, we did not receive an evalscript to create the legend against:

• Sentinel-3 SLSTR L2
• ENSST_by_GCOM-W-AMSR_JAXA

Also @dmoglioni @FedericoRondoni, you can define the legend.json and evalscript for getting the statistics in a similar manner like we did now: eurodatacube/eodash-assets@5916c04 while the new legend was generated by this script: https://github.com/eurodatacube/eodash-assets/blob/main/generators/cm_legend_generator.py

Summarized:

Finished: CDS7_windu_ERA5-SingleLevel_100m_GLOBAL CDS8_windv_ERA5-SingleLevel_100m_GLOBAL Modis_SNPP_2023 OHC300_Ocean_Heat_Content_upper_300m

Partially available: ENSST_by_GCOM-W-AMSR_JAXA SLSTR1_Sentinel-3-SLSTR-L2-LST

Not available: SSLC1_Seasonal_S1_AMP_hv_interferometric_coherence SSLC2_Seasonal_S1_COH12_hh_interferometric_coherence SLSTR2_Sentinel-3-SLSTR-L2-WST

[FedericoRondoni]

@lubojr @santilland the S1_AMP and S1_COH12 now should work. However, I see there is an issue with the SNPP yaml file. Can you check what it is and if it is something we have to change?
Thanks!

[lubojr]

@FedericoRondoni I have resolved the merge conflict about the SNPP file.

How do we decide CDS7_windu_ERA5-SingleLevel_100m_GLOBAL.yaml and above comments from Anca? It is not necessary to add the same dataset YAML again when we already have the windu and windv variables from CDS in the RACE dashboard.

Are the datasets the same? If yes, it would just be necessary to reference the CDS3_wind_10m_u and CDS4_wind_10m_v and then delete possbly both CDS5_wind_100m_u_newDeli CDS6_wind_100m_v_newDeli and CDS7_windu_ERA5-SingleLevel_100m_GLOBAL CDS8_windv_ERA5-SingleLevel_100m_GLOBAL? - #192

[FedericoRondoni]

@FedericoRondoni I have resolved the merge conflict about the SNPP file.

How do we decide CDS7_windu_ERA5-SingleLevel_100m_GLOBAL.yaml and above comments from Anca? It is not necessary to add the same dataset YAML again when we already have the windu and windv variables from CDS in the RACE dashboard.

Are the datasets the same? If yes, it would just be necessary to reference the CDS3_wind_10m_u and CDS4_wind_10m_v and then delete possbly both CDS5_wind_100m_u_newDeli CDS6_wind_100m_v_newDeli and CDS7_windu_ERA5-SingleLevel_100m_GLOBAL CDS8_windv_ERA5-SingleLevel_100m_GLOBAL? - #192

CDS3 and CDS4 are different datasets since they have a 10m resolution, while CDS5 and CDS6 are just a crop of CDS7 and CDS8. From our point of view, if they are not necessary for the stories purpose they can be removed and we can reference CDS7 and CDS8 inside the story

[lubojr]

@FedericoRondoni Thanks for confirmation. I just did the change in both the catalog and the story eodashMarkdown_EXTREME_POLLUTION_2

[lubojr]

Confirmed on meeting that is good to merge once assets are finalized and merged. Latest friday midday.