From 85f5ae7559b63a80d272662ad160b1dc7cf1bb73 Mon Sep 17 00:00:00 2001 From: Matthias Mohr Date: Thu, 27 Jun 2024 11:03:07 +0200 Subject: [PATCH] Convert SAR tables from HTML to Markdown --- .github/workflows/deploy-latest.yml | 34 +- .../Synthetic-Aperture-Radar/PFS.md | 1990 +---------------- .../Synthetic-Aperture-Radar/README.md | 2 +- 3 files changed, 92 insertions(+), 1934 deletions(-) diff --git a/.github/workflows/deploy-latest.yml b/.github/workflows/deploy-latest.yml index 89a2fef..e68b896 100644 --- a/.github/workflows/deploy-latest.yml +++ b/.github/workflows/deploy-latest.yml @@ -60,23 +60,23 @@ jobs: --resource-path=Specifications/Surface-Temperature Specifications/Surface-Temperature/PFS.md Specifications/Surface-Temperature/annex-1-card4l-requirement-examples.md - # - name: SAR - # uses: docker://pandoc/core:3.2 - # with: - # args: >- - # --standalone - # --shift-heading-level-by=-1 - # --from=gfm - # --reference-doc=.github/pandoc-template.docx - # --lua-filter=.github/pagebreak.lua - # --output=docs/CEOS-ARD_PFS_Synthetic-Aperture-Radar_latest.docx - # --resource-path=Specifications/Synthetic-Aperture-Radar - # Specifications/Synthetic-Aperture-Radar/PFS.md - # Specifications/Synthetic-Aperture-Radar/annex-1.1-general-processing-roadmap.md - # Specifications/Synthetic-Aperture-Radar/annex-1.2-topographic-phase-removal.md - # Specifications/Synthetic-Aperture-Radar/annex-2-polarimetric-radar.md - # Specifications/Synthetic-Aperture-Radar/annex-3-ocean-radar-backscatter-example.md - # Specifications/Synthetic-Aperture-Radar/annex-4-geocoded-single-look-complex-example.md + - name: SAR + uses: docker://pandoc/core:3.2 + with: + args: >- + --standalone + --shift-heading-level-by=-1 + --from=gfm + --reference-doc=.github/pandoc-template.docx + --lua-filter=.github/pagebreak.lua + --output=docs/CEOS-ARD_PFS_Synthetic-Aperture-Radar_latest.docx + --resource-path=Specifications/Synthetic-Aperture-Radar + Specifications/Synthetic-Aperture-Radar/PFS.md + Specifications/Synthetic-Aperture-Radar/annex-1.1-general-processing-roadmap.md + Specifications/Synthetic-Aperture-Radar/annex-1.2-topographic-phase-removal.md + Specifications/Synthetic-Aperture-Radar/annex-2-polarimetric-radar.md + Specifications/Synthetic-Aperture-Radar/annex-3-ocean-radar-backscatter-example.md + Specifications/Synthetic-Aperture-Radar/annex-4-geocoded-single-look-complex-example.md - uses: peaceiris/actions-gh-pages@v4 with: github_token: ${{ secrets.GITHUB_TOKEN }} diff --git a/Specifications/Synthetic-Aperture-Radar/PFS.md b/Specifications/Synthetic-Aperture-Radar/PFS.md index 57d2a86..0a988df 100644 --- a/Specifications/Synthetic-Aperture-Radar/PFS.md +++ b/Specifications/Synthetic-Aperture-Radar/PFS.md @@ -1,4 +1,3 @@ - --- title: CEOS-ARD Product Family Specification subtitle: Synethetic Aperture Radar @@ -117,1430 +116,67 @@ For this generic **CEOS-ARD for Synthetic Aperture Radar** PFS, as for the indiv *These are metadata records describing a distributed collection of pixels. The collection of pixels referred to must be contiguous in space and time. General metadata should allow the user to assess the overall suitability of the dataset and must meet the requirements listed below. The column “CEOS-ARD product” indicates to which CEOS-ARD SAR product (NRB, POL, ORB, GSLC) the parameter refers.* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#ParameterCEOS-ARD productRequirementsSelf-Assessment
1.1Traceability -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Data must be traceable to SI reference standard.

-

-

Note 1: Relationship to 3.5. Traceability requires an estimate of measurement uncertainty.

-

Note 2: Information on traceability should be available in the metadata as a single DOI landing page.

-
1.2Metadata Machine Readability -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Metadata is provided in a structure that enables a computer algorithm to be used consistently and to automatically identify and extract each component part for further use.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-

-
-

Goal (Desired) Requirements

-

As threshold, but metadata is formatted in accordance with CEOS-ARD SAR Metadata Specifications, v.1.0, or in a community endorsed standard that facilitates machine-readability, such as ISO 19115-2, Climate and Forecast (CF) convention and the Attribute Convention for Data Discovery (ACDD), etc.

-

-

-

-

-
1.3Product Type -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

CEOS-ARD product type name – or names in case of compliance with more than one product type – and, if required by the data provider, copyright.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.4Document Identifier -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Reference to CEOS-ARD for Synthetic Aperture Radar PFS document as URL.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.5Data Collection Time -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Number of source data acquisitions of the data collection is identified. The start and stop UTC time of data collection is identified in the metadata, expressed in date/time. In case of composite products, the dates/times of the first and last data takes and the per-pixel metadata 2.8 (Acquisition ID Image) is provided with the product.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.6Source Data Attributes -

Subsection describing (detailing) each SAR acquisition used to generate the ARD product.

-

-

Note: Source data attribute information are described for each acquisition and sequentially identified as acqID= 1, 2, 3, …

-
1.6.1Source Data Access -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

The metadata identifies the location from where the source data can be retrieved, expressed as a URL or DOI.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

The metadata identifies an online location from where the data can be consistently and reliably retrieved by a computer algorithm without any manual intervention being required.

-
1.6.2Instrument -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

The instrument used to collect the data is identified in the metadata:

-

- Satellite name

-

- Instrument name

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold, but including a reference to the relevant CEOS Missions, Instruments and Measurements Database record.

-
1.6.3 -

Source Data Acquisition

-

Time

-
-

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

The start date and time of source data is identified in the metadata, expressed in UTC in date and time, at least to the second.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.6.4Source Data Acquisition Parameters -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Acquisition parameters related to the SAR antenna:

-

- Radar band

-

- Centre frequency

-

- Observation mode (i.e., Beam mode name)

-

- Polarization(s) (listed as in original product)

-

- Antenna pointing [Right/Left]

-

- Beam ID (i.e., Beam mode Mnemonic)

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.6.5Source Data Orbit Information -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Information related to the platform orbit used for data processing:

-

- Pass direction [asc/desc) *

-

- Orbit data source [e.g., predicted/ definite/ precise/ downlinked, etc.]

-

-

* For source data crossing the North or South Pole, it is recommended to produce two distinct CEOS-ARD products and to use the appropriate “Pass direction” in each.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold, including also:

-

- Platform heading angle expressed in degrees [0 360] from North

-

- Orbit data file containing state vectors (minimum of 5 state vectors, from 10% of scene length before start time to 10% of scene length after stop time)

-

- Platform (mean) altitude.

-
1.6.6Source Data Processing Parameters -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Processing parameters details of the source data:

-

- Processing facility

-

- Processing date

-

- Software version

-

- Product level

-

- Product ID (file name)

-

- Azimuth number of looks

-

