NEXRAD
NEXRAD or Nexrad (Next-Generation Radar) is a network of 160 high-resolution S-band Doppler weather radars operated by the National Weather Service (NWS), an agency of the National Oceanic and Atmospheric Administration (NOAA) within the United States Department of Commerce, the Federal Aviation Administration (FAA) within the Department of Transportation, and the U.S. Air Force within the Department of Defense. Its technical name is WSR-88D, which stands for Weather Surveillance Radar, 1988, Doppler.
NEXRAD detects precipitation and atmospheric movement or wind. It returns data which when processed can be displayed in a mosaic map which shows patterns of precipitation and its movement. The radar system operates in two basic modes, selectable by the operator – a slow-scanning clear-air mode for analyzing air movements when there is little or no activity in the area, and a precipitation mode, with a faster scan for tracking active weather. NEXRAD has an increased emphasis on automation, including the use of algorithms and automated volume scans.
Contents
Deployment
In the 1970s, the U.S. Department of Commerce, Department of Defense and Department of Transportation found the need to replace the existing national radar network, consisting of WSR-74 and WSR-57 radars not utilizing Doppler technology that were respectively developed in 1974 and 1957, to better serve their operational needs. The Joint Doppler Operational Project (JDOP) was formed in 1976 at the National Severe Storms Laboratory (NSSL) to study the usefulness of using Doppler radar to identify severe and tornadic thunderstorms. Tests over the next three years, conducted by the National Weather Service and the Air Weather Service agency of the U.S. Air Force, found that Doppler radar provided much improved early detection of severe thunderstorms. A working group that included the JDOP published a paper providing the concepts for the development and operation of a national weather radar network. In 1979, the NEXRAD Joint System Program Office (JSPO) was formed to move forward with the development and deployment of the proposed NEXRAD radar network. That year, the NSSL completed a formal report on developing the NEXRAD system.[1][2]
When the proposal was presented to the Reagan administration, options were considered to build the radar systems: either allowing corporate bids to build the systems based on the schematics of the previously developed prototype radar or seek contractors to build their own systems using predetermined specifications. The JSPO group opted to select a contractor to develop and produce the radars that would be used for the national network. Radar systems developed by Raytheon and Unisys were tested during the 1980s, however it took four years to allow the prospective contractors to develop their proprietary models. Unisys was selected as the contractor, and was awarded a full-scale production contract in January 1990.[1][2]
Installation of an operational prototype was completed in the fall of 1990 in Norman, Oklahoma. The first installation of a WSR-88D for operational use in everyday forecasting was in Sterling, Virginia on June 12, 1992. The last system deployed as part of this installation campaign was installed in North Webster, Indiana on August 30, 1997. In 2011, a single new radar was added at Langley Hill, Washington to better cover the Pacific Coast of that area; other radars also filled gaps in coverage at Evansville, Indiana and Ft. Smith, Arkansas following the initial installations.[citation needed] The site locations were strategically chosen to provide the most overlapping coverage between radars in case one failed during a severe weather event. Where possible, they were co-located with NWS Weather Forecast Offices (WFOs) to permit quicker access to maintenance technicians.[3]
The NEXRAD radars incorporated a number of improvements over the radar systems that were previously in use. The new system provided Doppler velocity, improving tornado prediction ability by detecting any rotation present within the storm at different scan angles. It provided improved resolution and sensitivity, allowing operators to see features such as cold fronts, thunderstorm gust fronts, and mesoscale to even storm scale features of thunderstorms that had never been visible on radar. The NEXRAD radars also provided volumetric scans of the atmosphere allowing operators to interrogate the vertical structure of storms and additionally can act as wind profilers in providing detailed wind information for several kilometres above the radar site. The radars also had a much increased range allowing detection of weather features at much greater distances from the radar site.[4]
WSR-88D development, maintenance, and training are coordinated by the NEXRAD Radar Operations Center (ROC) located at the National Weather Center (NWC) in Norman, Oklahoma.[5]
Scan strategies
Unlike its predecessor, the WSR-88D antenna is not directly controllable by the user. Instead, the radar system continually refreshes its three-dimensional database via one of several predetermined scan patterns. Since the system samples the atmosphere in three dimensions, there are many variables that can be changed, depending on the desired output. There are currently nine Volume Coverage Patterns (VCP) available to NWS meteorologists. Each VCP is a predefined set of instructions that control antenna rotation speed, elevation angle, transmitter pulse repetition frequency and pulse width. The radar operator chooses from the VCPs based on the type of weather occurring:
- Clear Air or Light Precipitation: VCP 31 and 32
- Shallow Precipitation: VCP 21
- Convection: VCP 11, 12, 121, 211, 212, and 221[6]
VCP | Scan Time (min) | Elevation scans | Elevation angles (°) | Usage | Special attributes |
---|---|---|---|---|---|
11 | 5 | 14 | 0.5, 1.5, 2.4, 3.4, 4.3, 5.3, 6.2, 7.5, 8.7, 10, 12, 14, 16.7, 19.5 | Convection, especially when close to the radar | Has the best overall volume coverage |
211 | Convection, especially when close to the radar | Improves range-obscured velocity data over VCP 11 | |||
12 | 4.5 | 14 | 0.5, 0.9, 1.3, 1.8, 2.4, 3.1, 4.0, 5.1, 6.4, 8.0, 10.0, 12.5, 15.6, 19.5 | Convection, especially activity at longer ranges | Focuses on lower elevations to better sample the lower levels of storms |
212 | Widespread severe convective events | Improves range-obscured velocity data over VCP 12 | |||
121 | 6 | 9 | 0.5, 1.5, 2.4, 3.4, 4.3, 6.0, 9.9, 14.6, 19.5 | Large number of rotating storms, tropical systems, or when better velocity data is needed | Scans lower cuts multiple times with varying pulse repetition rates to greatly enhance velocity data |
21 | 5 | Shallow precipitation | Rarely used for convection due to sparse elevation data and long completion time | ||
221 | Widespread precipitation with embedded convection (i.e., tropical systems) | Improves range-obscured velocity data over VCP 121 | |||
31 | 10 | 5 | 0.5, 1.5, 2.5, 3.5, 4.5 | Detecting subtle boundaries or wintry precipitation | Long-pulse |
32 | Slow rotation speed allows for increased sensitivity; default clear-air mode, reduces wear on antenna mechanical components | Short-pulse |
Significant advancements in scanning techniques were instituted in the spring of 2014. These dynamic or adaptive scanning techniques include AVSET (Automated Volume Scan Evaluation and Termination) and SAILS (Supplemental Adaptive Intra-Volume Low-Level Scan). Both increase the temporal resolution of scans: (1) AVSET by automatically detecting when precipitation returns drop below a set threshold (typically 20 dBZ) at a certain height and then scanning at no higher tilts and (2) SAILS by rescanning the lowest tilt halfway through a volume scan. Volume scans previously required over four minutes to complete and these techniques cut that time by approximately half that span without the need for hardware upgrades.[7][8]
Enhancements
Super resolution
Deployed from March to August 2008,[9] the Super Resolution upgrade permitted the capability of the radar to produce much higher resolution data. Under legacy resolution, the WSR-88D provides reflectivity data at 1 km (0.62 mi) by 1 degree to Lua error in Module:Convert at line 272: attempt to index local 'cat' (a nil value). range, and velocity data at 0.25 km (0.16 mi) by 1 degree to a range of 230 km (140 mi). Super Resolution provides reflectivity data with a sample size of 0.25 km (0.16 mi) by 0.5 degree, and increase the range of Doppler velocity data to 300 km (190 mi). Initially, the increased resolution is only available in the lower scan elevations. Super resolution makes a compromise of slightly decreased noise reduction for a large gain in resolution.[10]
The improvement in azimuthal resolution increases the range at which tornadic mesoscale rotations can be detected. This allows for faster lead time on warnings and extends the useful range of the radar. The increased resolution (in both azimuth and range) increases the detail of such rotations, giving a more accurate representation of the storm. Along with providing better detail of detected precipitation and other mesoscale features, Super Resolution also provides additional detail to aid in other severe storm analysis. Super Resolution extends the range of velocity data and provides it faster than before, also allowing for faster lead time on potential tornado detection and subsequent warnings.[11]
Dual polarization
WSR-88D sites across the nation are currently being upgraded to polarimetric radar, which adds vertical polarization to the current horizontal radar waves, in order to more accurately discern what is reflecting the signal. This so-called dual polarization allows the radar to distinguish between rain, hail and snow, something the horizontally polarized radars cannot accurately do. Early trials have shown that rain, ice pellets, snow, hail, birds, insects, and ground clutter all have different signatures with dual polarization, which could mark a significant improvement in forecasting winter storms and severe thunderstorms.[12] The deployment of the dual polarization capability (Build 12) to NEXRAD sites began in 2010 and was completed by the summer of 2013. The radar at Vance Air Force Base in Enid, Oklahoma is the first operational WSR-88D to be modified to utilize dual polarization technology; the modified radar went into operation on March 3, 2011.[13]
Coverage gaps
WSR-88D has coverage gaps in many parts of the United States, often for terrain or budgetary reasons. Such notable gaps include many portions of the Rocky Mountains; Pierre, South Dakota; portions of northern Texas; large portions of the Nebraska panhandle; and areas near the borders of the Oklahoma and Texas Panhandles. At least one tornado has gone undetected by WSR-88D as a result of such a coverage gap, in Lovelady, Texas, where an EF1 that struck the town in April 2014 was not detected by radar. As a result of the coverage gap, initial reports of tornadic activity were treated with skepticism by the local National Weather Service forecast office. It is not likely that additional WSR-88Ds will be deployed, as the production line was shut down many years ago, and the National Weather Service faces budgetary concerns.[14][15]
Future enhancements
Phased array
Beyond dual-polarization, the advent of phased array radar will probably be the next major improvement in severe weather detection. Its ability to rapidly scan large areas would give an enormous advantage to radar meteorologists. Any large-scale installation by the NWS is unlikely to occur before 2020. The National Severe Storms Laboratory predicts that a phased array system will eventually replace the current network of WSR-88D radar transmitters.[16]
Applications
Usage
NEXRAD data is used in multiple ways. It is used by National Weather Service meteorologists and (under provisions of U.S. law) is freely available to users outside of the NWS, including researchers, media, and private citizens. The primary goal of NEXRAD data is to aid NWS meteorologists in operational forecasting. The data allows them to accurately track precipitation and anticipate its development and track. More importantly, it allows the meteorologists to track and anticipate severe weather and tornadoes. Combined with ground reports, tornado and severe thunderstorm warnings can be issued to alert the public about dangerous storms. NEXRAD data also provides information about rainfall rate and aids in hydrological forecasting. Data is provided to the public in several different forms, the most basic form being graphics published to the NWS website. Data is also available in two similar, but different, raw formats. Available directly from the NWS is Level III data, consisting of reduced resolution, low-bandwidth base products as well as many derived, post-processed products; Level II data consists of only the base products, but at their original resolution. Because of the higher bandwidth costs, Level II data is not available directly from the NWS. The NWS distributes this data freely to several top-tier universities which in turn distribute the data to private organizations.[17]
Operational locations
State (Abbreviation) |
City or Place Name | ICAO Location Identifier | Coordinates |
---|---|---|---|
PR | San Juan | TJUA | Lua error in package.lua at line 80: module 'strict' not found. |
ME | Loring AFB | KCBW | Lua error in package.lua at line 80: module 'strict' not found. |
ME | Portland | KGYX | Lua error in package.lua at line 80: module 'strict' not found. |
VT | Burlington | KCXX | Lua error in package.lua at line 80: module 'strict' not found. |
MA | Boston | KBOX | Lua error in package.lua at line 80: module 'strict' not found. |
NY | Albany | KENX | Lua error in package.lua at line 80: module 'strict' not found. |
NY | Binghamton | KBGM | Lua error in package.lua at line 80: module 'strict' not found. |
NY | Buffalo | KBUF | Lua error in package.lua at line 80: module 'strict' not found. |
NY | Montague | KTYX | Lua error in package.lua at line 80: module 'strict' not found. |
NY | New York City | KOKX | Lua error in package.lua at line 80: module 'strict' not found. |
DE | Dover AFB | KDOX | Lua error in package.lua at line 80: module 'strict' not found. |
PA | Philadelphia | KDIX | Lua error in package.lua at line 80: module 'strict' not found. |
PA | Pittsburgh | KPBZ | Lua error in package.lua at line 80: module 'strict' not found. |
PA | State College | KCCX | Lua error in package.lua at line 80: module 'strict' not found. |
WV | Charleston | KRLX | Lua error in package.lua at line 80: module 'strict' not found. |
VA | Norfolk/Richmond | KAKQ | Lua error in package.lua at line 80: module 'strict' not found. |
VA | Roanoke | KFCX | Lua error in package.lua at line 80: module 'strict' not found. |
VA | Sterling | KLWX | Lua error in package.lua at line 80: module 'strict' not found. |
NC | Morehead City | KMHX | Lua error in package.lua at line 80: module 'strict' not found. |
NC | Raleigh/Durham | KRAX | Lua error in package.lua at line 80: module 'strict' not found. |
NC | Wilmington | KLTX | Lua error in package.lua at line 80: module 'strict' not found. |
SC | Charleston | KCLX | Lua error in package.lua at line 80: module 'strict' not found. |
SC | Columbia | KCAE | Lua error in package.lua at line 80: module 'strict' not found. |
SC | Greer | KGSP | Lua error in package.lua at line 80: module 'strict' not found. |
GA | Atlanta | KFFC | Lua error in package.lua at line 80: module 'strict' not found. |
GA | Moody AFB | KVAX | Lua error in package.lua at line 80: module 'strict' not found. |
GA | Robins AFB | KJGX | Lua error in package.lua at line 80: module 'strict' not found. |
FL | Eglin AFB | KEVX | Lua error in package.lua at line 80: module 'strict' not found. |
FL | Jacksonville | KJAX | Lua error in package.lua at line 80: module 'strict' not found. |
FL | Key West | KBYX | Lua error in package.lua at line 80: module 'strict' not found. |
FL | Melbourne | KMLB | Lua error in package.lua at line 80: module 'strict' not found. |
FL | Miami | KAMX | Lua error in package.lua at line 80: module 'strict' not found. |
FL | Tallahassee | KTLH | Lua error in package.lua at line 80: module 'strict' not found. |
FL | Tampa | KTBW | Lua error in package.lua at line 80: module 'strict' not found. |
AL | Birmingham | KBMX | Lua error in package.lua at line 80: module 'strict' not found. |
AL | Fort Rucker | KEOX | Lua error in package.lua at line 80: module 'strict' not found. |
AL | Huntsville | KHTX | Lua error in package.lua at line 80: module 'strict' not found. |
AL | Maxwell AFB | KMXX | Lua error in package.lua at line 80: module 'strict' not found. |
AL | Mobile | KMOB | Lua error in package.lua at line 80: module 'strict' not found. |
MS | Brandon/Jackson | KDGX | Lua error in package.lua at line 80: module 'strict' not found. |
MS | Columbus AFB | KGWX | Lua error in package.lua at line 80: module 'strict' not found. |
TN | Knoxville/Tri Cities | KMRX | Lua error in package.lua at line 80: module 'strict' not found. |
TN | Memphis | KNQA | Lua error in package.lua at line 80: module 'strict' not found. |
TN | Nashville | KOHX | Lua error in package.lua at line 80: module 'strict' not found. |
KY | Fort Campbell | KHPX | Lua error in package.lua at line 80: module 'strict' not found. |
KY | Jackson | KJKL | Lua error in package.lua at line 80: module 'strict' not found. |
KY | Louisville | KLVX | Lua error in package.lua at line 80: module 'strict' not found. |
KY | Paducah | KPAH | Lua error in package.lua at line 80: module 'strict' not found. |
OH | Wilmington | KILN | Lua error in package.lua at line 80: module 'strict' not found. |
OH | Cleveland | KCLE | Lua error in package.lua at line 80: module 'strict' not found. |
MI | Detroit/Pontiac | KDTX | Lua error in package.lua at line 80: module 'strict' not found. |
MI | Gaylord | KAPX | Lua error in package.lua at line 80: module 'strict' not found. |
MI | Grand Rapids | KGRR | Lua error in package.lua at line 80: module 'strict' not found. |
MI | Marquette | KMQT | Lua error in package.lua at line 80: module 'strict' not found. |
IN | Evansville | KVWX | Lua error in package.lua at line 80: module 'strict' not found. |
IN | Indianapolis | KIND | Lua error in package.lua at line 80: module 'strict' not found. |
IN | North Webster | KIWX | Lua error in package.lua at line 80: module 'strict' not found. |
IL | Chicago | KLOT | Lua error in package.lua at line 80: module 'strict' not found. |
IL | Lincoln | KILX | Lua error in package.lua at line 80: module 'strict' not found. |
WI | Green Bay | KGRB | Lua error in package.lua at line 80: module 'strict' not found. |
WI | La Crosse | KARX | Lua error in package.lua at line 80: module 'strict' not found. |
WI | Milwaukee | KMKX | Lua error in package.lua at line 80: module 'strict' not found. |
MN | Duluth | KDLH | Lua error in package.lua at line 80: module 'strict' not found. |
MN | Minneapolis/St. Paul | KMPX | Lua error in package.lua at line 80: module 'strict' not found. |
IA | Davenport | KDVN | Lua error in package.lua at line 80: module 'strict' not found. |
IA | Des Moines | KDMX | Lua error in package.lua at line 80: module 'strict' not found. |
MO | Kansas City | KEAX | Lua error in package.lua at line 80: module 'strict' not found. |
MO | Springfield | KSGF | Lua error in package.lua at line 80: module 'strict' not found. |
MO | St. Louis | KLSX | Lua error in package.lua at line 80: module 'strict' not found. |
AR | Fort Smith | KSRX | Lua error in package.lua at line 80: module 'strict' not found. |
AR | Little Rock | KLZK | Lua error in package.lua at line 80: module 'strict' not found. |
LA | Fort Polk | KPOE | Lua error in package.lua at line 80: module 'strict' not found. |
LA | Lake Charles | KLCH | Lua error in package.lua at line 80: module 'strict' not found. |
LA | New Orleans | KLIX | Lua error in package.lua at line 80: module 'strict' not found. |
LA | Shreveport | KSHV | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Amarillo | KAMA | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Austin/San Antonio | KEWX | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Brownsville | KBRO | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Corpus Christi | KCRP | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Dallas/Ft. Worth | KFWS | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Dyess AFB | KDYX | Lua error in package.lua at line 80: module 'strict' not found. |
TX | El Paso | KEPZ | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Fort Hood | KGRK | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Houston/Galveston | KHGX | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Laughlin AFB | KDFX | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Lubbock | KLBB | Lua error in package.lua at line 80: module 'strict' not found. |
TX | Midland/Odessa | KMAF | Lua error in package.lua at line 80: module 'strict' not found. |
TX | San Angelo | KSJT | Lua error in package.lua at line 80: module 'strict' not found. |
OK | Frederick | KFDR | Lua error in package.lua at line 80: module 'strict' not found. |
OK | Oklahoma City | KTLX | Lua error in package.lua at line 80: module 'strict' not found. |
OK | Norman (Testbed) | No Level III Data | Lua error in package.lua at line 80: module 'strict' not found. |
OK | Tulsa | KINX | Lua error in package.lua at line 80: module 'strict' not found. |
OK | Vance AFB | KVNX | Lua error in package.lua at line 80: module 'strict' not found. |
KS | Dodge City | KDDC | Lua error in package.lua at line 80: module 'strict' not found. |
KS | Goodland | KGLD | Lua error in package.lua at line 80: module 'strict' not found. |
KS | Topeka | KTWX | Lua error in package.lua at line 80: module 'strict' not found. |
KS | Wichita | KICT | Lua error in package.lua at line 80: module 'strict' not found. |
NE | Grand Island/Hastings | KUEX | Lua error in package.lua at line 80: module 'strict' not found. |
NE | North Platte | KLNX | Lua error in package.lua at line 80: module 'strict' not found. |
NE | Omaha | KOAX | Lua error in package.lua at line 80: module 'strict' not found. |
SD | Aberdeen | KABR | Lua error in package.lua at line 80: module 'strict' not found. |
SD | Rapid City | KUDX | Lua error in package.lua at line 80: module 'strict' not found. |
SD | Sioux Falls | KFSD | Lua error in package.lua at line 80: module 'strict' not found. |
ND | Bismarck | KBIS | Lua error in package.lua at line 80: module 'strict' not found. |
ND | Grand Forks (Mayville) | KMVX | Lua error in package.lua at line 80: module 'strict' not found. |
ND | Minot AFB | KMBX | Lua error in package.lua at line 80: module 'strict' not found. |
MT | Billings | KBLX | Lua error in package.lua at line 80: module 'strict' not found. |
MT | Glasgow | KGGW | Lua error in package.lua at line 80: module 'strict' not found. |
MT | Great Falls | KTFX | Lua error in package.lua at line 80: module 'strict' not found. |
MT | Missoula | KMSX | Lua error in package.lua at line 80: module 'strict' not found. |
WY | Cheyenne | KCYS | Lua error in package.lua at line 80: module 'strict' not found. |
WY | Riverton | KRIW | Lua error in package.lua at line 80: module 'strict' not found. |
CO | Denver | KFTG | Lua error in package.lua at line 80: module 'strict' not found. |
CO | Grand Junction | KGJX | Lua error in package.lua at line 80: module 'strict' not found. |
CO | Pueblo | KPUX | Lua error in package.lua at line 80: module 'strict' not found. |
NM | Albuquerque | KABX | Lua error in package.lua at line 80: module 'strict' not found. |
NM | Cannon AFB | KFDX | Lua error in package.lua at line 80: module 'strict' not found. |
NM | Holloman AFB | KHDX | Lua error in package.lua at line 80: module 'strict' not found. |
AZ | Flagstaff | KFSX | Lua error in package.lua at line 80: module 'strict' not found. |
AZ | Phoenix | KIWA | Lua error in package.lua at line 80: module 'strict' not found. |
AZ | Tucson | KEMX | Lua error in package.lua at line 80: module 'strict' not found. |
AZ | Yuma | KYUX | Lua error in package.lua at line 80: module 'strict' not found. |
UT | Cedar City | KICX | Lua error in package.lua at line 80: module 'strict' not found. |
UT | Salt Lake City | KMTX | Lua error in package.lua at line 80: module 'strict' not found. |
ID | Boise | KCBX | Lua error in package.lua at line 80: module 'strict' not found. |
ID | Pocatello/Idaho Falls | KSFX | Lua error in package.lua at line 80: module 'strict' not found. |
NV | Elko | KLRX | Lua error in package.lua at line 80: module 'strict' not found. |
NV | Las Vegas | KESX | Lua error in package.lua at line 80: module 'strict' not found. |
NV | Reno | KRGX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | Beale AFB | KBBX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | Edwards AFB | KEYX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | Eureka | KBHX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | Los Angeles | KVTX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | Sacramento | KDAX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | San Diego | KNKX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | San Francisco | KMUX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | San Joaquin Valley | KHNX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | Santa Ana Mountains | KSOX | Lua error in package.lua at line 80: module 'strict' not found. |
CA | Vandenberg AFB | KVBX | Lua error in package.lua at line 80: module 'strict' not found. |
HI | Kauai | PHKI | Lua error in package.lua at line 80: module 'strict' not found. |
HI | Kohala | PHKM | Lua error in package.lua at line 80: module 'strict' not found. |
HI | Molokai | PHMO | Lua error in package.lua at line 80: module 'strict' not found. |
HI | South Shore | PHWA | Lua error in package.lua at line 80: module 'strict' not found. |
OR | Medford | KMAX | Lua error in package.lua at line 80: module 'strict' not found. |
OR | Pendleton | KPDT | Lua error in package.lua at line 80: module 'strict' not found. |
OR | Portland | KRTX | Lua error in package.lua at line 80: module 'strict' not found. |
WA | Langley Hill | KLGX | Lua error in package.lua at line 80: module 'strict' not found. |
WA | Seattle/Tacoma | KATX | Lua error in package.lua at line 80: module 'strict' not found. |
WA | Spokane | KOTX | Lua error in package.lua at line 80: module 'strict' not found. |
AK | Bethel | PABC | Lua error in package.lua at line 80: module 'strict' not found. |
AK | Fairbanks/Pedro Dome | PAPD | Lua error in package.lua at line 80: module 'strict' not found. |
AK | Kenai | PAHG | Lua error in package.lua at line 80: module 'strict' not found. |
AK | King Salmon | PAKC | Lua error in package.lua at line 80: module 'strict' not found. |
AK | Middleton Island | PAIH | Lua error in package.lua at line 80: module 'strict' not found. |
AK | Nome | PAEC | Lua error in package.lua at line 80: module 'strict' not found. |
AK | Sitka/Biorka Island | PACG | Lua error in package.lua at line 80: module 'strict' not found. |
GU | Andersen AFB | PGUA | Lua error in package.lua at line 80: module 'strict' not found. |
NA | Lajes Field, Azores | LPLA | Lua error in package.lua at line 80: module 'strict' not found. |
SK | Kunsan Air Base, South Korea | RKJK | Lua error in package.lua at line 80: module 'strict' not found. |
SK | Camp Humphreys, South Korea | RKSG | Lua error in package.lua at line 80: module 'strict' not found. |
JP | Kadena Air Base, Japan | RODN | Lua error in package.lua at line 80: module 'strict' not found. |
See also
- Canadian weather radar network
- Low level windshear alert system (LLWAS)
- Terminal Doppler Weather Radar (TDWR)
Notes
- ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ NEXRAD sites and coordinates by the National Climatic Data Center
References
- Atlas, David, Radar in Meteorology: Battan Memorial and 40th Anniversary Radar Meteorology Conference, published by the American Meteorological Society, Boston, 1990, 806 pages, ISBN 0-933876-86-6, AMS Code RADMET.
External links
Wikimedia Commons has media related to WSR-88D NEXRAD. |
- Theory of Doppler Weather Radar
- Frequently Asked Questions by NOAA
- Radar Frequently Asked Questions (FAQ) by Weather Underground
- Social & Economic Benefits of NEXRAD from "NOAA Socioeconomics" website initiative
- Real time data
- Research
- RADAR Research and Development by NSSL