Hi Stefan,
I've been working on some stuff and think we could help each other. I'm new to github and coding in general, so I'm not sure if this is the best spot to write this, but I couldn't find anywhere else.
I've been wanting to get into forecasting but was never strong enough with coding to make any real progress. I recently figured out how to best leverage chatgpt to help with the meat of the coding (I've been using Python) and it has been a huge help.
Over the past couple of weeks I've built out a POSTgresql database (also a big learning experience) that has all buoy, US coastal Tide, and US coastal wind/weather from 2018 to present. Tide data also is DB for the next year (present -> Aug 2025) because its very predictable and the wind/weather forecast is input for 15 days in the future. Each day the historical data (buoys, observed weather) is updated, and the weather forecast is replaced with the current forecast.
I use NOAA API for buoy and tide. Synopticdata API for historical weather, and open-meteo API for forecast.

I started this project with the idea that I could use machine learning to forecast waves (conditions, height, etc.). Like everyone else on earth that surfs, I use Surfline but I know there are ways to make it better. A 5ft 16s west swell is not going to be FAIR-GOOD in Ocean Beach, despite how many times it tells me that. Its going to be closeout walls of death. User input should be able to shape future forecasts.

My thought was to make forecasting tool or app that relies heavily on user input. i.e. 200 people put there rating in for a day, based on those inputs the model would be trained and know how it will be in the future, and so on. This is nothing revolutionary but I don't really see it being done in surf forecasting, at least in any real way. I think it will help with individual spots rather than forecasting for a whole county or region. We have the raw data and semi-reliable forecasted data, but the target rating (height, conditions, shape, etc.) is what I need.

Anyways, I've been working a ton on this lately and wanted to reach out because it seems like your going down similar paths. Feel free to reach out, or ignore completely!
Scott
[email protected]