How we verify every splash pad

Every record on SplashPadHub is anchored to a documented source, and every source carries a weight. The hierarchy is deliberate and runs in four tiers. Tier 1 is the operator of record: the official municipal parks-and-recreation department page, the county or regional park district site, or a state-park system page where applicable. These are treated as the canonical source for hours, season dates, fees, accessibility statements, and rules, because they are the entities that operate the pad and update the page when something changes.

Tier 2 is city and county open-data — GIS feature layers, parks-asset CSV exports, ArcGIS Hub catalogs, and Socrata-powered open-data portals. These are excellent for coordinates, footprint, install year, and amenity flags but stale on hours and fees, so we use them for spatial truth and defer to Tier 1 for operational fields.

Tier 3 is local journalism and chamber-of-commerce coverage: ribbon-cutting stories, summer-feature roundups, and tourism-bureau pages. These confirm existence and surface community context but are weighted lower for operational fields because they capture a moment rather than the live state.

Tier 4 is aggregated maps and community reports — Google/Apple/OSM placemarks, parent submissions through /submit, and forum mentions. We never publish a Tier 4 source as the sole basis for a listing; it must be corroborated by at least one Tier 1, 2, or 3 source before it appears.

Every pad on the site clears three independent passes before it is considered verified. Pass one is automated cross-check: a normalization script reconciles the candidate record against city park inventories, GIS layers, and any matching aggregated-map placemark, then runs a coordinate sanity check (in-state, not in a body of water, within a plausible parcel). Records with mismatched coordinates, missing addresses, or a single unverifiable source are quarantined for human review.

Pass two is manual editor review. A human editor opens the candidate record alongside the official parks-department page and at least one secondary source, confirms the name and address, captures the season window and operating hours verbatim, flags amenities only where the source explicitly says so, and signs the record with a last-verified timestamp. If the operator page is silent on an attribute, we leave that field blank rather than guess.

Pass three closes the loop with the public. The pad goes live, and every page exposes a corrections channel and a parent-report path through /submit. Reports route to a queue that an editor must triage within 5 business days. Confirmed reports trigger a re-verification of the relevant fields and a public entry in the changelog. The pass-three cycle is what keeps the directory honest after a pad opens for the season, breaks a feature, or quietly closes.

Every verified pad record is required to carry the following fields before it can publish. Identity: official pad name, parent-park name when distinct, and a stable slug. Location: street address, municipality, county, state, ZIP, and a precise latitude/longitude pair (six-decimal precision wherever the source supports it). Season: opening month/day and closing month/day, plus weather caveats when the operator publishes them.

Operations: daily operating hours, activation method (push button, motion sensor, continuous), and any posted age or behavior rules. Features: presence and explicit naming of toddler zone, ground spray, geyser jets, bucket dump, misters, shade structures, restrooms, parking, and indoor-versus-outdoor classification. Accessibility: ADA companion seating, paved approach paths, ground-level spray for wheelchair users, no-step entry, and any operator-published statement.

Fees: free, small-fee, or paid, with the exact dollar figure when posted. Provenance: at least one Tier 1 source URL and one corroborating source, plus a last-verified date and the editor handle that signed the record. Pages render every captured field and intentionally render an empty state for unknown fields rather than imputing them from photos, names, or category averages.

An equally important question is what does not belong in a splash-pad directory. We exclude swimming pools, wading pools, and any feature where the primary play surface holds standing water — those are aquatic facilities under a different operating model and code regime, and listing them here would dilute the directory's utility for parents searching specifically for zero-depth spray play.

We exclude private-club spray installations that do not admit non-members, including HOA-only spray decks, country-club kid pools, and resort water features that require a paid resort stay. The directory's contract with readers is that anything they find here is publicly accessible, even if a small admission fee applies. Pay-to-play parks are listed only when day passes are sold to the general public.

We exclude commercial water parks (those are a separate vertical with their own search intent), defunct or decommissioned pads (logged in the changelog with a closure note rather than silently removed), and indoor recreation-center spray features where the pad sits inside a paid facility. Indoor splash facilities may be added in a future indoor-pad section, but they are categorically different and would be flagged as such.

The directory rebuilds from a daily snapshot. Every 24 hours, the data pipeline regenerates JSON outputs, recomputes statistics, regenerates static pages affected by data changes, and republishes the open-data files. The daily cadence ensures that any correction landed in the previous 24 hours appears on the public site without waiting for a weekly batch.

On top of the daily rebuild, editors run a weekly sweep against a rotating subset of pads, prioritized by traffic, age of last verification, and any pending community reports. The weekly sweep is what catches mid-season feature breakages, fee changes, and quiet hours adjustments that a parks department updates on its own page without notifying anyone.