- Range number of looks (separate values for each beam, as necessary)

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold, plus additional relevant processing parameters, e.g., range- and azimuth look bandwidth and LUT applied.

-
1.6.7Source Data Image Attributes -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Image attributes related to the source data:

-

- Source Data geometry (slant range/ground range)

-

- Azimuth pixel spacing

-

- Range pixel spacing

-

- Azimuth resolution

-

- Range resolution

-

- Near range incident angle

-

- Far range incident angle

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Geometry of the image footprint expressed in WGS84 in a standardised format (e.g., WKT).

-
1.6.8Sensor Calibration -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Sensor calibration parameters are identified in the metadata or can be accessed using details included in the metadata. Ideally this would support machine to machine access.

-
1.6.9Performance Indicators -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Provide performance indicators on data intensity noise level (NEσ0 and/or NEβ0 and/or NEγ0 (noise equivalent Sigma- and/or Beta- and/or Gamma-Nought)). Provided for each polarization channel when available.

-

-

Parameter may be expressed as the mean and/or minimum and maximum noise equivalent values of the source data.

-

-

Values do not need to be estimated individually for each product, but may be estimated once for each acquisition mode, and annotated on all products.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Provide additional relevant performance indicators (e.g., ENL, PSLR, ISLR, and performance reference DOI or URL).

-
1.6.10Source Data Polarimetric Calibration Matrices -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

The complex-valued polarimetric distortion matrices with the channel imbalance and the cross-talk applied for the polarimetric calibration.

-
1.6.11Mean Faraday Rotation Angle -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

The mean Faraday rotation angle estimated from the polarimetric data and/or from models with reference to the method or paper used to derive the estimate.

-
1.6.12Ionosphere Indicator -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Flag indicating whether the backscatter imagery is “significantly impacted” by the ionosphere (0 – false, 1 – true). Significant impact would imply that the ionospheric impact on the backscatter exceeds the radiometric calibration requirement or goal for the imagery.

-
1.7CEOS-ARD Product AttributesSubsection containing information related to the CEOS-ARD product generation procedure and geographic parameters.
1.7.1Product Data Access -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Processing parameters details of the CEOS-ARD product:

-

- Processing facility

-

- Processing date

-

- Software version

-

- Location from where CEOS-ARD product can be retrieved, expressed as a URL or DOI.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

The metadata identifies an online location from where the data can be consistently and reliably retrieved by a computer algorithm without any manual intervention being required.

-
1.7.2Auxiliary Data -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

The metadata identifies the sources of auxiliary data used in the generation process, ideally expressed as DOIs.

-

-

Note: Auxiliary data includes DEMs, etc., and any additional data sources used in the generation of the product.

-
1.7.3Product Sample Spacing -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

CEOS-ARD product processing parameters details:

-

- Pixel (column) spacing

-

- Line (row) spacing

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.4Product Equivalent Number of Looks -

\[NRB]

-

\[POL]

-

\[ORB]

-

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Equivalent Number of Looks (ENL)

-
1.7.5Product Resolution -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Average spatial resolution of the CEOS-ARD product along:

-

- Columns

-

- Rows

-
1.7.6 -

Product

-

Filtering

-
-

\[NRB]

-

\[POL]

-

\[ORB]

-

-
-

Threshold (Minimum) Requirements

-

Flag if speckle filter has been applied [true/false].

-

-

Metadata should include:

-

- Reference to algorithm as DOI or URL

-

- Input filtering parameters

-

 - Type

-

 - Window size in pixel units

-

 - Any other parameters defining the speckle filter used

-

-

Mandatory for \[POL]: Advanced polarimetric filter preserving covariance matrix properties should be applied.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.7Product Bounding Box -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Two opposite corners of the product file (bounding box, including any zero-fill values) are identified, expressed in the coordinate reference system defined in 1.7.11.

-

-

Four corners of the product file are recommended for scenes crossing the Antemeridian, or the North or the South Pole.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.8Product Geographical Extent -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

The geometry of the SAR image footprint expressed in WGS84, in a standardised format (e.g., WKT Polygon).

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.9Product Image Size -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Image attributes of the CEOS-ARD product:

-

- Number of lines

-

- Number of pixels/lines

-

- File header size (if applicable)

-

- Number of no-data border pixels (if appl.)

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.10 -

Product

-

Pixel Coordinate Convention

-
-

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Coordinate referring to the Centre, or the Upper Left Corner or the Lower Left Corner of a pixel. Values are [pixel centre, pixel ULC or pixel LLC].

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.11Product Coordinate Reference System -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

The metadata lists the map projection (or geographical coordinates, if applicable) that was used and any relevant parameters required to geolocate data in that map projection, expressed in a standardised format (e.g., WKT).

-

-

Indicate EPSG code, if defined for the CRS.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.12Look Direction Polynomials\[ORB] -

Threshold (Minimum) Requirements

-

In case the per-pixel item 2.11 (Look Direction Image) is not provided, then a list of the polynomial coefficients ai necessary to reconstruct the look direction angle*, together with an estimate of the added error from use of polynomial vs. per-pixel more accurate values, shall be provided.

-

-

Example polynomial:

-

LookDir = a1Lat2 + a2Lon2 + a3LatLon + a4Lat + a5Lon + a6

-

-

where:

-

ai = polynomial coefficients

-

Lat = latitude

-

Lon = longitude

-

Lat and Lon are the related coordinates in the product map units [‘m’, ‘deg’, ‘arcsec’]

-

-

* The look direction angle represents the planar angle between north and each range direction. It is not constant in range, especially close to the poles.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.13Radar Unit Look Vector\[GSLC] -

Threshold (Minimum) Requirements

-

3-D components radar unit look vector, specified at centre of scene, in an Earth-Centred Earth-Fixed (ECEF) coordinate system (also called Earth Centred Rotating - ECR) is provided. It consists of unit vectors from antenna to surface pixel (i.e., positive Z component).

-

-

Only required if per-pixel metadata 2.12 (Radar Unit Look Vector Grid Image) is not provided.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.14Slant Range Sensor to Surface \[GSLC] -

Threshold (Minimum) Requirements

-

Slant range distance from the sensor to the surface, specified at centre of scene.

-

Only required if per-pixel metadata 2.13 (Slant Range Sensor to Surface Image) is not provided.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
1.7.15Reference Orbit -

\[NRB]

-

\[POL]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Usage: For \[NRB] & \[POL] only when per-pixel metadata 3.7 (Flattened phase) is provided. For \[GSLC] when a reference orbit is used instead of a virtual orbit (see Annex A 1.2).

-

-

Provide the absolute orbit number used as reference for topographic phase flattening. In case a virtual orbit has been used, provide orbit parameters or orbit state vectors as DOI or URL.

-

-

Provide scene-centred perpendicular baseline for the for the source data relative to the reference orbit used (for approximate use only).

