SwellOracle methodology

How SwellOracle Handles Buoy, Model and Surf Data

SwellOracle is designed to make ocean data easier to interpret, not to hide uncertainty. This methodology explains what each page represents and how to compare readings responsibly.

Observed stations and physical buoys

When a source identifies a physical instrument, SwellOracle preserves its station identifier, provider and observation time. A missing or delayed feed is shown as unavailable rather than replaced with invented values.

Different networks update on different schedules, so the timestamp is part of the reading and should be checked before comparing stations.

Marine model points

Model locations provide estimated conditions for a geographic grid point. They are useful for regional context, especially where no public buoy exists, but they are not measurements from an instrument in the water.

Model and observed readings are labelled separately throughout the site so a user can compare like with like.

History and comparisons

Historical rows are stored only when a reusable source observation changes. Charts are not fabricated for locations without a correctly identified series.

Comparisons should account for coastline orientation, exposure, period and direction; distance alone does not guarantee that two stations describe the same surf conditions.

Practical limits

SwellOracle does not replace local judgement, tide information, wind observations, official warnings or in-water safety decisions. Use the source, timestamp and local context together.

Practical takeaway