Why Your Weather App's Rain Total Doesn't Match Your Rain Gauge

Your weather app says a tenth of an inch fell last night. The gauge by your back fence is holding a full inch. Neither one is broken, and the gap between them has a straightforward explanation.

A weather app does not measure the rain at your house, and it does not calculate the number on the screen. It displays an estimate that a weather service built from radar and forecast models, then tuned toward your location using rainfall records from real ground stations nearby. None of that machinery can see where a single storm cell emptied over your street. Your gauge can.

The app’s number is an estimate. Your gauge is a measurement.

The app on your phone has no rain sensor in your yard, and it works out no rainfall of its own. The work happens upstream, at a weather service: the operation that runs the radar and the forecast models, or that buys the raw data from whoever does. The National Oceanic and Atmospheric Administration and its National Weather Service run that radar network and those models across the United States. A weather service reads the data, produces a rainfall number for your location, and then your app shows you the result.

A rain gauge actually catches the water that falls on the one spot where it stands, so as long as you placed it correctly, it’s an accurate measurement for that location. The app’s number is only an estimate for your location, assembled miles away from instruments that never touched your property.

The reasons the estimate and the gauge diverge start with the radar.

Radar reads a beam high above the ground

Weather radar never sees the rain landing in your yard. A radar station sends its beam out nearly level with the horizon, but the Earth curves away beneath it, so the farther the beam travels, the higher above the ground it ends up. Close to the station it travels low, through the air where rain is actually falling; farther out it passes above the weather instead of through it.

By about 60 miles from the station, the beam is roughly a kilometer up, around three-quarters of a mile. By 120 miles it sits near three kilometers up, high enough to miss shallow or low storms completely. The National Weather Service names beam overshoot the most common reason radar underestimates rainfall, and it worsens the farther you are from the radar.

National maps of low-level radar coverage show wide gaps across the rural United States, the mountain West most of all, where the nearest radar can sit a hundred miles or more away (Maddox et al., 2002). So if you live out in one of those gaps, or the rain was shallow and light, the beam catches only part of it or misses it entirely, and the total the app shows lands below what your gauge caught. The effect is stronger in the cool season, when rain clouds sit lower and more of the rain falls beneath the beam.

Even when the beam passes straight through the rain, it does not measure how much fell. It reads what bounces back.

Radar estimates the amount from an echo

What returns to the radar station is an echo, and its strength depends on the size and number of the raindrops it struck, not on the inches of water reaching the ground. To turn that echo into a rainfall amount, the weather service runs it through a formula that assumes a typical mix of drop sizes. Of course, no real storm perfectly matches that typical mix. A fine drizzle of many small drops and a hard burst of fewer large drops can send back nearly the same echo and still leave very different amounts in your gauge.

The real mix of drop sizes shifts from storm to storm, and over time during a single storm, so no one formula is right everywhere. That conversion has a standard name, the Z–R relationship, after the echo strength (Z) and the rainfall rate (R) it is meant to predict. As researchers writing in Weather and Forecasting found, “there is no unique Z–R relationship that can satisfy all meteorological phenomena” (Cunha et al., 2013). So the radar estimate runs high in some conditions and low in others.

Other distortions pile on top of that: melting snow aloft can return an oversized echo, heavy rain nearer the station weakens the signal reaching what lies beyond it, and hills can block the beam outright.

That estimate is only one input to the forecast models that build the number your app finally shows.

The estimate is tuned to your area, not your yard

The number your app shows for an hour of rain combines two things: the forecast model’s grid and live observations, including the same radar from the last two sections and the ground stations nearest you. If radar catches a heavy cell over your area, your number rises; if the closest gauges stayed dry, it falls.

Your exact coordinates still get their own value, and reaching it takes interpolation at a minimum: the service estimates the number at your point by weighting the values around it. Interpolation moves the number toward your spot using only the grid values it already has, and it tends to smooth the sharp peaks and wet the dry gaps (Accadia et al., 2003). The service also corrects for bias, a model’s habit of running persistently wet or dry in one place, by comparing years of its forecasts against what nearby stations actually recorded and shifting the number to remove the known error. Meteorologists call that step Model Output Statistics (Glahn et al., 2009).