-
+| # | Parameter | CEOS-ARD product | Requirements | Self-Assessment | +| :--: | :--: | :--: | :-- | :-- | +| **1.1** | **Traceability** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Data must be traceable to SI reference standard. *Note 1: Relationship to 3.5. Traceability requires an estimate of measurement uncertainty.* *Note 2: Information on traceability should be available in the metadata as a single DOI landing page.* | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.2** | **Metadata Machine Readability** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Metadata is provided in a structure that enables a computer algorithm to be used consistently and to automatically identify and extract each component part for further use. **Goal (Desired) Requirements** As threshold, but metadata is formatted in accordance with CEOS-ARD SAR Metadata Specifications, v.1.0, or in a community endorsed standard that facilitates machine-readability, such as ISO 19115-2, Climate and Forecast (CF) convention and the Attribute Convention for Data Discovery (ACDD), etc. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.3** | **Product Type** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** CEOS-ARD product type name – or names in case of compliance with more than one product type – and, if required by the data provider, copyright. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.4** | **Document Identifier** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Reference to CEOS-ARD for Synthetic Aperture Radar PFS document as URL. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.5** | **Data Collection Time** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Number of source data acquisitions of the data collection is identified. The start and stop UTC time of data collection is identified in the metadata, expressed in date/time. In case of composite products, the dates/times of the first and last data takes and the per-pixel metadata 2.8 (Acquisition ID Image) is provided with the product. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6** | **Source Data Attributes** | | Subsection describing (detailing) **each SAR acquisition** used to generate the ARD product. *Note: Source data attribute information are described for each acquisition and sequentially identified as acqID= 1, 2, 3, …* | | +| **1.6.1** | **Source Data Access** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** The metadata identifies the location from where the source data can be retrieved, expressed as a URL or DOI. **Goal (Desired) Requirements** The metadata identifies an online location from where the data can be consistently and reliably retrieved by a computer algorithm without any manual intervention being required. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.2** | **Instrument** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** The instrument used to collect the data is identified in the metadata: - Satellite name - Instrument name **Goal (Desired) Requirements** As threshold, but including a reference to the relevant CEOS Missions, Instruments and Measurements Database record. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.3** | **Source Data Acquisition** **Time** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** The start date and time of source data is identified in the metadata, expressed in UTC in date and time, at least to the second. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.4** | **Source Data Acquisition Parameters** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Acquisition parameters related to the SAR antenna: - Radar band - Centre frequency - Observation mode (i.e., Beam mode name) - Polarization(s) (listed as in original product) - Antenna pointing [Right/Left] - Beam ID (i.e., Beam mode Mnemonic) **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.5** | **Source Data Orbit Information** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Information related to the platform orbit used for data processing: - Pass direction [asc/desc) \* - Orbit data source [e.g., predicted/ definite/ precise/ downlinked, etc.] *\* For source data crossing the North or South Pole, it is recommended to produce two distinct CEOS-ARD products and to use the appropriate “Pass direction” in each.* **Goal (Desired) Requirements** As threshold, including also: - Platform heading angle expressed in degrees [0 360] from North - Orbit data file containing state vectors (minimum of 5 state vectors, from 10% of scene length *before* start time to 10% of scene length *after* stop time) - Platform (mean) altitude. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.6** | **Source Data Processing Parameters** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Processing parameters details of the source data: - Processing facility - Processing date - Software version - Product level - Product ID (file name) - Azimuth number of looks - Range number of looks (separate values for each beam, as necessary) **Goal (Desired) Requirements** As threshold, plus additional relevant processing parameters, e.g., range- and azimuth look bandwidth and LUT applied. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.7** | **Source Data Image Attributes** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Image attributes related to the source data: - Source Data geometry (slant range/ground range) - Azimuth pixel spacing - Range pixel spacing - Azimuth resolution - Range resolution - Near range incident angle - Far range incident angle **Goal (Desired) Requirements** Geometry of the image footprint expressed in WGS84 in a standardised format (e.g., WKT). | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.8** | **Sensor Calibration** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Sensor calibration parameters are identified in the metadata or can be accessed using details included in the metadata. Ideally this would support machine to machine access. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.9** | **Performance Indicators** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Provide performance indicators on data intensity noise level (NEσ0 and/or NEβ0 and/or NEγ0 (noise equivalent Sigma- and/or Beta- and/or Gamma-Nought)). Provided for each polarization channel when available. Parameter may be expressed as the mean and/or minimum and maximum noise equivalent values of the source data. Values do not need to be estimated individually for each product, but may be estimated once for each acquisition mode, and annotated on all products. **Goal (Desired) Requirements** Provide additional relevant performance indicators (e.g., ENL, PSLR, ISLR, and performance reference DOI or URL). | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.10** | **Source Data Polarimetric Calibration Matrices** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** The complex-valued polarimetric distortion matrices with the channel imbalance and the cross-talk applied for the polarimetric calibration. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.11** | **Mean Faraday Rotation Angle** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** The mean Faraday rotation angle estimated from the polarimetric data and/or from models with reference to the method or paper used to derive the estimate. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.6.12** | **Ionosphere Indicator** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Flag indicating whether the backscatter imagery is “significantly impacted” by the ionosphere (0 – false, 1 – true). Significant impact would imply that the ionospheric impact on the backscatter exceeds the radiometric calibration requirement or goal for the imagery. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7** | **CEOS-ARD Product Attributes** | | Subsection containing information related to the CEOS-ARD product generation procedure and geographic parameters. | | +| **1.7.1** | **Product Data Access** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Processing parameters details of the CEOS-ARD product: - Processing facility - Processing date - Software version - Location from where CEOS-ARD product can be retrieved, expressed as a URL or DOI. **Goal (Desired) Requirements** The metadata identifies an online location from where the data can be consistently and reliably retrieved by a computer algorithm without any manual intervention being required. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.2** | **Auxiliary Data** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** The metadata identifies the sources of auxiliary data used in the generation process, ideally expressed as DOIs. *Note: Auxiliary data includes DEMs, etc., and any additional data sources used in the generation of the product.* | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.3** | **Product Sample Spacing** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** CEOS-ARD product processing parameters details: - Pixel (column) spacing - Line (row) spacing **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.4** | **Product Equivalent Number of Looks** | \[NRB] \[POL] \[ORB] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Equivalent Number of Looks (ENL) | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.5** | **Product Resolution** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Average spatial resolution of the CEOS-ARD product along: - Columns - Rows | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.6** | **Product** **Filtering** | \[NRB] \[POL] \[ORB] | **Threshold (Minimum) Requirements** Flag if speckle filter has been applied [true/false]. Metadata should include: - Reference to algorithm as DOI or URL - Input filtering parameters  - Type  - Window size in pixel units  - Any other parameters defining the speckle filter used Mandatory for \[POL]: Advanced polarimetric filter preserving covariance matrix properties should be applied. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.7** | **Product Bounding Box** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Two opposite corners of the product file (bounding box, including any zero-fill values) are identified, expressed in the coordinate reference system defined in 1.7.11. Four corners of the product file are recommended for scenes crossing the Antemeridian, or the North or the South Pole. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.8** | **Product Geographical Extent** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** The geometry of the SAR image footprint expressed in WGS84, in a standardised format (e.g., WKT Polygon). **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.9** | **Product Image Size** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Image attributes of the CEOS-ARD product: - Number of lines - Number of pixels/lines - File header size (if applicable) - Number of no-data border pixels (if appl.) **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.10** | **Product** **Pixel Coordinate Convention** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Coordinate referring to the Centre, or the Upper Left Corner or the Lower Left Corner of a pixel. Values are [pixel centre, pixel ULC or pixel LLC]. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.11** | **Product Coordinate Reference System** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** The metadata lists the map projection (or geographical coordinates, if applicable) that was used and any relevant parameters required to geolocate data in that map projection, expressed in a standardised format (e.g., WKT). Indicate EPSG code, if defined for the CRS. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.12** | **Look Direction Polynomials** | \[ORB] | **Threshold (Minimum) Requirements** In case the per-pixel item 2.11 (Look Direction Image) is not provided, then a list of the polynomial coefficients aᵢ necessary to reconstruct the look direction angle\*, together with an estimate of the added error from use of polynomial vs. per-pixel more accurate values, shall be provided. Example polynomial: LookDir = a₁Lat² + a₂Lon² + a₃LatLon + a₄Lat + a₅Lon + a₆ where: aᵢ = polynomial coefficients Lat = latitude Lon = longitude Lat and Lon are the related coordinates in the product map units [‘m’, ‘deg’, ‘arcsec’] *\* The look direction angle represents the planar angle between north and each range direction. It is not constant in range, especially close to the poles.* **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.13** | **Radar Unit Look Vector** | \[GSLC] | **Threshold (Minimum) Requirements** 3-D components radar unit look vector, specified at centre of scene, in an Earth-Centred Earth-Fixed (ECEF) coordinate system (also called Earth Centred Rotating - ECR) is provided. It consists of unit vectors from antenna to surface pixel (i.e., positive Z component). Only required if per-pixel metadata 2.12 (Radar Unit Look Vector Grid Image) is not provided. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.14** | **Slant Range Sensor to Surface** | \[GSLC] | **Threshold (Minimum) Requirements** Slant range distance from the sensor to the surface, specified at centre of scene. Only required if per-pixel metadata 2.13 (Slant Range Sensor to Surface Image) is not provided. **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **1.7.15** | **Reference Orbit** | \[NRB] \[POL] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** ***Usage*:** For **\[NRB] & \[POL]** only when per-pixel metadata 3.7 (Flattened phase) is provided. For **\[GSLC]** when a reference orbit is used instead of a virtual orbit (see Annex A 1.2). Provide the absolute orbit number used as reference for topographic phase flattening. In case a virtual orbit has been used, provide orbit parameters or orbit state vectors as DOI or URL. Provide scene-centred perpendicular baseline for the for the source data relative to the reference orbit used (for approximate use only). | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | ### Per-Pixel Metadata -The following minimum metadata specifications apply to each pixel. Whether the metadata are provided in a single record relevant to all pixels or separately for each pixel is at the discretion of the data provider. Per-pixel metadata should allow users to discriminate between (choose) observations on the basis of their individual suitability for applications. Cloud optimized file formats are recommended. +*The following minimum metadata specifications apply to each pixel. Whether the metadata are provided in a single record relevant to all pixels or separately for each pixel is at the discretion of the data provider. Per-pixel metadata should allow users to discriminate between (choose) observations on the basis of their individual suitability for applications. Cloud optimized file formats are recommended.* *The column “CEOS-ARD product” indicates which CEOS-ARD SAR product(s) (NRB, POL, ORB, GSLC) the parameter refers to.* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#ParameterCEOS-ARD productRequirementsSelf-Assessment
2.1Metadata Machine Readability -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Metadata is provided in a structure that enables a computer algorithm to be used to consistently and automatically identify and extract each component/variable/layer for further use.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold, but metadata is formatted in accordance with CEOS-ARD SAR Metadata Specifications, v.1.0.

