Skip to content
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

Update to API v1.0.0, and also update extension versions #578

Merged
merged 1 commit into from
Jun 7, 2023

Conversation

gadomski
Copy link
Member

@gadomski gadomski commented Jun 7, 2023

Related Issue(s):

Description:

I've updated the core versions to v1.0.0, and each extension version to its latest. I've also updated the docs to point to the new extension locations after the breakout from the main repo.

To check validity, I spun up a stac-fastapi-pgstac instance that included this branch. I also had to use a patched version of stac-api-validator because of stac-utils/stac-api-validator#365. Before this PR, stac-api-validator reports:

INFO:stac_api_validator.validations:Validating STAC API - Core conformance class.
INFO:stac_api_validator.validations:Validating STAC API - Collections conformance class.
INFO:stac_api_validator.validations:Validating STAC API - Features conformance class.
Warnings:

- STAC API Specification <https://api.stacspec.org/v1.0.0/> is the latest version, but API advertises an older version or older versions.
- [Collections] : GET <http://localhost:8082/collections/joplin> has these stac-check recommendations: A STAC collection should contain a summaries field,It is recommended to store information like eo:bands in summaries,,Links in catalogs and collections should always have a 'title' field,
- [Collections] : GET <http://localhost:8082/collections/joplin> has these stac-check recommendations: A STAC collection should contain a summaries field,It is recommended to store information like eo:bands in summaries,,Links in catalogs and collections should always have a 'title' field,
Errors: none

After this PR:

INFO:stac_api_validator.validations:Validating STAC API - Core conformance class.
INFO:stac_api_validator.validations:Validating STAC API - Collections conformance class.
INFO:stac_api_validator.validations:Validating STAC API - Features conformance class.
Warnings:

- [Collections] : GET <http://localhost:8082/collections/joplin> has these stac-check recommendations: A STAC collection should contain a summaries field,It is recommended to store information like eo:bands in summaries,,Links in catalogs and collections should always have a 'title' field,
- [Collections] : GET <http://localhost:8082/collections/joplin> has these stac-check recommendations: A STAC collection should contain a summaries field,It is recommended to store information like eo:bands in summaries,,Links in catalogs and collections should always have a 'title' field,
Errors: none

PR Checklist:

  • pre-commit hooks pass locally
  • Tests pass (run make test)
  • Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
  • Changes are added to the CHANGELOG.

@gadomski gadomski added this to the 2.4.8 milestone Jun 7, 2023
@gadomski gadomski requested a review from philvarner June 7, 2023 18:32
@gadomski gadomski self-assigned this Jun 7, 2023
@gadomski gadomski merged commit 9b12aa9 into main Jun 7, 2023
@gadomski gadomski deleted the update-versions branch June 7, 2023 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update to STAC API v1.0.0 🎉
2 participants