Following up on our SpatioTemporal Asset Catalog 1.0.0 announcement, this post will finish our mini-series diving into the STAC specification and the ecosystem around it. This one is really about the future, where we see STAC heading in the next six months and beyond. And after this I hope to start an in-depth series of STAC posts that dives deeper into individual projects, highlighting all the great software and data in the STAC ecosystem.

The ‘STAC Ecosystem 1.0’ Vision

One of the core tenents of the STAC Community is that we focus on the process of building an interoperable ecosystem, with the specification serving as…


The SpatioTemporal Asset Catalog (STAC) Community is pleased to announce the release of version 1.0.0-beta.2 of the STAC API specification! A big thanks to Phil Varner for leading this release, and to everyone else who pitched in.

What is STAC API?

As we are welcoming many new people to the STAC community with the core STAC 1.0.0 release it’s probably worth explaining what this ‘API’ release is all about. STAC originally started from a desire to make a common API to help interoperability between satellite data providers, but soon evolved to focusing on the core JSON language to enable more general geospatial interoperability. The…


This post continues the STAC 1.0.0 announcement and updates on the community and spec, with an in-depth dive into one part of what we call the ‘STAC Ecosystem’. This is the ever-growing set of libraries, clients, and servers that rely on the STAC specification to build towards our goal of interoperability. The advanced state of this ecosystem is one of the things I’m most proud of with STAC, as one of the earliest goals was to have as much real-world validation as possible. …


While we just announced STAC 1.0.0, the initial post did not contain any of the typical information we normally include in a STAC release announcement. So in this post, we’ll dive into the details of what changed in the specification, including extensions, as well as some of the community highlights. And this will just be one of several posts diving deeper into STAC topics, including the wider ecosystem of tools.

Spec Changes

As always, the most definitive list of what has changed between versions of STAC is the CHANGELOG, but it’s always good to draw attention to the highlights. So I’ll summarize…


The SpatioTemporal Asset Catalog (STAC) community is pleased to announce the release of version 1.0.0. It’s safe to say we’re all quite proud of the release, as it’s been a large community effort for over three years. For those who haven’t heard of STAC, it provides a common language to describe a range of geospatial information, so it can more easily be indexed and discovered. You can learn more at the stacspec.org website, which we aim to update in the coming months to be an even better learning resource.

A Stable Foundation

I’m not going to go into all the details of the…


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…


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…


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!

The Backstory


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.

STAC Core OpenAPI

In This Release

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…


It’s been two months since we wrapped up the Cloud Native Geospatial Outreach Day and Sprint. I meant to get this post out much sooner, but life happens and 2020 is a tough year. But I wanted to announce all the winners of our experiment with ‘Community Awards’, as a companion to the Outreach Day Recap.

About the Awards

I know I’m a broken record thanking our sponsors, but I think it’s appropriate to do so for this section, as it’s entirely possible due to their support of our communities.

Chris Holmes

Product Architect @ Planet, Board Member @ Open Geospatial Consortium, Technical Fellow @ Radiant.Earth

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store