From 3bc04a0080013872076c6f523f02f8556f82aa9d Mon Sep 17 00:00:00 2001 From: Francis Charette-Migneault Date: Tue, 29 Oct 2024 15:32:26 -0400 Subject: [PATCH] Update README.md with wording about band name references --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 62feab4..dce0f89 100644 --- a/README.md +++ b/README.md @@ -297,10 +297,9 @@ and [Common Band Names][stac-band-names]. > Therefore, `eo:bands` should either be specified *only* under the Asset containing the `mlm:model` role > (see [Model Asset](#model-asset)), or define them *both* under the Asset and Item properties. If the second > approach is selected, it is recommended that the `eo:bands` under the Asset contains only the `name` or the -> `common_name` property, such that all other details about the bands are defined at the Item level. -> An example of such representation is provided in +> `common_name` property, such that all other details about the bands are defined and cross-referenced by name +> with the Item-level band definitions. An example of such representation is provided in > [examples/item_eo_bands_summarized.json](examples/item_eo_bands_summarized.json). ->

> For an example where `eo:bands` are entirely defined in the Asset on their own, please refer to > [examples/item_eo_bands.json](examples/item_eo_bands.json) instead. >