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 pystac migrate for STAC spec 1.1.0 #1383

Open
Tracked by #1375
jsignell opened this issue Jul 31, 2024 · 3 comments · May be fixed by #1491
Open
Tracked by #1375

Update pystac migrate for STAC spec 1.1.0 #1383

jsignell opened this issue Jul 31, 2024 · 3 comments · May be fixed by #1491
Assignees
Milestone

Comments

@jsignell
Copy link
Member

jsignell commented Jul 31, 2024

pystac provides tools for migrating that walk the cataolog and migrate the STAC version and the extension versions. So those functions will need to be updated for this new version of STAC.

@jsignell jsignell added this to the STAC spec version 1.1.0 milestone Jul 31, 2024
@gadomski gadomski modified the milestones: STAC spec version 1.1.0, v1.11 Sep 21, 2024
@jsignell
Copy link
Member Author

jsignell commented Dec 2, 2024

It was mentioned in the STAC call today that stac-migrate and stac-rs both have versions of the migration code at this point. So that can be used as a jumping off point.

@jsignell
Copy link
Member Author

jsignell commented Jan 3, 2025

Reading through https://github.com/stac-utils/stac-rs/blob/main/crates/core/src/migrate.rs it looks like the main changes are:

@gadomski
Copy link
Member

gadomski commented Jan 6, 2025

something to do with properties that I can't quite figure out

That's just to make the license migration generic for all STAC things (we have to work on the properties dict for Items instead of the item itself).

@jsignell jsignell self-assigned this Jan 10, 2025
@jsignell jsignell linked a pull request Jan 10, 2025 that will close this issue
4 tasks
@jsignell jsignell linked a pull request Jan 10, 2025 that will close this issue
4 tasks
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 a pull request may close this issue.

2 participants