From a3260fe82cf4fca8d2bc731317ae3d81d8120335 Mon Sep 17 00:00:00 2001 From: Matthias Mohr Date: Fri, 9 Aug 2024 14:40:55 +0200 Subject: [PATCH] Update radar --- json-schema/radar/product.json | 3 --- json-schema/radar/source.json | 3 --- radar-source.md | 11 +++++------ radar.md | 19 +++++-------------- 4 files changed, 10 insertions(+), 26 deletions(-) delete mode 100644 json-schema/radar/product.json delete mode 100644 json-schema/radar/source.json diff --git a/json-schema/radar/product.json b/json-schema/radar/product.json deleted file mode 100644 index 077404a..0000000 --- a/json-schema/radar/product.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - -} \ No newline at end of file diff --git a/json-schema/radar/source.json b/json-schema/radar/source.json deleted file mode 100644 index 077404a..0000000 --- a/json-schema/radar/source.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - -} \ No newline at end of file diff --git a/radar-source.md b/radar-source.md index 31614a8..e02d2f6 100644 --- a/radar-source.md +++ b/radar-source.md @@ -1,6 +1,8 @@ # CEOS-ARD for Radar - Source Data -- **Identifier:** +- **Scope:** Item, Collection +- **Extension [Maturity Classification]:** Proposal +- **Owner**: @m-mohr This extension specifies how to create [STAC] Items for Source Data that comply to the [CEOS-ARD product family specifications] (PFS) for radar sensors. @@ -76,6 +78,7 @@ The fields can be provided either in the [Collection](radar.md#stac-collections) | platform | 1.6.2 | **REQUIRED.** Satellite name in lower-case. | Requirement 1.6.2 asks to provide links to: + - [CEOS Missions Database] record(s) - [CEOS Instruments Database] record(s) - [CEOS Measurements Database] record(s) @@ -93,13 +96,9 @@ Requirement 1.6.2 asks to provide links to: ### Projection -> \[!WARNING] -> **Deprecation Notice:** In a future version of the version of the projection extension `proj:epsg` will be replaced by `proj:code`. -> It is recommended to provide both for now. - | Field Name | Req. | Description | | ------------------------------------- | ----- | ------------------------------------------------------------ | -| proj:epsg / proj:wkt2 / proj:projjson | 1.6.7 | **REQUIRED**. Coordinate Reference System (CRS). One of the fields is required to be provided. | +| proj:code / proj:wkt2 / proj:projjson | 1.6.7 | **REQUIRED**. Coordinate Reference System (CRS). One of the fields is required to be provided. | | proj:bbox | 1.7.7 | **REQUIRED**. The source data geometry in the given CRS. | ### SAR diff --git a/radar.md b/radar.md index b700526..1915404 100644 --- a/radar.md +++ b/radar.md @@ -1,11 +1,6 @@ # CEOS-ARD for Radar -- **Title:** CEOS-ARD for Radar -- **Identifier:** - - Product: - - Source(s): see [Source Data](radar-source.md) -- **Field Name Prefix:** - -- **Scope:** Item +- **Scope:** Item, Collection - **Extension [Maturity Classification]:** Proposal - **Owner**: @m-mohr @@ -59,7 +54,7 @@ This profile doesn't define new STAC fields, it's just a profile that uses As the identifier for this profile is just a collection of existing extensions and only defines required fields, you get a good bit of validation already without providing the identifier/schema of this profile in `stac_extensions`. If your metadata is already compliant to this profile, you can omit the identifier for this profile in -`stac_extensions` to avoid costly regeneration of the Items. You won't get validation whether all required +`stac_extensions` to avoid costly regeneration of the Items. You won't get validation whether all required fields are present, but this could be checked manually in the CEOS assessment/review. The following STAC extensions are relevant for this profile: @@ -125,16 +120,12 @@ The fields can be provided either in the [Collection](#stac-collections) or in e ### Projection -The metadata is **required** to specify the coordinate reference system through either `proj:epsg` or one of the alternatives. - -> \[!WARNING] -> **Deprecation Notice:** In a future version of the version of the projection extension `proj:epsg` will be replaced by `proj:code`. -> It is recommended to provide both for now. +The metadata is **required** to specify the coordinate reference system through either `proj:code` or one of the alternatives. | Field Name | Req. | Description | | ------------------------------------- | ------ | ------------------------------------------------------------ | -| proj:epsg / proj:wkt2 / proj:projjson | 1.7.11 | **REQUIRED**. One of the fields is required to be provided, recommended is `proj:epsg`. If there's no suitable EPSG code, set `proj:epsg` to `null` and add either `proj:wkt2` or `proj:projjson`. | -| proj:bbox | 1.7.7 | **REQUIRED**. The bounding box of the acquisition in the projection defined in proj:epsg / proj:wkt2 / proj:projjson. | +| proj:code / proj:wkt2 / proj:projjson | 1.7.11 | **REQUIRED**. One of the fields is required to be provided, recommended is `proj:code`. If there's no suitable CRS code, set `proj:code` to `null` and add either `proj:wkt2` or `proj:projjson`. | +| proj:bbox | 1.7.7 | **REQUIRED**. The bounding box of the acquisition in the projection defined in proj:code / proj:wkt2 / proj:projjson. | ### Links