Community Support

[This post is marked as unsolved] Thunderstorm module  

  RSS
jukkapartanenmonenafi
(@jukkapartanenmonenafi)
Eminent Member

Hello all,

Has anyone configured thunderstrom module ? I have a own blizortung lightning radar, and it pushing out text file (filename bo.json) as follows:

{"real":[1520081404,486,0,4125,0,0],"last":["2018-03-03 12:48:31",1520081311,41,31,2380,172,"3 km",168,0],"lastown":["2018-03-03 06:14:02",1520057642,44,-6,1.1882352941176,216,"1.2 km",629,0],"stat":[4125,1,1,1520057705,2828,2828,641,1520077084,651],"graph2":[[1519995600000,235],[1519999200000,266],[1520002800000,286],[1520006400000,387],[1520010000000,458],[1520013600000,354],[1520017200000,406],[1520020800000,632],[1520024400000,421],[1520028000000,332],[1520031600000,270],[1520035200000,444],[1520038800000,286],[1520042400000,224],[1520046000000,122],[1520049600000,177],[1520053200000,151],[1520056800000,233],[1520060400000,277],[1520064000000,355],[1520067600000,337],[1520071200000,436],[1520074800000,567],[1520078400000,556],[1520082000000,402]],"stgraph2":[[1519995600000,0],[1519999200000,0],[1520002800000,0],[1520006400000,0],[1520010000000,0],[1520013600000,0],[1520017200000,1],[1520020800000,0],[1520024400000,1],[1520028000000,3],[1520031600000,0],[1520035200000,0],[1520038800000,0],[1520042400000,0],[1520046000000,0],[1520049600000,0],[1520053200000,0],[1520056800000,0],[1520060400000,1],[1520064000000,0],[1520067600000,0],[1520071200000,0],[1520074800000,0],[1520078400000,0],[1520082000000,0]],"strikes":[[1520081311,41.2618,31.6033]],"clusters":[]}

Can anyone help ?

My web site:

http://www.zalama.net/euroblitz/Web/euroblitz_webpage.php?lang=en

 

Quote
Posted : 03/03/2018 1:57 pm
Pierre Lannoy
(@pierre-lannoy)
Member Admin

Hello @jukkapartanenmonenafi !

