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.


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.

It’s been just over three weeks since the Cloud Native Geospatial Outreach Day. Everyone I’ve talked to felt it was an incredible event, and I definitely concur. Thankfully we managed to record almost all of it, so if you missed it you can still catch the content on youtube!

RadiantEarth edited and put together this playlist for the full event.

I wanted to give a recap of the event and share some of my favorite parts.

Welcome & Overview

Details on the Sprint & Outreach Day agenda and awards

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.

Scenes from the first STAC Sprint, before it was even called STAC

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.

Sign up here!

So the ‘Outreach Day’ will aim to introduce…

Just wanted to give a quick update on STAC Sprint #6, starting next week! Our first major focus is on ‘software’ — upgrading and building out the tooling that creates and makes use of the SpatioTemporal Asset Catalog (STAC) specification. So far we’ve got over 50 people signed up, with people interested in working on SNAP, Intake-stac, Open Data Cube, Microsoft’s Planetary Computer, Franklin, GeoTools, GeoServer, pygeoapi, trying STAC out with point clouds, radio occultation data, TileDB Arrays, zarr, and of course working on core tools.

Please sign up if you’re interested in joining. I plan to send out the…

Signup here

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…

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