Reading California Doppler Radar Is Not As Simple As You Think
Doppler radar stations across California form a network that covers most of the state, but the coverage is far from uniform. If you're trying to track storms along the central coast or read what's happening in the southern desert valleys, you already know the echoes can vanish or give you contradictory data. I spent years watching raw radar returns and learning which stations to trust and which ones to ignore depending on where the weather was moving. The NEXRAD system uses S-band wavelength, which is 10 centimeters. That wavelength choice matters because it determines how the radar interacts with precipitation. Larger drops reflect more energy back to the antenna, which is why you get stronger returns from heavy rain than from light drizzle. But there is a threshold. Very large hail or heavy rain can saturate the signal, and the radar understates the intensity instead of showing you the real picture. I learned this the hard way during a storm in the mountains east of Fresno where the displays showed only moderate rain while actual conditions were producing flash flooding. The basic physics behind Doppler radar involves sending out electromagnetic pulses and measuring two things from the returned signal: reflectivity and velocity. Reflectivity tells you how much precipitation is in the air. Velocity tells you whether the targets are moving toward or away from the radar site. This velocity data is what makes the system actually useful for detecting rotation inside thunderstorms. Without it, you are just watching rain happen. With it, you can spot mesocyclones before they produce tornadoes.
California has roughly twenty NEXRAD sites covering the state and parts of the surrounding region. The primary sites include San Francisco, San Jose, Sacramento, Reno, Las Vegas, Los Angeles, and San Diego. When a storm moves through, multiple radars can see it simultaneously. That should sound like an advantage, and it is, up to a point. The problem is that each radar sits at a different angle and distance from the same weather system. What one site interprets as a rotating updraft, another might read as wind shear from a different layer. Cross-referencing multiple sites takes practice.
How The Data Actually Gets To You
Radar products come through a few standard channels. The most accessible is probably the mobile app approach used by the major weather services. These pull data from the same WSR-88D network but often add compression and display tricks that can obscure real details. If you want the raw product, the National Weather Service archives are available directly, though the interface is not exactly user-friendly. Base reflectivity is the fundamental product. It shows precipitation intensity at a given altitude slice. Base velocity shows wind movement. The combination of these two, displayed side by side, is where most of the practical analysis happens. Beyond those basics, there are derived products like spectrum width and differential reflectivity, but those require a bit more background to use effectively. One thing most people miss about base reflectivity is that the radar beam spreads out as it travels higher in altitude. At twenty miles away, the beam is maybe a quarter mile wide. At sixty miles out, it is closer to a mile across. This means distant echoes are less precise than nearby ones. A storm fifteen miles from the site will look sharp and detailed. A storm forty miles out will look smeared. When I first started reading radar seriously, I kept misjudging the size of systems because I forgot about beam divergence. Now I always check the range before making any call about storm boundaries.
Get the Full Details
California-Specific Complications
Mountainous terrain creates shadow zones in the radar coverage. The Sierra Nevada range blocks signals from stations to the west. If you are trying to monitor weather in the high valley areas east of the crest, the nearest radar might be giving you incomplete data. Los Angeles basin stations sometimes struggle with low-altitude storms because the urban clutter gets filtered out by the processing algorithms. I spent an entire afternoon chasing what I thought was a developing line of storms near the Antelope Valley, only to realize the echoes were ground clutter bouncing off radio towers. The Pacific marine layer is another feature that causes regular headaches. Stratiform clouds like fog and stratus don't produce strong enough reflectivity to show up clearly on base velocity or even base reflectivity in many cases. You will see hints of it, but it can be easy to overlook. During my time tracking the May gray and June gloom cycles along the coast, I had to train myself to watch for weak, widespread returns that didn't follow the normal convective patterns. These features move slowly and don't produce the sharp velocity signatures that storms do. They are easy to write off as noise if you aren't paying attention. Atmospheric ducting happens more often in California than in most other states because of the temperature inversions that form over the coastal waters. These inversions can cause the radar beam to bend downward and pick up non-meteorological echoes from surfaces that should be below the horizon. I encountered this regularly at the San Diego site during summer months. The velocity displays would show apparent wind patterns that made no sense for the actual weather. Checking the elevation angles and comparing across nearby sites helped me filter out the ducting artifacts.
Practical Ways To Use This Data
If you are tracking severe weather, start with the velocity couplets. A couplet is a area where inbound winds sit right next to outbound winds. That pattern inside a storm cloud is the signature of rotation. The color scale on the velocity display runs from green through cyan to blue on the inbound side and through yellow to red on the outbound side. When you see that tight transition from blue to red across just a few grid cells, that is what you focus on. Ignore the reflectivity for a moment. The rotation might not show up in the intensity data until it is too late. For general forecasting, base reflectivity combined with animated loops gives you a decent picture of where precipitation is heading. Most apps show three or five minute loops. Watch the direction and speed of the echoes. If a storm is moving at ten miles per hour, it will be somewhere entirely different in an hour. If it is nearly stationary, you should plan accordingly. Moving systems are easier to predict. Stationary systems are where people get surprised. There is no free tool that gives you perfect real-time access to the raw WSR-88D data in California. The government provides the data through the National Centers for Environmental Information, and you can download individual volume scans, but the files are large and the format is technical. The NWS has a public radar viewer that covers most of what people need. For more detailed work, the Iowa Environmental Mesonet hosts archived NEXRAD data that can be pulled with some effort.
What The Data Won't Tell You
Radar is a snapshot of precipitation in the sky right now, or in the recent past if you are looking at a loop. It does not tell you what is happening on the ground if the precipitation evaporates before it reaches the surface. That virga issue is common in southern California. The radar will show heavy rain returning from a thunderstorm, but by the time it crosses into the desert floor, it is just dry air. I learned that lesson during a monsoon season when the radar looked amazing and the ground stayed completely dry for miles around. Light rain and drizzle are another blind spot. The S-band wavelength requires a certain minimum drop size and concentration to generate a readable return. Drizzle often falls below that threshold. If you are expecting persistent light rain and the radar shows nothing, it might actually be coming down. Don't assume the radar is wrong just because it isn't showing what you expect. Sometimes it is just not sensitive enough for your particular situation. The biggest limitation, honestly, is that radar only covers the sky above it. Below the beam, especially at long ranges, there is a gap. The Earth curves away from the radar line of sight. This is why mountain communities sometimes find out about heavy snow only after it is already on the ground. The beam has passed overhead by then. Checking the elevation angle of the current scan can help you understand how much ground coverage you are actually getting at any given time.
