Get funded to code software for STAC!

Announcing three open requests for proposals for SpatioTemporal Asset Catalog (STAC) projects

In my previous post, I shared that we’ll be funding a number of different STAC initiatives. One of our goals with the STAC ecosystem funding is to grow the number of contributors working on STAC. To that end, we have three completely open requests for proposals that are designed to help fund developers to have some paid time on a few key projects. We encourage everyone to apply and are especially interested in proposals from traditionally underrepresented groups.

This will be the second open call for proposals we’ve done, and this time we’re trying to evolve the process a bit, by being fully transparent with the total budget. We are flexible with the exact deliverables, so each RFP has a number of ideas and proposals can choose which issues they want to tackle. With the STAC Browser and stactools projects, our main goal is to bring in more contributors. So we’ll look at the proposed work as well as people’s backgrounds to decide. Individuals and companies are both encouraged to apply — our hope is at the end of the work to have another go-to option who can take funded work to develop fixes and new features, and ideally help out with some of the day-to-day maintenance.

The RFP’s are available online:

We are open to proposals from individuals and companies, and all proposals are due April 1st. Read the above links for all the details, and read on for an overview of each.

STAC Browser RFP

STAC Browser is one of the foundational projects of the STAC Ecosystem, and it’s been going in exciting new directions as Matthias Mohr has been iterating on version 3.0. This is a ground-up rewrite, resulting in a faster and more maintainable codebase. He’s been working alone on it for a while, with 7 alpha releases, and he should get to a first beta release in the next couple of months. But his time is limited, as he’s got a full-time job on OpenEO and squeezes this in when he has spare hours. With that schedule he’s actually unable to take on more paid work, so we’re hoping to use this funding to help a new contributor get up to speed, ideally a person or company who would be interested in future funded projects.

So we’ve got a set budget of $8000 USD, and are open to a variety of work items. Matthias has done a great job organizing the issue tracker with good tasks to take on, so we’re looking for proposals that tackle a few of those issues. But we’re also more than open to new ideas as well, if there are things you’ve wanted to work on in STAC Browser and some funded time would help you prioritize it. To respond to the RFP see the STAC Browser RFP and follow its directions.

STAC API Validation RFP

After 5 beta releases, we should see the first 1.0.0 Release Candidate of STAC API in the next week or two. This means there is no more planned functionality before 1.0.0, and we’re mostly looking for feedback from implementations as they upgrade to be compliant with the spec. One of the most important tools to help implementors is a validation tool, so they can just use automated tooling to tell them where they aren’t spec-compliant, instead of trying to check and interpret every single line of text.

There is a great start to this with the stac-api-validator tool, and that is potentially a great codebase to expand upon. But the RFP is not assuming that is the answer — we are open to other codebases that fully test the specification. We’ve got a budget of $15,000 USD for this, and are hoping that is enough to cover all the basics of spec compliance, and potentially even go a bit beyond. To respond to the RFP see the STAC API Validation RFP document and follow the directions there.

stactools RFP

The final RFP is for stactools, another foundational project in the ecosystem. It has grown to be a number of related packages that provide a ton of interesting functionality on the type of the core pystac project. As with the other projects we have a set budget of $5000 USD. The primary goal is to help maintain and improve the project, and like STAC Browser we hope to bring in new contributors to help the core developers. The RFP and the issue tracker have a number of great ideas of how to help out, and we are open to a variety of work plans in the proposals. To respond to the RFP see the stactools RFP document and follow the directions there.

Thanks to our Sponsors

And of course, none of this would be possible without the generous support of our sponsors for the STAC Ecosystem initiative. You can read more about it in our STAC updates from February and October.

We look forward to your proposals! And if you’ve got any questions don’t hesitate to get in touch — instructions on how to do so are on each proposal.



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
Chris Holmes

Chris Holmes


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