Skip to content

Commit

Permalink
Bands RFC #1213
Browse files Browse the repository at this point in the history
  • Loading branch information
m-mohr committed Sep 27, 2023
1 parent 5e5dba3 commit a1f038f
Show file tree
Hide file tree
Showing 14 changed files with 961 additions and 730 deletions.
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.

### Added

- `bands` is a new field in common metadata to replace `eo:bands` and `raster:bands` ([#1213](https://github.com/radiantearth/stac-spec/discussions/1213))
- The fields `data_type`, `nodata`, `statistics` and `unit` have been added to common metadata ([#1213](https://github.com/radiantearth/stac-spec/discussions/1213))
- The `keywords` field known from Collections is available in common metadata. ([#1187](https://github.com/radiantearth/stac-spec/issues/1187))

### Changed
Expand Down
12 changes: 6 additions & 6 deletions best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -276,7 +276,7 @@ providing them at the Asset level can prove to be very useful for using the data
with different spatial resolution than the overall best resolution. Note this should not be used for different
spatial resolutions due to specific processing of assets - look into the [raster
extension](https://github.com/stac-extensions/raster) for that use case.
- `eo:bands` ([EO extension](https://github.com/stac-extensions/eo/)):
- `bands` (e.g. in combination with the [EO extension](https://github.com/stac-extensions/eo/)):
Provide spectral band information, and order of bands, within an individual asset.
- `proj:epsg`/`proj:wkt2`/`proj:projjson` ([projection extension](https://github.com/stac-extensions/projection/)):
Specify different projection for some assets. If the projection is different
Expand All @@ -287,7 +287,7 @@ providing them at the Asset level can prove to be very useful for using the data
If assets have different spatial resolutions and slightly different exact bounding boxes,
specify these per asset to indicate the size of the asset in pixels and its exact GeoTransform in the native projection.
- `sar:polarizations` ([sar extension](https://github.com/stac-extensions/sar)):
Provide the polarization content and ordering of a specific asset, similar to `eo:bands`.
Provide the polarization content and ordering of a specific asset.
- `sar:product_type` ([sar extension](https://github.com/stac-extensions/sar)):
If mixing multiple product types within a single Item, this can be used to specify the product_type for each asset.

Expand Down Expand Up @@ -559,11 +559,11 @@ in the array are meaningless, as each Item is describing its transform, so combi
So if the values contained in the array are independently meaningful (not interconnected) and there aren't hundreds of potential
values then it is likely a good candidate to summarize.

We do highly recommend including an [`eo:bands`](https://github.com/stac-extensions/eo/blob/main/README.md#eobands)
summary if your Items implement `eo:bands`,
We do highly recommend including a [`bands`](./item-spec/common-metadata.md#bands)
summary if your Items implement `bands`,
especially if it represents just one satellite or constellation. This should be a union of all the potential bands that you
have in assets. It is ok to only add the summary at the Collection level without putting an explicit `eo:bands` summary at the
`properties` level of an Item, since that is optional. This gives users of the Collection a sense of the sensor capabilities without
have in assets. It is ok to only add the summary at the Collection level without putting `bands` at the
`properties` level of an Item. This gives users of the Collection a sense of the sensor capabilities without
having to examine specific Items or aggregate across every Item.

Note that the ranges of summaries don't have to be exact. If you are publishing a catalog that is constantly updating with
Expand Down
44 changes: 22 additions & 22 deletions examples/collection-only/collection-with-schemas.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"stac_version": "1.0.0",
"stac_extensions": [
"https://stac-extensions.github.io/eo/v1.0.0/schema.json",
"https://stac-extensions.github.io/eo/v2.0.0/schema.json",
"https://stac-extensions.github.io/sat/v1.0.0/schema.json",
"https://stac-extensions.github.io/view/v1.0.0/schema.json"
],
Expand Down Expand Up @@ -199,77 +199,77 @@
}
]
},
"eo:bands": [
"bands": [
{
"title": "B1",
"common_name": "coastal",
"center_wavelength": 4.439,
"eo:common_name": "coastal",
"eo:center_wavelength": 4.439,
"gsd": 60
},
{
"title": "B2",
"common_name": "blue",
"center_wavelength": 4.966,
"eo:common_name": "blue",
"eo:center_wavelength": 4.966,
"gsd": 10
},
{
"title": "B3",
"common_name": "green",
"center_wavelength": 5.6,
"eo:common_name": "green",
"eo:center_wavelength": 5.6,
"gsd": 10
},
{
"title": "B4",
"common_name": "red",
"center_wavelength": 6.645,
"eo:common_name": "red",
"eo:center_wavelength": 6.645,
"gsd": 10
},
{
"title": "B5",
"center_wavelength": 7.039,
"eo:center_wavelength": 7.039,
"gsd": 20
},
{
"title": "B6",
"center_wavelength": 7.402,
"eo:center_wavelength": 7.402,
"gsd": 20
},
{
"title": "B7",
"center_wavelength": 7.825,
"eo:center_wavelength": 7.825,
"gsd": 20
},
{
"title": "B8",
"common_name": "nir",
"center_wavelength": 8.351,
"eo:common_name": "nir",
"eo:center_wavelength": 8.351,
"gsd": 10
},
{
"title": "B8A",
"center_wavelength": 8.648,
"eo:center_wavelength": 8.648,
"gsd": 20
},
{
"title": "B9",
"center_wavelength": 9.45,
"eo:center_wavelength": 9.45,
"gsd": 60
},
{
"title": "B10",
"center_wavelength": 1.3735,
"eo:center_wavelength": 1.3735,
"gsd": 60
},
{
"title": "B11",
"common_name": "swir16",
"center_wavelength": 1.6137,
"eo:common_name": "swir16",
"eo:center_wavelength": 1.6137,
"gsd": 20
},
{
"title": "B12",
"common_name": "swir22",
"center_wavelength": 2.2024,
"eo:common_name": "swir22",
"eo:center_wavelength": 2.2024,
"gsd": 20
}
]
Expand Down
Loading

0 comments on commit a1f038f

Please sign in to comment.