Open jsignell opened 2 months ago
Note: I ended up making a milestone for this and making all the items into individual tickets.
@jsignell I'm starting work on v1.1.0 support, and I think I'd like to get rid of the milestone and only use this ticket to track v1.1.0 issues. My reasoning is that some of these issues can be solved without breaking pystac (e.g. #1379) and others are breaking (e.g. changing the docstring for #1377 will inherently "move" pystac to v1.1.0). We'll also eventually need to update DEFAULT_STAC_VERSION which will be breaking as well.
Tl;dr: I'm proposing closing the STAC spec version 1.0.0
milestone in favor of this tracking issue, and instead opening a v1.11
milestone to go along with the existing v2.0
milestone.
I'm proposing closing the STAC spec version 1.0.0 milestone in favor of this tracking issue, and instead opening a v1.11 milestone to go along with the existing v2.0 milestone.
That plan sounds good to me! I felt a little wierd making a milestone that wasn't necessarily tied to a release.
At some point in the near future version 1.1.0 of the STAC spec will be released. PRs are still being merged in, but the current list of high-profile changes is at: https://github.com/radiantearth/stac-spec/blob/v1.1.0-release/CHANGELOG.md
These are the changes that I think will need to be made in pystac (in the order they appear in the stac-spec changelog):
item.geometry
cannot be aGeometryCollection
(not sure this one requires any action)