Add new datasets: STORY EXTEME POLLUTION (INDIA/PAQUISTAN)

[AparicioSF]

• Carbon monoxide maps - Sentinel-5P

  • [x] Data integration - carbon monoxide N1-CO
  • [x] Yaml configuration
  • [x] eodashboard integration working link

• Fire datasets (VIIRS I-Band) - I think it can be downloaded from here source

  • [x] Data integration (Modis_SNPP_2023)
  • [x] Yaml configuration
  • [x] eodashboard integration working link

• Wind dataset (horizontal winds at 100m) - source

  • [x] Data integration
  • [x] Yaml configuration (in principle working but wrong config)
  • [x] eodashboard integration working (in principle working but wrong config)

• Science Hub Challenge (datasets in Xcube)

  • [x] Data integration, cubes has been made avaialble following "cubes" priority
    • Selviga Sinnathamby-Elie Zoghbi-Natacha Kaminski-[CHALLENGE n°1 extreme air pollution episodes in Northern India and Pakistan] (WInd UV and Tropomi data cubes)
  • [x] Yaml configuration
  • placeholder yaml files have been created for available datasets here
  • PLES team (@FedericoRondoni) feel free to work on branch to add information to YAML files
  • [x] eodashboard integration working integration of 3 datasets received here

[AlessandroScremin]

Carbon monoxide should be already avaialbe as global layer

Fires: VIIRS 375 are avaialbe only till 2021. IF needed for 2023 onlhy MODIS avaialbe and was already ingested in the GEODB

Wind dataset ingested GLOBALLY for 2023.

@FedericoRondoni could you please add the yaml and MD file for Fires (MODIS only) and wind Dataset?

here the references: wind datasets: VIS_ERA5_SINGLELEVEL_WIND_U_100M_GLOBAL > ac99bb32-a94d-4f4f-b8dd-c0098ca07665 evalscript: //VERSION=3 function setup() { return { input: [{ bands: ["WindU100m", "dataMask"], // Specify correct band names here }], output: { bands: 4, sampleType: "UINT8" } }; }

function evaluatePixel(sample) { // Correctly access WindU100m band instead of windu10m var arr = colorBlend(sample.WindU100m, [-4, -3, -2, -1, 0, 1, 2, 3, 4], [ [11,53,135], [11,116,197], [78,181,250], [171,234,243], [244,252,237], [251,212,95], [247,133,0], [221,24,0], [163,1,0] ]);

if (sample.dataMask == 1) { arr.push(255); } else { arr.push(0); }

return arr; }

VIS_ERA5_SINGLELEVEL_WIND_V_100M_GLOBAL > f70007f3-da80-4c23-b3ae-adc8634ca7c7 evalscript: //VERSION=3 function setup() { return { input: [{ bands: ["WindV100m", "dataMask"], // Specify correct band names here }], output: { bands: 4, sampleType: "UINT8" } }; }

function evaluatePixel(sample) { // Correctly access WindV100m band instead of windu10m var arr = colorBlend(sample.WindV100m, [-4, -3, -2, -1, 0, 1, 2, 3, 4], [ [11,53,135], [11,116,197], [78,181,250], [171,234,243], [244,252,237], [251,212,95], [247,133,0], [221,24,0], [163,1,0] ]);

if (sample.dataMask == 1) { arr.push(255); } else { arr.push(0); }

return arr; }

[santilland]

Needs to be for 2023, will be checked for Fire datasets (VIIRS I-Band)

[FedericoRondoni]

@santilland @lubojr, concerning the Fire story MODIS dataset, I have checked, and the YAML file is already present. I think you created it. I have applied some changes related to the details of the dataset and added the GeoDB ones as resources. I don't know what the Collection-only resource is or if the GeoDB is correctly accessed (it creates some issues). It would be great if you could clarify this point for this and future indicators.

In any case, I think that for this story, we are good.

Here you can find the pull request: https://github.com/eurodatacube/eodash-catalog/pull/183 And here is the one for the assets: https://github.com/eurodatacube/eodash-assets/pull/54

[santilland]

Hello @FedericoRondoni yes, you are correct, Lubo already integrated this dataset. The collection-only resource is something we use when special functionality is needed in the client that has not yet been mapped to STAC based logic. So, the MODIS dataset combines multiple datasets using an area selection. So not all the data in geodb can be shown at once. We are working on defining a STAC based process definition that will replace this approach in the future. So for uncommon, non standard data integration we can take care of integration. You can find the current integration here: https://www.eodashboard.org/explore?indicator=Modis_SNPP_2023 I will remove the for now unnecessary Resource configuration you added to the Yaml file, which seems to create an issue.

[santilland]

@FedericoRondoni i pushed a commit to your branch, make sure you do a pull before continuing your edits

[FedericoRondoni]

@FedericoRondoni i pushed a commit to your branch, make sure you do a pull before continuing your edits

Hi @santilland I'm not sure I know what you mean. I don't see any action from my side to be done. Sorry in advance if it is a silly question, but I still don't know all the GitHub aspects.

[santilland]

@FedericoRondoni if you are working directly on github, all should be fine, sorry for the confusion. It would only be necessary to do a git pull if you are working in the branch locally on your computer and then pushing the changes

[aapopescu]

@FedericoRondoni , here is the JN with the information for the yamls of the "maps generated from study" 3_OpenChallengeNotebook[RMSH]-[Challenge1]Sinnathamby_Kaminski_Zoghbi.ipynb.zip

[FedericoRondoni]

YAML files ready and pulled with this request https://github.com/eurodatacube/eodash-catalog/pull/186