Add VIIRS S-NPP 375m: Temporal Coverage: 20 January 2012 - present

[aapopescu]

Please check if dataset is available at VEDA

If not, please add this data from https://firms.modaps.eosdis.nasa.gov/download/

[lubojr]

USA subset dataset seems to be present in VEDA (if I got the correct one) 1) https://radiantearth.github.io/stac-browser/#/external/staging-stac.delta-backend.com/collections/eis_fire_newfirepix linking to OGC API Features endpoint: 2) https://firenrt.delta-backend.com/collections/public.eis_fire_snapshot_newfirepix_nrt which has the actual detections.

@aapopescu Are we interested in just USA? Then we can have a look at integrating from the above, otherwise we might need to ingest the data to GeoDB.

Fyi @santilland

[santilland]

@AlessandroScremin please help us by integrating global data for 2023 from original data (daily average) EOX to look at integrating VEDAs USA data

[dmoglioni]

@santilland @lubojr I reparsed, integrated and ingested the data on the new collection MODIS_timeseries. Could you please cross-check it? Thank you.

[lubojr]

@aapopescu We would suggest to integrate the data as a daily time entries in the time selection tool and a Custom area draw to retrieve and show the detection point features + additionally custom area draw to get a time series chart of number of detections throughout the year over the custom drawn area (same principle as trucks detections) with the exception that there would be no corresponding MODIS layer underneath - (as was s2l2a on trucks)

The reason for that Sentinel Hub does not have any newer Modis data than 02/2023. Maybe we can find another source if needed?

Is this in line with your expectations on the integration into the dashboard?

cc @santilland

Example of properties of one detection

{
        "id": 2570969,
        "created_at": "2024-06-21T10:29:12.332707+00:00",
        "modified_at": null,
        "geometry": "0101000020E61000008A1F63EE5A42F2BF8E75711B0D201D40",
        "aoi": "7.2813,-1.1412",
        "brightness": "319.3",
        "scan": "3.6",
        "track": "1.8",
        "date_time": "2023-01-10T13:07:00",
        "satellite": "Aqua",
        "instrument": "MODIS",
        "confidence": "20",
        "version": "61.03",
        "bright_t31": "305.1",
        "frp": "41.3",
        "daynight": "D",
        "type": "0"
    }

[lubojr]

• Catalog update in https://github.com/eurodatacube/eodash-catalog/pull/157 - Please review metadata @FedericoRondoni
• Client update in https://github.com/eurodatacube/eodash/pull/2614

https://eodash-trilateral-testing.eox.at/VIIRS_SNPP_2023/?catalog=viirs-snpp-2023&indicator=VIIRS_SNPP_2023&area=POLYGON%28%2880.61465300887551+19.19955232476258%2C84.32773022253578+19.19955232476258%2C84.32773022253578+23.033481644041586%2C80.61465300887551+23.033481644041586%2C80.61465300887551+19.19955232476258%29%29

[lubojr]

:arrow_up: We've integrated the CO S5p PAL from Sentinel Hub additionally as a layer. Also extended S2L2A time interval to +-1 day around the detections (to catch more orbits around the wildfire event). It really shows of the increase of CO drastically.

For example for following area in Greece on 18.7.2023:

https://eodash-trilateral-testing.eox.at/VIIRS_SNPP_2023/?catalog=viirs-snpp-2023&indicator=Modis_SNPP_2023&area=POLYGON%28%2820.555283352918774+35.83843632791326%2C25.541051594620388+35.83843632791326%2C25.541051594620388+41.705431234524156%2C20.555283352918774+41.705431234524156%2C20.555283352918774+35.83843632791326%29%29

[AlessandroScremin]

@lubojr

It's interesting .

i noticed another interesting use case...massive fires with co emissions in turkey but affecting also greece...

2023-08-22

@dmoglioni I think you can show this example at IGARSS as well new multiple layers overlay.

[AlessandroScremin]

@aapopescu @lubojr

I was considering to use also S3 SLSTR F1 FRP products...together with MODIS data and S5P... I think we need only to create a new layer in the configuration as for the S5P CO...or you can retrive it directly from SH. it alraeady a layer for S3 SLSTR

here a screenshot of the product for same date pver turkey/greece 2023-08-22

[lubojr]

@AlessandroScremin We would need a new configuration the same way as for S5P CO.

[AlessandroScremin]

@lubojr se vogliamo provare...poi possiamo decidere se inserirlo o meno

ecco il layer

ID: S3_SLSTR_F1_BRIGHTNESS_TEMPERATURE

e qui leval script

//VERSION=3 const blue_red = [ [273, 0xffffff], [274, 0xfefce7], [283, 0xFDE191], [293, 0xf69855], [303, 0xec6927], [323, 0xaa2d1d], [363, 0x650401], [473, 0x3d0200] ];

const viz = new ColorRampVisualizer(blue_red);

function evaluatePixel(samples) { let val = samples.F1; val = viz.process(val); val.push(samples.dataMask); return val; }

function setup() { return { input: [{ bands: [ "F1", "dataMask" ] }], output: { bands: 4 } } }

[lubojr]

@AlessandroScremin @aapopescu We have integrated the Sentinel-3 SLSTR Brightness temperature daily as a layer and updated the legends according to used layers.

Still to do to merge to eodashboard:

• [ ] review of Markdown and YAMLs