You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*In 2026 we are proud to continue supporting NASA teams, building from our work with the [NASA Openscapes Mentors](https://nasa-openscapes.github.io/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.*
15
16
17
+
*Cross-posted at [openscapes.org/blog](https://openscapes.org/blog), [nasa-openscapes.github.io/news](https://nasa-openscapes.github.io/news)*.
## NASA suborbital science and Openscapes proposed support
19
22
20
-
NASA Earthdata has volumes of remote sensing data collected by [platforms in space, air, water, and land](https://www.earthdata.nasa.gov/data/platforms). Substantial suborbital data is collected from from airborne sampling via airplanes, ground networks, and field sampling on land, boats, and buoys.
23
+
NASA Earthdata has volumes of remote sensing data collected by [platforms in space, air, water, and land](https://www.earthdata.nasa.gov/data/platforms). Substantial suborbital data is collected from airborne sampling via airplanes, ground networks, and field sampling on land, boats, and buoys.
21
24
22
-
Suborbital science teams are science teams that create and use suborbital data via NASA programs like [EVS-4](https://essp.nasa.gov/earth-pathfinder-quests/projects/earth-venture-suborbital-evs-4/). The science teams use suborbital data to ground-truth satellite data, as well as other awesome research like studying Arctic coastlines via the [FORTE mission](https://espo.nasa.gov/forte) and glaciers and ice sheets via the [Snow4Flow mission](https://snow4flow.lpl.arizona.edu/).
25
+
Suborbital science teams are teams that create and use suborbital data via NASA programs like [EVS-4](https://essp.nasa.gov/earth-pathfinder-quests/projects/earth-venture-suborbital-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](https://espo.nasa.gov/forte) and glaciers and ice sheets via the [Snow4Flow mission](https://snow4flow.lpl.arizona.edu/).
23
26
27
+
<<<<<<< HEAD
24
28
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.
29
+
=======
30
+
Suborbital teams connect with NASA Distributed Active Archive Center (DAAC) staff at both 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 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.
31
+
>>>>>>> 4f43cdabd15292a128c1d2fdc3fb603a58630bce
25
32
26
33
Staff at many NASA DAACs work with science teams to archive and use suborbital data, including:
27
34
@@ -33,9 +40,9 @@ Staff at many NASA DAACs work with science teams to archive and use suborbital d
Our NASA Openscapes Mentor Community has been collaborating tosupport Earthdata users. 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](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](https://nasa.github.io/VITALS/), which has developed [specific airborne tools](https://nasa.github.io/VITALS/python/Finding_Coincident_Airborne_and_Orbital_Data.html).
43
+
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](https://nasa-openscapes.github.io/earthdata-cloud-cookbook). Many other tools and resources have originated from these cross-agency Openscapes relationships with the DAACs, such as [VITALS](https://nasa.github.io/VITALS/), which has developed [specific airborne tools](https://nasa.github.io/VITALS/python/Finding_Coincident_Airborne_and_Orbital_Data.html).
37
44
38
-
In our NASA Openscapes Mentor Community, most of the DAACs listed above that are supporting suborbital work have been consistent contributors in past five years. Our goal in 2026 is to increase our support for NASA suborbital science teams to develop reproducible workflows. In March, we are thrilled to welcome [Ronny Hernández Mora](https://ronnyale.com/) 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.
45
+
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](https://ronnyale.com/) 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.
39
46
40
47
Below is our planned approach from our proposal, presented through POP: Purpose, Outcomes, Process.
41
48
@@ -51,13 +58,13 @@ Suborbital science teams will create reusable open source notebooks (Jupyter, Qu
51
58
52
59
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.
53
60
54
-
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; and we will strengthen these relationships further as a cross-DAAC community. We will onboard 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.
55
-
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](https://earthaccess.readthedocs.io/en/stable/) python library, and writing documentation that focuses on reuse and onboarding others to these workflows.
56
-
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, tutorials, cloud optimization).
61
+
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.
62
+
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.
63
+
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`, tutorials, cloud optimization).
57
64
58
65
### Methodology
59
66
60
-
We will follow the NASA Openscapes Flywheel mechanism ([Robinson & Lowndes 2022](https://eartharxiv.org/repository/view/4560)) to facilitate and scale open source practices (e.g. from groups like [Pangeo](https://pangeo.io/), [rOpenSci](https://ropensci.org/), [The Carpentries](https://carpentries.org/)):
67
+
We will follow the NASA Openscapes Flywheel mechanism [@robinson2022] to facilitate and scale open source practices (e.g. from groups like [Pangeo](https://pangeo.io/), [rOpenSci](https://ropensci.org/), [The Carpentries](https://carpentries.org/)):
61
68
62
69
-**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:
63
70
@@ -69,13 +76,13 @@ We will follow the NASA Openscapes Flywheel mechanism ([Robinson & Lowndes 2022]
69
76
70
77
- 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".)
71
78
72
-
- Building trust so they would prioritize time for the Clinic, as we design the Clinic to fit their needs.
79
+
- Building trust with science teams so they would prioritize time for the Clinic, as we design the Clinic to fit their needs.
73
80
74
81
-**To empower teams through the Notebook Clinic** we will draw from what we’ve learned from leading [27 Champions Cohorts](https://openscapes.org/initiatives#champions-program) (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:
75
82
76
83
- 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.
77
84
78
-
- Focusing on developing relationships with potential participants (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.
85
+
- 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.
79
86
80
87
- 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.
81
88
@@ -85,8 +92,6 @@ We will follow the NASA Openscapes Flywheel mechanism ([Robinson & Lowndes 2022]
85
92
86
93
- Adding Notebook Clinic lessons to the Earthdata Cloud Cookbook for discoverability and reuse.
87
94
88
-
<!---->
89
-
90
95
-**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:
91
96
92
97
- "Defaulting to open" as always: open documentation, contributing to the NASA Earthdata Cookbook, and storytelling via blogs and talks will center this work.
0 commit comments