The National Lightning Detection Network, NLDN, consists of over 100 remote, ground-based sensing stations located across the United States that instantaneously detect the electromagnetic signals given off when lightning strikes the earth's surface. These remote sensors send the raw data via a satellite-based communications network to the Network Control Center operated by Vaisala Inc. in Tucson, Arizona. Within seconds of a lightning strike, the NCC's central analyzers process information on the location, time, polarity, and communicated to users across the country.

More information:
http://thunderstorm.vaisala.com

Lightning stroke data from the National Lightning Detection Network (NLDN) for the IMPACTS 2023 campaign.

This dataset contains lightning data from the National Lightning Detection Network (NLDN), which consists of 100 remote, ground-based sensing stations located across the United States. These data are available in .tar files grouped by day. These data were recorded within the time period of the DC3 project from 14 May to 30 June 2012. This dataset is password protected.

This data set contains the cloud-to-ground and in-cloud lightning data from the National Lightning Detection Network (NLDN).

The U.S. National Lightning Detection Network is a commercial lightning detection network operated by Vaisala. A network of over 100 antennae are connected to a central processor that records the time, polarity, signal strength, and number of strokes of each cloud-to-ground lightning flash detected over the United States. This dataset consists of a subset of data for the period of the Midlatitude Continental Convective Clouds Experiment (MC3E).

Lightning stroke data from the National Lightning Detection Network (NLDN) for particular periods during the IMPACTS_2022 campaign. Data are available for 14-15, 17-20, and 28-31 January as well as 4-5, 12-13, 17-20, and 24-26 February 2022.

The data consists of cloud-to-ground lightning strikes recorded by Vaisala's National Lightning Detection Network (NLDN) and aggregated into 0.1° latitude by 0.1° longitude tiles by the National Centers for Environmental Information. This means that all daily strikes within each 0.1° x 0.1° area are summed and assigned to the geographic coordinates representing the center of that area.

It's important to note that because the length of a degree of latitude decreases as you move away from the equator, the area covered by each tile becomes smaller the farther north you go. For instance, tiles at 50°N measure roughly 7 km by 11 km, while those at 20°N are about 10 km by 11 km—making the southern tiles nearly 43% larger in area.

For more information, you can see the https://ghrc.nsstc.nasa.gov/uso/ds_docs/nldn/gai_dataset.html#

Lightning stroke data from the National Lightning Detection Network (NLDN) for particular periods during the IMPACTS_2020 campaign. Data are available for 11-13, 17-19, 24-26, and 31 January as well as 1-8, 12-14, 18-19, and 24-28 February 2020.

Last Revised: February 2016

Map Information

This nowCOAST™ time-enabled map service provides maps of lightning strike density data from the NOAA/National Weather Service/NCEP's Ocean Prediction Center (OPC) which emulate (simulate) data from the future NOAA GOES-R Global Lightning Mapper (GLM). The purpose of this product is to provide mariners and others with enhanced "awareness of developing and transitory thunderstorm activity, to give users the ability to determine whether a cloud system is producing lightning and if that activity is increasing or decreasing..." Lightning Strike Density, as opposed to display of individual strikes, highlights the location of lightning cores and trends of increasing and decreasing activity. The maps depict the density of lightning strikes during a 15 minute time period at an 8 km x 8 km spatial resolution. The lightning strike density maps cover the geographic area from 25 degrees South to 80 degrees North latitude and from 110 degrees East to 0 degrees West longitude. The map units are number of strikes per square km per minute multiplied by a scaling factor of 10^3. The strike density is color coded using a color scheme which allows the data to be easily seen when overlaid on GOES imagery and to distinguish areas of low and high density values. The maps are updated on nowCOAST™ approximately every 15 minutes. The latest data depicted on the maps are approximately 12 minutes old (or older). Given the spatial resolution and latency of the data, the data should NOT be used to activite your lightning safety plans. Always follow the safety rule: when you first hear thunder or see lightning in your area, activate your emergency plan. If outdoors, immediately seek shelter in a substantial building or a fully enclosed metal vehicle such as a car, truck or van. Do not resume activities until 30 minutes after the last observed lightning or thunder. For more detailed information about layer update frequency and timing, please reference the
nowCOAST™ Dataset Update Schedule.