Twice a year we run a season-change pulse: a directory-wide re-verification in early May (before Memorial Day opening) and again in early September (before Labor Day closing). The pulse refreshes opening and closing dates, captures any newly built pads added during the off-season, and retires pads that closed during the prior season. Every pad page renders its own last-verified timestamp so visitors can see exactly when the record was last touched, and pages that have not been re-verified within the current cycle are flagged in the editor dashboard for priority review.

Calling a pad 'wheelchair accessible' is a claim that families plan trips around, so we hold it to a stricter standard than other features. A pad is marked accessible only when at least three conditions are documented in writing by the operator or independently verified: an ADA-compliant approach path (paved or firm-stable surface, no steps, gradient and width meeting ADA Chapter 4 guidance), at least one ground-level spray feature reachable from the accessible path, and either a wheelchair-accessible companion seat near the pad or a transfer-friendly bench within the deck perimeter.

Where the operator publishes a formal accessibility statement, we link to it directly from the pad page. Where the statement is absent but conditions are visible from operator-published imagery (site plans, Google Street View, or parent-submitted photos under permissive license), we record what we can verify and explicitly note in the description what is undocumented. We do not infer accessibility from age, build cost, or the presence of a single curb cut.

Pads that fail one or more of the three conditions are not labeled accessible. They may still appear in the directory with a note describing what is and is not accessible, because partial information is more useful to a planning family than a binary yes/no. The accessibility review is part of every editor pass and the season-change pulse, because curb conditions and path surfaces degrade between cycles.

Sources disagree often enough that we have a written rule for it. When the official parks-department page conflicts with a Tier 2 GIS extract — say the parks site says hours are 10am-8pm but the GIS feature attribute says 9am-9pm — Tier 1 wins on operational fields and we flag the disagreement in the editor notes. When Tier 1 is silent and Tier 2 disagrees with Tier 3 (for example, a chamber feature says the pad opens Memorial Day weekend, but a city blog post says it opens June 1), we publish the more conservative window and surface the uncertainty in the description.

When a parent report from /submit contradicts every higher-tier source — a family says the pad has been closed for three weeks and the city site still shows it open — we treat the parent report as a verification trigger rather than a publication trigger. An editor calls the parks-and-recreation department or pulls the most recent council-meeting minutes to resolve the disagreement, and only after resolution do we change the public record. The disagreement and resolution both land in the changelog so readers can audit how a fact was established.

When a disagreement cannot be resolved within five business days, the pad page renders a visible 'status uncertain' note with a date and a link to the corrections channel. We would rather show a reader that a fact is contested than pretend it is settled. The same rule applies to fees, accessibility, and feature flags: where sources conflict, the page surfaces the conflict instead of hiding it behind a confident-sounding default.

Everything we verify is published as open data. The directory's daily JSON snapshot, per-state extracts, machine-readable schema, and field dictionary are available at /splash-pad-data, with stable URLs that do not break between rebuilds. The open-data feed is the same source-of-truth that powers the public site — there is no premium tier, no held-back fields, and no paywalled endpoint.

The data is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). Researchers, journalists, parks departments, and AI agents are free to use, redistribute, and build on it commercially or non-commercially as long as they credit SplashPadHub and link back to splashpadhub.com near the data. Attribution boilerplate is published alongside the snapshots so reusers can paste the right credit string without guessing.

Every snapshot carries a generated-at timestamp, the directory version, the license string, and a totals block (pads, states, cities, percent verified, percent geocoded). Schema changes are versioned and announced in the changelog before they ship, with a deprecation window before any breaking removal. Citation-grade reuse depends on stable structures, and the open-data contract is treated with the same discipline as the public pages.

Mistakes are inevitable in a directory with thousands of records updated by humans against parks-department pages that themselves change without notice. The standing commitment is that confirmed inaccuracies are corrected within 24-48 hours of verification, and that every correction is logged publicly with a date, the prior value, the new value, and the source that triggered the change.

The public correction log lives at /changelog. It captures four classes of edits: data corrections (a fact was wrong and is now right), verification refreshes (a record was re-confirmed against sources without changing), additions (new pads added to the directory), and removals (pads decommissioned, rebuilt as something else, or discovered to be private after publication). Each entry links back to the affected pad page so a reader can audit the prior state.

Where a correction came from a parent submission, the changelog credits the community without exposing the submitter's identity (we never publish submitter emails or names). Where a correction came from a parks-department outreach, we credit the department by name. The errata commitment is what makes the directory trustworthy under journalism and academic citation standards: not that we are never wrong, but that when we are, it is fixed quickly, transparently, and with an audit trail.