Neptune Dashboard

A Next.js (App Router) dashboard that displays ocean water-quality nowcasts and 3-day forecasts for many beach locations from a single deployment.

Forecast data is produced by the separate project-neptune model repo and pushed into this repo as CSVs by GitHub Actions.

Architecture

• One repo, one main serves every location.
• Location is a URL route segment: /hermosa, /manhattan, /<slug>.
• A LOCATIONS registry in lib/data.ts holds every per-location value (display name, station codes, beach names, map fallback center).
• Per-location data folders live under public/data/<slug>/ and each contain: nowcast_latest.csv, forecast_3day.csv, history_3day.csv, thresholds.csv.
• Per-location nowcast archives live under data/nowcast-archive/<slug>/ — one nowcast_<date>.csv per published day, written by scripts/archive-nowcast.py in the same commit as the nowcast it copies. scripts/build-history.py reads these in preference to project-neptune's shared archive so the 7-day window's past cells replay exactly what the board published that day. Deliberately outside public/ — it is a build-time input, not something to serve.
• Components are generic — they receive location values as props and hardcode nothing.
• / redirects to the default location (/hermosa); unknown slugs return a 404.

Adding a location

1. Add one entry to the LOCATIONS registry in lib/data.ts:

   newslug: {
     slug: "newslug",
     displayName: "New Beach, CA",
     stations: ["DHS999"],
     beachNames: { DHS999: "New Beach - Main" },
     mapFallbackCenter: [33.0, -118.0], // [lat, lng]
   },
   

2. Create public/data/newslug/ and populate it with that location's CSVs (this is what the project-neptune daily-refresh workflow writes into).

No per-location code changes are required.

Getting Started

npm install
npm run dev

Open http://localhost:3000; it redirects to the default location. Visit /hermosa or /manhattan directly to view a specific location.

Build

npm run build

Deploy

Deploys on the Vercel Platform. See the Next.js deployment docs for details.

Beach requests

The on-site form lives at /california/request-beach (preview: /sandbox/request-beach). Apply its additive database schema with node scripts/apply-beach-requests-schema.mjs before deployment. Submissions store email, message, source, and creation time in beach_requests; sandbox requests are tagged separately. To export live requests privately: node scripts/export-beach-requests.mjs /absolute/path/beach-requests.csv. The export excludes sandbox records and refuses to overwrite an existing file. Requests are not marketing subscriptions. Run node scripts/test-beach-requests.mjs for storage and endpoint validation.