Background Information

The source for the data is OPC's gridded lightning strike density data on an 8x8 km grid. The gridded data emulate the spatial resolution of the future Global Lightning Mapper (GLM) instrument to be flown on the NOAA GOES-R series of geostationary satellites, with the first satellite scheduled for launch in late 2016.

The gridded data is based on data from Vaisala's ground based U.S. National Lightning Detection Network (NLDN) and its global lightning detection network referred to as the Global Lightning Dataset (GLD360). These networks are capable of detecting cloud-to-ground strikes, cloud-to-ground flash information and survey level cloud lightning information. According to the National Lightning Safety Institute, NLDN uses radio frequency detectors in the spectrum 1.0 kHz through 400 kHz to measure energy discharges from lightning as well as approximate distance and direction. According to Vaisala, the GLD360 network is capable of a detection efficiency greater than 70% over most of the Northern Hemisphere with a median location accuracy of 5 km or better. OPC's gridded data are coarser than the original source data from Vaisala's networks. The 15-minute gridded source data are updated at OPC every 15 minutes at 10 minutes past the valid time.

The lightning strike density product from NWS/NCEP/OPC is considered a derived product or Level 5 product ("NOAA-generated products using lightning data as input but not displaying the contractor transmitted/provided lightning data") and is appropriate for public distribution.

Time Information

This map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.

In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.

This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.

This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.

When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.

Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:

  Issue a returnUpdates=true request (ArcGIS REST protocol only)
  for an individual layer or for the service itself, which will return
  the current start and end times of available data, in epoch time format
  (milliseconds since 00:00 January 1, 1970). To see an example, click on
  the "Return Updates" link at the bottom of the REST Service page under
  "Supported Operations". Refer to the
  ArcGIS REST API Map Service Documentation
  for more information.


  Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against
  the proper layer corresponding with the target dataset. For raster
  data, this would be the "Image Footprints with Time Attributes" layer
  in the same group as the target "Image" layer being displayed. For
  vector (point, line, or polygon) data, the target layer can be queried
  directly. In either case, the attributes returned for the matching
  raster(s) or vector feature(s) will include the following:


      validtime: Valid timestamp.


      starttime: Display start time.


      endtime: Display end time.


      reftime: Reference time (sometimes referred to as
      issuance time, cycle time, or initialization time).


      projmins: Number of minutes from reference time to valid
      time.


      desigreftime: Designated reference time; used as a
      common reference time for all items when individual reference
      times do not match.


      desigprojmins: Number of minutes from designated
      reference time to valid time.




  Query the nowCOAST™ LayerInfo web service, which has been created to
  provide additional information about each data layer in a service,
  including a list of all available "time stops" (i.e. "valid times"),
  individual timestamps, or the valid time of a layer's latest available
  data (i.e. "Product Time"). For more information about the LayerInfo
  web service, including examples of various types of requests, refer to
  the 
  nowCOAST™ LayerInfo Help Documentation

References

Kithil, 2015: Overview of Lightning Detection Equipment, National
Lightning Safety Institute, Louisville, CO. (Available from
http://www.lightningsafety.com/nsli_ihm/detectors.html).


NASA and NOAA, 2014: Geostationary Lightning Mapper (GLM). (Available at
http://www.goes-r.gov/spacesegment/glm.html).


NWS, 2013: Lightning Strike Density Product Description Document.
NOAA/NWS/NCEP/Ocean Prediction Center, College Park, MD (Available at
http://www.opc.ncep.noaa.gov/lightning/lightning_pdd.php
and http://products.weather.gov/PDD/Experimental%20Lightning%20Strike%20Density%20Product%2020130913.pdf).


NOAA Knows Lightning. NWS, Silver Spring, MD (Available at
http://www.lightningsafety.noaa.gov/resources/lightning3_050714.pdf).


Siebers, A., 2013: Soliciting Comments until June 3, 2014 on an
Experimental Lightning Strike Density product (Offshore Waters). Public
Information Notice, NOAA/NWS Headquarters, Washington, DC (Available at
http://www.nws.noaa.gov/om/notification/pns13lightning_strike_density.htm).

All the files can be opened in Matlab or Python using scipy.io.loadmat. Tower_info.mat contains information on 1451 towers selected in this study. After_upgrade.mat (before the 2013 upgrade) and before_upgrade.mat (after the 2013 upgrade) give the median location error, median location error in EW and median location in NS for each tower with identifed area with elevated event density .

The NASA Marshall Space Flight Center Lightning Nitrogen Oxides Model (LNOM) combines detailed, flash-specific measurements of lightning with both theoretical and empirical laboratory results to obtain estimates of lightning NOx production. Each LNOM dataset is based on measurements from a specific regional VHF Lightning Mapping Array (LMA), and on ground flash location, peak current, and stroke multiplicity data from the National Lightning Detection Network (NLDN). Both the LMA and NLDN data are used to determine the flash type (ground or cloud) of each flash occurring within an analysis cylinder. The LNOM analyzes the LMA sources to estimate the total channel length of each flash. It also produces the Segment Altitude Distribution (SAD) product by dicing up the lightning channel into 10-m segments, and then tallies those segments as a function of altitude. From all of the 10-m segments, the LNOM computes the vertical lightning NOx profile inside the analysis cylinder and the total NOx produced by each flash. A summation of the NOx profiles contributed to the analysis cylinder by each flash gives the final lightning NOx profile product for the analysis period studied (typically a 1 month profile). The LNOM NOx profiles include NOx from several non-return stroke lightning NOx production mechanisms. Users of LNOM data typically include regional air quality and global chemistry/climate modelers who need to better-parameterize lightning NOx sources. Rather than assigning an unrealistic fixed amount of NOx to ground and cloud flashes, the modeler can employ LNOM data to assign realistic (and statistical) NOx profiles to each flash.

This password protected dataset contains the Vaisala National Lightning Detection Network (NLDN) data for the region from 28-49 N and 75-103W during the PLOWS 2009-2010 field season (November 2009 to 10 March 2010). These data contain NLDN lightning stroke data with the following parameters: date, time, latitude, longitude, polarity and peak current. This dataset was made available from Vaisala, Inc. free of charge to PLOWS investigators ONLY and all users are required to abide by the Vaisala NLDN data policy to researchers: 1) Lightning data supplied by Vaisala may not be used for direct comparisons with other lightning detection networks, unless approved by the Development Center for Meteorology. This is to ensure proper lightning data interpretation, proper analysis techniques and the appropriateness of the lightning dataset to be used in comparisons. 2) Prior to submission of any publication employing data provided under this policy, Vaisala must be given the opportunity to look over elements of the manuscript related to Vaisala data for technical accuracy. Vaisala will also be open to assisting the authors by providing additional technical details if so desired by both Vaisala and the authors. Vaisala must be acknowledged as the source of the information and data. 3) There can be no proprietary or commercial restrictions on the research results, and the investigator(s) must be directly associated with an academic or research organization. 4) Archival of the data is allowed, but the data will not be shared with or sold to another party without Vaisala's expressed permission. Before access can be granted, the user must fill out and sign the Vaisala Lightning Data Research Policy to signify their agreement with these terms. The agreement is available online: http://www.eol.ucar.edu/projects/plows/documents/Vaisala_Lightning_Data_Research_Policy.pdf When completed and signed the form should be sent to: Steve Williams NCAR/EOL P.O. Box 3000 Boulder, CO 80307...

LULC files possess the land use land classification data used in this project. Files labeled "SH" and "LH" are sensible and latent heat data respectively. Lastly, NLDN files are the lightning data from the national lightning detection network/NOAA NCEI.

This password protected dataset contains the National Lightning Detection Network (NLDN) data for a 100km radius of Mt. Lemmon during the CuPIDO project period (July-August 2006). These data contain NLDN cloud-to-ground strokes and NLDN LF cloud event data with the following parameters: date, time, latitude, longitude, polarity and peak current, lightning event type, chi square value, and length of the semi-major axis of the error ellipse. This dataset was made available from Vaisala, Inc. free of charge to CuPIDO investigators ONLY and all users are required to abide by the Vaisala NLDN data policy to researchers: (1) These data may not be sold or shared with another party outside CuPIDO; (2) These data may not be used for direct comparisons with other lightning detection networks without approval of Vaisala, Inc.; 3) Prior to submission of any publication using these data, Vaisala, Inc. must be given the opportunity to review elements of the manuscript related to Vaisala, Inc. for technical accuracy; (4) Vaisala, Inc. must be acknowledged as the source of the Information and data; and (5) There can be no proprietary or commercial restrictions on the research results and all investigator(s) must be directly associated with an academic or research organization. Any questions on this data policy should be addressed directly to the Vaisala, Inc. Point of contact. Please contact Steve Williams (NCAR/EOL) via e-mail (sfw at ucar dot edu) with your acceptance of the above Vaisala, Inc. NLDN data policy to obtain access to these data.