I can possibly help by adding to Weather Station the possibility to collect and use this type of file, but I need some information like:

  • the description of the format
  • possible access points (are there any APIs on the site you give the url or is it self hosted files?)
  • quotas for queries and, more generally, conditions to access it from many locations/Weather Station installations...
  • The link between this and euweather.eu (I haven't understand it, sorry)
  • etc.

If you have these informations I can get an eye..

If you like Weather Station, please consider to make a review to help make it known. That would be the best way to thank me...

ReplyQuote
Posted : 03/03/2018 2:19 pm
Gerhard Witteveen
(@gerhard)
Reputable Member 🇳🇱 🇧🇪 Editor

I'd love that! I also have 2 Blitzortung-detectors! So, I'm all for some form of implementation of Blitzortung!

Gerhard

ReplyQuote
Posted : 03/03/2018 8:25 pm
Gerhard Witteveen
(@gerhard)
Reputable Member 🇳🇱 🇧🇪 Editor

Here is the description of the raw-blitzortung data. Blitzortung is very strict in publishing the data. The data can only be used for the participant. This makes sense, because the data of a single user is worthless. You need at least 8 participating stations to be able to calculate the location for the lightning. The basic usage-restrictions are at the end of the attached.

************************************************************************************************

Access to the raw data
Each participant is entitled to access the computed lightning data in raw text format. The archive data files are stored at our data server "data.blitzortung.org" and are distributed to the directories

  • Data_1 for region 1 (Europe),
  • Data_2 for region 2 (Oceania),
  • Data_3 for region 3 (North America),
  • Data_4 for region 4 (Asia), and
  • Data_5 for region 5 (South America).

Each data directory contains sub-directories named by "Protected/Strikes/" followed by the date and time of the lightning strikes in UTC times. The access to the data files is protected by your loginname/email and password for blitzortung.org. Each data file contains lightning strike information of 10 minutes. Each line of these files consists of one variable coded in "JSON" (JavaScript Object Notation). Files older than 24 hours are only available as "zgip" files. For example, the file

contains the lightning stike data for Region 1 (Europe) of 1'st August 2013 between 10:30 to 10:39.999999999. Informations about all stations can be found in the file

The lightning data files and the stations file are updated every minute. You need to check whether the file is available in gzip format as "XX.json.gz" or in simple text format as "XX.json".

The last strike data entries from all regions together up to the current time can also be accessed via the following url. It considers the last 100000 entries (with signals involved) / 1000000 entries (without signals involved). To keep the transfer rate as high as possible, the data is not read from the disk but from the main memory.

The returned records are sorted time descending. The parameters of the script have the following meaning.

  • numer=x provides the last x entries (default = 100)
  • time=t provides the latest entries after time stamp t (given as UTC Nano Epoch Seconds)
  • west=lon provides only entries with a longitude of at least lon (default = -180)
  • east=lon provides only entries with longitude of at most lon (default = 180)
  • north=lat provides only entries with a latitude of at most lat (default = 90)
  • south=lat provides only entries with a latitude of at least lat (default = -90)
  • sig=0/1 provides entries excluding/including the information of the signals involved (default = 0)

Example: The follwing url provides the last 10 entries from the last 1000000 entries with a longitude between -10.0° and 40.0°, a latitude between 70.0° and 20.0°, and without the information about the signals involved.

Each line of the data files contains one JSON codes variable.

Each variable of the lightning strike files may have the following members.

  • time = time stamp in nano seconds
  • lat = latitude in degree (decimal)
  • lon = longitude in degree (decimal)
  • alt = altitude in meter
  • pol = polarity, -1 or +1
  • mds = maximal deviation span in nano seconds
  • mcg = maximal circular gap in degree (for example, 210 degree = the detectors are in a sector of 150 degree from the point of view of the impact position)
  • sig = array of signals

Each signal of the sig array may have the following members.

  • sta = station that has received the signal
  • time = time difference to the time of the lightning strike in nano seconds
  • lat = latitude of the detector in degree (decimal)
  • lon = longitude of the detector in degree (decimal)
  • alt = altitude of the detector in meter
  • status = status of the signal (bit 1 = polarity negative, bit 2 = polarity positive, bit 3 = used for computation)

Each variable of the stations file may have the following members.

  • station = station number
  • user = user
  • city = city
  • comments = comments
  • country = country
  • website = website
  • latitude = latitude in decimal degree
  • longitude = longitude in decimal degree
  • altitude = altitude in meter
  • controller_board = controller board
  • firmware = controller firmware
  • controller_status = controller status (0 = unknown, 10 = offline, 20 = idle, 30 = running, 40 = interference, 50 = invalid data, 60 = invalid signal, 70 = bad gps, 80 = no amplifiers , 90 = controller fault, 100 communication error)
  • input_0_board = amplifier board at channel 0
  • input_1_board = amplifier board at channel 1
  • input_2_board = amplifier board at channel 2
  • input_3_board = amplifier board at channel 3
  • input_4_board = amplifier board at channel 4
  • input_5_board = amplifier board at channel 5
  • input_0_firmware = firmware for amplifier at channel channel 0
  • input_1_firmware = firmware for amplifier at channel channel 1
  • input_2_firmware = firmware for amplifier at channel channel 2
  • input_3_firmware = firmware for amplifier at channel channel 3
  • input_4_firmware = firmware for amplifier at channel channel 4
  • input_5_firmware = firmware for amplifier at channel channel 5
  • input_0_gain = gain for amplifier at channel channel 0
  • input_1_gain = gain for amplifier at channel channel 1
  • input_2_gain = gain for amplifier at channel channel 2
  • input_3_gain = gain for amplifier at channel channel 3
  • input_4_gain = gain for amplifier at channel channel 4
  • input_5_gain = gain for amplifier at channel channel 5
  • input_0_antenna = antenna for amplifier at channel 0
  • input_1_antenna = antenna for amplifier at channel 1
  • input_2_antenna = antenna for amplifier at channel 2
  • input_3_antenna = antenna for amplifier at channel 3
  • input_4_antenna = antenna for amplifier at channel 4
  • input_5_antenna = antenna for amplifier at channel 5
  • signals = number of received signals at the last hour
  • last_signal = date and time of the last received signal
  • last_signal_nsec = time of the last received signal in nano seconds
  • last_strike = date and time of the last affected strike
  • last_strike_nsec = time of the last affected strike in nano seconds
  • 50_km_60_m_a = number of strikes detected by the network up to a distance of 50 km around the station within the last 60 minutes
  • 500_km_60_m_a = the same for 500 km
  • 5000_km_60_m_a = the same for 5000 km
  • 50_km_60_m = number of strikes of "50_km_60_m_a" the station was involved
  • 500_km_60_m = the same for 500 km
  • 5000_km_60_m = the same for 5000 km
  • 50_km_60_m_e = effectivity of the station in % up to a distance of 50 km around the station within the last 60 minutes
  • 500_km_60_m_e = the same for 500 km
  • 5000_km_60_m_e = the same for 5000 km
The participants can use these links for presenting own maps or statistical evaluations on their own web sites. It is also allowed to collect the data to create a separate private archive and to provide access by other users to maps and statistical informations created from the own archive.
Please note: The authors of the provided data are "all" participants of the network. It is not the intention of the project to publish raw data, to provide access to raw data, or to market raw data to others. This removes a main motivation to join the project and leads to a disintegration of the network. Please note also the privacy policies if using informations from "stations.json.gz". A commercial use of data from Blitzortung.org is prohibited.
ReplyQuote
Posted : 03/03/2018 8:37 pm
jukkapartanenmonenafi
(@jukkapartanenmonenafi)
Eminent Member

Here is description of data:

real: Time, Strikes/h, close, strikes today, own strikes/h, own close

last: Last strike time,timestamp,lat,lon,distance, bearing,deviation,BO users,strength

lastown: last own strike time,timestamp,lat,lon,distance,bearing,deviation,BO users,strength

stat: strikes today,own strikes today,own max strikes/h,last strikes,farest own strike,closest own strike,BO max strikes/h,last strike,max users

graph & graph 2: stats data timestamp, amount

strikes: last strikes timestamp, lat, lon

clusters: cluster coordinates

I think most useful is "Last":  Last strike time,timestamp,lat,lon,distance, bearing,deviation,BO users,strength

and max distance shown strike would be limited  150 - 300 km. All data fields are of course available.

ReplyQuote
Posted : 26/03/2018 6:05 pm
jukkapartanenmonenafi
(@jukkapartanenmonenafi)
Eminent Member

Any Ideas ? Iam not pushing… just reminding  😀 

ReplyQuote
Posted : 21/04/2018 6:40 pm
Pierre Lannoy
(@pierre-lannoy)
Member Admin

Hello all.

After a deep review of usage conditions, I can't provide access to blizortung.org data from Weather Station. I'm sorry for that.

If you like Weather Station, please consider to make a review to help make it known. That would be the best way to thank me...

ReplyQuote
Posted : 16/02/2019 2:39 pm

To participate, please connect first!