Skip to content

Commit ceff596

Browse files
authored
Merge pull request #1305 from radiantearth/dev
Merge to master for 1.1.0-beta.1 release
2 parents fd8fb4e + 5076180 commit ceff596

Some content is hidden

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

48 files changed

+2901
-1387
lines changed

.circleci/config.yml

+3-3
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ jobs:
33
test_examples_node:
44
working_directory: ~/stac
55
docker:
6-
- image: circleci/node:12
6+
- image: cimg/node:lts
77
steps:
88
- checkout
99
- run:
@@ -27,7 +27,7 @@ jobs:
2727
test_docs:
2828
working_directory: ~/stac
2929
docker:
30-
- image: circleci/node:12
30+
- image: cimg/node:lts
3131
steps:
3232
- checkout
3333
- run:
@@ -39,7 +39,7 @@ jobs:
3939
publish_schemas:
4040
working_directory: ~/stac
4141
docker:
42-
- image: circleci/node:12
42+
- image: cimg/node:lts
4343
steps:
4444
- checkout
4545
- run:

.remarkignore

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
/CODE_OF_CONDUCT.md
2+
/CHANGELOG.md
3+
.github/pull_request_template.md

CHANGELOG.md

+57-5
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,63 @@
11
<!--lint disable maximum-line-length-->
22
# Changelog
3+
34
All notable changes to this project will be documented in this file.
45

56
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
67
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
78

89
## [Unreleased]
910

