Merge pull request #600 from radiantearth/dev

Release 0.8.0

.gitignore

@@ -59,3 +59,7 @@ typings/
 
 # next.js build output
 .next
+
+# IntelliJ IDEA files
+.idea/
+*.iml

CHANGELOG.md

@@ -6,7 +6,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## Unreleased
 
-## [v0.8.0-RC1] - 2019-08-23
+## [v0.8.0] - 2019-10-11
 
 ### Changed
 - 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:
@@ -24,6 +24,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - Allow `various` for the `license` fields.
 - Clarified meaning of SAR and EO platform, constellation, and instrument
 - Numerous typos, clarification and general word-smithing
+- Changed GeoTIFF media type from `image/vnd.stac.geotiff` to `image/tiff; application=geotiff`, changed Cloud-optimized GeoTiff media type from `image/vnd.stac.geotiff; cloud-optimized=true` to `image/tiff; application=geotiff; profile=cloud-optimized`.
 
 ### Added
 - **stac_version**: Each Item must specify the STAC version.
@@ -40,6 +41,16 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - 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
 - [Scientific extension](extensions/scientific/README.md) can be used in Collections.
 
+### Fixed
+- Updated language, fixed typos and examples.
+- Renamed `pc:schema` to `pc:schemas` in the Point Cloud extension.
+
+### Changes since 0.8.0rc1
+- [Label extension](extensions/label/README.md):
+    - moved label:classes to be a list of Class Objects from a single Class Object in spec markdown and json schema (matching previous example JSON).
+    - moved label:overview to be a list of Overview Objects from a single Overview Object in spec markdown and json schema (matching previous example JSON).
+    - Renamed fields to use plural forms (`label:property` -> `label:properties`, `label:task` -> `label:tasks`, `label:method` -> `label:methods` and `label:overview` -> `label:overviews`)
+
 
 ## [v0.7.0] - 2019-05-06
 
@@ -132,25 +143,25 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [v0.5.2] - 2018-07-12
 