The national radar mosaic produces rainfall maps on a grid about a kilometer across (MRMS), and the beam that fills them is roughly that wide by the time it reaches you, a kilometer or more overhead. The gauges anchoring the estimate can sit miles away in different rain. A four-inch rain gauge catches water through an opening about the size of a coffee can, roughly 81 square centimeters. Combine and correct those inputs and you get a good value for the area around you. The finest detail any of them carries is about a kilometer wide, and your yard is a few square feet inside that.

For broad, steady rain that falls evenly for miles, that is plenty, and the estimate agrees with your gauge to within a few hundredths of an inch. The gap opens with scattered summer storms, when one cell drops an inch on a single street and leaves the next block dry. A radar pixel a kilometer wide and a mile up cannot tell which street caught the core, and interpolation can only blend the numbers already on the grid.

Sometimes the rain never reaches the ground

On a dry day, rain can fall from a cloud and evaporate in the warm air below before it reaches the ground, trailing the faint gray streaks you sometimes see hanging beneath a cloud. Meteorologists call it virga. It is common in dry climates and at the leading edge of a storm, before the air near the ground has had time to moisten.

The radar reads the rain up in the cloud and counts it; up there, it is real rain. Your gauge stays empty, because none of it reached the ground. The app can then post a tenth of an inch on a day your gauge never moves, because the radar saw real rain up high that never made it down.

Every reason so far has come down to where the rain fell. The last one is different: the number you saw can still change after the storm ends.

The number isn’t final the moment the storm ends

While rain is falling, and in the first hours after it stops, the number in your app is still an estimate: the fast radar reading blended with the model, the same machinery from the last few sections. The measured total comes later. Observers read their gauges, automated stations report in, and the service folds those ground readings into the radar to settle on a corrected total.

That settling takes time. A first corrected total can take hours, and the carefully gauge-checked version can land a day or more after the storm. So if you held your gauge up against the app the morning after, you may have been comparing your final reading to the app’s draft.

Most weather apps make this worse by never going back. They show whatever number was current when you looked and do not swap in the revised total when it publishes, so an early estimate that ran low stays low in your memory long after the official record has corrected itself.

This gap is only about timing. Check the app again a few days on, and its corrected total has usually moved closer to what your gauge caught. It will not match exactly. Even the final gauge-corrected totals differ from real gauges by roughly a third of an inch on average, across more than 22,000 comparisons (Cocks et al., 2017), for the spatial reasons already covered.

Those are the reasons the two numbers come apart. The forecasting behind the estimate, meanwhile, keeps improving year over year.

The forecast keeps getting better. Your gauge still wins.

Weather prediction has improved steadily for half a century. The broad measure is forecast lead time, and it has gained roughly one extra day of useful forecast per decade, the steady advance forecasters call the quiet revolution (Bauer, Thorpe & Brunet, 2015). Rainfall has shared in it: the Weather Prediction Center’s skill at forecasting where an inch of rain will fall has roughly doubled since the 1960s, most of the gain coming after 1995 as Doppler radar, satellite data, and high-resolution models came online (Novak et al., 2014).

NOAA runs the radar network and the forecast models on an annual budget in the billions, on a pair of supercomputers each running about fifteen quadrillion calculations a second; Europe’s ECMWF and other national agencies run their own. The United States is folding its separate models into a single modern forecasting system, the radar fleet has been upgraded to sharpen its rain estimates, and artificial-intelligence forecast models from Google, Huawei, and ECMWF now run alongside the physics-based ones.

All of that sharpens the same things: whether it will rain, how much will fall across a region, and how many days ahead the system can see it coming. None of it can drop a single storm cell onto one street address, because rainfall at a single point is the tail end of a chaotic chain, sensitive to conditions too small and too fleeting for any model to resolve at the resolutions they run today.

A correctly placed gauge measures what fell on your ground; the forecast, however good, only estimates it. So the practical habit is to treat the app’s number as the forecast for your area and the gauge as your record of what actually landed.

