EasyWeather Format: Difference between revisions

m
No edit summary
m (→‎Usage of easyweather.dat fields for Cumulus input of latest record:: clarification based on latest forum exchange)
 
==Usage of easyweather.dat fields for Cumulus input of latest record:==
People with non Fine Offset stations may wish to create data in this format for input to Cumulus running continuously, only the last record on the file is ever read, checking its time-stamp differs from the last one read.
See the forum (http://sandaysoft.com/forum/viewtopic.php?f=4&t=4344) for more details: Cumulus does not see any station date and time fields when reading a Fine Offset weather station received transmission or processing readings in its memory via USB.
Note when reading easyweather.dat (or equivalent format input), Cumulus does read the station originated date and time fields, and checks that they have changed before using new data from the file. To get Cumulus to read the file, configure a station type of "Easyweather (using .dat file)", and supply the full path to your file (it can have any name you wish), and the interval at which it is to be read. Note that Cumulus only reads the last line in the file, and that this method is only suitable for 'live' data, i.e. you cannot close Cumulus down and expect it to catch up again later. This method of using Cumulus is available on an "as is" basis; if it works for you, fine, but strictly speaking it is unsupported.
 
*Note when reading easyweather.dat (or equivalent formatted input), Cumulus will read the station originated date and time fields, and Cumulus checks that they have changed before using new data from the file.
Here's the format of the initial part of an 'easyweather.dat' file record, with the fields Cumulus uses in bold. The separator between each field can either be a space or a comma, both are treated the same (hence date and time are regarded as separate fields even though they are separated by a space in real EasyWeather file). Note that EasyWeather always uses full stops for decimals. There are more fields after the ones shown (see example records shown above for the two .dat formats; and http://www.jim-easterbrook.me.uk/weather/ew/).
*To get Cumulus to read the file, configure a station type of "Easyweather (using .dat file)", and supply the full path to your file (it can have any name you wish), and the interval at which it is to be read.
*Note that Cumulus only reads the last line in the file, and that this method is only suitable for 'live' data, i.e. you cannot close Cumulus down and expect it to catch up again later.
*This method of using Cumulus is available on an "as is" basis; if it works for you, fine, but strictly speaking it is unsupported.
 
Here's the format of the initial part of an 'easyweather.dat' file record, with the fields Cumulus uses in bold. The separator between each field can either be a space or a comma, both are treated the same (hence date and time are regarded as separate fields even though they are separated by a space in real EasyWeather file whilst in the real file other fields are separated by commas). Note that EasyWeather always uses full stops for decimals. There are more fields after the ones shown (see example records shown above for the two .dat formats; and http://www.jim-easterbrook.me.uk/weather/ew/).
*0 - Record no
*1 - Transfer date
*21 - rain total
*22 - rain since last reading
*'''23 - rain in last hour''' (used as Cumulus rain rate, i.e. a rain amount for a period of one hour is the rate in units of amount per hour)
*24 - rain last 24 hours
*25 - rain last 7 days
*26 - rain last 30 days
*'''27 - rain last year''' (Used as Cumulus rain counter which can be any ever-increasing counter, but it needs to be in the same units as 23 - rain in last hour). The longer this counter continues before resetting to zero, the better for Cumulus.
*'''27 - rain last year''' (used as rain 'counter' to determine other totals)
 
''For easyweatherplus.dat only:''
5,838

edits