-
2.2Data Mask Image -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Mask image indicating:

-

- Valid data

-

- Invalid data

-

- No data

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Mask]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int, ...]

-

- Bits per Sample

-

- Byte Order

-

- Bit Value Representation

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold, including additional bit value representations, e.g.:

-

- Layover (masked as invalid data in threshold)

-

- Radar shadow (masked as invalid data in threshold)

-

- Ocean water

-

- Land (recommended for \[ORB])

-

- RTC applied (e.g., for maritime scenes with land samples for which RTC has been applied)

-

- DEM gap filling (i.e., interpolated DEM over gaps)

-
2.3Scattering Area Image -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Usage: Recommended for scenes that include land areas.

-

-

DEM-based scattering area image used for Gamma-Nought terrain normalisation is provided. This quantifies the local scattering area used to normalise for radiometric distortions induced by terrain to the measured β0 backscatter. The terrain-flattened γT0 is best understood as β0 divided by the local scattering area.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Scattering Area]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-
2.4Local Incident Angle Image -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

DEM-based Local Incident angle image is provided.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Angle]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-

-

Note: For maritime \[ORB] scenes when no land areas are covered, a geoid model could be used for the calculation of the local incident angle

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
2.5Ellipsoidal Incident Angle Image -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Ellipsoidal incident angle is provided.

-

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Angle]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-

- Reference Ellipsoid Name

-

-

Note: For maritime \[ORB] scenes when no land areas are covered, the ellipsoidal incident angle is nearly identical to the geoid based local incident angle.

-
2.6Noise Power Image -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Estimated Noise Equivalent σ0 (or β0 or γ0, as applicable) used for noise removal, if applied, for each channel. NEσ0 and NEγ0 are both based on a simplified ellipsoid Earth model.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Gamma-Nought, Sigma-Nought, Beta-Nought]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-
2.7Gamma-to- Sigma Ratio Image -

\[NRB]

-

\[POL]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Ratio of the integrated area in the Gamma projection over the integrated area in the Sigma projection (ground). Multiplying RTC γT0 by this ratio results in an estimate of RTC σT0.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Ratio]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-
2.8Acquisition ID Image -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Note: Required for multi-source product only.

-

-

Acquisition ID, or acquisition date, for each pixel is identified.

-

-

In case of multi-temporal image stacks, use source acquisition ID (i.e., 1.6 acqID values) to list contributing images.

-

-

In case of Date, data represent (integer or fractional) day offset to reference observation date [UTC]. Date used as reference (“Day 0”) is provided in the metadata.

-

-

Pixels not representing a unique date (e.g., pixels averaged in image overlap zones) are flagged with a pre-set pixel value that is provided in the metadata.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Day, Time, ID]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per sample

-

- Byte Order

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

In case of image composites, the sources for each pixel are uniquely identified.

-
2.9Per-pixel DEM -

\[NRB]

-

\[POL]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Provide DEM or DSM as used during the geometric and radiometric processing of the SAR data, resampled to an exact geometric match in extent and resolution with the CEOS-ARD SAR image product. Can also be provided with \[ORB] products containing land areas.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Height]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-
2.10Per-pixel
Geoid
\[ORB] -

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Provide Geoid as used during the geometric and radiometric processing of the SAR data, resampled to an exact geometric match in extent and resolution with the CEOS-ARD ORB image product.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Height]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-

- Ground Sampling Distance

-
#ParameterCEOS-ARD productRequirementsSelf-Assessment
2.11Look
Direction
Image
\[ORB] -

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Look Direction Image is provided. It represents the planar angle between north and each range direction.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Angle]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-
2.12Radar Unit Look Vector Grid Image\[GSLC] -

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

3-D components radar unit look vector, specified at each pixel in an Earth-Centred Earth-Fixed (ECEF) coordinate system (also called Earth Centred Rotating – ECR) is provided. It consists of unit vectors from the antenna to the surface pixel (i.e., positive Z component).

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [3D unit vector]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Float, ...]

-

- Bits per Sample

-

- Byte Order

-
2.13Slant Range Sensor to Surface Image\[GSLC] -

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Slant range distance from the sensor to the surface, specified at each pixel in an Earth-Centred Earth-Fixed (ECEF) coordinate system (also called Earth Centred Rotating – ECR) is provided.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Distance]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Float, ...]

-

- Bits per Sample

-

- Byte Order

-
2.14InSAR Phase Uncertainty Image\[GSLC] -

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired)l Requirements

-

