Last week the STAC community came together and sprinted to release version 1.0.0-rc.1, the most critical step on our path to STAC spec 1.0.0. This is a ‘release candidate’, meaning we believe the specification is completely set for 1.0.0, but we want to put it in the hands of implementors and gather feedback and reviews before the final release.

So if you have implemented STAC in the past please take the time to upgrade your software or catalog to the latest specification (see the change summary below for what’s changed). Our aim is to sprint for the next few weeks to upgrade as many implementations as possible to validate for the final release. The nature of a ‘release candidate’ means that if any implementations find problems in the specification we will make another ‘release candidate’ and give it a couple of weeks for feedback, doing so until we iron out all the issues. The newly formed Project Steering Committee has aligned on targeting the end of April for 1.0.0 final release, aiming to do any needed additional release candidates before then.

It’s almost time! The SpatioTemporal Asset Catalog (STAC) specification has been maturing for over 3 years, and already has a rich ecosystem of tools with hundreds of millions of assets cataloged. The core community has agreed that it’s time to put a pin on it and lock in a super stable specification that can be a core building block for years to come. We believe STAC will be the foundation of something truly special: A transformation to a ‘Cloud Native Geospatial’ world that will open up unimaginable innovation.

Our goal has been to build simple, flexible building blocks to expose geospatial data in order to enable others to build incredible value on top of that. This can only happen if there’s a stable base to rely upon. In the next couple of months, we hope to release 1.0.0. Our goal goes beyond just releasing the specification: We aim to make sure there is a ‘complete’ core ecosystem of tools to make it easy for people to create, use, and get value from STAC. See below for our plan, details on our sprint, and also ways that organizations can directly support STAC.

As SpatioTemporal Asset Catalog (STAC) specification matures one of the more frequent questions we get asked is the relationship between STAC and the Open Geospatial Consortium (OGC). I wanted to write this post to help clarify, at both a technical and an organizational level.

The tl;dr version is:

‘STAC API implements and extends the OGC API — Features standard, and our shared goal is for STAC API to become a full OGC standard’

The longer version has a lot more detail, but if you’re interested then read on!

I’m pleased to share that we’ve just released STAC API 1.0.0-beta.1. This is our first release of the API since we split the specification, with STAC now living in its own repository. You can see the latest specification in the stac-api-spec repository, and we link to browsable API representations of the major portions below.

What started out as a pretty modest release ended up snowballing into a major amount of work, but I think we’re all pretty proud of the end state. Our main goal was to have a version of the API that was released standalone, independent of the STAC Core releases. In previous versions, it was just assumed that a version number applied to both the STAC content and the API. So we wanted to enable services could be more explicit about which version of each they supported — one could upgrade the service to 1.0.0-beta.1 API, but have it still serve STAC 0.9.0 Items.

How the STAC tool ecosystem is growing towards supporting truly open spatial data.

The STAC specification is transforming the way data providers and consumers are thinking about how to work with open spatial data. It provides a clear, common language for spatial data that is flexible and developed by an open community. But what is a language without the tools that speak it? The open-source STAC tooling ecosystem is a critical part of making spatial data open and accessible for use. In this post, I’ll talk about why access to that tooling provides is so important, and describe two instances of collaboration I experienced in the recent STAC and Cloud Native Geospatial sprints that, to me, exemplifies the growth of STAC tooling.

I wanted to share some background and more details about the Cloud Native Geospatial Outreach Day and Sprint (1 week away! September 8th — signup here), which has grown out of the SpatioTemporal Asset Catalog (STAC) community sprints. One of our goals for STAC has been to make it a truly collaborative community, and one that is welcoming as possible. We believe that the best standards are forged from diverse use cases and perspectives coming together and collaborating. We started with a gathering of 25 people from 14 organizations and have always sought to bring more people into the fold.

On September 8th we will be continuing SpatioTemporal Asset Catalog (STAC) Sprint #6, but we decided to expand its scope to include more of the ‘Cloud Native Geospatial’ ecosystem. The core idea of Cloud Native Geospatial is articulated in this ‘blog series’, with the first post positing the question: ‘what would the geospatial world look like if we built everything from the ground up on the cloud?’. The second post introduced the Cloud Optimized GeoTIFF (COG), and it has since emerged as a default format for anyone doing geospatial on the cloud.

With the SpatioTemporal Asset Catalog (STAC) spec recently reaching 1.0.0-beta, we figured it’s time for one final sprint before we push out 1.0.0 final. The goal with STAC has always been to ensure that the specification meets real-world needs, by always iterating its improvements in conjunction with actual implementations. One early goal was to reach 1 billion records in STAC before we go to 1.0.0, but we achieved that much earlier than expected. But the various catalogs have not necessarily upgraded to the latest STAC version right when it comes out. So our main goal for the sprint is going to be to upgrade all the STAC software and catalogs to the latest 1.0.0 beta specification and ideally add several new catalogs and data types. The goal will be to ensure that STAC is flexible enough to handle anything, so when we reach 1.0.0 the core will not need to change.