11+
## [v1.1.0-beta.1] - 2024-08-08
12+
13+
### Added
14+
15+
- `bands` is a new field in common metadata to replace `eo:bands` and `raster:bands` ([#1213](https://github.com/radiantearth/stac-spec/discussions/1213))
16+
- The fields `data_type`, `nodata`, `statistics` and `unit` have been added to common metadata ([#1213](https://github.com/radiantearth/stac-spec/discussions/1213))
17+
- The `keywords` field known from Collections is available in common metadata. ([#1187](https://github.com/radiantearth/stac-spec/issues/1187))
18+
- New fields `method`, `headers` and `body` in the Link Object. ([#1198](https://github.com/radiantearth/stac-spec/issues/1198))
19+
- The `license` field additionally supports SPDX expressions and the value `other`.
20+
- The `roles` field known from Assets and Providers is available in common metadata. ([#1267](https://github.com/radiantearth/stac-spec/issues/1267))
21+
- The `collection` relation type is added to the list of known relation types. ([#1236](https://github.com/radiantearth/stac-spec/issues/1236))
22+
- The `item_assets` field in Collections are integrated from extension into the core Collection spec. ([#1275](https://github.com/radiantearth/stac-spec/issues/1275))
23+
- Validation for absolute self link in item schema. ([#1281](https://github.com/radiantearth/stac-spec/issues/1281))
24+
- Best practice: Link titles should exactly reflect the title of the corresponding entity ([#1168](https://github.com/radiantearth/stac-spec/issues/1168))
25+
26+
### Changed
27+
28+
- Common Metadata:
29+
- Clarify in various field descriptions that the fields do not only apply to Items
30+
- Validate the fields also in Catalogs, Collections and Links
31+
- If a description is given, require that it is not empty
32+
- Clarified URL resolving mechanics, e.g. that trailing slashes in URLs are significant ([#1212](https://github.com/radiantearth/stac-spec/discussions/1212))
33+
- All JSON Schema `$id` values no longer have `#` at the end.
34+
- Two spatial bounding boxes in a Collection don't make sense and will be reported as invalid by the schema. ([#1243](https://github.com/radiantearth/stac-spec/issues/1243))
35+
- Clarify in descriptions that start_datetime and end_datetime are inclusive bounds ([#1280](https://github.com/radiantearth/stac-spec/issues/1280))
36+
- Moved the STAC structural relations into commons
37+
- Moved general descriptions about Assets and Links into commons
38+
- Moved common metadata from the item-spec into commons, but kept the JSON schemas in the item-spec for backward compatibility
39+
40+
### Deprecated
41+
42+
- `license`: The values `proprietary` and `various` are deprecated in favor of SPDX expressions and `other`.
43+
44+
### Removed
45+
46+
- "Strongly recommended" language around `self` links in the item spec. ([#1173](https://github.com/radiantearth/stac-spec/pull/1173))
47+
48+
### Fixed
49+
50+
- Several typos and minor language changes
51+
- Clarification on unique parent link requirement ([#1279](https://github.com/radiantearth/stac-spec/pull/1279))
52+
- Clarified that collection IDs should be unique across all collections in the corresponding root catalog
53+
- Clarified that item IDs should be unique per collection
54+
- Clarified which media types should be used for the hierarchical relation types
55+
- Clarified in the Markdown specification that GeometryCollections are not allowed as Item Geometry ([#1160](https://github.com/radiantearth/stac-spec/pull/1160))
56+
- Best practice: Do not recommend subdirectories for Items without sidecar files ([#1195](https://github.com/radiantearth/stac-spec/pull/1195))
57+
- Clarified that multiple collections can point to an Item, but an Item can only point back to a single collection. ([#1273](https://github.com/radiantearth/stac-spec/pull/1273))
58+
- Restructured asset role types and clarified usage of the roles `thumbnail`, `overview` and `visual` ([#1272](https://github.com/radiantearth/stac-spec/pull/1272))
59+
- Clarified that JSON Schema draft-07 is the default version for Collection summaries and other versions may not be supported
60+
1061
## [v1.0.0] - 2021-05-25
1162

1263
### Added
@@ -169,7 +220,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
169220
### Added
170221
- ItemCollection requires `stac_version` field, `stac_extensions` has also been added
171222
- A `description` field has been added to Item assets (also Asset definitions extension)
172-
- Field `mission` to [Common Metadata fields](item-spec/common-metadata.md)
223+
- Field `mission` to [Common Metadata fields](commons/common-metadata.md)
173224
- Extensions:
174225
- [Version Indicators extension](https://github.com/stac-extensions/version/blob/main/README.md), new `version` and `deprecated` fields in STAC Items and Collections
175226
- Data Cube extension can be used in Collections, added new field `description`
@@ -179,7 +230,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
179230
- STAC API:
180231
- Added the [Item and Collection API Version extension](https://github.com/radiantearth/stac-api-spec/tree/master/extensions/version/README.md) to support versioning in the API specification
181232
- Run `npm run serve` or `npm run serve-ext` to quickly render development versions of the OpenAPI spec in the browser
182-
- [Basics](item-spec/common-metadata.md#basics) added to Common Metadata definitions with new `description` field for
233+
- [Basics](commons/common-metadata.md#basics) added to Common Metadata definitions with new `description` field for
183234
Item properties
184235
- New fields to the `link` object to facilitate [pagination support for POST requests](https://github.com/radiantearth/stac-api-spec/tree/master/api-spec.md#paging-extension)
185236
- `data` role, as a suggestion for a common role for data files to be used in case data providers don't come up with their own names and semantics
@@ -191,7 +242,7 @@ Item properties
191242
- Added field `roles` to Item assets (also Asset definitions extension), to be used similarly to Link `rel`
192243
- Updated API yaml to clarify bbox filter should be implemented without brackets. Example: `bbox=160.6,-55.95,-170,-25.89`
193244
- Collection `summaries` merge array fields now
194-
- Several fields have been moved from extensions or item fields to the [Common Metadata fields](item-spec/common-metadata.md):
245+
- Several fields have been moved from extensions or item fields to the [Common Metadata fields](commons/common-metadata.md):
195246
- `eo:platform` / `sar:platform` => `platform`
196247
- `eo:instrument` / `sar:instrument` => `instruments`, also changed from string to array of strings
197248
- `eo:constellation` / `sar:constellation` => `constellation`
@@ -215,7 +266,7 @@ Item properties
215266
- `search` extension renamed to `context` extension. JSON object renamed from `search:metadata` to `context`
216267
- Removed "next" from the search metadata and query parameter, added POST body and headers to the links for paging support
217268
- Query Extension - type restrictions on query predicates are more accurate, which may require additional implementation support
218-
- Item `title` definition moved from core Item fields to [Common Metadata Basics](item-spec/common-metadata.md#basics)
269+
- Item `title` definition moved from core Item fields to [Common Metadata Basics](commons/common-metadata.md#basics)
219270
fields. No change is required for STAC Items.
220271
- `putFeature` can return a `PreconditionFailed` to provide more explicit information when the resource has changed in the server
221272
- [Sort extension](https://github.com/radiantearth/stac-api-spec/tree/master/extensions/sort) now uses "+" and "-" prefixes for GET requests to denote sort order.
@@ -232,7 +283,7 @@ fields. No change is required for STAC Items.
232283
- `gsd` and `accuracy` from `eo:bands` in the [EO extension](https://github.com/stac-extensions/eo/blob/main/README.md)
233284
- `sar:absolute_orbit` and `sar:center_wavelength` fields from the [SAR extension](https://github.com/stac-extensions/sar/blob/main/README.md)
234285
- `data_type` and `unit` from the `sar:bands` object in the [SAR extension](https://github.com/stac-extensions/sar/blob/main/README.md)
235-
- Datetime Range (`dtr`) extension. Use the [Common Metadata fields](item-spec/common-metadata.md) instead
286+
- Datetime Range (`dtr`) extension. Use the [Common Metadata fields](commons/common-metadata.md) instead
236287
- STAC API:
237288
- `next` from the search metadata and query parameter
238289
- In API, removed any mention of using media type `multipart/form-data` and `x-www-form-urlencoded`
@@ -453,6 +504,7 @@ See the [milestone 0.4.0 in the issue tracker](https://github.com/radiantearth/s
453504
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.
454505

455506
[Unreleased]: <https://github.com/radiantearth/stac-spec/compare/master...dev>
507+
[v1.1.0-beta.1]: <https://github.com/radiantearth/stac-spec/compare/v1.0.0..v1.1.0-beta.1>
456508
[v1.0.0]: <https://github.com/radiantearth/stac-spec/compare/v1.0.0-rc.4..v1.0.0>
457509
[v1.0.0-rc.4]: <https://github.com/radiantearth/stac-spec/compare/v1.0.0-rc.3..v1.0.0-rc.4>
458510
[v1.0.0-rc.3]: <https://github.com/radiantearth/stac-spec/compare/v1.0.0-rc.2..v1.0.0-rc.3>

CITATION.cff

+3-3
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ preferred-citation:
88
type: standard
99
title: "SpatioTemporal Asset Catalog (STAC) specification"
1010
abstract: "Making geospatial assets openly searchable and crawlable."
11-
version: 1.0.0
12-
year: 2021
13-
date-released: 2021-05-21
11+
version: 1.1.0-beta.1
12+
year: 2024
13+
date-released: 2024-08-08
1414
license: Apache-2.0
1515
url: https://stacspec.org
1616
repository: https://github.com/radiantearth/stac-spec

CODE_OF_CONDUCT.md

+106-50
Original file line numberDiff line numberDiff line change
@@ -2,75 +2,131 @@
22

33
## Our Pledge
44

5-
In the interest of fostering an open and welcoming environment, we as
6-
contributors and maintainers pledge to making participation in our project and
7-
our community a harassment-free experience for everyone, regardless of age, body
8-
size, disability, ethnicity, sex characteristics, gender identity and expression,
9-
level of experience, education, socio-economic status, nationality, personal
10-
appearance, race, religion, or sexual identity and orientation.
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, caste, color, religion, or sexual
10+
identity and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
1114

1215
## Our Standards
1316

14-
Examples of behavior that contributes to creating a positive environment
15-
include:
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
1619

17-
- Using welcoming and inclusive language
18-
- Being respectful of differing viewpoints and experiences
19-
- Gracefully accepting constructive criticism
20-
- Focusing on what is best for the community
21-
- Showing empathy towards other community members
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the overall
26+
community
2227

23-
Examples of unacceptable behavior by participants include:
28+
Examples of unacceptable behavior include:
2429

25-
- The use of sexualized language or imagery and unwelcome sexual attention or
26-
advances
27-
- Trolling, insulting/derogatory comments, and personal or political attacks
28-
- Public or private harassment
29-
- Publishing others' private information, such as a physical or electronic
30-
address, without explicit permission
31-
- Other conduct which could reasonably be considered inappropriate in a
32-
professional setting
30+
* The use of sexualized language or imagery, and sexual attention or advances of
31+
any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email address,
35+
without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
3338

34-
## Our Responsibilities
39+
## Enforcement Responsibilities
3540

36-
Project maintainers are responsible for clarifying the standards of acceptable
37-
behavior and are expected to take appropriate and fair corrective action in
38-
response to any instances of unacceptable behavior.
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
3945

40-
Project maintainers have the right and responsibility to remove, edit, or
41-
reject comments, commits, code, wiki edits, issues, and other contributions
42-
that are not aligned to this Code of Conduct, or to ban temporarily or
43-
permanently any contributor for other behaviors that they deem inappropriate,
44-
threatening, offensive, or harmful.
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
4550

4651
## Scope
4752

48-
This Code of Conduct applies both within project spaces and in public spaces
49-
when an individual is representing the project or its community. Examples of
50-
representing a project or community include using an official project e-mail
51-
address, posting via an official social media account, or acting as an appointed
52-
representative at an online or offline event. Representation of a project may be
53-
further defined and clarified by project maintainers.
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
5458

5559
## Enforcement
5660

5761
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58-
reported by contacting the project team at [stac-spec-admins@googlegroups.com](mailto:stac-spec-admins@googlegroups.com). All
59-
complaints will be reviewed and investigated and will result in a response that
60-
is deemed necessary and appropriate to the circumstances. The project team is
61-
obligated to maintain confidentiality with regard to the reporter of an incident.
62-
Further details of specific enforcement policies may be posted separately.
62+
reported to the community leaders responsible for enforcement at
63+
[stac-spec-admins@googlegroups.com](mailto:stac-spec-admins@googlegroups.com).
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
6384

64-
Project maintainers who do not follow or enforce the Code of Conduct in good
65-
faith may face temporary or permanent repercussions as determined by other
66-
members of the project's leadership.
85+
**Community Impact**: A violation through a single incident or series of
86+
actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or permanent
93+
ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within the
113+
community.
67114

68115
## Attribution
69116

70-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71-
available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.1, available at
119+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+
121+
Community Impact Guidelines were inspired by
122+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
72123

73-
[homepage]: <https://www.contributor-covenant.org>
124+
For answers to common questions about this code of conduct, see the FAQ at
125+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+
[https://www.contributor-covenant.org/translations][translations].
74127

75-
For answers to common questions about this code of conduct, see
76-
<https://www.contributor-covenant.org/faq>
128+
[homepage]: https://www.contributor-covenant.org
129+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+
[Mozilla CoC]: https://github.com/mozilla/diversity
131+
[FAQ]: https://www.contributor-covenant.org/faq
132+
[translations]: https://www.contributor-covenant.org/translations

0 commit comments

Comments
 (0)