You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Item `title` definition moved from core Item fields to [Common Metadata Basics](item-spec/common-metadata.md#basics)
21
-
fields. No change is required for STAC Items.
22
-
-`putFeature` can return a `PreconditionFailed` to provide more explicit information when the resource has changed in the server
23
-
-[Sort extension](api-spec/extensions/sort) now uses "+" and "-" prefixes for GET requests to denote sort order.
24
-
- Clarified how `/search` links must be added to `/` and changed that links to both GET and POST must be provided now that the method can be specified in links.
25
-
- Moved angle definitions between extensions `view` and `sat`
- Moved angle definitions from extensions `eo` and new `view` extension
43
+
-`eo:off_nadir` -> `view:off_nadir`
44
+
-`eo:azimuth` -> `view:azimuth`
45
+
-`eo:incidence_angle` -> `view:incidence_angle`
46
+
-`eo:sun_azimuth` -> `view:sun_azimuth`
47
+
-`eo:sun_elevation` -> `view:sun_elevation`
72
48
- Extensions:
73
49
- Data Cube extension: Changed allowed formats (removed PROJ string, added PROJJSON / WKT2) for reference systems
74
50
-[Checksum extension](extensions/checksum/README.md) is now using self-identifiable hashes ([Multihash](https://github.com/multiformats/multihash))
@@ -80,28 +56,43 @@ fields. No change is required for STAC Items.
80
56
- Fields extension has a simplified format for GET parameters
81
57
-`search` extension renamed to `context` extension. JSON object renamed from `search:metadata` to `context`
82
58
- Removed "next" from the search metadata and query parameter, added POST body and headers to the links for paging support
83
-
- Query Extension - type restrictions on query predicates are more accurate, which may require additional implementation support.
59
+
- Query Extension - type restrictions on query predicates are more accurate, which may require additional implementation support
60
+
- Item `title` definition moved from core Item fields to [Common Metadata Basics](item-spec/common-metadata.md#basics)
61
+
fields. No change is required for STAC Items.
62
+
-`putFeature` can return a `PreconditionFailed` to provide more explicit information when the resource has changed in the server
63
+
-[Sort extension](api-spec/extensions/sort) now uses "+" and "-" prefixes for GET requests to denote sort order.
64
+
- Clarified how `/search` links must be added to `/` and changed that links to both GET and POST must be provided now that the method can be specified in links
84
65
85
66
### Removed
86
67
-`version` field in STAC Collections. Use [Version Extension](extensions/version/README.md) instead
87
68
-`summaries` field from Catalogs. Use Collections instead
88
-
- Asset Types (pre-defined values for the keys of individual assets, *not* media types) in Items. Use the asset's `roles` instead.
89
-
-`license` field doesn't allow SPDX expressions any longer. Use `various` and links instead.
69
+
- Asset Types (pre-defined values for the keys of individual assets, *not* media types) in Items. Use the asset's `roles` instead
70
+
-`license` field doesn't allow SPDX expressions any longer. Use `various` and links instead
90
71
- Extensions:
91
72
-`eo:platform`, `eo:instrument`, `eo:constellation` from EO extension, and `sar:platform`, `sar:instrument`, `sar:constellation` from the [SAR extension](extensions/sar/README.md)
92
73
- Removed from EO extension field `eo:epsg` in favor of `proj:epsg`
93
74
-`gsd` and `accuracy` from `eo:bands` in the [EO extension](extensions/eo/README.md)
94
75
-`sar:absolute_orbit` and `sar:center_wavelength` fields from the [SAR extension](extensions/sar/README.md)
95
76
-`data_type` and `unit` from the `sar:bands` object in the [SAR extension](extensions/sar/README.md)
96
-
- Datetime Range (`dtr`) extension. Use the [Common Metadata fields](item-spec/common-metadata.md) instead.
77
+
- Datetime Range (`dtr`) extension. Use the [Common Metadata fields](item-spec/common-metadata.md) instead
97
78
- STAC API:
98
79
-`next` from the search metadata and query parameter
80
+
- In API, removed any mention of using media type `multipart/form-data` and `x-www-form-urlencoded`
99
81
100
82
### Fixed
101
83
102
-
- The `license` field in Item and Collection spec explicitly mentions that the value `proprietary` without a link means that the data is private.
103
-
- Clarified how to fill `stac_extensions`.
84
+
- The `license` field in Item and Collection spec explicitly mentions that the value `proprietary` without a link means that the data is private
85
+
- Clarified how to fill `stac_extensions`
104
86
- More clarifications; typos fixed
87
+
- Fixed Item JSON Schema now `allOf` optional Common Metadata properties are evaluated
88
+
- Clarified usage of optional Common Metadata fields for STAC Items
89
+
- Clarified usage of paging options, especially in relation to what OGC API - Features offers
90
+
- Allow Commonmark in asset description, as it's allowed everywhere else
91
+
- Put asset description in the API
92
+
- Fixed API spec regarding license expressions
93
+
- Added missing schema in the API Version extension
94
+
- Fixed links in the Landsat example in the collection-spec
Copy file name to clipboardExpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ The minimal amount is specified right now, but best practices should emerge with
29
29
## Current version and branches
30
30
31
31
The [master branch](https://github.com/radiantearth/stac-spec/tree/master) is the 'stable' version of the spec. It is currently version
32
-
**0.9.0-rc2** of the specification. The
32
+
**0.9.0** of the specification. The
33
33
[dev](https://github.com/radiantearth/stac-spec/tree/dev) branch is where active development takes place, and may have inconsistent examples.
34
34
Whenever dev stabilizes a release is cut and we merge dev in to master. So master should be stable at any given time.
35
35
It is possible that there may be small releases in quick succession, especially if they are nice improvements that do
| stac_version | string |**REQUIRED.** The STAC version the catalog implements. STAC versions can be mixed, but please keep the [recommended best practices](../best-practices.md#mixing-stac-versions) in mind. |
99
-
| stac_extensions |[string]| A list of extensions the Catalog implements. |
100
-
| id | string |**REQUIRED.** Identifier for the catalog. |
101
-
| title | string | A short descriptive one-line title for the catalog. |
102
-
| description | string |**REQUIRED.** Detailed multi-line description to fully explain the catalog. [CommonMark 0.29](http://commonmark.org/) syntax MAY be used for rich text representation. |
103
-
| links |[[Link Object](#link-object)]|**REQUIRED.** A list of references to other documents. |
| stac_version | string |**REQUIRED.** The STAC version the catalog implements. STAC versions can be mixed, but please keep the [recommended best practices](../best-practices.md#mixing-stac-versions) in mind. |
99
+
| stac_extensions |[string]| A list of extension identifiers the Catalog implements. |
100
+
| id | string |**REQUIRED.** Identifier for the catalog. |
101
+
| title | string | A short descriptive one-line title for the catalog. |
102
+
| description | string |**REQUIRED.** Detailed multi-line description to fully explain the catalog. [CommonMark 0.29](http://commonmark.org/) syntax MAY be used for rich text representation. |
103
+
| links |[[Link Object](#link-object)]|**REQUIRED.** A list of references to other documents. |
104
104
105
105
**stac_extensions**: A list of extensions the Catalog implements. This does NOT declare the extensions of children or Items. The list contains URLs to the JSON Schema files it can be validated against. For official [content extensions](../extensions/README.md#list-of-content-extensions), a "shortcut" can be used. This means you can specify the folder name of the extension, for example `pointcloud` for the Point Cloud extension. This does *not* apply for API extensions. If the versions of the extension and the catalog diverge, you can specify the URL of the JSON schema file.
106
106
This list must only contain extensions that extend the Catalog itself, see the the 'Scope' column in the list of extensions.
@@ -145,7 +145,7 @@ might look something like this:
145
145
146
146
```json
147
147
{
148
-
"stac_version": "0.9.0-rc2",
148
+
"stac_version": "0.9.0",
149
149
"id": "NAIP",
150
150
"description": "Catalog of NAIP Imagery",
151
151
"links": [
@@ -163,7 +163,7 @@ A typical '_child_' sub-catalog could look similar:
0 commit comments