You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-18Lines changed: 25 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ To describe frame start and end times, use the
36
36
| sar:frequency_band| string |**REQUIRED.** The common name for the frequency band to make it easier to search for bands across instruments. See section "Common Frequency Band Names" for a list of accepted names. |
37
37
| sar:center_frequency| number | The center frequency of the instrument, in gigahertz (GHz). |
38
38
| sar:polarizations|\[string]|**REQUIRED.** Any combination of polarizations. |
39
-
| sar:product_type| string |**REQUIRED.** The product type, for example `SSC`, `MGD`, or `SGC`|
39
+
| sar:product_type| string |***DEPRECATED** in favor of [`product:type`](https://github.com/stac-extensions/product).* The product type, for example `SSC`, `MGD`, or `SGC`|
40
40
| sar:resolution_range| number | The range resolution, which is the maximum ability to distinguish two adjacent targets perpendicular to the flight path, in meters (m). |
41
41
| sar:resolution_azimuth| number | The azimuth resolution, which is the maximum ability to distinguish two adjacent targets parallel to the flight path, in meters (m). |
42
42
| sar:pixel_spacing_range| number | The range pixel spacing, which is the distance between adjacent pixels perpendicular to the flight path, in meters (m). Strongly RECOMMENDED to be specified for products of type `GRD`. |
@@ -61,23 +61,6 @@ for instance for `HH+HV` add both `HH` and `HV`.
61
61
**Important:** In the `properties` of a STAC Item `sar:polarizations` must be a set with unique elements.
62
62
In assets `sar:polarizations` can contain duplicate elements and, if possible, the polarizations must appear in the same order as in the file.
63
63
64
-
#### sar:product_type
65
-
66
-
The product type defines the type of processed data contained in the assets. A list of suggestions include:
This can vary by data provider, who all may use slightly different names. Sentinel-1 for instance uses `GRD`, which is the same as the more general `MGD` and `SLC` instead of `SGC`.
80
-
81
64
### Common Frequency Band Names
82
65
83
66
The `sar:frequency_band` is the name that is commonly used to refer to that band's spectral
@@ -94,6 +77,30 @@ properties. The table below shows the common name based on the wavelength and fr
94
77
| K | 1.1 - 1.7 | 18 - 26.5 ||
95
78
| Ka | 0.75 - 1.1 | 26.5 - 40 ||
96
79
80
+
### Product type
81
+
82
+
The product type for SAR data defines the type of processed data contained in the assets.
83
+
A list of suggestions for [`product:type`](https://github.com/stac-extensions/product) include:
This can vary by data provider, who all may use slightly different names.
97
+
Sentinel-1 for instance uses `GRD`, which is the same as the more general `MGD` and `SLC` instead of `SGC`.
98
+
99
+
**Note:**
100
+
- v1.0 of the extension did require `sar:product_type`.
101
+
- v1.1 deprecates `sar:product_type` and it's not required any longer, but `product:type` is **strongly recommended**.
102
+
- v2.0 will require `product:type` as part of this extension and remove `sar:product_type`.
103
+
97
104
### Date and Time
98
105
99
106
In SAR, you usually have frame start and end time. To describe this information it is recommended to use the [Date and Time Range fields](https://github.com/radiantearth/stac-spec/blob/master/item-spec/common-metadata.md#date-and-time-range).
0 commit comments