Millions of Gallons

Methodology

Everything on this site is computed from one input: a list of meter readings with timestamps. This page explains each step so the results can be checked, challenged, and improved. The code is in the repository under src/lib.

Input

A CSV from a utility portal. Badger BEACON exports have the columns Location_ID, Read_Unit, Read, Endpoint_SN, Read_Time: a cumulative register reading in thousands of gallons every 15 minutes. The parser turns consecutive readings into interval usage in gallons, snaps rounding noise to zero, drops duplicates, and flags backwards reads and gaps. Generic exports are handled by looking for a timestamp column and either a cumulative reading or a per-interval usage column, with unit conversion.

Sessions and the irrigation fingerprint

A session is a run of consecutive intervals at or above 80 gallons per hour (20 gallons per 15 minutes). Showers, baths and laundry produce one or two such intervals. A multi-zone sprinkler system produces many in a row.

A session is labeled irrigation if it runs 45 minutes or more and moves 150 gallons or more, or if it starts at a recurring clock time (a 15-minute slot, give or take one, where substantial sessions begin on five or more distinct days) and runs at least 30 minutes and 100 gallons. A home is said to have an irrigation system when at least eight scheduled irrigation sessions, totaling 2,000 gallons or more, occur across two or more months. This is the answer to the question the project started with: can you tell from the meter alone whether a house has sprinklers? Yes.

Detectors

Leak

For each day, take the smallest interval. A healthy home hits zero at some point overnight. When the daily minimum is above zero for three or more consecutive days, something is flowing continuously. The gallons figure is a lower bound: the daily minimum multiplied out over the day. Severity is by average gallons per day: under 50 warning, 50 to 200 serious, over 200 critical. A run that ends before the data does is reported as "found and fixed."

Vacation

Indoor life is many small draws a day. After removing irrigation intervals, a day with two or fewer small draws (under 15 gallons each) and under 30 gallons of non-irrigation use is an away day. Three or more in a row is an absence. Irrigation that ran during an absence is reported, as is any other flow, because nobody was home to cause it. The detector needs a home that normally shows at least six small draws a day.

District rules

Each district's rules are stored as typed constraints with citations (see Watering rules): allowed-day schemes (odd/even by house number, day of week, day of week by parity, last digit of address, or zone map), banned hours, seasonal bans, rain rules, and maximum days per week. Every irrigation session is checked against every rule in force on its date. When a scheme needs a house number that was not provided, both parities are evaluated and reported side by side. Banned-hours violations count only the minutes inside the window.

Rain

Daily precipitation and reference evapotranspiration (ET0) come from the Open-Meteo historical API for the ZIP code's coordinates. A rain rule fires when the day's rainfall meets the district's trigger (0.25 inch when unspecified), and optionally the day after a rain of 0.5 inch or more.

Overwatering

For each week with irrigation, need = ET0 x 0.8 (a cool-season turf crop coefficient) minus effective rain (capped at 0.5 inch per day), in inches, times 0.623 gallons per square foot per inch, times lawn area (default 5,000 sq ft, adjustable). Applied is the week's irrigation gallons. Excess is applied minus need, floored at zero. Without weather, need is one inch a week.

Frequency and timing

Median watering days per week across weeks with irrigation; five or more is flagged. Share of irrigation starting between 10 AM and 6 PM is flagged when the district has no mandatory hours rule of its own; 25% of that water is counted as recoverable evaporation loss.

Anomalies

Days at four times the median daily use or more, not explained by irrigation, and large unscheduled sessions. Reported for information: pool fills, hoses left on, bursts.

Scorecard

Recoverable gallons = leak + half of away-irrigation + rain-day irrigation + the largest single behavioral opportunity (overwatering excess, frequency, timing, or wrong-day). The largest is taken rather than the sum because they overlap. Grade is the recoverable share of total use: under 5% A, under 15% B, under 30% C, under 50% D, otherwise F. Dollar savings use the rate you enter (default $5 per 1,000 gallons). Energy uses 1.8 kWh per 1,000 gallons, a typical figure for groundwater supply with pumping, treatment and distribution, and 0.5 lb CO₂ per kWh.

