Update news/2026-03-03-suborbital/index.qmd

Co-authored-by: Andy Teucher <andy.teucher@gmail.com>

Author: jules32

news/2026-03-03-suborbital/index.qmd

@@ -37,7 +37,7 @@ Suborbital science teams will create reusable open source notebooks (Jupyter, Qu
 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. Our approach of engage • empower • amplify is cyclical, and for this suborbital work will start with **amplify**.
 
 1.  **Amplifying suborbital science teams involves bringing them into the fold of the NASA Openscapes Flywheel, along with increasing numbers of NASA center staff.** By connecting users (science teams) and NASA Openscapes Mentors (DAAC user support staff), data access issues will be surfaced for NASA development teams (e.g. earthaccess, CMR, cloud optimization). Throughout, we will share and connect suborbital science teams with others at NASA, StratusGeo, and the broader open science community so they become confident contributors to further support science with NASA Earthdata.
-2.  **Developing a suborbital science team community.** Suborbital teams are already meeting in smaller groups, perhaps based on mission or a specific DAAC; and we will strengthen these relationships further as a cross-DAAC community. This will involve joining meetings already ongoing, asking questions and building relationships, giving talks, sending followup messages, having open documentation of activities, 1:1 conversations; all to welcome and support scientists with busy schedules. We will lead ~biweekly “Coworking” learning meetings with suborbital science teams where we will increasingly fold in NASA center staff to learn and build relationships with suborbital users. For suborbital science teams, this will be a chance to help find what is common (i.e. airborne data 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.
+2.  **Engage suborbital science teams to help build a community.** Suborbital teams are already meeting in smaller groups, perhaps based on mission or a specific DAAC; and we will strengthen these relationships further as a cross-DAAC community. This will involve joining meetings already ongoing, asking questions and building relationships, giving talks, sending followup messages, having open documentation of activities, 1:1 conversations; all to welcome and support scientists with busy schedules. We will lead ~biweekly “Coworking” learning meetings with suborbital science teams where we will increasingly fold in NASA center staff to learn and build relationships with suborbital users. For suborbital science teams, this will be a chance to help find what is common (i.e. airborne data 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.
 3.  **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. This Clinic will not focus on specific datasets, but the methods for writing reusable analyses that combine different datasets, using open source tooling and practices. We will develop a process to add suborbital teams’ tutorials after the Notebook Clinic to the NASA Earthdata Cookbook for increased discoverability and reuse.
 
 ### Methodology