Estimate of uncertainty in InSAR phase is provided, such as finite signal to noise ratio, quantization noise, or DEM error. Identification of which error sources are included will be provided as DOI/URL reference or brief description. It represents statistical variation from known noise sources only.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Angle]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Float, ...]

-

- Bits per Sample

-

- Byte Order

-
2.15Atmospheric Phase Correction Image\[GSLC] -

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Phase correction value at each pixel, if applied. DOI/URL reference to algorithm or brief description is provided.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Angle]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Float, ...]

-

- Bits per Sample

-

- Byte Order

-
2.16Ionospheric Phase Correction Image\[GSLC] -

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Phase correction value at each pixel, if applied. DOI/URL reference to algorithm or brief description is provided.

-

-

File format specifications/ contents provided in metadata:

-

- Sample Type [Angle]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Float, ...]

-

- Bits per Sample

-

- Byte Order

-
+| # | Parameter | CEOS-ARD product | Requirements | Self-Assessment | +| :--: | :--: | :--: | :-- | :-- | +| **2.1** | **Metadata Machine Readability** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Metadata is provided in a structure that enables a computer algorithm to be used to consistently and automatically identify and extract each component/variable/layer for further use. **Goal (Desired) Requirements** As threshold, but metadata is formatted in accordance with CEOS-ARD SAR Metadata Specifications, v.1.0. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.2** | **Data Mask Image** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Mask image indicating: - Valid data - Invalid data - No data File format specifications/ contents provided in metadata: - Sample Type [Mask] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int, ...] - Bits per Sample - Byte Order - Bit Value Representation **Goal (Desired) Requirements** As threshold, including additional bit value representations, e.g.: - Layover (masked as invalid data in threshold) - Radar shadow (masked as invalid data in threshold) - Ocean water - Land (recommended for \[ORB]) - RTC applied (e.g., for maritime scenes with land samples for which RTC has been applied) - DEM gap filling (i.e., interpolated DEM over gaps) | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.3** | **Scattering Area Image** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** ***Usage:*** Recommended for scenes that include land areas. DEM-based scattering area image used for Gamma-Nought terrain normalisation is provided. This quantifies the local scattering area used to normalise for radiometric distortions induced by terrain to the measured β0 backscatter. The terrain-flattened γT0 is best understood as β0 divided by the local scattering area. File format specifications/ contents provided in metadata: - Sample Type [Scattering Area] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.4** | **Local Incident Angle Image** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** DEM-based Local Incident angle image is provided. File format specifications/ contents provided in metadata: - Sample Type [Angle] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order *Note: For maritime \[ORB] scenes when no land areas are covered, a geoid model could be used for the calculation of the local incident angle* **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.5** | **Ellipsoidal Incident Angle Image** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Ellipsoidal incident angle is provided. File format specifications/ contents provided in metadata: - Sample Type [Angle] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order - Reference Ellipsoid Name *Note: For maritime \[ORB] scenes when no land areas are covered, the ellipsoidal incident angle is nearly identical to the geoid based local incident angle.* | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.6** | **Noise Power Image** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Estimated Noise Equivalent σ0 (or β0 or γ0, as applicable) used for noise removal, if applied, for each channel. NEσ0 and NEγ0 are both based on a simplified ellipsoid Earth model. File format specifications/ contents provided in metadata: - Sample Type [Gamma-Nought, Sigma-Nought, Beta-Nought] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.7** | **Gamma-to- Sigma Ratio Image** | \[NRB] \[POL] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Ratio of the integrated area in the Gamma projection over the integrated area in the Sigma projection (ground). Multiplying RTC γT0 by this ratio results in an estimate of RTC σT0. File format specifications/ contents provided in metadata: - Sample Type [Ratio] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.8** | **Acquisition ID Image** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** ***Note: Required for multi-source product only.*** Acquisition ID, or acquisition date, for each pixel is identified. In case of multi-temporal image stacks, use source acquisition ID (i.e., 1.6 acqID values) to list contributing images. In case of Date, data represent (integer or fractional) day offset to reference observation date [UTC]. Date used as reference (“Day 0”) is provided in the metadata. Pixels not representing a unique date (e.g., pixels averaged in image overlap zones) are flagged with a pre-set pixel value that is provided in the metadata. File format specifications/ contents provided in metadata: - Sample Type [Day, Time, ID] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per sample - Byte Order **Goal (Desired) Requirements** In case of image composites, the sources for each pixel are uniquely identified. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.9** | **Per-pixel DEM** | \[NRB] \[POL] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Provide DEM or DSM as used during the geometric and radiometric processing of the SAR data, resampled to an exact geometric match in extent and resolution with the CEOS-ARD SAR image product. Can also be provided with \[ORB] products containing land areas. File format specifications/ contents provided in metadata: - Sample Type [Height] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.10** | **Per-pixel Geoid** | \[ORB] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Provide Geoid as used during the geometric and radiometric processing of the SAR data, resampled to an exact geometric match in extent and resolution with the CEOS-ARD ORB image product. File format specifications/ contents provided in metadata: - Sample Type [Height] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order - Ground Sampling Distance | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.11** | **Look Direction Image** | \[ORB] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Look Direction Image is provided. It represents the planar angle between north and each range direction. File format specifications/ contents provided in metadata: - Sample Type [Angle] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.12** | **Radar Unit Look Vector Grid Image** | \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** 3-D components radar unit look vector, specified at each pixel in an Earth-Centred Earth-Fixed (ECEF) coordinate system (also called Earth Centred Rotating – ECR) is provided. It consists of unit vectors from the antenna to the surface pixel (i.e., positive Z component). File format specifications/ contents provided in metadata: - Sample Type [3D unit vector] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.13** | **Slant Range Sensor to Surface Image** | \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Slant range distance from the sensor to the surface, specified at each pixel in an Earth-Centred Earth-Fixed (ECEF) coordinate system (also called Earth Centred Rotating – ECR) is provided. File format specifications/ contents provided in metadata: - Sample Type [Distance] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.14** | **InSAR Phase Uncertainty Image** | \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired)l Requirements** Estimate of uncertainty in InSAR phase is provided, such as finite signal to noise ratio, quantization noise, or DEM error. Identification of which error sources are included will be provided as DOI/URL reference or brief description. It represents statistical variation from known noise sources only. File format specifications/ contents provided in metadata: - Sample Type [Angle] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.15** | **Atmospheric Phase Correction Image** | \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Phase correction value at each pixel, if applied. DOI/URL reference to algorithm or brief description is provided. File format specifications/ contents provided in metadata: - Sample Type [Angle] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **2.16** | **Ionospheric Phase Correction Image** | \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Phase correction value at each pixel, if applied. DOI/URL reference to algorithm or brief description is provided. File format specifications/ contents provided in metadata: - Sample Type [Angle] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Float, ...] - Bits per Sample - Byte Order | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | ### Radiometrically Corrected Measurements @@ -1548,337 +184,18 @@ The following minimum metadata specifications apply to each pixel. Whether the m *The column “CEOS-ARD product” indicates which CEOS-ARD SAR product (NRB, POL, ORB, GSLC) the parameter refers to.* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#ParameterCEOS-ARD productRequirementsSelf-Assessment
3.1Backscatter
Measurements
-

\[NRB]

-

-
-

Threshold (Minimum) Requirements \[NRB]

-

“Terrain-flattened” Radiometrically Terrain Corrected (RTC) Gamma-Nought backscatter coefficient (γT0) is provided for each polarization.

-

File format specifications/contents provided in metadata:

-

- Measurement Type [Gamma-Nought]