-Minor bug fixes on 0.5.1 for the schema files. Thanks @francbartoli 
+Minor bug fixes on 0.5.1 for the schema files. Thanks @francbartoli
 
 
 ## [v0.5.1] - 2018-07-06
 
 Minor bug fixes from 0.5.1 release
 
 *  [Update openapi / swagger specs for new 'links'](https://github.com/radiantearth/stac-spec/commit/480d4fb02b4a7e880c7ca01320fe2773260ba595)
-* [minor fixes on collection extension](https://github.com/radiantearth/stac-spec/pull/124) - thanks @m-mohr 
-* [minor cbers example updates](https://github.com/radiantearth/stac-spec/pull/123) - thanks @fredliporace 
+* [minor fixes on collection extension](https://github.com/radiantearth/stac-spec/pull/124) - thanks @m-mohr
+* [minor cbers example updates](https://github.com/radiantearth/stac-spec/pull/123) - thanks @fredliporace
 
 
 ## [v0.5.0] - 2018-07-01
 
 The 0.5.0 release of the STAC spec is an iteration forward on the spec, with a number of core improvements. Highlights include:
 
-* **Links is now a dictionary** - This is the most core change done. It aligns the structure with the 'asset' change in 0.5.0, making it easier for clients to look up the link that they want more easily. The schema is updated to this (and actually checks assets better now, thanks @mojodna ) 
+* **Links is now a dictionary** - This is the most core change done. It aligns the structure with the 'asset' change in 0.5.0, making it easier for clients to look up the link that they want more easily. The schema is updated to this (and actually checks assets better now, thanks @mojodna )
 
-* **Transactions Extension** - There is now a transaction extension for the STAC API, thanks to @hgs-msmith and @hgs-trutherford 
+* **Transactions Extension** - There is now a transaction extension for the STAC API, thanks to @hgs-msmith and @hgs-trutherford
 
 * **Collections iterations** @matthewhanson has evolved the collections extension, adding in some namespace type hints on it, and explaining it more clearly.
 
@@ -163,9 +174,9 @@ Full list of issues and pull requests at https://github.com/radiantearth/stac-sp
 
 A few minor improvements on the release. ([issues](https://github.com/radiantearth/stac-spec/issues?utf8=%E2%9C%93&q=milestone%3A0.4.1+))
 
-* @hgs-msmith got a swagger version of the spec, and made some minor improvements to the openapi version #103 and #102 
+* @hgs-msmith got a swagger version of the spec, and made some minor improvements to the openapi version #103 and #102
 * @francbartoli and @m-mohr pointed out some inconsistencies with landsat, so got the openapi updated #106
-* @m-mohr pointed out some issues with landsat example, so updated those #105 
+* @m-mohr pointed out some issues with landsat example, so updated those #105
 * @hgs-trutherford pointed out that the planet example was a bit confusing, so updated it to the EO profile.
 
 
@@ -174,7 +185,7 @@ A few minor improvements on the release. ([issues](https://github.com/radiantear
 The 0.4.0 is the first 'official' release of the SpatioTemporal Asset Catalog (STAC) specification!
 
 It is the result of the [ft. collins sprint](https://github.com/radiantearth/community-sprints/tree/master/03072018-ft-collins-co), the second in person meeting of the STAC community. But it also includes
-a number of improvements from remote contributors. 
+a number of improvements from remote contributors.
 
 Highlights include:
 
@@ -188,12 +199,13 @@ Highlights include:
 
 * Numerous small improvements and bug fixes.
 
-See the [milestone 0.4.0 in the issue tracker](https://github.com/radiantearth/stac-spec/milestone/3) for the complete lists of improvements. 
+See the [milestone 0.4.0 in the issue tracker](https://github.com/radiantearth/stac-spec/milestone/3) for the complete lists of improvements.
 
 Thanks @hgs-msmith, @matthewhanson, @hgs-trutherford, @rouault, @joshfix, @alkamin, @hemphillda, @jeffnaus  and @fredliporace for contributing to the spec directly, and to [everyone](https://github.com/opengeospatial/wfs3hackathon/blob/master/notes/introductions.md#participants) who participated in the [Ft Collins sprint](https://github.com/radiantearth/community-sprints/tree/master/03072018-ft-collins-co) and brought great ideas.
 
 
 [Unreleased]: https://github.com/radiantearth/stac-spec/compare/master...dev
+[v0.8.0]: https://github.com/radiantearth/stac-spec/compare/v0.7.0...v0.8.0
 [v0.7.0]: https://github.com/radiantearth/stac-spec/compare/v0.6.2...v0.7.0
 [v0.6.2]: https://github.com/radiantearth/stac-spec/compare/v0.6.1...v0.6.2
 [v0.6.1]: https://github.com/radiantearth/stac-spec/compare/v0.6.0...v0.6.1

README.md

@@ -29,7 +29,7 @@ The minimal amount is specified right now, but best practices should emerge with
 ## Current version and branches
 
 The [master branch](https://github.com/radiantearth/stac-spec/tree/master) is the 'stable' version of the spec. It is currently version 
-**0.8.0-RC1** of the specification. The 
+**0.8.0** of the specification. The 
 [dev](https://github.com/radiantearth/stac-spec/tree/dev) branch is where active development takes place, and may have inconsistent examples. 
 Whenever dev stabilizes a release is cut and we merge dev in to master. So master should be stable at any given time.
 It is possible that there may be small releases in quick succession, especially if they are nice improvements that do 
@@ -71,7 +71,7 @@ just the Items a user requests in their query. The API is specified as a couple
 **Extensions:** The *[extensions/](extensions/)* folder is where extensions live. Extensions can extend the 
 functionality of the core spec or add fields for specific domains.
 
-**Additional documents** include the current [roadmap](roadmap.md) and a complementary [how to help](how-to-help.md)
+**Additional documents** A complementary [how to help](how-to-help.md)
 document, a [list of implementations](implementations.md), 
 and a discussion of the collaboration [principles](principles.md) and specification approach.