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
-**History**: [Prior to March 2nd 2021](https://github.com/radiantearth/stac-spec/commits/4a841605ad83a16f45fcb88ed90117d6c77a7f04/extensions/processing)
9
10
10
-
Processing metadata is considered to be data that indicate from which processing chain a data originates and how the data itself has been produced.\
11
+
Processing metadata is considered to be data that indicate from which processing chain a data originates and how the data itself has been produced.
11
12
Overall, it helps to increase traceability and search among processing levels and multiple algorithm versions.
12
13
13
-
Often, data items are the result of one or more waterfall processing pipeline. Tracing information such as the processing facility,\
14
+
Often, data items are the result of one or more waterfall processing pipeline. Tracing information such as the processing facility,
14
15
the algorithm version or the processing date helps in the data version management.
15
16
16
-
This extension applies to STAC Items and STAC Collections. As these processing information are often closely bound to the Collection level\
17
+
This extension applies to STAC Items and STAC Collections. As these processing information are often closely bound to the Collection level
17
18
and therefore are shared across all items, it is recommended adding the fields to the corresponding STAC Collection.
18
19
19
20
- Examples:
@@ -22,10 +23,10 @@ and therefore are shared across all items, it is recommended adding the fields t
22
23
-[JSON Schema](json-schema/schema.json)
23
24
-[Changelog](./CHANGELOG.md)
24
25
25
-
## Item Properties and Collection Fields
26
+
## Item Properties and Collection Provider Fields
26
27
27
28
- For Items, the fields are placed in the properties. Additionally, STAC allows all Item properties to be used in the Asset Object.
28
-
- For Collections, the fields are placed in the [Provider Objects](https://github.com/radiantearth/stac-spec/blob/master/collection-spec/collection-spec.md#provider-object)\
29
+
- For Collections, the fields are placed in the [Provider Objects](https://github.com/radiantearth/stac-spec/blob/master/collection-spec/collection-spec.md#provider-object)
29
30
for the `providers` that have the role `producer` or `processor` assigned.
30
31
31
32
| Field Name | Type | Description |
@@ -47,34 +48,28 @@ In Items that declare this `processing` extension, it is recommended to add one
47
48
48
49
### Suggested Processing Levels
49
50
50
-
The `processing:level` is the name that is commonly used to refer to that processing level properties.\
51
+
The `processing:level` is the name that is commonly used to refer to that processing level properties.
51
52
The table below shows some processing level used by the industry for some data product.
52
53
53
-
Each level represents a step in the abstraction process by which data relevant to physical information (raw, level 0, level 1)\
54
-
are turned into data relevant to geo physical information (level 2, level 3), and finally turned into data relevant to thematic information (level4)
54
+
Each level represents a step in the abstraction process by which data relevant to physical information (raw, level 0, level 1)
55
+
are turned into data relevant to geo physical information (level 2, level 3), and finally turned into data relevant to thematic information (level 4)
55
56
56
57
This list is not exhaustive and can be extended with the processing level specific to a data product.
57
58
58
-
| Level Name | Description | Typical data product |
| RAW | Data in their original packets, as received from the instrument. |[Sentinel-1 RAW](https://sentinel.esa.int/web/sentinel/technical-guides/sentinel-1-sar/products-algorithms/level-0-products/raw)|
61
-
| L0 | Reconstructed unprocessed instrument data at full space time resolution with all available supplemental information to be used in subsequent processing (e.g., ephemeris, health and safety) appended. |[Landsat Level 0](https://www.usgs.gov/media/files/landsat-8-level-0-reformatted-data-format-control-book)|
62
+
| L0 | Reconstructed unprocessed instrument data at full space time resolution with all available supplemental information to be used in subsequent processing (e.g., ephemeris, health and safety) appended. |[Landsat Level 0](https://www.usgs.gov/media/files/landsat-8-level-0-reformatted-data-format-control-book)|
62
63
| L1 | Unpacked, reformatted level 0 data, with all supplemental information to be used in subsequent processing appended. Optional radiometric and geometric correction applied to produce parameters in physical units. Data generally presented as full time/space resolution. A wide variety of sub level products are possible (see below). |[Sentinel-1 Level 1](https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/product-types-processing-levels/level-1)[Sentinel-2 L1A](https://sentinel.esa.int/web/sentinel/user-guides/sentinel-2-msi/product-types/level-1a)|
63
-
| L2 | Retrieved environmental variables (e.g., ocean wave height, soil-moisture, ice concentration) at the same resolution and location as the level 1 source data. A wide variety of sub-level products are possible (see below). |[Sentinel-2 L2A](https://earth.esa.int/web/sentinel/technical-guides/sentinel-2-msi/level-2a-processing)|
64
-
| L3 | Data or retrieved environmental variables which have been spatiallyand/or temporally re-sampled (i.e., derived from level 1 or 2 products). Such re-sampling may include averaging and compositing. A wide variety of sub-level products are possible (see below). |[ENVISAT Level-3](http://envisat.esa.int/level3/), [Sentinel-2 L3](https://s2gm.sentinel-hub.com/)|
65
-
| L4 | Model output or results from analyses of lower level data (i.e.,variables that are not directly measured by the instruments, but are derived from these measurements) ||
66
-
67
-
## Extensions
68
-
69
-
The [extensions page](https://stac-extensions.github.io/) gives an overview about related extensions. Of particular relevance to processing levels:
70
-
71
-
- the [Sat Extension Specification](https://github.com/stac-extensions/sat/blob/main/README.md) to describe data collected from a satellite.
64
+
| L2 | Retrieved environmental variables (e.g., ocean wave height, soil-moisture, ice concentration) at the same resolution and location as the level 1 source data. A wide variety of sub-level products are possible (see below). |[Sentinel-2 L2A](https://earth.esa.int/web/sentinel/technical-guides/sentinel-2-msi/level-2a-processing)|
65
+
| L3 | Data or retrieved environmental variables which have been spatiallyand/or temporally re-sampled (i.e., derived from level 1 or 2 products). Such re-sampling may include averaging and compositing. A wide variety of sub-level products are possible (see below). |[ENVISAT Level-3](http://envisat.esa.int/level3/), [Sentinel-2 L3](https://s2gm.sentinel-hub.com/)|
66
+
| L4 | Model output or results from analyses of lower level data (i.e.,variables that are not directly measured by the instruments, but are derived from these measurements) ||
72
67
73
68
## Relation types
74
69
75
70
The following types should be used as applicable `rel` types in the
0 commit comments