search

GeoscienceAustralia / ga_sar_workflow

InSAR processing workflow used by Geoscience Australia
Apache License 2.0
3 stars 0 forks source link

Dead link in RSAT sensor code #357

Open truth-quark opened 2 years ago

truth-quark commented 2 years ago

The following link is now dead: https://github.com/GeoscienceAustralia/gamma_insar/blob/pygamma_workflow/insar/sensors/rsat2.py#L71

mwheeler commented 2 years ago

Easy to get the info out of archive.org - according to the last snapshot the info was a summary from:

RADARSAT-2 Product Description. MacDonald, Dettwiler and Associates Ltd. RN-SP-52-1238. Issue 1/13: March 21, 2016.

RADARSAT-2 NITF 2.1 Product Format Definition. MacDonald, Dettwiler and Associates Ltd. RN-SP-52-8207. Issue 2/1: May 22, 2015.

RADARSAT-2 Product Format Definition. MacDonald, Dettwiler and Associates Ltd., , RN-RP-51-2713, Issue 1/5. November 24, 2003.

Though those publications, like most RS2 info, is proprietary / probably need some sort of NDA to access those from MacDonald, Dettwiler and Associates.

The relevant info was:

File name Format Required Contents/details
product.xml Extensible Markup Language Yes Key file name. Contains metadata that applies to the data set.
imagery_n.tif GeoTIFF Yes Image data, one file for each polarization channel, where n represents HH or HV or VH or VV, as applicable.
BrowseImage.tif TIFF No Image browse file in TIFF format.
lutSigma.xml Extensible Markup Language Yes, for all products except SSG and SPG Lookup table (LUT) to transform raster values to sigma-nought (sigma0) values.
lutBeta.xml Extensible Markup Language Yes, for all products except SSG and SPG Lookup table (LUT) to transform raster values to beta-nought (sigma0) values.
lutGamma.xml Extensible Markup Language Yes, for all products except SSG and SPG Lookup table (LUT) to transform raster values to gamma-nought (sigma0) values.
RS2EULA*.pdf Portable Document Format No Product end-user license agreement (EULA).
Readme.txt ASCII No Readme file.
label.txt ASCII No Label file.

However i think it's out of scope for us to document proprietary thirdparty file structures in gamma_insar, especially when as far as I'm aware there's multiple RS2 data brokers w/ different data formats - and it's not us who define what structure we support (but rather GAMMA itself who supports different data formats).