Supporting NASA suborbital science teams to develop reproducible workflows

blog
nasa-framework
Author

Julie Lowndes

Published

March 3, 2026

In 2026 we are proud to continue supporting NASA teams, building from our work with the NASA Openscapes Mentors from across the NASA Distributed Active Archive Centers (DAACs) over the past five years. NASA Openscapes Mentors support scientists using data from satellite and suborbital missions — with suborbital meaning missions via airplanes, ground networks, and field sampling on land, boats, and buoys. This year we have additional focus supporting suborbital science teams to develop reproducible workflows and growing the NASA Openscapes Mentor community supporting suborbital data.

Cross-posted at openscapes.org/blog, nasa-openscapes.github.io/news.


NASA suborbital science and Openscapes proposed support

NASA Earthdata has volumes of remote sensing data collected by platforms in space, air, water, and land. Substantial suborbital data is collected from airborne sampling via airplanes, ground networks, and field sampling on land, boats, and buoys.

Suborbital science teams are teams that create and use suborbital data via NASA programs like EVS-4. The science teams use suborbital data to ground-truth satellite data, as well as to conduct other awesome research like studying Arctic coastlines via the FORTE mission and glaciers and ice sheets via the Snow4Flow mission.

Suborbital teams connect with NASA Distributed Active Archive Center (DAAC) staff at the beginning and the end of the data cycle, and receive additional support from other NASA centers and NASA Headquarters (HQ). The science teams design and run the missions to collect the data using planes, boats, etc, and then archive the data in the DAACs. Then, they also retrieve the data from the DAACs for their analyses, meaning they are relying on the DAACs for the processing as well as storage and distribution. Thus, relationships with science teams and DAACs are very important for effective collaboration and communication, as well as for establishing standards and common workflows.

Staff at many NASA DAACs work with science teams to archive and use suborbital data, including:

  • Oak Ridge National Laboratory ORNL,
  • National Snow and Ice Data Center NSIDC,
  • Atmospheric Science Data Center ASDC,
  • Global Hydrometeorology Resource Center GHRC,
  • Land Processes LP DAAC,
  • Ocean Biology OB.DAAC,
  • Physical Oceanography PO.DAAC

Our NASA Openscapes Mentor Community has been collaborating across the DAACs to support Earthdata users and doing so efficiently and with less maintenance burden, while closing previously unseen gaps, together and openly. NASA Openscapes Mentors have created “go-to” resources for staff and users using NASA Earthdata – such as the earthaccess python library and tutorials in the Earthdata Cloud Cookbook. Many other tools and resources have originated from these cross-agency Openscapes relationships with the DAACs, such as VITALS, which has developed specific airborne tools.

In our NASA Openscapes Mentor Community, most of the DAACs listed above that are supporting suborbital work have been consistent contributors over the past five years. Our goal in 2026 is to increase specific support for NASA suborbital science teams to develop reproducible workflows. In March, we are thrilled to welcome Ronny Hernández Mora to the Openscapes core team to support this work! Ronny works at the intersection of Earth data, open and reproducible workflows, and has spent the last past eight years teaching professionals and researchers in industry and academia how to adopt collaborative, open, and maintainable workflows in real-world contexts.

Below is our planned approach from our proposal, presented through POP: Purpose, Outcomes, Process.

Purpose

The purpose is to develop user skills and reproducible workflows for using NASA suborbital data. This work will help communities using NASA Earthdata and open science more broadly, as well as growing the NASA Openscapes community in a new focus area. This work is in collaboration with the CryoCloud (StratusGeo) Community, which is an exciting continuation of the JupyterHub community work we have been collaborating on with them with in the past years.

Outcomes

Suborbital science teams will create reusable open source notebooks (Jupyter, Quarto, GitHub) to analyze their data archived at the NASA DAACs. They can learn no matter where they are starting from, using other existing data or for planning purposes if they do not yet have their own missions data in hand. This may mean learning new skills (coding, version control, documenting and collaborating for reuse), and working with colleagues in new ways as they develop confidence in the open ecosystem to continue their work. At the same time, Openscapes will increase the Mentor capacity of staff at NASA centers by onboarding suborbital-focused user support staff, and also by engaging operational and communications staff, and program managers.

Process

This work will be aligned with NASA HQ priorities to identify and meet suborbital teams, understand goals, progress, tooling, and needs. The following are distinct but overlapping activities: engage • empower • amplify.

  1. Engaging suborbital science teams to help build a community. Suborbital teams are already meeting in smaller sub-groups, perhaps based on mission or a specific field; we will strengthen these relationships further as a cross-DAAC community. We will onboard new NASA Openscapes Mentors from NASA’s SoAR (Suborbital Archive Readiness) Team and other parts of NASA to collaborate across the agency to support science teams.
  2. Empowering suborbital science teams involves leading a Notebook Clinic that will be remote, cohort-based, and designed for their needs. Lessons will focus on developing reproducible workflows with Jupyter Notebooks, Quarto, and GitHub, using the earthaccess python library, and writing documentation that focuses on reuse and onboarding others to these workflows.
  3. Amplifying the work of suborbital science teams involves bringing them into the fold of the NASA Openscapes Flywheel, along with additional NASA center staff. By connecting users (science teams) and NASA Openscapes Mentors and building skills and relationships together, data access issues will be surfaced for NASA development teams (e.g. earthaccess, Cookbook tutorials, cloud optimization).

Methodology