-

- Backscatter Expression Convention [linear amplitude or linear power*]

-

- Polarization [HH/HV/VV/VH]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-

-

*Note: Transformation to the logarithm decibel scale is not required or desired as this step can be completed by the user if necessary.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
3.1Backscatter
Measurements
-

-

\[POL]

-

-
-

Threshold (Minimum) Requirements \[POL]

-

Measurements can be:

-

-

Normalised Radar Covariance Matrix (CovMat)

-

Diagonal (equivalent to \[NRB]) and upper diagonal elements of the terrain-flattened Gamma-Nought (γT0) Covariance Matrix are provided for coherent dual (e.g., HH-HV, VV-VH, or …) and fully polarimetric (e.g., HH- HV-VH-VV) acquisitions.

-

-

And/or

-

-

Polarimetric Radar Decomposition (PRD)

-

The individual components of the polarimetric decomposition obtained from the terrain-flattened (Gamma-Nought (γT0)) covariance matrix.

-

File format specifications/contents provided in metadata:

-

- Measurement Type [CovMat/PRD]

-

- Measurement convention unit [linear amplitude, linear power,

-

` `angle]

-

- Individual covariance matrix element or/and Individual component

-

` `of the decomposition [C3m11, C3m12, … or H, A, alpha, or ...]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/ Float/Complex, etc.]

-

- Bits per Sample

-

- Byte Order

-

-

Note: It is recommended to keep CovMat or PRD measurement files separated. Otherwise, specify the multi-channel format order [BIP, BIL, BSQ]

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
3.1Backscatter
Measurements
-

-

\[ORB]

-

-
-

Threshold (Minimum) Requirements \[ORB]

-

Geoid-corrected Sigma-Nought backscatter coefficient (σ0) is provided for each polarization.

-

-

File format specifications/contents provided in metadata:

-

- Measurement Type [Sigma-Nought]

-

- Backscatter Expression Convention [linear amplitude or linear power*]

-

- Backscatter Conversion Equation

-

- Polarization [HH/HV/VV/VH]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-

*Note: Transformation to the logarithm decibel scale is not required or desired as this step can be easily completed by the user if necessary.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Radiometrically Terrain-corrected Sigma-Nought backscatter coefficient (σT0) is provided for each polarization.

-
3.1Backscatter
Measurements
\[GSLC] -

Threshold (Minimum) Requirements

-

Radiometric and Phase Terrain-flattened Gamma-Nought backscatter coefficient (γT0), in complex number format, is provided for each polarization (e.g., HH, HV, VV, VH).

-

-

File format specifications/contents provided in metadata:

-

- Measurement Type [Gamma-Nought]

-

- Backscatter Expression Convention [linear amplitude or linear power*]

-

- Polarization [HH/HV/VV/VH]

-

