Approved Vendor
Archive Lightning Data
Overview
Real-time lightning data generally has a latency (from detection to user display) of less than 1 minute. Near real-time is considered greater than 1 minute latency. These types of data are generally used for operational purposes such as situational awareness, alerting, immediate causal analysis, rapid deployment, personnel and equipment safety, and tactical planning.
In contrast, archived or historical lightning data is any data that is older than 24 hours from time of detection. Historical lightning data of this nature is very valuable for forensic analysis, after-the-fact fault analysis, longer-term logistical and operational planning, claims resolutions, research, statistical analysis, and integration with a variety of market-specific information.
Formats
Archived USPLN lightning data can be obtained in a variety of ways and formats. Data is available for large or small areas, from 2004 to current day. NAPLN data outside of the continental US and GLN data have been archived since late 2008. Options for archival data include:
- Premium licensing option in conjunction with real-time data services.
- Text, XML, KML or shapefile format, which can be ingested into commercial or custom software.
- JPG, PNG or other graphical output of lightning data overlaid in Google Earth or GIS.
- Bulk datasets that can be integrated with business data for statistical analysis.
Data Content
Archive data files include the following content:
Archive data in KML format plotted in Google Earth:
- Date / Time (UTC); to millisecond precision in datasets after 2008
- Latitude and longitude (decimal degrees)
- Peak amplitude of event with signal polarity (amps)
- Indication of lightning event type
- Error ellipse semi major/minor axes (km); orientation of semi-major axis (degrees), in datasets after 2008
"2009-06-26 10:23:12","549","42.5628843","-70.4568508","-10700","0.25","0.25","-49"
"2009-06-26 10:24:48","118","42.5448978","-70.3732445","0","0.25","0.25","-49"
"2009-06-26 10:24:48","297","42.5437512","-70.4220905","-20000","0.25","0.25","-43"
"2009-06-26 10:24:48","361","42.5573448","-70.3274864","-16200","0.5","0.25","-43"
"2009-06-26 10:26:06","381","42.5303845","-70.3767344","0","0.5","0.25","-44"
"2009-06-26 10:26:41","574","42.5506026","-70.3984027","-7800","0.5","0.25","-45"
"2009-06-26 10:31:25","279","42.5660926","-70.3597541","-15500","0.5","0.25","-45"
Data may be provided for all parameters or reduced based on customer requirements, such as cloud-to-ground strokes or latitude/longitude information only.
"2009-06-26 10:24:48","118","42.5448978","-70.3732445","0","0.25","0.25","-49"
"2009-06-26 10:24:48","297","42.5437512","-70.4220905","-20000","0.25","0.25","-43"
"2009-06-26 10:24:48","361","42.5573448","-70.3274864","-16200","0.5","0.25","-43"
"2009-06-26 10:26:06","381","42.5303845","-70.3767344","0","0.5","0.25","-44"
"2009-06-26 10:26:41","574","42.5506026","-70.3984027","-7800","0.5","0.25","-45"
"2009-06-26 10:31:25","279","42.5660926","-70.3597541","-15500","0.5","0.25","-45"
Data may be provided for all parameters or reduced based on customer requirements, such as cloud-to-ground strokes or latitude/longitude information only.
