Removed deprecated fields, require alternative external fields

Author: m-mohr

CHANGELOG.md

@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Removed
+
+- `sar:instrument_mode`
+- `sar:product_type`
+
 ## [v1.2.0] - 2025-03-29
 
 ### Added

README.md

@@ -64,17 +64,15 @@ The fields in the table below can be used in these parts of STAC documents:
 | sar:observation_direction   | string    | Antenna pointing direction relative to the flight trajectory of the satellite, either `left` or `right`. |
 | sar:relative_burst          | number    | Identification number that uniquely identifies a burst cycle within each repeat cycle. |
 | sar:beam_ids                | \[string] | Composition of the swath of the SAR acquision referencing the beam identifiers. |
-| sar:product_type            | string    | ***DEPRECATED** in favor of [`product:type`](https://github.com/stac-extensions/product).* See [Product type](#product-type). |
-| sar:instrument_mode         | string    | ***DEPRECATED** in favor of [`altm:instrument_mode`](https://github.com/stac-extensions/altimetry).* See [Instrument details](#instrument-details). |
 
 > \[!CAUTION]  
 >
 > - v1.0 of the extension did require `sar:product_type` and `sar:instrument_mode`.
-> - v1.1 deprecates `sar:product_type` and it's not required any longer, but
+> - v1.1 deprecated `sar:product_type` and it's not required any longer, but
 >   [`product:type`](https://github.com/stac-extensions/product) is **strongly recommended**.
-> - v1.2 deprecates `sar:instrument_mode` and it's not required any longer, but
+> - v1.2 deprecated `sar:instrument_mode` and it's not required any longer, but
 >   [`altm:instrument_mode` and `altm:instrument_type`](https://github.com/stac-extensions/altimetry) are **strongly recommended**.
-> - v2.0 is going to remove `sar:product_type` and `sar:instrument_mode`.
+> - v2.0 removed `sar:product_type` and `sar:instrument_mode`.
 
 ### Additional Field Information
 

json-schema/schema.json

@@ -138,11 +138,9 @@
     "require_any_field": {
       "$comment": "Please list all fields here so that we can force the existence of one of them in other parts of the schemas.",
       "anyOf": [
-        {"required": ["sar:instrument_mode"]},
         {"required": ["sar:frequency_band"]},
         {"required": ["sar:center_frequency"]},
         {"required": ["sar:polarizations"]},
-        {"required": ["sar:product_type"]},
         {"required": ["sar:resolution_range"]},
         {"required": ["sar:resolution_azimuth"]},
         {"required": ["sar:pixel_spacing_range"]},
@@ -158,14 +156,6 @@
       "$comment": "Add your new fields here. Don't require them here, do that above in the item schema.",
       "type": "object",
       "properties": {
-        "sar:instrument_mode": {
-          "title": "Instrument Mode",
-          "type": "string",
-          "examples": [
-            "WV"
-          ],
-          "minLength": 1
-        },
         "sar:frequency_band": {
           "title": "Frequency Band",
           "type": "string",
@@ -187,16 +177,6 @@
         "sar:polarizations": {
           "$ref": "#/definitions/sar_polarizations"
         },
-        "sar:product_type": {
-          "title": "Product type",
-          "type": "string",
-          "minLength": 1,
-          "examples": [
-            "SSC",
-            "MGD",
-            "SGC"
-          ]
-        },
         "sar:resolution_range": {
           "title": "Resolution range (m)",
           "type": "number",