- Data Format [Raw/GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-

-

*Note: Transformation to the logarithm decibel scale is not required or desired as this step can be easily completed by the user if necessary.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
3.2Scaling Conversion -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

If applicable, indicate the equation to convert pixel linear amplitude/power to logarithmic decibel scale, including, if applicable, the associated calibration (dB offset) factor, and/or the equation used to convert compressed data (int8/int16/float16) to float32.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold, but use of float32.

-
3.3Noise Removal -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Flag if noise removal* has been applied (Y/N). Metadata should include the noise removal algorithm and reference to the algorithm as URL or DOI.

-

-

*Note: Thermal noise removal and image border noise removal to remove overall scene noise and scene edge artefacts, respectively.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

As threshold.

-
3.4Radiometric Terrain Correction Algorithm -

\[NRB]

-

\[POL]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Adjustments were made for terrain by modelling the local contributing scattering area using the preferred choice of a published peer-reviewed algorithm to produce radiometrically terrain corrected (RTC) γT0 backscatter estimates.

-

-

Metadata references, e.g.:

-

- a citable peer-reviewed algorithm

-

- technical documentation regarding the algorithm used to generate the backscatter estimates is expressed as URLs or DOIs

-

- the sources of auxiliary data used to make corrections

-

-

Goal for \[GSLC] product type

-

-

Note: Examples of technical documentation include an Algorithm, Theoretical Basis Document, product user guide, etc.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

-

Goal for \[GSLC] product type

-

-

Require resolution of DEM better than the output product resolution when applying terrain corrections.

-
3.5Radiometric
Accuracy
-

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Uncertainty (e.g., bounds on γ0 or σ0) information is provided as document referenced as URL or DOI. SI traceability is achieved.

-
3.6Mean Wind- Normalised Backscatter Measurements\[ORB] -

Threshold (Minimum) Requirements

-

Not required.

-
-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Usage: Only for Maritime scene

-

-

Mean wind-normalised (over ocean) backscatter coefficient is provided for each available polarization. It is calculated as the ratio between the backscatter intensity and a simulated backscatter intensity image generated using an ocean surface wind model such as, e.g., Quilfen et al. (1998) or Vachon and Dobson (2000) for VV and HH polarization respectively.

-

-

File format specifications/contents provided in metadata:

-

- Measurement Type [Wind-Normalised Backscatter]

-

 Backscatter Expression Convention [intensity ratio]

-

- Polarization [HH/HV/VV/VH]

-

- Data Format [GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-

-

Note: Reference wind model, wind speed and direction used for reference backscattering coefficient should be provided.

-
3.7Flattened Phase -

\[NRB]

-

\[POL]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Usage: Alternative to \[GSLC] product for \[NRB] and \[POL] products

-

The Flattened Phase is the interferometric phase for which the topographic phase contribution is removed. It is derived from the range-Doppler SLC product using a DEM and the orbital state vectors with respect to a reference orbit (see Annex A1.2). The use of the Flattened Phase with the \[NRB] or \[POL] intensity (3.1 Backscatter measurement) provides the \[GSLC] equivalent, as follows:

-

GSLC = sqrt(NRB) x exp(j FlattenPhase)

-

File format specifications/contents provided in metadata:

-

- Measurement Type [Flattened Phase]

-

- Reference Polarization [HH/HV/VV/VH]

-

- Data Format [GeoTIFF/NetCDF, …]

-

- Data Type [Int/Float, ...]

-

- Bits per Sample

-

- Byte Order

-

-

In case of polarimetric data, indicate the reference polarization.

-
+| # | Parameter | CEOS-ARD product | Requirements | Self-Assessment | +| :--: | :--: | :--: | :-- | :-- | +| **3.1** | **Backscatter Measurements** | \[NRB] | **Threshold (Minimum) Requirements \[NRB]** ***“Terrain-flattened” Radiometrically Terrain Corrected (RTC) Gamma-Nought backscatter coefficient*** ( $`\gamma^0_T`$ ) is provided for each polarization. File format specifications/contents provided in metadata: - Measurement Type [Gamma-Nought] - Backscatter Expression Convention [linear amplitude or linear power\*] - Polarization [HH/HV/VV/VH] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order *\*Note: Transformation to the logarithm decibel scale is not required or* desired *as this step can be completed by the user if necessary.*** **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **3.1** | **Backscatter Measurements** | \[POL] | **Threshold (Minimum) Requirements \[POL]** Measurements can be: ***Normalised Radar Covariance Matrix (CovMat)*** Diagonal (equivalent to \[NRB]) and upper diagonal elements of the terrain-flattened Gamma-Nought ( $`\gamma^0_T`$ ) Covariance Matrix are provided for coherent dual (e.g., HH-HV, VV-VH, or …) and fully polarimetric (e.g., HH- HV-VH-VV) acquisitions. And/or ***Polarimetric Radar Decomposition (PRD)*** The individual components of the polarimetric decomposition obtained from the terrain-flattened (Gamma-Nought ( $`\gamma^0_T`$ )) covariance matrix. File format specifications/contents provided in metadata: - Measurement Type [CovMat/PRD] - Measurement convention unit [linear amplitude, linear power, angle] - Individual covariance matrix element or/and Individual component of the decomposition [C3m11, C3m12, … or H, A, alpha, or ...] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/ Float/Complex, etc.] - Bits per Sample - Byte Order *Note: It is recommended to keep CovMat or PRD measurement files separated. Otherwise, specify the multi-channel format order [BIP, BIL, BSQ]* **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **3.1** | **Backscatter Measurements** | \[ORB] | **Threshold (Minimum) Requirements \[ORB]** ***Geoid-corrected Sigma-Nought backscatter coefficient*** (σ⁰) is provided for each polarization. File format specifications/contents provided in metadata: - Measurement Type [Sigma-Nought] - Backscatter Expression Convention [linear amplitude or linear power\*] - Backscatter Conversion Equation - Polarization [HH/HV/VV/VH] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order *\*Note: Transformation to the logarithm decibel scale is not required or* desired *as this step can be easily completed by the user if necessary.* **Goal (Desired) Requirements** Radiometrically Terrain-corrected Sigma-Nought backscatter coefficient ( $`\sigma^0_T`$ ) is provided for each polarization. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **3.1** | **Backscatter Measurements** | \[GSLC] | **Threshold (Minimum) Requirements** Radiometric and Phase Terrain-flattened Gamma-Nought backscatter coefficient ( $`\gamma^0_T`$ ), in complex number format, is provided for each polarization (e.g., HH, HV, VV, VH). File format specifications/contents provided in metadata: - Measurement Type [Gamma-Nought] - Backscatter Expression Convention [linear amplitude or linear power\*] - Polarization [HH/HV/VV/VH] - Data Format [Raw/GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order *\*Note: Transformation to the logarithm decibel scale is not required or* desired *as this step can be easily completed by the user if necessary.* **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **3.2** | **Scaling Conversion** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** If applicable, indicate the equation to convert pixel linear amplitude/power to logarithmic decibel scale, including, if applicable, the associated calibration (dB offset) factor, and/or the equation used to convert compressed data (int8/int16/float16) to float32. **Goal (Desired) Requirements** As threshold, but use of float32. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **3.3** | **Noise Removal** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Flag if noise removal\* has been applied (Y/N). Metadata should include the noise removal algorithm and reference to the algorithm as URL or DOI. *\*Note: Thermal noise removal and image border noise removal to remove overall scene noise and scene edge artefacts, respectively.* **Goal (Desired) Requirements** As threshold. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **3.4** | **Radiometric Terrain Correction Algorithm** | \[NRB] \[POL] \[GSLC] | **Threshold (Minimum) Requirements** Adjustments were made for terrain by modelling the local contributing scattering area using the preferred choice of a published peer-reviewed algorithm to produce radiometrically terrain corrected (RTC) $`\gamma^0_T`$ backscatter estimates. Metadata references, e.g.: - a citable peer-reviewed algorithm - technical documentation regarding the algorithm used to generate the backscatter estimates is expressed as URLs or DOIs - the sources of auxiliary data used to make corrections ***Goal*** for \[GSLC] product type *Note: Examples of technical documentation include an Algorithm, Theoretical Basis Document, product user guide, etc.* **Goal (Desired) Requirements** ***Goal*** for \[GSLC] product type Require resolution of DEM better than the output product resolution when applying terrain corrections. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **3.5** | **Radiometric Accuracy** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Uncertainty (e.g., bounds on γ⁰ or σ⁰) information is provided as document referenced as URL or DOI. SI traceability is achieved. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **3.6** | **Mean Wind- Normalised Backscatter Measurements** | \[ORB] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** ***Usage:*** Only for Maritime scene Mean wind-normalised (over ocean) backscatter coefficient is provided for each available polarization. It is calculated as the ratio between the backscatter intensity and a simulated backscatter intensity image generated using an ocean surface wind model such as, e.g., Quilfen et al. (1998) or Vachon and Dobson (2000) for VV and HH polarization respectively. File format specifications/contents provided in metadata: - Measurement Type [Wind-Normalised Backscatter]  Backscatter Expression Convention [intensity ratio] - Polarization [HH/HV/VV/VH] - Data Format [GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order *Note: Reference wind model, wind speed and direction used for reference backscattering coefficient should be provided*. | Explanation / Justification: … Other feedback: … | +| **3.7** | **Flattened Phase** | \[NRB] \[POL] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** ***Usage: Alternative to \[GSLC] product for \[NRB] and \[POL] products*** The Flattened Phase is the interferometric phase for which the topographic phase contribution is removed. It is derived from the range-Doppler SLC product using a DEM and the orbital state vectors with respect to a reference orbit (see Annex A1.2). The use of the Flattened Phase with the **\[NRB]** or **\[POL]** intensity (3.1 Backscatter measurement) provides the \[GSLC] equivalent, as follows: **GSLC** = sqrt(**NRB**) x exp(j FlattenPhase) File format specifications/contents provided in metadata: - Measurement Type [Flattened Phase] - Reference Polarization [HH/HV/VV/VH] - Data Format [GeoTIFF/NetCDF, …] - Data Type [Int/Float, ...] - Bits per Sample - Byte Order In case of polarimetric data, indicate the reference polarization. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | ### Geometric Corrections @@ -1886,172 +203,13 @@ Geometric corrections are steps that are taken to place the measurement accurate *The column “CEOS-ARD product” indicates to which CEOS-ARD SAR product (NRB, POL, ORB, GSLC) the parameter refers.* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#ParameterCEOS-ARD productRequirementsSelf-Assessment
4.1Geometric Correction Algorithm -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Metadata references, e.g.:

-

- A metadata citable peer-reviewed algorithm,

-

- Technical documentation regarding the implementation of that algorithm expressed as URLs or DOIs

-

- The sources of auxiliary data used to make corrections.

-

- Resampling method used for geometric processing of the source data.

-

-

Note: Examples of technical documentation can include e.g., an Algorithm Theoretical Basis Document (ATBD), a product user guide.

-
4.2 -

Digital
Elevation

-

Model

-
-

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Usage: For products including land areas

-

-

a) During ortho-rectification, the data provider shall use the same DEM that was used for the radiometric terrain flattening to ensure consistency of the data stack.

-

b) Provide reference to Digital Elevation Model used for geometric terrain correction.

-

c) Provide reference to Earth Gravitational Model (EGM) used for geometric correction

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

a) A DEM with comparable or better resolution to the resolution of the output CEOS-ARD product shall be used if available. Else, the upsampled DEM is identified.

-

b) Resampling method used for preparation of the DEM.

-

c) Method used for resampling the EGM.

-
4.3Geometric Accuracy -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Accurate geolocation is a prerequisite to radar processing to correct for terrain and to enable interoperability between radar sensors.

-

The absolute geolocation error (ALE) for a sensor is typically assessed through analysis of Single Look Complex (SLC) imagery and measured along the slant range and azimuth directions (case A: SLC ALE). The end-to-end “ARD” ALE of the final CEOS-ARD product could be measured directly in the final image product in the chosen map projection, i.e., in the map coordinate directions: e.g., Northing and Easting (case B: ARD ALE). Providing accuracy estimates based on measurements following at least one scheme (A or B or both) meets the threshold requirement.

