For now the script will always use field 2 && 5 as in km,
In your field-descriptions those fields are described as having km as unit
field# 2 => current close rate/min (< 50km)
field# 5 => last strike distance (km)
But there is also a field #20 “Measure (set in config.ini)” which contents is km.
Can that field contain some other unit, f.i. miles and will that effect field 2 && 5?
Hi!
Have tested the file you posted and it seems to be ok.
When it comes to field 20 in the setup file it can certainly apply to miles or other values, think that is according to what the system is set up with.
Then fields 2-5 will show as that choice.
This is just something I think is right if someone knows more about this would have been nice.
Unfortunately NSD2013 is failing on me as well. NSLog appears to be much more stable but obviously creates files in a different format to that expected. This is the data format:
NSRealtime.txt - Comma Delimited - Updated with each Strike - Suitable for rapid uploads to be used by javascript routines.
Position Type Name Description
0 int Year yyyy
1 int Month mm
2 int Day dd
3 int Hour hh
4 int Minute mm
5 int Second ss
6 int Bearing Degrees
7 int Distance Km or Mi as Selected
8 int TRAC X
9 int TRAC Y
10 string Strike Type +CG, -CG, +IC, -IC
11 int +CG 1-Yes, 0-No
12 int -CG 1-Yes, 0-No
13 int +IC 1-Yes, 0-No
14 int -IC 1-Yes, 0-No
15 int Strikes Since Midnight
16 int Noises Since Midnight
17 int Close Since Midnight
18 int CG+ Since Midnight
19 int CG- Since Midnight
20 int IC+ Since Midnight
21 int IC- Since Midnight
22 int Peak Rate Per Min Since Midnight
23 string Peak Rate Time hh:mm:ss
24 int Strikes /Min
25 int Noises /Min
26 int Close /Min
27 int +CG /Min
28 int -CG /Min
29 int +IC /Min
30 int -IC /Min
31 int Current Rate Minutes - X below
32 int X Min Strikes User Selectable counter
33 int X Min Noises 2 Min - 60 Min
34 int X Min Close
35 int X Min +CG
36 int X Min -CG
37 int X Min +IC
38 int X Min -IC
39 string Upload Rate Normal or High
40 string Up Time hh:mm:ss (154:08:23 )
41 string Last Strike Time hh:mm:ss
42 int Days Ave Bearing Degrees
43 int Day’s Ave Distance Km or Mi as Selected
44 int 1 Min Ave Bearing
45 int 1 Min Ave Distance
46 int X Min Ave Bearing
47 int X Min Ave Distance
48 int Peak Burst Rate Per Sec Since Midnight
49 string Peak Burst Time hh:mm:ss
50 int Strikes Minutes # of Minutes stored in NSStrikes.txt
51 int Antenna Offset 1 - 360
52 int Distance Units Being Used 0 = km, 1 = mi
A very nice thing for someone like me who has the UV and solar radiation sensor, would be to have in the UV data box also the graph and the value of the evapotranspiration
Sorry, but the first two points do not belong into the wishlist.
Those are errors in the setup or scripts. LIML airport returns no valid data, you can check yourself
This is a fast link to the data of LIML https://tgftp.nws.noaa.gov/data/observations/metar/stations/LIML.TXT
The result is
There is now a setting in the script for that (line 47)
If set to true, the rounded indoor-temperature will be displayed in the house-image.
The box above the house will not be displayed in that case.