Read a sample: 1. The Radar Screen Is Not the Sky
A thunderstorm sits on the western edge of your phone screen. Its rain core is a bright patch of color, the highway ahead looks clear, and a small location marker shows your car moving along the road. At first glance, the picture seems to answer a practical question: Can we keep driving?
It may help you ask a better question, but it cannot answer that one by itself.
The colored patch is not a live photograph of the storm. It is a display built from radar observations, processed and delivered to an application that places them on a map. The storm has continued to move and change while those observations were being collected and displayed. The radar also sampled parts of the atmosphere above the ground, not every stretch of pavement along your route.
Meanwhile, the road may be telling a different story. Rain could be arriving ahead of the displayed core. A gust could be pushing dust across the highway. Water might be collecting in a low spot. A hill could hide the storm from view until you crest it. None of those details is guaranteed to appear on a radar screen in a form you can recognize in time.
This book is about learning to read radar without expecting more from it than it can give. Radar is an extraordinarily useful observing tool. It can help you find precipitation, follow the evolution of a storm, and investigate winds moving toward or away from a radar site. Used alongside forecasts, official warnings, and observations from the road, it can make your understanding richer. Used as a moving shield between you and a thunderstorm, it can encourage dangerous confidence.
The distinction begins with a simple habit: treat every radar image as evidence about the atmosphere, not as the atmosphere itself.
Weather radar sends out pulses of energy and listens for energy returned by objects in the atmosphere. Raindrops, snowflakes, hailstones, insects, and other targets can all influence what comes back. Radar products turn those measurements into displays designed to answer different questions.
The product most beginners recognize is reflectivity. Its colors generally represent the strength of returned energy, often associated with precipitation. A stronger return may suggest heavier precipitation or hail, but a color alone does not identify precisely what is falling at the surface. Different applications can also use different color scales. A vivid red patch may draw your eye, but the legend and product label matter more than the emotional effect of the color.
Another important product is velocity. Rather than showing the strength of the return, velocity estimates motion toward or away from the radar. It can provide clues about storm winds and rotation, but it does not display the full wind field. A wind moving mostly across the radar’s line of sight may be less apparent in that measurement than a wind moving directly toward or away from the radar.
These products are related, but they do not say the same thing. A reflectivity image can help you locate a precipitation core; it cannot, by itself, tell you the wind speed at a particular intersection. A velocity image can suggest a pattern of motion; it cannot, by itself, establish every hazard beneath that pattern. Later chapters will give each product the attention it deserves. For now, the important point is that a radar screen is a selection of measurements, not a complete picture of a storm.
Even an apparently straightforward blank area requires care. It may mean there is little detectable precipitation in the displayed product at the sampled height. It does not necessarily mean the air is calm, the road is dry, the view is unobstructed, or the route is free of danger. Strong winds, lightning, and rapidly changing conditions can affect places outside the most conspicuous precipitation on the screen.
A radar image has an age, even when it has just appeared on your phone. Collecting observations takes time. Processing and transmitting them takes time. Your application may refresh on its own schedule, and a weak connection may leave an older image on the screen without making the delay obvious.
Imagine stopping at a gas station and opening a radar app. The storm appears west of your intended route. You watch the colors for a moment, put the phone away, and continue driving. Several minutes later, the image you remember is already older, and the storm may have moved, grown, weakened, or developed in a direction you did not anticipate.
A timestamp is therefore not a minor technical detail. It tells you something essential about the evidence you are using. Check the time associated with the displayed product, not merely the current time on your device. If an animation is available, look at the times on its frames as well. A smooth loop can make observations seem continuous even though the frames are separated by gaps.
An animation can help reveal recent movement and changes in structure. It is not a promise that the next frame will follow the same path. Storms can change speed or direction, and new areas of precipitation can develop where none were obvious before. Projecting a colored shape forward in your mind may be useful as a question—What if it continues this way?—but it should not become an assurance that other outcomes are impossible.
Different parts of what appears to be one image can also come from observations made…