|
| 1 | +--- |
| 2 | +title: "People, structure, mechanics: How we led the earthaccess December 15 Hackday online and in New Orleans" |
| 3 | +# description: "Subtitle" |
| 4 | +author: |
| 5 | + - name: Amy Steiker |
| 6 | + orcid: 0000-0002-3039-0260 |
| 7 | + - name: Luis Lopez |
| 8 | + orcid: 0000-0003-4896-3263 |
| 9 | + - name: Joseph H Kennedy |
| 10 | + orcid: 0000-0002-9348-693X |
| 11 | + - name: Aaron Friesz |
| 12 | + orcid: 0000-0003-4096-3824 |
| 13 | + - name: Matt Fisher |
| 14 | + orcid: 0000-0003-3260-5445 |
| 15 | + - name: Max Jones |
| 16 | + - name: Danny Kaufman |
| 17 | + orcid: 0000-0002-1487-7298 |
| 18 | + - name: Julius Busecke |
| 19 | + orcid: 0000-0001-8571-865X |
| 20 | + - name: Saber Brasher |
| 21 | + orcid: 0000-0003-2925-5691 |
| 22 | + - name: Mahsa Jami |
| 23 | + - name: Jessica Scheick |
| 24 | + orcid: 0000-0002-3421-4459 |
| 25 | + - name: Diane Fritz |
| 26 | + - name: Erik Bolch |
| 27 | + orcid: 0000-0003-2470-4048 |
| 28 | + - name: Nathan Roberts |
| 29 | + orcid: 0000-0001-6625-671X |
| 30 | + - name: Aimee Barciauskas |
| 31 | + - name: Rupesh Shrestha |
| 32 | + orcid: 0000-0002-3140-6623 |
| 33 | + - name: Chuck Daniels |
| 34 | + - name: Andy Barrett |
| 35 | + orcid: 0000-0003-4394-5445 |
| 36 | + - name: Chris Battisto |
| 37 | + orcid: 0000-0002-9608-3634 |
| 38 | + - name: Mikala Beig |
| 39 | + - name: Michele Thornton |
| 40 | + orcid: 0000-0002-6533-6328 |
| 41 | + - name: Andy Teucher |
| 42 | + orcid: 0000-0002-7840-692X |
| 43 | + - name: Stefanie Butland |
| 44 | + orcid: 0000-0002-5427-8951 |
| 45 | + - name: Julie Lowndes |
| 46 | + orcid: 0000-0003-1682-3872 |
| 47 | +date: 2026-02-04 |
| 48 | +citation: |
| 49 | + url: https://nasa-openscapes.github.io/news/2026-02-04-earthaccess-dec15-hackday/ |
| 50 | +categories: [blog, nasa-framework] |
| 51 | +image: earthaccess-stickerheads_20251215.jpg |
| 52 | +--- |
| 53 | + |
| 54 | +*On December 15, 2025 we led a hackday funded by [ESIP](https://www.esipfed.org/) (Earth Science Information Partners), in collaboration with [CNG](https://cloudnativegeo.org/) (Cloud Native Geospatial) and Openscapes. 41 people participated, with 14 in person and 27 joining remotely. 22 co-leads and facilitators from many organizations were critical to its success, including six [NASA DAACs (Earthdata Data Centers)](https://www.earthdata.nasa.gov/centers), [Development Seed](https://developmentseed.org/), [UC Berkeley Center for Data Science & Environment](https://dse.berkeley.edu/), [University of New Hampshire](https://eos.unh.edu/), ESIP, and Openscapes. This blog post is focusing on the people, structure, and mechanics behind the hackday – the reality of how we put this together. This was a HUGE collaborative effort with folks stepping up to help facilitate and lead, with limited time. We are proud of the people we brought together, and what we accomplished. Thank you all facilitators – all are co-authors! We plan to share outcomes from the hackday at the July 2026 ESIP Summer Meeting in Austin Texas.* |
| 55 | + |
| 56 | +*Quicklinks:* |
| 57 | + |
| 58 | +- [*Earthaccess python library*](https://earthaccess.readthedocs.io/en/stable/) |
| 59 | +- [*ESIP FUNding Friday article*](https://www.esipfed.org/funding-friday-where-creativity-meets-science/) |
| 60 | +- [*Crossing the chasm together - notes from ESIP July 2025 meeting*](https://openscapes.org/blog/2025-11-16-esip-july-2025/) *- includes account of singing our pitch for the hackday at ESIP Summer Meeting in Seattle July 2025* |
| 61 | + |
| 62 | +------------------------------------------------------------------------ |
| 63 | + |
| 64 | +## Goals |
| 65 | + |
| 66 | +The goal we pitched to [ESIP’s FUNding Friday](https://wiki.esipfed.org/FUNding_Friday_Projects) was to build a prototype and roadmap for “Growing the Family” by integrating [earthaccess](https://earthaccess.readthedocs.io/en/stable/) with non-NASA Earth science data ([NOAA](https://www.noaa.gov/), [USGS](https://www.usgs.gov/), [Copernicus](https://dataspace.copernicus.eu/), and more!). We designed the event to focus on building the community of earthaccess contributors and adopters; we were equally interested in growing ideas as much as we were interested in developing technology to support earthaccess growth. For those new to earthaccess, it's a Python library that simplifies access to NASA Earth science data, turning complex authentication and data discovery into just a few lines of code. It's becoming essential infrastructure for researchers working with Earth observation data, and with this hackday, we wanted to expand its community and expand its reach beyond NASA to other Earth science data providers. |
| 67 | + |
| 68 | +::::: grid |
| 69 | +::: g-col-7 |
| 70 | +{fig-alt="screenshot of zoom window with 6 by 5 squares of smiling waving people" fig-align="left" width="100%"} |
| 71 | +::: |
| 72 | + |
| 73 | +::: g-col-5 |
| 74 | +{fig-alt="photo of eleven smiling women and men holding up hexagonal stickers" fig-align="left"} |
| 75 | +::: |
| 76 | +::::: |
| 77 | + |
| 78 | +*Zoomie (Zoom selfie) of virtual and in-person hackday participants (with earthaccess hex stickers!).* |
| 79 | + |
| 80 | +## The hackday: what we did |
| 81 | + |
| 82 | +The hackday was hybrid: online and in-person in New Orleans (independent of AGU2025 but conveniently co-located for attendees). We shared four tracks in advance as topics folks might want to focus on: |
| 83 | + |
| 84 | +- STAC (SpatioTemporal Asset Catalogs) Integrations – “Growing the Family” |
| 85 | + |
| 86 | +- User Stories – Understanding Pain Points and Priorities |
| 87 | + |
| 88 | +- User Onboarding and LLM Support |
| 89 | + |
| 90 | +- Data Virtualization |
| 91 | + |
| 92 | +Leads opened GitHub Issues or Discussions for tracks so that folks could consider and discuss these in advance. This is part of lowering barriers to participation, but also capturing progress, notes, and discussions. |
| 93 | + |
| 94 | +We had a Zoom breakout room for each track (everyone was logged into Zoom to be more inclusive of remote participants). We had one Agenda document (screenshot) with Tabs for each track, and time at the beginning, middle, and end for all tracks to come back together in the Main room and share out. |
| 95 | + |
| 96 | +::: blockquote-blue |
| 97 | +> *"It is amazing to see all the specialists working together to address the real, unprepared needs of the participants…The shared notes document was the best part—it captured all the details, including questions, answers, and links, from every group and participant."* - **Alexys H Rodríguez, participant** |
| 98 | +::: |
| 99 | + |
| 100 | +::: {style="text-align:center;"} |
| 101 | +{fig-alt="screenshot of agenda doc with welcome text and timeline for the 5-hour session" fig-align="center" width="60%"} |
| 102 | +::: |
| 103 | + |
| 104 | +## Planning the hackday |
| 105 | + |
| 106 | +Planning the hackday was a study in how generous people fuel collaboration across groups, reusing (“[forking](https://docs.google.com/presentation/d/10RbeoshmsHx06ZIFA1x-KERbrMkcBtnOtFVyt9UCs5o/edit?slide=id.g3af247f9d45_0_0#slide=id.g3af247f9d45_0_0)”) existing structures and using existing communication channels, and being comfortable with “good enough” given the time and resources we had. For example, some folks were only able to lead during a portion of the session time, and many were not able to fully polish slidedecks ahead of time. Our event planning phase was during the government shutdown, so we were missing people, and others were over-taxed with responsibilities. Even so, folks prioritized time where they could, and we focused on communicating openly and early to invite participants to sign up and also to coordinate our facilitator team and design the plan. CNG created a [registration page](https://luma.com/7hp819zp) for participant sign-ups that we shared with our communities. We coordinated largely through a single spreadsheet where we listed “hackday facilitators” (earthaccess maintainers and NASA Openscapes Mentor community) and mapped out availability and roles. |
| 107 | + |
| 108 | +::: {style="text-align:center;"} |
| 109 | +{fig-alt="screenshot of spreadsheet listing facilitator names, roles, in-person or online, breakout rooms they will help in" fig-align="center" width="75%"} |
| 110 | +::: |
| 111 | + |
| 112 | +Hackday funds from ESIP went to the venue rentals for the hackday and social hour, smoothly coordinated by CNG. Hackdays cost more than \$5K, however, and this did not compensate for the time for the 22 facilitators involved. Their time was generously covered “in kind” by their employers (listed in the preface). |
| 113 | + |
| 114 | +We have survey responses that will help us support earthaccess adopters and contributors – and help us lead successful events in the future. |
| 115 | + |
| 116 | +## Building Community, not just Code |
| 117 | + |
| 118 | +There is so much value in the people and organizations working together to lead this event, it’s impossible to overstate. We saw our approach have impact: building a welcoming contributor community (users are contributors!) around a transformative python library supported by technical and human infrastructure. Diverse participants, some who’ve already been involved and some new to earthaccess who were keen to collaborate came from many different organizations, including NASA DAACs, DevelopmentSeed, UCBerkeley, [Earthscope hub](https://www.earthscope.org/data/geolab/), and NOAA. They were developers, contributors, newcomers, users, learners. People joined from across the US, and from Poland, India, and Canada. |
| 119 | + |
| 120 | +Several people indicated they were new to earthaccess and for some this was their first-ever hackday! We aimed to “grow the family” and ease people’s introduction by running a 2-day event in November - [A welcome to NASA Earthdata and earthaccess](https://openscapes.org/blog/2025-11-27-nasa-champions-2025-summary/). Day 1 consisted of lessons and demos and Day 2 had people getting hands-on experience by running those demos themselves in breakout rooms they chose. This clearly lowered some barriers to hackday participation and contribution to earthaccess in general. One participant joined the November event, where she got more familiar with contributing, joined our biweekly earthaccess hackdays, and then contributed in this hackday. She’s now a full contributor with [pull requests](https://github.com/search?q=repo%3Ansidc%2Fearthaccess+ana-sher&type=pullrequests) merged into earthaccess! |
| 121 | + |
| 122 | +## Early Outcomes and next steps ESIP Summer Meeting 2026 |
| 123 | + |
| 124 | +**We continue to have [Tuesday biweekly hackdays](https://github.com/nsidc/earthaccess/discussions/440) to move progress forward - please join us! - and we’ll continue on these Tracks as well. To learn more, please peruse the discussions, issues, and other content on the [earthaccess GitHub repository](https://github.com/nsidc/earthaccess).** |
| 125 | + |
| 126 | +Here are some early outcomes (many still being worked on!), that we will describe in more detail at the ESIP Summer Meeting: |
| 127 | + |
| 128 | +**STAC Track:** |
| 129 | + |
| 130 | +- GitHub [Issues](https://github.com/nsidc/earthaccess/issues?q=state%3Aopen%20label%3A%22impact%3A%20stac%22); [Discussions](https://github.com/nsidc/earthaccess/discussions?discussions_q=is%3Aopen+label%3A%22impact%3A+stac%22). |
| 131 | + |
| 132 | +- We created a Pull Request (<https://github.com/nsidc/earthaccess/pull/1171>) that’s a test of querying [CMR](https://www.earthdata.nasa.gov/about/esdis/eosdis/cmr) (Common Metadata Repository) and parsing them as [STAC](https://stacspec.org/) (SpatioTemporal Asset Catalogs) items. |
| 133 | + |
| 134 | +- Most important: Deciding not to reimplement pystac client. |
| 135 | + |
| 136 | +- End goal to have same 3-lines of code to access anything with a STAC client. Maybe more modular. |
| 137 | + |
| 138 | +**User stories Track:** |
| 139 | + |
| 140 | +- Focusing around engagement of earthaccess. How do users find earthaccess? How do they initially engage with it? What are some pain points? |
| 141 | + |
| 142 | +- Ideas to ease engagement: Creating a zine and cheatsheet, widely used in the R community |
| 143 | + |
| 144 | +- Next steps: Ideas around what to include in cheatsheet(s), how to expand reach, and how to make earthaccess more accessible for more people |
| 145 | + |
| 146 | +**User Onboarding Track:** |
| 147 | + |
| 148 | +- Leading newcomers through basic tutorials, including [OPeNDAP](https://www.opendap.org/) tutorial that Chris Battisto ran |
| 149 | + |
| 150 | +- Welcoming newcomers, experimenting accessing Daymet data that a participant works with |
| 151 | + |
| 152 | +- Good questions around services and how it relates to earthaccess (ex harmony, harmony-py and OPeNDAP) |
| 153 | + |
| 154 | +**Data Virtualization Track:** |
| 155 | + |
| 156 | +- First half focused on shared learning about virtual datacube concepts and implementations |
| 157 | + |
| 158 | +- Lots of next steps: |
| 159 | + |
| 160 | + - DevSeed/Aimee Barciauskas spinning up monthly meeting on Virtual Datasets beginning January 2026 |
| 161 | + |
| 162 | + - James Gallagher is organizing a session at ESIP to come up with a standard for chunk manifests... virtualizarr, zarr, dmrpp, and more, with a goal to have a draft for the summer meeting |
| 163 | + |
| 164 | + - Max Jones posted some cool metrics on how fast data access can be with virtual data cubes with different stacks (Luis) |
| 165 | + |
| 166 | + - Danny Kaufman was inspired to finally work on Icechunk-ifying a collection from ASDC! |
0 commit comments