Skip to content

Commit c48e2b4

Browse files
Merge pull request #294 from radiantearth/dev
release 0.6.0-rc1
2 parents 0c6451e + f118939 commit c48e2b4

File tree

90 files changed

+7673
-7171
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

90 files changed

+7673
-7171
lines changed

.circleci/config.yml

+7-5
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,15 @@ jobs:
1313
- run:
1414
name: install
1515
command: |
16-
cd json-spec
16+
cd validation
1717
npm install
1818
1919
- run:
2020
name: validate
2121
command: |
22-
cd json-spec
23-
echo 'doing nothing'
24-
# node_modules/.bin/ajv validate -s json-schema/stac-item.json -r json-schema/geojson.json -d sample.json --verbose
25-
# node_modules/.bin/ajv validate -s json-schema/stac-item.json -r json-schema/geojson.json -d examples/landsat8-sample.json --verbose
22+
cd validation
23+
npm run validate_catalog -- -d ../catalog-spec/examples/catalog.json
24+
npm run validate_collection -- -d ../collection-spec/examples/sentinel2.json
25+
npm run validate_extension -- -s ../extensions/scientific/schema.json -d ../extensions/scientific/example-merraclim.json
26+
npm run validate_item -- -d ../item-spec/examples/sample.json
27+
# ToDo: More files should be validated

CHANGELOG.md

