JUPITER · PALM BEACH COUNTY
OFFSHORE SCUBAKnow before you go underwater.
Fresh official marine data, one clear dive-day decision—and an honest label on what is measured versus modeled.
THE ANSWER, UP FRONT
Jupiter offshore conditionsImportant: “GO” means the configured condition thresholds are met. It never guarantees safe diving.
WIND—Lake Worth Pier sensor
WATER—Surface temperature
WAVE PERIOD—Dominant wave
TIDE STAGE—Jupiter Inlet
WHY THIS RESULT
What is driving visibility?
—/ 100
The model will explain which live inputs are helping or hurting once the feeds respond.
72-HOUR MARINE GRID
Three-day dive outlook
Based on the National Weather Service coastal marine grid—not a site-specific dive guarantee.
TRANSPARENT BY DESIGN
How the visibility estimate works
CURRENT MODEL
42% waves+24% wind+18% tide+16% thunder
The available inputs are reweighted when a feed is missing, then the confidence drops. Stale critical sources apply a score penalty. The resulting score is mapped to a conservative placeholder range in feet.
GO Score ≥ 78 · waves ≤ 2 ft · wind ≤ 12 kt · thunder < 40%
WATCH Score ≥ 62 · waves ≤ 3.5 ft
HOLD Critical data missing or stale
STILL TO CONNECT & CALIBRATE
Visibility is not an official NOAA observation. The model should be recalibrated against time-aligned local diver reports before being treated as predictive.
PROVENANCE & STALENESS
Every source, timestamped
SourceStation / productData timeStatus
Connecting…———
One clean endpoint for the front end. /api/jupiter normalizes NOAA CO-OPS tides, NDBC observations, NWS forecasts and NWS alerts into stable JSON with per-source freshness metadata.
Use this as a planning aid, not a safety clearance. Verify the latest official marine forecast, inlet and current conditions, your operator’s guidance, regulations, and your own training before entering the water.