The rule-compliant badge

A separate, positive counterpart to the scorecard above. It is earned only when at least one mandatory watering rule was actually evaluated against the data (not skipped for missing weather or a missing house number) and none of the rules that were evaluated show a violation. An irrigation system has to be detected at all; there is nothing to be compliant about without one.

The headline gallons figure is deliberately conservative and uses no external or assumed "typical household" baseline. It is: the number of days, within this household's own watering season (from its first to its last detected irrigation session) and restricted to the household's own normal watering days under its district's allowed-day rule when one exists, that the district's rain rule would have blocked watering and this household genuinely applied under 100 gallons that day — multiplied by this household's own median irrigation session size. Every input to that number comes from the household's own data; nothing is compared to anyone else's usage.

The shareable image is generated on request from those numbers (/api/badge, using Next.js's built-in ImageResponse) and stores nothing server-side.

The no-irrigation badge

A household with no detected automatic sprinkler system at all earns a different, separate badge — not a weaker version of the rule-compliant one, and not nothing. It is arguably the better outcome of the two, since there is no irrigation to misuse in the first place.

It deliberately carries no gallons-saved figure. Putting a number on it would mean guessing how much water this specific lawn would have used with a sprinkler system — a comparison to a hypothetical the meter never recorded, not a measurement of anything that happened. Every other number on this site, including the rule-compliant badge's figure above, is computed only from a household's own observed data; inventing an external "average lawn" baseline here would break that rule just to avoid an empty space. So the badge says so directly instead: the achievement is real, the number is not knowable, and it shows only what is actually known — total and average daily use, and the small share of that use that looked irrigation-shaped at all.

Lot lookup and lawn area

The address is geocoded with the US Census Geocoder (OpenStreetMap's Nominatim as fallback). The point is then looked up in public parcel services: Nassau County's Land Records Viewer map service, whose geometry is in New York Long Island state-plane feet so the recorded shape area is square feet, and the New York State GIS statewide tax-parcel service, which covers 38 counties including Suffolk and Westchester and carries the assessor's lot size. Both are free and require no account. Outside New York, and only if the site operator has configured it, ReportAll USA fills in nationwide parcel data; it is billed per lookup with no monthly minimum, so it is entirely optional and the rest of the site does not depend on it. Building footprints on the lot come from OpenStreetMap. Irrigated lawn is estimated as lot minus buildings minus an allowance for driveway and walks (8% of the lot, between 400 and 3,000 sq ft). Where no parcel record exists, or the estimate looks wrong, the user outlines the grass on satellite imagery and the geodesic area of that polygon is used, minus any building inside it.

Weekly watering need and schedule

Need for the coming week is the Open-Meteo forecast of reference evapotranspiration times 0.8, minus effective rainfall capped at 0.5 inch per day, converted to gallons over the lawn area. Sessions per week: one when need is under 0.5 inch, two under 1.1 inch, otherwise three, capped by any district limit. Run time per zone is inches per session divided by the head type's precipitation rate and efficiency (fixed spray 1.5 in/hr at 65%, rotor 0.6 at 75%, rotary nozzle 0.4 at 80%, drip 0.5 at 90%). Each of the next seven days is checked against the district's allowed-day scheme, banned hours, season ban, and rain rule, and days with a 60% or higher chance of a quarter inch or more are not recommended.

AI second opinion

The detectors are rules, and rules can be fooled: a pool fill looks like a long irrigation run, a running toilet looks like a small drip system. For the largest and most ambiguous events the site can ask Jev, a decision model from TypeSafe AI, three typed questions: what category is this event (a choice among six), how avoidable is it (a probability), and what priority does it deserve (a score on four levels). The model returns probability distributions, never free text, so the answer can be shown next to the rule-based label and audited. Only the event features (date, time, duration, gallons, peak rate, rain that day) are sent, never the raw file.

Limits