-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge to master for 1.1.0-beta.1 release #1305
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`ollections` -> `Collections`
docs: fix collectionless item title in catalog example
Fix a typo in collection-spec.md
Minor punctuation fix in best practices
Co-authored-by: Matthew Hanson <[email protected]>
`proj:epsg` should be summarised as an array of all values, not a Range Object, per [stac-fields](https://github.com/stac-utils/stac-fields/blob/v1.0.0-beta.10/fields.json#L575) and [other examples](https://github.com/radiantearth/stac-spec/blob/v1.0.0/examples/collection-only/collection.json#L90).
Co-authored-by: Matthew Hanson <[email protected]> Co-authored-by: Chris Holmes <[email protected]>
There was some confusing language about when `self` links should be used. This commit fixes the language in the "Use of links" section of the best practices document, and updates the wording in the item spec to reference the best practices section.
Minor spelling changes
fix(examples): change epsg summary example to an array of all values
Reword recommendations around `self` links in the item spec
* update code of conduct to v2.1
Update dev to include recent changes on master
… in the corresponding root catalog. (#1209)
* Keywords in common metadata * Added keywords in simple example * Minor alignment and clarification --------- Co-authored-by: Matthias Mohr <[email protected]>
According to the spec of the `eo` extension, the `center_wavelength` is given in micrometers (µm), but the examples sometimes contained them in nanometers (extended-item.json) or tens of nanometers (in "collection-only" folder; interestingly there from B10 upwards it was already correct).
Co-authored-by: Matthias Mohr <[email protected]>
Co-authored-by: Matthias Mohr <[email protected]>
Co-authored-by: Matthias Mohr <[email protected]>
Co-authored-by: Matthias Mohr <[email protected]>
Co-authored-by: Matthias Mohr <[email protected]>
* chore: Clarify that item IDs should be unique per collection * chore: Clarify that item IDs should be unique per collection
* Initial new field in links * updated changelog * format table * links moved to common metadata * Map<string, *> * Update item-spec/common-metadata.md Co-authored-by: Matthias Mohr <[email protected]> * Update common-metadata.md with HTTP headers description * Update item-spec/json-schema/item.json Co-authored-by: Matthias Mohr <[email protected]> * Update item-spec/common-metadata.md Co-authored-by: Matthias Mohr <[email protected]> * Update item-spec/common-metadata.md Co-authored-by: Matthias Mohr <[email protected]> * Update item-spec/common-metadata.md Co-authored-by: Matthias Mohr <[email protected]> * Update item-spec/common-metadata.md Co-authored-by: Matthias Mohr <[email protected]> * link object section review * link headers schema * Update item-spec/common-metadata.md Co-authored-by: Matthias Mohr <[email protected]> * Update item-spec/json-schema/item.json Co-authored-by: Matthias Mohr <[email protected]> --------- Co-authored-by: Matthias Mohr <[email protected]>
Integrate item_assets field from extension into core Collection spec
No multiple parents
Co-authored-by: Emmanuel Mathot <[email protected]> Co-authored-by: Pete Gadomski <[email protected]>
…xamples (#1303) * Update version numbers, incl. projection extension * Small corrections * Update to beta.1 * npm run check -> npm test * Fix outdated examples * Fix validation, upgrade CI * Guess a release date --------- Co-authored-by: Emmanuel Mathot <[email protected]>
emmanuelmathot
approved these changes
Aug 6, 2024
gadomski
approved these changes
Aug 6, 2024
matthewhanson
approved these changes
Aug 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue(s): None
Proposed Changes: