Dataset Factory★ EST. 2026 · BEST AT 800×600 ★
★ WELCOME TO THE DATASET FACTORY ★ PUBLIC DATA → CHECKED BUILDS → HONEST BASELINES ★ NO POP-UPS ★ NO COOKIES ★ NO TRACKERS ★ HAND-MADE HTML ★ UNDER CONSTRUCTION SINCE THE NINETIES ★
Release notes · 2026-11-16 · announcement

Ca Beach Advisory Duration

Suitability and evaluation

Evaluation setting: retrospective research. Read the prediction setting and limitations below. Public validation is development data; downloadable holdout labels must stay outside the evaluated agent workspace.

When a county health officer issues a new beach water-quality posting, will that posting remain in force for at least seven days?

Population: Advisory records in the beach-advisories CSV whose advisory class is the posting class; closure and rain advisory records are excluded and counted, and a permanent-posting value is not separable in the observed AdvisoryType data so permanent postings that the publisher folds into the posting class remain included and are recorded as a limitation. The issue date comes from DateofAdvisory and must fall from 2005-01-01 through 2023-12-31; the removal date comes from DateOpened and must be present and on or after the issue date so the whole-day duration is defined. Records sharing a beach, issue date and class are collapsed to the earliest source row so repeated episode rows do not repeat the label. Records starting in the seven days before 2016-01-01, 2020-01-01 or 2024-01-01 are dropped by the boundary embargo. Records with a missing or negative duration are excluded because the label cannot be computed; they are never treated as negative.

Target: y = 1 if the advisory record is a posting (the bacteria-standard advisory class, not a sewage closure, not a pre-emptive rain advisory, not a permanent posting) and its recorded end date is at least 7 calendar days after its start date; y = 0 if it ends within 7 days. Records with no end date (still open at extraction) or with end date before start date are excluded.

Prediction time: The advisory issue date, day 0, taken from DateofAdvisory. Only the advisory class, issue date, beach identity, county, station inventory and earlier posting issue dates are used. For duration rates only earlier training-split records whose recorded removal date closed before this row and before 2016-01-01 are used. DateOpened, DURATION CALCULATED, the spatial extent fields and the derived duration are withheld.

Splits: Chronological by advisory start date, no random shuffling: train = 2005-01-01 through 2015-12-31; eval = 2016-01-01 through 2019-12-31; holdout = 2020-01-01 through 2023-12-31. Boundary embargo: any record whose start date falls in the 7 days before a split boundary is dropped, and any record whose end date crosses a boundary is retained only in the earlier split but excluded from feature/label computation for the later split. If the observed earliest year is later than 2005, the train window starts at the first complete calendar year instead, and the boundaries 2016/2020 are unchanged.

Outcome horizon: 7 days from advisory start.

Inputs: advisory_class: Advisory class; the population is restricted to the posting class, so this column is constant posting after filtering. It records the declared population control. AdvisoryType in the observed publisher data carries posting, closure, rain and null values; a permanent posting is not a separable code, so it remains inside the posting class and is recorded as a limitation.; start_month: Calendar month of the advisory issue date, known at day 0 and capturing seasonality in dry-weather runoff and sampling.; start_day_of_week: Day of week of the advisory issue date, known at day 0 and capturing weekday sampling and staffing patterns.; county: County or jurisdiction of the advisory or joined station, proxying local re-sampling protocol and signage practice. Missing values are the explicit UNKNOWN category, not zero.; beach_id: Stable hashed beach key built from the source beach identifier or beach name plus county; it is not the advisory row identifier.; prior_postings_365d: Count of earlier posting issue dates for the same beach in the trailing 365 days, strictly before the current issue date, computed on the deduplicated history; known at day 0 and not a label-derived rate.; prior_mean_closed_duration_days_365d: Mean recorded duration of earlier same-beach training postings whose recorded removal date is strictly before the scored issue date and whose issue date is in the trailing 365 days. Only training-split labels removed before 2016-01-01 are used, so eval and holdout labels never enter. Missingness is retained when no qualifying training record exists.; days_since_prior_posting: Days since the most recent earlier posting issue date for the same beach, or missing if none; known at day 0.; station_count: Number of station-inventory rows joined to the beach; missing when no station match, not zero.; latitude: Mean station latitude for the beach, falling back to the advisory coordinate; missing when unavailable.; longitude: Mean station longitude for the beach, falling back to the advisory coordinate; missing when unavailable.; monitoring_agency: Station or advisory monitoring agency; UNKNOWN when missing, not zero.

→ Open the dataset page for numbers, files and checksums

★ THANKS FOR VISITING · BOOKMARK THIS PAGE · TELL A FRIEND ABOUT THE DATASET FACTORY · SIGN THE GUESTBOOK BEFORE YOU LEAVE ★