+111
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
# Changelog
2+
All notable changes to this project will be documented in this file.
3+
4+
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
5+
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
6+
7+
## [Unreleased]
8+
9+
-
10+
11+
## [v0.6.0-rc1] - 2018-10-16
12+
13+
### Fixed
14+
- Reorganized and cleaned up repository
15+
- Fixed examples throughout
16+
17+
### Added
18+
- **Collections added**: Collections are a type of Catalog with additional fields, such as provider and license. Items must belong to a single Collection.
19+
- **Extension maturity**: Protocol for providing maturity classification for extensions based on stability and implementations.
20+
- **Commons extension**: The previous 'Collections' extension is now the 'Commons' extension and allows an Item to inherit properties from it's Collection.
21+
- **Datetime-range extension**: Extension for providing start and end datetimes.
22+
- **Scientific extension**: Extension for providings links to scientific publications relating to the data.
23+
- **rel types**: A list of supported 'rel' types are provided for use when specifying links, 'derived_from' and 'license' types added.
24+
- **eo:constellaion**: A new field in the EO specification to specify a grouping of platforms.
25+
- **stac_version**: The stac_version field is required on all Catalogs (and Collections)
26+
- **JSON schemas**: Added JSON schemas where they were missing.
27+
28+
### Changed
29+
- **Endpoints**: Main catalog endpoint at /stac, search endpoint now at /stac/search
30+
- **eo:bands**: The eo:bands field is now an array rather than a dictionary, and has been moved inside of 'properties' in a STAC Item.
31+
- **Catalog fields**: Catalogs have a smaller number of basic fields: id, stac_version, title (optional), description, and links. The new Collections type contains additional fields.
32+
- **links**: The links fields are now an array rather than a dictionary.
33+
- **properties**: Fields with the data type array or objects are allowed inside the `properties` in a STAC Item.
34+
- **description**: Description fields now allow formatting with CommonMark.
35+
- **assets**: Fields changed names: name to title and mime_type to type.
36+
37+
### Removed:
38+
* **provider**: Provider field in Items got removed. Use Collections instead.
39+
* **license**: License field in Items got removed. Use Collections instead.
40+
41+
42+
## [v0.5.2] - 2018-07-12
43+
44+
Minor bug fixes on 0.5.1 for the schema files. Thanks @francbartoli
45+
46+
47+
## [v0.5.1] - 2018-07-06
48+
49+
Minor bug fixes from 0.5.1 release
50+
51+
* [Update openapi / swagger specs for new 'links'](https://github.com/radiantearth/stac-spec/commit/480d4fb02b4a7e880c7ca01320fe2773260ba595)
52+
* [minor fixes on collection extension](https://github.com/radiantearth/stac-spec/pull/124) - thanks @m-mohr
53+
* [minor cbers example updates](https://github.com/radiantearth/stac-spec/pull/123) - thanks @fredliporace
54+
55+
56+
## [v0.5.0] - 2018-07-01
57+
58+
The 0.5.0 release of the STAC spec is an iteration forward on the spec, with a number of core improvements. Highlights include:
59+
60+
* **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 )
61+
62+
* **Transactions Extension** - There is now a transaction extension for the STAC API, thanks to @hgs-msmith and @hgs-trutherford
63+
64+
* **Collections iterations** @matthewhanson has evolved the collections extension, adding in some namespace type hints on it, and explaining it more clearly.
65+
66+
* **eo:crs to eo:epsg** In the EO profile @matthewhanson brought in a change to use EPSG code, instead of full Well Known Text, to make it easy to reference.
67+
68+
Full list of issues and pull requests at https://github.com/radiantearth/stac-spec/milestone/5?closed=1
69+
70+
71+
## [v0.4.1] - 2018-04-24
72+
73+
A few minor improvements on the release. ([issues](https://github.com/radiantearth/stac-spec/issues?utf8=%E2%9C%93&q=milestone%3A0.4.1+))
74+
75+
* @hgs-msmith got a swagger version of the spec, and made some minor improvements to the openapi version #103 and #102
76+
* @francbartoli and @m-mohr pointed out some inconsistencies with landsat, so got the openapi updated #106
77+
* @m-mohr pointed out some issues with landsat example, so updated those #105
78+
* @hgs-trutherford pointed out that the planet example was a bit confusing, so updated it to the EO profile.
79+
80+
81+
## [v0.4.0] - 2018-04-06
82+
83+
The 0.4.0 is the first 'official' release of the SpatioTemporal Asset Catalog (STAC) specification!
84+
85+
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
86+
a number of improvements from remote contributors.
87+
88+
Highlights include:
89+
90+
* Updates to the core **`Item` JSON specification**, including simplifying to a single datetime, moving thumbnails from 'links' to 'assets', making assets a dictionary for easier lookup and requiring `self` links to be absolute links.
91+
92+
* Alignment of **STAC API** with the new [WFS 3](https://github.com/opengeospatial/WFS_FES/) specification
93+
94+
* Cleanup of the **static catalog** specification for greater clarity around the catalog
95+
96+
* A first cut of an **Earth Observation Profile**, as well as a new collections extension to support it.
97+
98+
* Numerous small improvements and bug fixes.
99+
100+
See the [milestone 0.4.0 in the issue tracker](https://github.com/radiantearth/stac-spec/milestone/3) for the complete lists of improvements.
101+
102+
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.
103+
104+
105+
[Unreleased]: https://github.com/radiantearth/stac-spec/compare/master...dev
106+
[v0.6.0-rc1]: https://github.com/radiantearth/stac-spec/compare/v0.5.2...v0.6.0-rc1
107+
[v0.5.2]: https://github.com/radiantearth/stac-spec/compare/v0.5.1...v0.5.2
108+
[v0.5.1]: https://github.com/radiantearth/stac-spec/compare/v0.5.0...v0.5.1
109+
[v0.5.0]: https://github.com/radiantearth/stac-spec/compare/v0.4.1...v0.5.0
110+
[v0.4.1]: https://github.com/radiantearth/stac-spec/compare/v0.4.0...v0.4.1
111+
[v0.4.0]: https://github.com/radiantearth/stac-spec/tree/v0.4.0

CONTRIBUTING.md

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
## Contributing
2+
3+
Anyone building software that catalogs imagery or other geospatial assets is welcome to collaborate.
4+
Our goal is to be a collaboration of developers, not [architecture astronauts](http://www.joelonsoftware.com/articles/fog0000000018.html).
5+
A number of developers met in person and [sprinted on specs](https://github.com/radiantearth/boulder-sprint/)
6+
and made a number of key decisions.
7+
8+
The best way to contribute is to try to implement the specification and give feedback on what worked
9+
well and what could be improved. Currently there are a few major things to still work out, so if you
10+
are interested in implementing you should jump on our [gitter channel](https://gitter.im/SpatioTemporal-Asset-Catalog/Lobby)
11+
and check in on how ready the spec is and how you can support it. For the next bit of time you'll
12+
probably be encouraged to just do what feels best in some areas, so we can capture best practices
13+
and standardize.
14+
15+
Any proposed changes to the specification should be done as pull requests. Please make these
16+
requests against the [dev](https://github.com/radiantearth/stac-spec/tree/dev) branch (this will
17+
require you to switch from the default of 'master', which we keep so it displays first). Ideally a
18+
proposed change would also update all of the examples, but for now that is not required - the team
19+
can validate and update all examples before a release. But it is recommended to update at least a
20+
couple examples to reflect the change.
21+
22+
All pull requests require a review of two team members.

0 commit comments

Comments
 (0)