The gauge earns that only when it is placed and read correctly, which is where the practical steps begin.

What you can do about the mismatch

Three habits close most of the gap between the app and your gauge: a well-placed gauge, a neighbor’s station to check against, and a season-long record of what your gauge caught.

A decent gauge is cheap, and where you put it matters more than what you paid. Set it under an eave, against a fence, or close to the house, and it catches splash, wind eddies, and runoff that have nothing to do with what fell from the sky. Put it in the open, away from buildings and trees, at a height that clears ground splash. The national CoCoRaHS network of volunteer observers, whose daily readings the National Weather Service relies on, standardizes on one four-inch gauge and strict siting rules for exactly this reason. How to choose a gauge and where to site it is covered in our guide to the best rain gauges.

A pricier gauge is not automatically a better one. Home weather stations that estimate rain with a tipping or vibration sensor routinely read low against a plain manual gauge beside them. Tempest owners say so in the company’s community forums. One wrote that “last night the Tempest reports we got .38”, we actually got .87”.” Another, comparing a single storm, logged “2.3” in my old plastic tube gauge and 1.59” on the Tempest.” A simple tube, placed and read properly, is hard to beat.

Before spending anything, you can get a second opinion from a neighbor’s gauge. The Weather Underground network of personal weather stations maps thousands of backyard setups, and looking up the nearest one shows what actually fell a street or two over. As one regular on a lawn-care forum put it, “get on weather underground and find a neighbor with a PWS that measures rainfall and see how much they have gauged.” The nearest station can still be a mile off, in rain that fell differently than yours.

A single gauge reading tells you about today. A running record, kept over weeks, tells you whether the season is wet or dry and saves you from second-guessing the two numbers every morning. A few rain-tracking apps are built around this: you log what your own gauge caught, the app treats that as the day’s official figure, and it keeps the weather-service estimate alongside for the days you miss. Rain Tally is one such virtual rain gauge. Which apps do this well, and how they compare, is in our roundup of apps for tracking rainfall totals.

Common questions

Why is my weather app’s rain total different from my rain gauge?

Your weather app does not measure rain at your address. It shows an estimate a weather service builds from radar and forecast models, tuned toward your location. Radar reads a beam high overhead and infers the amount from the echo, and scattered storms vary street to street, so the estimate cannot land exactly on your yard. Your gauge measures the water that actually fell on one spot.

Is my rain gauge or my weather app more accurate?

For your own ground, a correctly placed gauge is more accurate, because it measures the water that fell at that exact point. The app’s estimate is strongest for broad, steady rain close to a radar, and weakest in scattered storms, far from the nearest radar, or when rain evaporates before it reaches the ground. Volunteer networks like CoCoRaHS treat the manual gauge as ground truth for the same reason.

Why did my rain total change after the storm was over?

The number during and just after a storm is a fast estimate from radar and the forecast models. The official total is recalculated afterward, as ground-station readings come in and the figure is gauge-corrected, which takes hours to days. Even that corrected total is an area estimate, not your gauge; the best gauge-corrected products still miss real gauges by roughly a third of an inch on average.

Does a home weather station fix the problem?

Not reliably. Stations that estimate rain with a tipping or vibration sensor can read well below a plain manual gauge sitting beside them, as Tempest owners regularly report. A station adds wind, temperature, and convenience, but for rainfall amount a correctly placed manual gauge stays the reference.

Where should I put a rain gauge for an accurate reading?

Put it in the open, away from buildings, fences, and overhanging trees, at a height that clears ground splash, so wind and obstructions do not distort the catch. Poor placement is the most common reason a gauge reads wrong. Our guide to the best rain gauges covers selection and placement in detail.

Are weather forecasts getting more accurate, and will a better app ever match my gauge?

Forecasting keeps improving, by about a day of useful lead time per decade, with rainfall-forecast skill roughly doubled since the 1960s. Those gains tighten the outlook for your region. The fix is not a better app or a more accurate forecast. If no weather service can measure the rain on your own patch of ground, then what you need is a good gauge in the right spot and a record that keeps what it caught.