Use the data without giving it more certainty than it has.
These guides explain the calculations behind the tool and the limits that keep a derived score from becoming a fake safety verdict.
Wave height vs. wave period: what a buoy is really telling you
Why a 6-foot sea at 8 seconds is not the same signal as 6 feet at 18 seconds, and how CoastEventRadar uses both without making surf-safety claims.
Read guide →GUIDEKing tide vs. highest tide: why the labels are not interchangeable
How to use a local highest-tide ranking without falsely calling every top-percentile tide an official King Tide event.
Read guide →GUIDEHow to plan a coast weekend with tides, waves and weather in the right order
A repeatable workflow for choosing the day and time first, then checking live ocean context and official alerts.
Read guide →GUIDEHow CoastEventRadar scores a coastal opportunity
What goes into the score, what is deliberately left out, and why a high score is not a safety rating.
Read guide →GUIDEObserved vs. predicted water level: the coastal anomaly worth watching
Why the gap between NOAA observation and astronomical prediction can matter more than the prediction alone.
Read guide →GUIDEHow to find the best daylight low tides without scrolling a year of tide tables
A practical way to rank low tides by rarity and daylight instead of hunting manually.
Read guide →GUIDENOAA tides, NWS weather, NDBC buoys and wildlife reports: what each source actually tells you
The source map behind the radar and the limits that prevent false precision.
Read guide →