Dear Coastal High-Frequency Radar (HFR) and Integrated Ocean Observing System (IOOS) Communities,
Thank you to all who've completed the subject poll and, to those of you would haven't and would like to share your feedback, please see the link here for your submission by C.O.B. Wednesday.
Best regards,
Brian
Dear Coastal High-Frequency Radar (HFR) and Integrated Ocean Observing System (IOOS) Communities,
Thank you for all for the input you provided to the subject survey. That survey is now closed and Sarina and I in the IOOS Office will be reviewing the feedback received so that we may get back to you accordingly in the days following the July 4th U.S. Independence Day holiday with more information and the schedule for our HFR Community Team's inaugural meeting. Tentatively we're thinking of holding that kick-off meeting (remotely, via Google Meet) sometime during the last week of July 2026, so if you know of any major conflicting events during that time, please feel free to send a heads-up to Sarina at sarin...@noaa.gov.
Best regards,
Brian
Dear Coastal High-Frequency Radar (HFR) Communities of Practice and Interest,
Bottom-line up-front (BLUF): Fill out the Google Form here before close-of-business 8/13/2026 if you're interested in helping out the HFR Community Team by additionally serving on its Convening Committee.To elaborate...Thank you to everyone who has expressed their interest in the HFR Community Team and who joined us on 7/29/2026 for our first meeting! As we then discussed (and as per the e-mail thread below, and Team Charter here), we're looking for Team members who are additionally interested in serving on the Team's "Convening Committee".So that the HFR Community Team is self-sustaining, we need a subset of the Team's members to additionally serve on the Team's Convening Committee. The Convening Committee will perform the work needed to keep the Team running smoothly, such as running meetings, developing agendas, organizing materials, and guiding technical discussion topics. Convening Committee members will meet in the months in between each bimonthly meeting of the whole HFR Community Team, to help plan and author that meeting’s agenda.In line with the feedback received from the previous survey of the HFR Community Team, the Convening Committee will be capped at 6 members (excluding the IOOS Surface Currents Program Manager) and will serve 2-year terms, with half rotating out each year to promote continuity and knowledge transfer. The final selection of the Convening Committee from respondents to this survey will be by the IOOS Surface Currents Program Manager, to balance Geographic/Regional Association perspectives, technical roles, and manufacturer expertise. Convening Committee members may step down if their bandwidth changes; vacancies will be filled with another volunteer.I hope you will consider taking on this additional role to help maintain and organize our Team, and if you have any questions please feel free to let me know.
Best regards,
Brian
On Tue, Jul 28, 2026 at 1:58 PM Brian Zelenke - NOAA Federal <brian....@noaa.gov> wrote:
Dear Coastal High-Frequency Radar (HFR) Communities of Practice and Interest,
In addition to a friendly reminder that the subject meeting will be held tomorrow—as described by the attachments and e-mail thread forwarded below—the following are a few further items of interest:
- ROWG-14 Workshop Report available here. A report on the proceedings of the 14th Radiowave Operators Working Group Workshop (ROWG-14) that was held May 5–7, 2026 in Newport, Oregon, U.S.A. is available here, and by clicking on the "Meeting Summaries" tab at the website here.
- HFRNet data product generation code available on GitHub here. With the transition of the NOAA IOOS Surface Currents Program's HFR data assembly center (DAC) known as "HFRNet" into the internal NOAA NESDIS Common Cloud Framework (NCCF) system complete as of July 2025, the codebase used in the NCCF to create HFRNet's data products has been published on GitHub here. This is a work-in-progress, with more documentation and guidance on how to provide feedback to come.
- HFRNet website code available on GitHub here. The website here provides visualizations, documentation, statistics, and diagnostics for HFR stations and the products generated from their data in the NCCF. The release of that website's code in GitHub here includes all four parts of the web application: an interactive map client (PHP, JS), a data API (Python), a database (MySQL), and the operational scripts (Python). Each component comes with its separate README.md file and its own Docker Compose configuration. A top-level Docker Compose file is also provided to run the client, API, and database together, making it straightforward to launch a complete local instance.
- If you haven't done so already, please review any pages, documentation, or THREDDS server links on your own websites to see if they contain the old HFRNet address (which had cordc.ucsd.edu in its URL) and replace them with links to the new HFRNet website or NOAA-NDBC's HFR THREDDS data server, as appropriate. Also, note that NOAA's National Data Buoy Center (NDBC) provides the sister website here, which is another way for you to visualize and access these same HFRNet data products.
Looking forward to speaking with you tomorrow!
Best regards,
Brian
---------- Original message ---------
From: Brian Zelenke - NOAA Federal <brian....@noaa.gov>
Date: Tue, Jul 14, 2026 at 7:51 PM
Subject: Invitation: HFR Community Team Meeting @ Wed Jul 29, 2026 2pm - 2:50pm (EDT)
To: Radiowave Operators Working Group (ROWG) <rowg...@email.rutgers.edu>, Radiowave Oceanography Workshop <r...@msi.ucsb.edu>, _NOS IOOS_RA_Contacts <ioos.ra....@noaa.gov>
Cc: Sarina Mann - NOAA Affiliate <sarin...@noaa.gov>
Dear Coastal High-Frequency Radar (HFR) Communities of Practice and Interest,
Please join us for our inaugural meeting of the HFR Community Team. (Also, thank you again to everyone who filled out the HFR Community Team Structure & Interest Survey we sent back on June 3, 2026 to help us prepare for this team's formation!)
You will find attached to this e-mail:
- For you to read carefully in advance of this meeting to help with your decision to participate, a PDF of this Team's charter—a collaborative, living document created to establish our shared purpose and mission, define this team's scope and boundaries, and set guiding principles and operational expectations for how we will work together (subject to change; the latest version of the Charter is available as a Google Doc here).
- A PDF of this meeting's agenda (also subject to change; the living version of this agenda is available as a Google Doc here).
- A "*.ics" universal calendar file, containing the subject event's details like title, date, time, connection information, and description. You can import this event file into your calendar platform of choice like Google Calendar, Apple Calendar, or Microsoft Outlook. Also, please feel free to share this e-mail and calendar invite file with others who may be interested.
As a reminder, this team aims to address the operational, scientific, and technical challenges inherent in maintaining a healthy, resilient, and high-functioning national HFR network that is responsive to the needs of its stakeholders. Invited to join this Team include those who are:
Broad voluntary participation is intended, including by both domestic and international collaborators, and Team meetings will be conducted virtually via Google Meet.
- users and creators of HFR data products;
- representatives from IOOS Regional Associations (RAs);
- staff in the IOOS Office and other collaborating offices of the National Oceanic & Atmospheric Administration (NOAA);
- and Principal Investigators (PIs), sensor manufacturers, data managers, technicians, and stakeholders engaged in HFR-related research, development, and operations.
Note: A separate Convening Committee will later be formed to help run meetings and develop agendas.
To ensure equity and accessibility across time zones, we plan to vary future meeting times and rotate the day of the week to better accommodate schedules.
----
Thank you—we look forward to connecting,