Basic metadata addition to output products of S1 routines

[kautlenbachs]

Spatio Temporal Asset Catalog (STAC) compatible output

[kautlenbachs]

https://github.com/stac-extensions/sar

[kautlenbachs]

https://pta.data.lit.fmi.fi/stac/catalog/Sentinel-1_daily_mosaiikki/Sentinel-1_daily_mosaiikki_2017-01-02.json

[kautlenbachs]

https://52north.org/delivery/GSV2020/tutorials/Appel_Analyzing_MultiVariable_Earth_Observation_Data_Cubes_Tutorial.pdf

[kautlenbachs]

There are 2-3 possible scenarios after investigation:

• GeoJSON (with STAC) (https://github.com/stac-extensions/sar)
  • Actually a weak standard, have not managed to find to be actually used
  • Need to expand with custom fields to embed metadata when intention is for continued processing (breaks standard?!?!) - suggestion is to use SNAP's ZNAP format's product_metadata.json
• XML
  • Copy SNAP's GeoTIFF + XML format
  • Also possibility to embed XML inside the GeoTIFF (which SNAP also does)
  • CARD4L
  • Currently only for backscatter (https://ceos.org/ard/ )

Easy to do, but probably time consuming, very uncertain if any options above are actually going to be useful -> maybe some simple metadata tags embedded in geotiff of the main things (subswaths, arguments etc) (fast to implement hence possible to implement something else)

[kautlenbachs]

For COG, generate footprints https://docs.sentinel-hub.com/api/latest/api/byoc/

[kautlenbachs]

https://youtu.be/mn6hy0cXGY4?t=179

[kautlenbachs]

Simple plan: Name the GDAL band according to the polarization. Also add polarization to the filename. For coherence add sensing time end according to the secondary scene.

[kautlenbachs]

The most possible candidate would be probably new S1 product's metadata formats - https://sentinel.esa.int/web/sentinel/sentinel-1-ard-normalised-radar-backscatter-nrb-product

[kautlenbachs]

Calibration output:

Coherence: