Skip to content

Commit 3bc04a0

Browse files
authored
Update README.md with wording about band name references
1 parent 11c0ad4 commit 3bc04a0

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

README.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -297,10 +297,9 @@ and [Common Band Names][stac-band-names].
297297
> Therefore, `eo:bands` should either be specified *only* under the Asset containing the `mlm:model` role
298298
> (see [Model Asset](#model-asset)), or define them *both* under the Asset and Item properties. If the second
299299
> approach is selected, it is recommended that the `eo:bands` under the Asset contains only the `name` or the
300-
> `common_name` property, such that all other details about the bands are defined at the Item level.
301-
> An example of such representation is provided in
300+
> `common_name` property, such that all other details about the bands are defined and cross-referenced by name
301+
> with the Item-level band definitions. An example of such representation is provided in
302302
> [examples/item_eo_bands_summarized.json](examples/item_eo_bands_summarized.json).
303-
> <br><br>
304303
> For an example where `eo:bands` are entirely defined in the Asset on their own, please refer to
305304
> [examples/item_eo_bands.json](examples/item_eo_bands.json) instead.
306305
> <br><br>

0 commit comments

Comments
 (0)