-
Notifications
You must be signed in to change notification settings - Fork 123
0.4.0 - Merge develop to master #114
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
Merged
Conversation
This file contains hidden or 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
update dev
Narrow v0.6.2 - v0.7.0 SAR version
Also changed the migrate test to consider all examples, not just ones that are of a previous STAC version.
Fixed issue with reading ItemCollections directly.
In STAC 0.9.0 there is a heavier use of remote schemas; this slowed down the jsonschema validation over larger catalogs. These changes help speed things up by caching all requiured remote schemas and passing them to the RefResolver, so that the remote schemas listed in "schemas" and "aux_schemas" will only be read once.
The remote URL has a JSON error. This URL should be reverted once a fix is in place on the main stac-spec repo.
Also, created a script to pull down examples from new STAC versions. This commit breaks tests. These will be fixed in follow up commits.
From 0.9.0 CHANGELOG: A description field has been added to Item assets (also Asset definitions extension)
From CHANGELOG for 0.9.0: Several fields have been moved from extensions or item fields to the Common Metadata fields: eo:platform / sar:platform => platform eo:instrument / sar:instrument => instruments, also changed from string to array of strings eo:constellation / sar:constellation => constellation
From CHANGELOG for 0.9.0: Moved angle definitions from extensions eo and new view extension eo:off_nadir -> view:off_nadir eo:azimuth -> view:azimuth eo:incidence_angle -> view:incidence_angle eo:sun_azimuth -> view:sun_azimuth eo:sun_elevation -> view:sun_elevation
revert eo styling
fix bug in `make_absolute_href`
Previously fully_resolve was on stac_object, which operated the same for catalogs and items. Catalogs were not calling fully_resolve on links that were previously resolved themselves, causing the recursive resolution strategy to fail if links were previously resovled. Fixed this exposed an issue where Item's full_resolve should not be recursive - or else a situation occurs where trying to fully resolve the item's collection from the item causes an infinite loop. This fixes the issue by splitting the implementation of fully_resolve to handle Catalogs and Items separately.
This test was previously adding an item that had invalid links; this corrects the test to check for valid items.
Also some small cleanup changes related to the collection cache.
Signed-off-by: Rob Emanuele <rdemanuele@gmail.com>
Remove hard-coded tmp directory from unit tests
Migrate the existing Travis CI testing workflow to GitHub Actions, by achieving the following success criteria: - Trigger linters, code formatters, and test suites on pull requests - Ensure that the builds test against Python version 3.6-3.8 - Cache dependencies across builds - Trigger PyPI releases of Python 3.x packages on tagged releases
- Add view extension if there are eo fields info that moved to view. - Remove datetime-range extension in 0.9
fix __repr__ bug
…eature/rde/refactor-ext
Ensure that the CI workflow is triggered when changes are pushed to the develop and master branches. In addition, this scopes the GitHub Actions badge status to the develop branch.
Add primary Git branches to CI workflow
Refactor extensions.
Upgrade to STAC 0.9.0
Update README and documentation in prep for 0.4 release.
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.
This merges develop to master in preparation for the 0.4.0 release.
This includes changes from the 0.3.4 release as I mistakenly went directly from develop to the 0.3 branch in that release.