Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added required c:id to Item, moved "optional" label #124

Merged
merged 1 commit into from
Jul 6, 2018
Merged

Added required c:id to Item, moved "optional" label #124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions extensions/stac-collection-spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ A group of STAC `Item` objects from a single source can share a lot of common me
| element | type info | name | description |
|----------------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------|
| c:id | string | Collection ID | Machine readable ID for the collection
| c:name | string | Collection Name (optional) | A name given to the Collection, used for display
| c:name | string (optional) | Collection Name | A name given to the Collection, used for display
| c:description | string (optional) | Collection Description | A human readable description of the collection

A `Collection` does not have many specific fields, as it may contain any fields that are in the core spec as well as any other extension. This provides maximum flexibility to data providers, as some the set of common metadata fields can vary between different types of data. For instance, Landsat and Sentinel data always has a eo:off_nadir value of 0, because those satellites are always pointed downward (i.e., nadir), while satellite that can be pointed will have varying eo:off_nadir values.
Expand Down Expand Up @@ -61,6 +61,7 @@ The fields from the `Collection` record can be merged with an `Item` record to g
{
"id": "SCENE_001",
"properties": {
"c:id": "my_collection",
"datetime": "2017-01-01T00:00:00Z",
"geometry": {...}
},
Expand Down Expand Up @@ -188,4 +189,4 @@ This is an example `Collection` for Landsat-8 imagery and uses the [EO extension
"fwhm": 1.0
}
}
```
```