rcodede

This package is in the earliest stages of development and should be used with caution.

The goal of rcodede is to simplify the usage of the CODE-DE satellite data repository with R and provide functions for basic processing steps with the esa SNAP Graph Processing Tool.

Installation

You can install the development version from GitHub with:

install.packages("devtools")
devtools::install_github("felixlobert/rcodede")

If the included functions for the processing of satellite data shall be used, esa SNAP has to be installed on the system and the SNAP Graph Processing tool (GPT) has to be executable from the command line. You can check this by typing “gpt” to the command line. If the console shows the GPT context menu after you press enter, you are ready to go.

Dockerized SNAP

Alternatively, you can use a dockerized version of SNAP which is less prone to errors. The image is automatically installed when you use a processing function from rcodede and all file paths to the orbit files and the DEM provided by CODE-DE are set. Just make sure docker is installed on your machine and docker = TRUE is set when the processing function is called.

Examples

Query available scenes

This is a basic example which shows you how to query available Sentinel-1 scenes for a given area of interest and multiple filter criteria. The function rcodede::getScenes creates an HTTP-GET request for the CODE-DE EO Finder API and processes the results for an easy usage. ?getScenes shows you, which criteria are supported at the moment.

# load simple features library
library(sf)

# Create example AOI
aoi <- c(10.441054, 52.286959) %>%
  sf::st_point() %>%
  sf::st_sfc(crs = 4326)

# load rcodede package
library(rcodede)

# Query footprints and metadata of available scenes for the AOI and given criteria
scenes <- 
  getScenes(
    aoi = aoi,
    startDate = "2019-01-01",
    endDate = "2019-01-15",
    satellite = "Sentinel1",
    productType = "SLC",
    view = T
  )

This table shows the 5 top entries of the resulting sf object:

date	platform	orbitDirection	relativeOrbitNumber	centroidLat	centroidLon	productPath	numberAoiGeoms	footprint
2019-01-02	S1B	ascending	117	52.32027	9.727361	/codede/Sentinel-1/SAR/SLC/2019/01/02/S1B_IW_SLC__1SDV_20190102T170751_20190102T170818_014318_01AA3A_FF22.SAFE	1	POLYGON ((7.595577 52.91906…
2019-01-03	S1A	ascending	44	52.16575	11.819360	/codede/Sentinel-1/SAR/SLC/2019/01/03/S1A_IW_SLC__1SDV_20190103T170016_20190103T170044_025316_02CD10_3344.SAFE	1	POLYGON ((9.6748 52.76576, …
2019-01-05	S1A	descending	66	51.98302	10.031724	/codede/Sentinel-1/SAR/SLC/2019/01/05/S1A_IW_SLC__1SDV_20190105T053336_20190105T053403_025338_02CDE5_DD48.SAFE	1	POLYGON ((11.62581 50.96621…
2019-01-06	S1B	descending	168	52.72275	12.320578	/codede/Sentinel-1/SAR/SLC/2019/01/06/S1B_IW_SLC__1SDV_20190106T052428_20190106T052456_014369_01ABD6_2CFC.SAFE	1	POLYGON ((13.9049 51.68368,…
2019-01-08	S1A	ascending	117	52.37313	9.685434	/codede/Sentinel-1/SAR/SLC/2019/01/08/S1A_IW_SLC__1SDV_20190108T170833_20190108T170900_025389_02CFCA_312E.SAFE	1	POLYGON ((7.54464 52.97379,…

Basic Processing

If the CODE-DE satellite data repository is mounted to the used machine, processing steps can be directly executed to the queried scenes.

Coherence Estimation

The next example shows the estimation of the interferometric coherence for two subsequent Sentinel-1 scenes. To ensure similar acquisition geometries of the scenes, only one relative orbit is selected.

# filter for scenes from same orbit to ensure same acquisition geometry
scenes.filtered <-
  scenes %>%
  dplyr::filter(relativeOrbitNumber == 117)

mapview::mapview(
  x = scenes.filtered,
  alpha.regions = .15,
  map.types = "Esri.WorldImagery",
  zcol = "relativeOrbitNumber"
) +
  mapview::mapview(
    x = aoi,
    color = "black",
    col.regions = "white",
    alpha.regions = .5,
    legend = FALSE
  )

The function rcodede::estimateCoherence creates a command for the esa SNAP Graph Processing Tool that is executed in the background if execute = TRUE. A pre-built SNAP-Workflow delivered with the package is then applied to the selected scenes. If execute = FALSE, the command is returned as string instead. The output is written to a defined path and is returned if return = TRUE. Several processing parameters such as the spatial resolution of the output raster or the desired polarizations can be set.

# estimate the coherence for the first two scenes in the sf object
coherence <-
  estimateCoherence(
    scene1 = scenes.filtered$productPath[2],
    scene2 = scenes.filtered$productPath[1],
    fileName = "coherence.tif",
    resolution = 10,
    polarisation = "VH",
    aoi = aoi,
    aoiBuffer = 300,
    execute = TRUE,
    return = TRUE
  )

The created coherence raster or stack can then be plotted or further processed:

# plot the returned coherence raster
mapview::mapview(
  x = coherence$layer,
  layer.name = paste0("Coherence VH\n", scenes.filtered$date[2]),
  alpha = .5,
  na.color = "transparent",
  map.types = "Esri.WorldImagery"
) +
  mapview::mapview(
    x = aoi,
    color = "black",
    col.regions = "white",
    alpha.regions = .5,
    legend = FALSE
  )