We will follow the NASA Openscapes Flywheel mechanism (Robinson and Lowndes 2022) to facilitate and scale open source practices (e.g. from groups like Pangeo, rOpenSci, The Carpentries):

  • To engage the suborbital community we will reuse and grow from what works from the last five years of building the NASA Openscapes Mentor community, and connect to community momentum at NASA. This will not happen in a vacuum, but coordinating with other NASA groups takes time. We know scientists and NASA staff are at the same time busy and feeling stuck+alone, and not knowing where to ask for help. This work involves:

    • Joining suborbital scientists at existing meetings already ongoing, getting a sense of the group, giving talks, asking questions and building relationships, sending followup messages, having open documentation of activities, scheduling 1:1 conversations, seeking out people at conferences; all to welcome and support scientists with busy schedules.

    • Meeting with and onboarding new NASA Mentors from NASA’s SoAR (Suborbital Archive Readiness) Team and other parts of NASA to collaborate across the agency to support science teams

    • Contributing to the Earthdata Cloud Cookbook to support Mentors in their workshops and tutorial goals.

    • Hosting regular “Coworking” learning meetings with suborbital science teams where we will increasingly fold in NASA center staff to learn and build relationships with suborbital users. These are a light-weight way where they connect and help solve common challenges. This will be a chance to help find what is common (i.e. airborne instrumentation differs but they all have flight tracks; all need to learn version control and write metadata), and build together, always with a “future us” and reuse mindset.

    • Teaching and role-modeling open facilitation and documentation using the same tools that science teams use for analysis (ex: Google Docs, Quarto, Jupyter Notebooks, GitHub) as well as psychological safety and social infrastructure that underpins collaborative science. We empower partners by providing templates and processes (emails, agendas, checklists, etc.) that they just need to tweak and deploy to start off a new thing (for example, regular science team meetings). And we engage them in the broader open community too (for example from NOAA Fisheries Openscapes Mentors: “I need to make this report, or methods manual”. “Oh hey, Here’s one I made. I’ll turn it into a template on GitHub.” And “I’ve made project management checklists, see if this would help you”.)

    • Building trust with science teams so they would prioritize time for the Clinic, as we design the Clinic to fit their needs.

  • To empower teams through the Notebook Clinic we will draw from what we’ve learned from leading 27 Champions Cohorts (Openscapes’ flagship program where we have helped 175 teams make real change around reproducible and transparent workflows). We will design the Clinic for what best meets suborbital team needs, likely forking the structure of the Champions program: 10 weeks, 1.5 hours each week, with alternating weeks being lesson-based and hands-on work-based. Our approach includes:

    • Not focusing on specific datasets, but rather the methods for writing reusable analyses that combine different datasets, using open source tooling and practices. After the Notebook Clinic we will develop a process to add suborbital teams’ new tutorials to the NASA Earthdata Cookbook for increased discoverability and reuse.

    • Focusing on developing relationships with potential participants (engagement above) as well as developing the Clinic itself. The Clinic will build on the rhythm from Coworking and be a friendly place to learn. We will invite suborbital teams to join via a short nomination form, which Openscapes has found to both increase buy-in and decrease attrition.

    • Prioritizing learning and engagement by controlling the size of the cohort. We will keep the cohort to a maximum of 35 people; we have found this is best for learning, since it enables active engagement and any bigger starts feeling like a webinar. 

    • Developing lessons to focus on building code-based reusable workflows with Jupyter Notebooks, Quarto, and GitHub, using the earthaccess python library and other open source tools, and writing documentation that focuses on onboarding. We will develop documentation, tutorials, and templates the teams can reuse.

    • Teaching with an open facilitation approach, drawing on our experience as Carpentries certified instructors, using agendas for live shared note taking, and having multiple channels for asking help, including asynchronous chat and synchronous breakout rooms.

    • Adding Notebook Clinic lessons to the Earthdata Cloud Cookbook for discoverability and reuse.

  • To amplify suborbital teams and grow the Mentor community we will create opportunities to share work, both through talks and through a mechanism for adding contributions to the Earthdata Cloud Cookbook. This involves:

    • “Defaulting to open” as always: open documentation, contributing to the NASA Earthdata Cookbook, and storytelling via blogs and talks will center this work.

    • Giving talks to different groups, particularly with NASA staff, including NASA Openscapes’ network of open source communities, industry, academia, other government agencies. 

    • Connecting suborbital teams to Openscapes’ network of engineers, teachers, managers, scientists, facilitators - we can help people get the help they need, and help their work get in front of people who need to hear about it.

    • Onboarding new NASA Mentors from NASA’s SoAR (Suborbital Archive Readiness) Team and other parts of NASA to collaborate across DAACs and across the agency to support science teams.

    • Improving documentation and onboarding for suborbital teams (and anyone) to contribute workflows to the NASA Earthdata Cloud Cookbook.

    • Throughout, sharing and connecting suborbital science teams with others at NASA, CryoCloud, NOAA Fisheries Openscapes and the broader open science community so they become confident contributors to further support science with NASA Earthdata.

References

Robinson, Erin, and Julia S. Stewart Lowndes. 2022. “The Openscapes Flywheel: A Framework for Managers to Facilitate and Scale Inclusive Open Science Practices,” October. https://doi.org/https://doi.org/10.31223/X5CQ02.

Citation

BibTeX citation:
@online{lowndes2026,
  author = {Lowndes, Julie},
  title = {Supporting {NASA} Suborbital Science Teams to Develop
    Reproducible Workflows},
  date = {2026-03-03},
  url = {https://nasa-openscapes.github.io/news/2026-03-03-suborbital/},
  langid = {en}
}
For attribution, please cite this work as:
Lowndes, Julie. 2026. “Supporting NASA Suborbital Science Teams to Develop Reproducible Workflows.” March 3, 2026. https://nasa-openscapes.github.io/news/2026-03-03-suborbital/.