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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+34-1
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,40 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
6
6
7
7
## Unreleased
8
8
9
-
None yet.
9
+
## [v0.8.0-RC1] - 2019-08-23
10
+
11
+
### Changed
12
+
- Updated specification to base on WFS3 draft 2 (OGC API - Features - Part 1: Core, v1.0.0-draft.2). This leads to many changes in the API and one change in STAC collections, notably:
13
+
- The structure of the field `extent` in STAC and WFS Collections changed.
14
+
- Query parameter `time` was renamed to `datetime` and accepts slightly different values.
15
+
- WFS links have additional fields `hreflang` and `length`.
16
+
- WFS Collections have additional fields `crs` and `itemType`.
17
+
- `time` API parameter changed to `datetime`
18
+
- The API intersects parameter now accepts a GeoJSON Geometry (any type) *instead* of a GeoJSON Feature.
19
+
- API: Clarification on `include` and `exclude` parameters in the field extension and notes on default values.
20
+
- API: queries should contain either `bbox` or `intersects`.
21
+
- API: Core API now has reserved parameters to prevent overlap with extensions
22
+
- Updated bbox definitions in API, Item, and Collection specs to include support for optional elevation values.
23
+
- Moved Single Item Extension to core (`license` and `providers` properties for Items).
24
+
- Allow `various` for the `license` fields.
25
+
- Clarified meaning of SAR and EO platform, constellation, and instrument
26
+
- Numerous typos, clarification and general word-smithing
27
+
28
+
### Added
29
+
-**stac_version**: Each Item must specify the STAC version.
30
+
-**stac_extensions**: Introduced this field for Items, Catalogs and Collections.
31
+
- Property `summaries` have been added to catalogs and collections.
32
+
- API Transaction extension supports optimistic locking through use of the ETag header.
33
+
- Asset Definition Extension added to Collections to allow specifying details about Assets that may appear in member Items.
34
+
-[Single File Catalog extension](extensions/single-file-stac/README.md) added as a format to have a set of Collections and Items in a single file.
35
+
-[Label extension](extensions/label/README.md) added with additional fields for describing labeled data, such as used for training data or from the output of a classification
36
+
- Timestamp fields added to `Item`: `created` and `updated` to refer to the datetime the metadata file was created or updated.
37
+
- Added Search Metadata API extension which adds fields to a response from a STAC API such as the number of items found and how many were returned.
38
+
- ItemCollection class added to spec that is a GeoJSON FeatureCollection of Items, such as what would be returned from a search. Located in item directory.
39
+
-`in` operator added to the query extension (to check if value is in a list of values)
40
+
- New bands added to the [common band names](extensions/eo/README.md#common-band-names) for the EO extension: yellow, rededge, and 2 narrow NIR bands
41
+
-[Scientific extension](extensions/scientific/README.md) can be used in Collections.
Copy file name to clipboardExpand all lines: README.md
+5-6
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.7.0** of the specification. The
32
+
**0.8.0-RC1** 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
@@ -63,11 +63,10 @@ In the context of STAC it is most likely a collection of STAC Items that is made
63
63
It includes things like the spatial and temporal extent of the data, the license, keywords, etc.
64
64
It enables discovery at a higher level than individual items, providing a simple way to describe sets of data.
65
65
66
-
**[api-spec/](api-spec/)** extends the core publishing capabilities of STAC with an active REST search endpoint that returns
67
-
just the Items a user requests in their query. It is specified as a couple [OpenAPI](http://openapis.org) documents, one
68
-
[standalone](api-spec/STAC-standalone.yaml) and one that is [integrated with WFS3](api-spec/WFS3core%2BSTAC.yaml)
69
-
(see [WFS3 on GitHub](https://github.com/opengeospatial/wfs_fes) for info on it). The documents also include the `/stac/`
70
-
endpoint which is a way for a dynamic server to provide catalog and collection browsing.
66
+
**[api-spec/](api-spec/)** extends the core publishing capabilities of [WFS 3](https://github.com/opengeospatial/wfs_fes) with two
67
+
STAC-related endpoints. They add catalog and collection browsing and an active STAC REST search endpoint that returns
68
+
just the Items a user requests in their query. The API is specified as a couple [OpenAPI](http://openapis.org) documents, one is just the
69
+
[minimal core API](api-spec/STAC.yaml) and the other one [integrates the API extensions](api-spec/STAC-extensions.yaml).
71
70
72
71
**Extensions:** The *[extensions/](extensions/)* folder is where extensions live. Extensions can extend the
73
72
functionality of the core spec or add fields for specific domains.
0 commit comments