Skip to content

About

EGU How to share your remote sensing data demo

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 

Repository files navigation

EGU-presentation

EGU How to share your remote sensing data demo

  • Once upon a time, sharing a remote sensing dataset involved either sending a .zip file over email, or uploading the file to an exchange server, where the other user could download it. Or copying it on a hard drive and travelling

  • The idea behind cloud storage platforms such as CDSE is that instead of sharing the actual data file, you can share the exact code used for creating it, and it will be faster to re-generate the dataset on the cloud but still provide exactly the same results

  • So how do you generate a custom data product? On CDSE, the easiest way is in Copernicus Browser, using custom evalscripts. For example, here is a true color image of the recent Lesachtal wildfire: link.dataspace.copernicus.eu/veic However, here you don't see much, the smoke gets in the way.

  • here is a better way to visualize it, a custom script that uses Sentinel-2-s short wave infrared bands to highlight the radiative power of the fire: https://custom-scripts.sentinel-hub.com/custom-scripts/sentinel-2/markuse_fire/

  • this is the example of the Lesachtal fire visualized using the script https://link.dataspace.copernicus.eu/2adv

  • So any specific combination of data source(s) and analysis algorithm(s) is called a configuration. If you have a preferred combination, you can save that in Copernicus Browser, and use it next time when you open the Browser. Here is an example of the same fire:

  • EGU_how_to_share_wildfire configuration: This involves specific layers for estimating fire risk, identifying fires, guiding firefighting efforts and assessing the damage

Overview of configuration in Copernicus Browser

2 separate configurations: EGU_how_to_share_wildfire_Sentinel_2

  • Active fire with Markuse Fire
  • fire damage sentinel-2 burnt area)
  • sentinel-2 true color (for visual interpretation)

EGU_How_to_share_wildfire_CLMS

  • fire damage CLMS burnt area (standard product)
  • fire damage evapotranspiration (for assessing vegetation health)
  • risk land cover (for assessing risk to buildings, roads etc)
  • risk land surface temperature hourly (for assessing immediate fire risk)
  • risk latent heat flux (for understanding how susceptible vegetation is to fire)
  • risk soil water index (for understanding local wetness/dryness)
  • active fire terrain model (for estimating fire spread and containment effort)
  • sentinel-2 true color (for visual interpretation)

is this a comprehensive set of custom data products for managing and understanding wildfires?

how do you build such a configuration? Walkthrough of CDSE Sentinel Hub configuration utility: https://shapps.dataspace.copernicus.eu/dashboard/#/configurations/

How do you share a configuration with somebody?

Copy to another account - and they will have access to this config as well in their Copernicus Browser

Can you add such a configuration to an external viewer?

QGIS sentinel hub plugin

Alternative pathway in QGIS: new WMS layer

  • In QGIS layer manager, just choose "New WMS Layer"
  • in the dashboard, under "service endpoints" select WMS, and copy the URL
  • paste it to the QGIS wizard
  • add your credentials
  • your layer is set up

this will work similarly in other desktop GIS software (including smartphone applications)

Further reads

About

EGU How to share your remote sensing data demo

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors