We are pleased to announce the release of version 0.5.0 of the STAC specification! Though a ‘major’ release since there is a version bump due to a very core change, it is a relatively ‘minor’ release as major releases go.
Unlike the last two major releases, this one is not the result of a big bang of energy from an in-person sprint, like we had from Boulder and Ft. Collins. Instead it’s just the typical open source progress of people collaborating online when they’re able to find time. Most of the activity is in the github repo, as well as lots of great discussion in our gitter channel. We are excited for our next sprint in August, and it’s shaping up to be a great gathering — submit on the form if you’re interested in joining.
As for the 0.5.0 release, there were still a number of great steps forward. Highlights include from the release notes include:
- Links is now a dictionary — This is the most core change done. It aligns the structure with the ‘asset’ change in 0.5.0, making it easier for clients to look up the link that they want more easily. The schema is updated to this (and actually checks assets better now, thanks @mojodna )
- Transactions Extension — There is now a transaction extension for the STAC API, thanks to @hgs-msmith and @hgs-trutherford
- Collections iterations @matthewhanson has evolved the collections extension, adding in some namespace type hints on it, and explaining it more clearly.
eo:epsgIn the EO profile @matthewhanson brought in a change to use EPSG code, instead of full Well Known Text, to make it easy to reference.
You can also check out the full list of issues and pull requests in the github repository.
I’m excited that iteration of the specification is getting in to a groove, and is truly being fleshed out by real usage. I updated the ‘static catalog examples’ in the repository, and it was really cool to see the list of real world implementations get longer. I’m most excited about CBERS and SpaceNet, as they are both exposing their full catalog as STAC, and it’s the primary structure to get at their real data. And they’ve been helping guide the specification. We’re also seeing the GUI tools iterate and start to inform how the spec should evolve, making it more a part of the web.
Things are still evolving, but it’s feeling like the major changes are slowing down. The next goal is to stand up more and more data as STAC, and continue to tweak and evolve as the data and tooling continues to expand.