-

Estimates of the ALE is provided as a bias and a standard deviation, with (Case A) SLC ALE expressed in slant range and azimuth, and (Case B) ARD ALE expressed in map projection dimensions.

-

Note 1: This assessment is often made through comparison of measured corner reflector positions with their projected location in the imagery. In some cases, other mission calibration/validation results may be used. Note 2: The ALE is not typically assessed for every processed image, but through an ALE assessment by the data processing team characterizing all or (usually a subset) of the generated products.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Output product sub-sample accuracy should be less than or equal to 0.1 (slant range) pixel radial root mean square error (rRMSE).

-

-

Provide documentation of estimates of ALE as DOI or URL.

-
4.4Geometric Refined Accuracy -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

Not required.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Values provided under 4.3 Geometric accuracy are provided by the SAR mission Cal/Val team.

-

-

CEOS-ARD processing steps could include method refining the geometric accuracy, such as cross-correlation of the SAR data in slant range with a SAR scene simulated from a DSM or DEM.

-

-

Methodology used (name and reference), quality flag, geometric standard deviation values should be provided.

-
4.5Gridding Convention -

\[NRB]

-

\[POL]

-

\[ORB]

-

\[GSLC]

-
-

Threshold (Minimum) Requirements

-

A consistent gridding/sampling frame is used. The origin is chosen to minimise any need for subsequent resampling between multiple products (be they from the same or different providers). This is typically accomplished via a “snap to grid” in relation to the most proximate grid tile in a global system.*

-

-

* If a product hierarchy of resolutions exists (or is planned), the multiple resolutions should nest within each other (e.g., 12.5m, 25m, 50m, 100m, etc.), and not be disjoint.

-
-

Achieved level: Threshold / Goal

-

Explanation / Justification: …

-

Other feedback: …

-
-

Goal (Desired) Requirements

-

Provide DOI or URL to gridding convention used.

-

-

When multiple providers share a common map projection, providers are encouraged to standardise the origins of their products among each other.

-

-

In the case of UTM/UPS coordinates, the upper left corner coordinates should be set to an integer multiple of sample intervals from a 100 km by 100 km grid tile of the Military Grid Reference System's 100k coordinates (“snap to grid”).

-

-

For products presented in geographic coordinates (latitude and longitude), the origin should be set to an integer multiple of samples in relation to the closest integer degree.

-
+| # | Parameter | CEOS-ARD product | Requirements | Self-Assessment | +| :--: | :--: | :--: | :-- | :-- | +| **4.1** | **Geometric Correction Algorithm** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Metadata references, e.g.: - A metadata citable peer-reviewed algorithm, - Technical documentation regarding the implementation of that algorithm expressed as URLs or DOIs - The sources of auxiliary data used to make corrections. - Resampling method used for geometric processing of the source data. *Note: Examples of technical documentation can include e.g., an Algorithm Theoretical Basis Document (ATBD), a product user guide*. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **4.2** | **Digital Elevation** **Model** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** ***Usage:*** For products including land areas a) During ortho-rectification, the data provider shall use the same DEM that was used for the radiometric terrain flattening to ensure consistency of the data stack. b) Provide reference to Digital Elevation Model used for geometric terrain correction. c) Provide reference to Earth Gravitational Model (EGM) used for geometric correction **Goal (Desired) Requirements** a) A DEM with comparable or better resolution to the resolution of the output CEOS-ARD product shall be used if available. Else, the upsampled DEM is identified. b) Resampling method used for preparation of the DEM. c) Method used for resampling the EGM. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **4.3** | **Geometric Accuracy** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Accurate geolocation is a prerequisite to radar processing to correct for terrain and to enable interoperability between radar sensors. The absolute geolocation error (ALE) for a sensor is typically assessed through analysis of Single Look Complex (SLC) imagery and measured along the slant range and azimuth directions (case A: SLC ALE). The end-to-end “ARD” ALE of the final CEOS-ARD product could be measured directly in the final image product in the chosen map projection, i.e., in the map coordinate directions: e.g., Northing and Easting (case B: ARD ALE). Providing accuracy estimates based on measurements following at least one scheme (A or B or both) meets the threshold requirement. Estimates of the ALE is provided as a bias and a standard deviation, with (Case A) SLC ALE expressed in slant range and azimuth, and (Case B) ARD ALE expressed in map projection dimensions. *Note 1: This assessment is often made through comparison of measured corner reflector positions with their projected location in the imagery. In some cases, other mission calibration/validation results may be used. Note 2: The ALE is not typically assessed for every processed image, but through an ALE assessment by the data processing team characterizing all or (usually a subset) of the generated products.* **Goal (Desired) Requirements** Output product sub-sample accuracy should be less than or equal to 0.1 (slant range) pixel radial root mean square error (rRMSE). Provide documentation of estimates of ALE as DOI or URL. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **4.4** | **Geometric Refined Accuracy** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** Not required. **Goal (Desired) Requirements** Values provided under 4.3 Geometric accuracy are provided by the SAR mission Cal/Val team. CEOS-ARD processing steps could include method refining the geometric accuracy, such as cross-correlation of the SAR data in slant range with a SAR scene simulated from a DSM or DEM. Methodology used (name and reference), quality flag, geometric standard deviation values should be provided. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | +| **4.5** | **Gridding Convention** | \[NRB] \[POL] \[ORB] \[GSLC] | **Threshold (Minimum) Requirements** A consistent gridding/sampling frame is used. The origin is chosen to minimise any need for subsequent resampling between multiple products (be they from the same or different providers). This is typically accomplished via a “snap to grid” in relation to the most proximate grid tile in a global system.\* *\* If a product hierarchy of resolutions exists (or is planned), the multiple resolutions should nest within each other (e.g., 12.5m, 25m, 50m, 100m, etc.), and not be disjoint.* **Goal (Desired) Requirements** Provide DOI or URL to gridding convention used. When multiple providers share a common map projection, providers are encouraged to standardise the origins of their products among each other. In the case of UTM/UPS coordinates, the upper left corner coordinates should be set to an integer multiple of sample intervals from a 100 km by 100 km grid tile of the Military Grid Reference System's 100k coordinates (“snap to grid”). For products presented in geographic coordinates (latitude and longitude), the origin should be set to an integer multiple of samples in relation to the closest integer degree. | Achieved level: Threshold / Goal Explanation / Justification: … Other feedback: … | ## Summary Self-Assessment Table diff --git a/Specifications/Synthetic-Aperture-Radar/README.md b/Specifications/Synthetic-Aperture-Radar/README.md index 221a3b3..1da0259 100644 --- a/Specifications/Synthetic-Aperture-Radar/README.md +++ b/Specifications/Synthetic-Aperture-Radar/README.md @@ -13,7 +13,7 @@ The Markdown file is meant for editing through Pull Requests, all other files ar - [Annex 2 Polarimetric Radar](annex-2-polarimetric-radar.md) - [Annex 3 Ocean Radar Backscatter example](annex-3-ocean-radar-backscatter-example.md) - [Annex 4 Geocoded Single-Look Complex example](annex-4-geocoded-single-look-complex-example.md) -- Word (tbd) +- [Word](https://ceos-org.github.io/ceos-ard/CEOS-ARD_PFS_Synthetic-Aperture-Radar_latest.docx) - Excel (Metadata, tbd) > \[!NOTE]