Field note · August 12, 2026
1,146 zeros in tip_usd, and what they mean
14.3% of one column is exactly zero. Whether that is a measurement or an absence changes every aggregate built on it.
tip_usd on ride-hail-trips is zero in 1,146 of 8,000 rows — 14.3% of the column.
Zero in a numeric column almost always means one of two things, and they need different handling. Either the thing was measured and came out zero, or the thing did not happen and zero is standing in for absence. 14.3% of this column is zero, which is far too much to be an accident of measurement.
Averaging across both meanings gives you a number that describes neither group. The mean of tip_usd including zeros is 3.13. Excluding them it is roughly 3.65 — a different number about a different population.
select
count(*) filter (where tip_usd = 0) as zero_rows,
count(*) filter (where tip_usd > 0) as positive_rows,
avg(tip_usd) as mean_all,
avg(tip_usd) filter (where tip_usd > 0) as mean_positive
from ride_hail_trips;The reporting version is usually two numbers rather than one: the rate at which the thing happens, and the size when it does. Those move independently, and a single average hides which one changed. A drop in the combined mean could be fewer events or smaller events, and you cannot tell them apart after the fact.
Same shape as the null problem, except nothing warns you, because zero is a perfectly valid number and every aggregate happily includes it.