Technical Board 2026_01_28

[ChrisJohnNOAA]

Attendees:
Seth Champagne, Lynn Dewitt, Chris John, Roy Mendelssohn, Shane St Savage, Micah Wengren

1. Review previous action items

• (Chris) Co-ordinate with presenters to schedule January showcase
• (@SethChampagneNRL ) Check with NAVO about open sourcing WMS implementation
  Seth: Discussions started about open sourcing WMS, but currently stuck behind needing to update.
  See new Action Item below.
• (Chris) Make sure there is proper tracking of items left for JTE
• (Chris) Make sure GenerateDatasetsXml updates are covered in priority projects/issues
• (Chris) Open a discussion about the Grid Axis identification

All done, though we’ll check in with Seth about progress next time.

2. Go over the priority projects and discuss any changes we'd like to make.

Zarr3 support: Now available as a Java library.

NetCDF4 as an output: discussed as a priority.

3. Review of 2.30 and discuss release plan

2.29 ended up getting out late, and the holidays meant not a lot of time in December, so 2.30 will likely be a light release, maybe just one big feature.

JTE: Lots of progress. Hoping to have it ready to be used behind a feature flag.

4. Plans for 2.31

JTE: Polish and UI improvements (in JTE).

GenerateXML:

• Discussion on moving it out from where it is to make it easier to find and run.
• Find some way to improve this short term, maybe with json input and example files. Longer term potentially including a page in ERDDAP to generate datasets xml.
• Security concerns about editing were raised; need a plan.

5. Demos for the next showcase?

Potential topics discussed:

• JTE - ready for use demo
• Accessing private datasets (Sunny)
• erddapy, other python packages (Filipe)
• rerddap
• Matlab?
• erddap2arcgisonline
• ERDDAP with xarray (uses OPeNDAP)

6. GSoC

Chris is not going to be able to be the primary mentor this year.

Project ideas if anyone wants to mentor:

• GenerateDatasetsXML improvements
• WMS, graphing, and other UI improvements
• Zarr v3, NetCDF4 support (this one is tricky since it currently requires a C++ dependency)

Action Items

• @SethChampagneNRL: Check in next time on progress of NAVO open sourcing.
• @ChrisJohnNOAA: Add a file format section to the priority projects.
• @ChrisJohnNOAA: Reach out to package maintainers for next showcase demos.
• @ChrisJohnNOAA: Document GSoC ideas in the GSoC IOOS issues (GitHub Form).