From 344a0674f48b8023f31f2700c8792c7e57905b9b Mon Sep 17 00:00:00 2001 From: Emmanuel Mathot Date: Thu, 27 Jun 2024 16:14:05 +0200 Subject: [PATCH 1/4] Dewscribe ItemCollection and CollectionCollection --- collection-spec/collection-spec.md | 6 ++++++ item-spec/item-spec.md | 11 ++++++++++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/collection-spec/collection-spec.md b/collection-spec/collection-spec.md index 74c687eb..926f4990 100644 --- a/collection-spec/collection-spec.md +++ b/collection-spec/collection-spec.md @@ -341,3 +341,9 @@ it is allowed to re-use the metadata fields defined by extensions for Items in t This makes much sense for fields such as `platform` or `proj:epsg`, which are often the same for a whole Collection, but doesn't make much sense for `eo:cloud_cover`, which usually varies heavily across a Collection. The data provider is free to decide, which fields are reasonable to be used. + +## Generic Collection of Collections + +When a set of Items must be grouped together in unique file +>> TBC +https://github.com/radiantearth/stac-api-spec/blob/604ade6158de15b8ab068320ca41e25e2bf0e116/ogcapi-features/openapi-collections.yaml#L121 diff --git a/item-spec/item-spec.md b/item-spec/item-spec.md index c1fde3aa..fcb63951 100644 --- a/item-spec/item-spec.md +++ b/item-spec/item-spec.md @@ -313,7 +313,7 @@ that talks about common use cases of additional fields for assets. ## Media Type for STAC Item A STAC Item is a GeoJSON file ([RFC 7946](https://tools.ietf.org/html/rfc7946)), and thus should use the -[`application/geo+json`](https://tools.ietf.org/html/rfc7946#section-12) as the [Media Type](https://en.wikipedia.org/wiki/Media_type) +[`application/geo+json`](https://tools.ietf.org/html/rfc7946#section-12) as the [Media Type](https://en.wikipedia.org/wiki/Media_type) (previously known as the MIME Type). ## Extensions @@ -322,3 +322,12 @@ There are emerging best practices, which in time will evolve in to specification particular domains or uses. The [extensions page](../extensions/README.md) gives an overview about relevant extensions for STAC Items. + +## Generic Collections of Items + +When a set of Items must be grouped together in unique file, the [ItemCollection](https://github.com/radiantearth/stac-api-spec/blob/main/fragments/itemcollection/README.md) +object must be used. + +Similarly to the relationship between a GeoJSON Feature and a STAC Item, +a STAC ItemCollection should be a valid GeoJSON [FeatureCollection](https://tools.ietf.org/html/rfc7946#section-3.3) +to allow interoperability with existing tools that support GeoJSON. From a3757ea01470f1fb8db67e73c54250a9a3ec2e31 Mon Sep 17 00:00:00 2001 From: Emmanuel Mathot Date: Thu, 4 Jul 2024 09:41:41 +0200 Subject: [PATCH 2/4] moved to READMEs --- collection-spec/README.md | 7 +++++++ collection-spec/collection-spec.md | 6 ------ item-spec/README.md | 11 +++++++++++ item-spec/item-spec.md | 9 --------- 4 files changed, 18 insertions(+), 15 deletions(-) diff --git a/collection-spec/README.md b/collection-spec/README.md index ecd8046e..1dd89d85 100644 --- a/collection-spec/README.md +++ b/collection-spec/README.md @@ -44,3 +44,10 @@ a collection and be able to adapt it to most any data model. Implementors are encouraged to do what makes sense for them, and to check out the [examples](../examples/) and [other implementations](https://stacindex.org/catalogs) for current best practices. + +## Generic Collection of Collections + +In some cases, a set of Collections must be grouped together in a unique file such as in the response +of the [collections search in a catalog](https://github.com/radiantearth/stac-api-spec/tree/release/v1.0.0/ogcapi-features#collections-collections). +When a set of Items must be grouped together in unique file, the [CollectionCollection](https://github.com/radiantearth/stac-api-spec/blob/604ade6158de15b8ab068320ca41e25e2bf0e116/ogcapi-features/openapi-collections.yaml#L121) +structure as defined in STAC API must be used. diff --git a/collection-spec/collection-spec.md b/collection-spec/collection-spec.md index 926f4990..74c687eb 100644 --- a/collection-spec/collection-spec.md +++ b/collection-spec/collection-spec.md @@ -341,9 +341,3 @@ it is allowed to re-use the metadata fields defined by extensions for Items in t This makes much sense for fields such as `platform` or `proj:epsg`, which are often the same for a whole Collection, but doesn't make much sense for `eo:cloud_cover`, which usually varies heavily across a Collection. The data provider is free to decide, which fields are reasonable to be used. - -## Generic Collection of Collections - -When a set of Items must be grouped together in unique file ->> TBC -https://github.com/radiantearth/stac-api-spec/blob/604ade6158de15b8ab068320ca41e25e2bf0e116/ogcapi-features/openapi-collections.yaml#L121 diff --git a/item-spec/README.md b/item-spec/README.md index cd45a670..242e4c57 100644 --- a/item-spec/README.md +++ b/item-spec/README.md @@ -21,3 +21,14 @@ schemas validate additional fields defined in *[Common Metadata](common-metadata **Common Metadata:** A set of commonly-used fields for STAC Items is listed in *[common-metadata.md](common-metadata.md)*. + +## Generic Collections of Items + +In some cases, a set of Items must be grouped together in a unique file such as in the response +of a [collection search query](https://github.com/radiantearth/stac-api-spec/tree/release/v1.0.0/ogcapi-features#collection-items-collectionscollectioniditems). +When a set of Items must be grouped together in unique file, the [ItemCollection](https://github.com/radiantearth/stac-api-spec/blob/main/fragments/itemcollection/README.md) +object must be used. + +Similarly to the relationship between a GeoJSON Feature and a STAC Item, +a STAC ItemCollection should be a valid GeoJSON [FeatureCollection](https://tools.ietf.org/html/rfc7946#section-3.3) +to allow interoperability with existing tools that support GeoJSON. diff --git a/item-spec/item-spec.md b/item-spec/item-spec.md index fcb63951..7cd8bbe0 100644 --- a/item-spec/item-spec.md +++ b/item-spec/item-spec.md @@ -322,12 +322,3 @@ There are emerging best practices, which in time will evolve in to specification particular domains or uses. The [extensions page](../extensions/README.md) gives an overview about relevant extensions for STAC Items. - -## Generic Collections of Items - -When a set of Items must be grouped together in unique file, the [ItemCollection](https://github.com/radiantearth/stac-api-spec/blob/main/fragments/itemcollection/README.md) -object must be used. - -Similarly to the relationship between a GeoJSON Feature and a STAC Item, -a STAC ItemCollection should be a valid GeoJSON [FeatureCollection](https://tools.ietf.org/html/rfc7946#section-3.3) -to allow interoperability with existing tools that support GeoJSON. From dd6c2c022093ef769e91802a00c03dee400cae7f Mon Sep 17 00:00:00 2001 From: Emmanuel Mathot Date: Thu, 4 Jul 2024 14:07:05 +0200 Subject: [PATCH 3/4] Update item-spec/README.md Co-authored-by: Matthias Mohr --- item-spec/README.md | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/item-spec/README.md b/item-spec/README.md index 242e4c57..1fc11209 100644 --- a/item-spec/README.md +++ b/item-spec/README.md @@ -22,13 +22,11 @@ schemas validate additional fields defined in *[Common Metadata](common-metadata **Common Metadata:** A set of commonly-used fields for STAC Items is listed in *[common-metadata.md](common-metadata.md)*. -## Generic Collections of Items - -In some cases, a set of Items must be grouped together in a unique file such as in the response -of a [collection search query](https://github.com/radiantearth/stac-api-spec/tree/release/v1.0.0/ogcapi-features#collection-items-collectionscollectioniditems). -When a set of Items must be grouped together in unique file, the [ItemCollection](https://github.com/radiantearth/stac-api-spec/blob/main/fragments/itemcollection/README.md) -object must be used. - -Similarly to the relationship between a GeoJSON Feature and a STAC Item, -a STAC ItemCollection should be a valid GeoJSON [FeatureCollection](https://tools.ietf.org/html/rfc7946#section-3.3) -to allow interoperability with existing tools that support GeoJSON. +> \[!NOTE] +> In cases where a set of Items is grouped together (e.g. for providing search results), +> the [ItemCollection](https://github.com/radiantearth/stac-api-spec/blob/main/fragments/itemcollection/README.md) +> object has been defined in the STAC API specification. +> +> Similarly to the relationship between a GeoJSON Feature and a STAC Item, +> a STAC ItemCollection should be a valid GeoJSON [FeatureCollection](https://tools.ietf.org/html/rfc7946#section-3.3) +> to allow interoperability with existing tools that support GeoJSON. From c2ac766fd441b4f1c1ada6e2d485f5b0d4f00a7f Mon Sep 17 00:00:00 2001 From: Emmanuel Mathot Date: Mon, 8 Jul 2024 13:19:58 +0200 Subject: [PATCH 4/4] Update collection-spec/README.md Co-authored-by: Matthias Mohr --- collection-spec/README.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/collection-spec/README.md b/collection-spec/README.md index 1dd89d85..04f10cd9 100644 --- a/collection-spec/README.md +++ b/collection-spec/README.md @@ -44,10 +44,7 @@ a collection and be able to adapt it to most any data model. Implementors are encouraged to do what makes sense for them, and to check out the [examples](../examples/) and [other implementations](https://stacindex.org/catalogs) for current best practices. - -## Generic Collection of Collections - -In some cases, a set of Collections must be grouped together in a unique file such as in the response -of the [collections search in a catalog](https://github.com/radiantearth/stac-api-spec/tree/release/v1.0.0/ogcapi-features#collections-collections). -When a set of Items must be grouped together in unique file, the [CollectionCollection](https://github.com/radiantearth/stac-api-spec/blob/604ade6158de15b8ab068320ca41e25e2bf0e116/ogcapi-features/openapi-collections.yaml#L121) -structure as defined in STAC API must be used. +> \[!NOTE] +> In cases where a set of Collections is grouped together (e.g. for providing search results), +> the [CollectionCollection](https://github.com/radiantearth/stac-api-spec/blob/main/fragments/collectioncollection/README.md) +> object has been defined in the STAC API specification.