Emmanuel Mathot

I agree. I created a [new issue](https://github.com/radiantearth/stac-spec/issues/1300) for the required title in 2.0.

IMO, the problem is in the multiple definitions of `gsd`. One given [here](https://github.com/radiantearth/stac-spec/blob/master/item-spec/common-metadata.md#gsd) is not inline with the one given [here](https://github.com/radiantearth/stac-spec/blob/master/item-spec/item-spec.md#additional-fields-for-assets) ? Personally, we apply the latter one and use...

> Mention that the top-level metadata might be nominal. @m-mohr Could you please recall me what you meant by nominal?

Where is the CollectionCollection definition?I only find this reference: https://github.com/radiantearth/stac-api-spec/tree/main/ogcapi-features#collections-collections

Concerning the last commit, there is no way to make suggestions on unchanged file so I simply committed it. Let me know.

> We should discuss whether we want to explicitly disallow to use of "bands" for single-band use-cases where instead people must provide the properties at the asset/item properties level directly....

you mean allowing single band to be able to set properties only at band level?

The env var name can be different. then the regex is more flexible in order to support virtual hosting path style. e.g. `https://bucket1.s3.acme.org`, `https://bucket2.s3.acme.org`, `https://bucket3.s3.acme.org` --> `^https://.*\.s3\.acme\.org`

documentation added

Hello @vincentsarago Thanks for your comment. I understand the will to keep rasterio aligned with GDAL. Digging for more information for this discussion, I figured out that in any case...