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):
Description:
With increased heterogeneity of extensions in the ecosystem, especially breaking changes like proj v2, there's more and more schema allowed in a valid STAC value. Handling these in pystac is ... tricky.
On read+load, pystac has the concept of "migration", where fields on STAC objects and in STAC extensions are moved around and updated to the latest versions. Migration is currently ON by default when using
from_file
:pystac/pystac/stac_object.py
Line 633 in 21a0bbb
However, it is OFF by default when using
from_dict
:pystac/pystac/stac_object.py
Line 650 in 21a0bbb
This inconsistent behavior is confusing to users (and, tbh, developers). We should align on one. As discussed in #1504, defaulting to
migrate=True
seems like the best idea for the ecosystem generally.PR Checklist:
scripts/test
)