• Update Frequency: Weekly

Data from this dataset can be downloaded/accessed through this dataset page and Kaggle's API.

Context

Severe weather is defined as a destructive storm or weather. It is usually applied to local, intense, often damaging storms such as thunderstorms, hail storms, and tornadoes, but it can also describe more widespread events such as tropical systems, blizzards, nor'easters, and derechos.

The Severe Weather Data Inventory (SWDI) is an integrated database of severe weather records for the United States. The records in SWDI come from a variety of sources in the NCDC archive. SWDI provides the ability to search through all of these data to find records covering a particular time period and geographic region, and to download the results of your search in a variety of formats. The formats currently supported are Shapefile (for GIS), KMZ (for Google Earth), CSV (comma-separated), and XML.

Content

The current data layers in SWDI are:
- Filtered Storm Cells (Max Reflectivity >= 45 dBZ) from NEXRAD (Level-III Storm Structure Product)
- All Storm Cells from NEXRAD (Level-III Storm Structure Product)
- Filtered Hail Signatures (Max Size > 0 and Probability = 100%) from NEXRAD (Level-III Hail Product)
- All Hail Signatures from NEXRAD (Level-III Hail Product)
- Mesocyclone Signatures from NEXRAD (Level-III Meso Product)
- Digital Mesocyclone Detection Algorithm from NEXRAD (Level-III MDA Product)
- Tornado Signatures from NEXRAD (Level-III TVS Product)
- Preliminary Local Storm Reports from the NOAA National Weather Service
- Lightning Strikes from Vaisala NLDN

Disclaimer:
SWDI provides a uniform way to access data from a variety of sources, but it does not provide any additional quality control beyond the processing which took place when the data were archived. The data sources in SWDI will not provide complete severe weather coverage of a geographic region or time period, due to a number of factors (eg, reports for a location or time period not provided to NOAA). The absence of SWDI data for a particular location and time should not be interpreted as an indication that no severe weather occurred at that time and location. Furthermore, much of the data in SWDI is automatically derived from radar data and represents probable conditions for an event, rather than a confirmed occurrence.

Acknowledgements

Dataset Source: NOAA. This dataset is publicly available for anyone to use under the following terms provided by the Dataset Source — http://www.data.gov/privacy-policy#data_policy — and is provided "AS IS" without any warranty, express or implied, from Google. Google disclaims all liability for any damages, direct or indirect, resulting from the use of the dataset.

Cover photo by NASA on Unsplash
Unsplash Images are distributed under a unique Unsplash License.

The Severe Weather Data Inventory (SWDI) is an integrated database of severe weather records for the United States. SWDI enables a user to search through a variety of source data sets in the NCDC (now NCEI) archive in order to find records covering a particular time period and geographic region, and then to download the results of the search in a variety of formats. The formats currently supported are Shapefile (for GIS), KMZ (for Google Earth), CSV (comma-separated), and XML. The current data layers in SWDI are: Storm Cells from NEXRAD (Level-III Storm Structure Product); Hail Signatures from NEXRAD (Level-III Hail Product); Mesocyclone Signatures from NEXRAD (Level-III Meso Product); Digital Mesocyclone Detection Algorithm from NEXRAD (Level-III MDA Product); Tornado Signature from NEXRAD (Level-III TVS Product); Preliminary Local Storm Reports from the NOAA National Weather Service; Lightning Strikes from Vaisala NLDN.