meteohub.de

To implement my Leuven-Template for Meteobridge on the same level as for other weather-programs I am still missing some selectors.
Meteobridge WiKi: http://meteobridge.com/wiki/index.php/Templates

24 hour values:
val1, val2, val3, ..., val60: could they be extended with val1h, val2h, val3h, ..., val24h ?
These 24h values are available for rain/evo (as sum-, delta-) with the explanation: "This is useful to do trend analysis over various time spans."
But those 24hour graphs are also needed for outside temp, pressure and so on.
I now have to read the WeatherUnderground data to get those 24 hour graphs, but not all users of the template are willing to upload to WU.

Last rain:
To display the date/time of "last rain occured at xx" or to display the condition "it is raining" I need a value for the last change of the cumulative value of rain0total
The -age selector only gives the last time the sensor was transmitting, but I need the "number of seconds since the last change in value" or "the date-time the last change was detected".

Sensor contact lost
The mbsystem-lastgooddata gives the last correct data received. But when there is no contact with the ISS, the Davis will still send correct inside sensor-data so this value is useless in most cases.
Could a selector -lastgooddata be added for at least one outside sensor?
It would realy help to display a meaningfull status page if this selector would be avialable for every sensor connected. These values are already available on the "Live Data tab".

Wind direction range
[wind0dir-dmax.0:--] => returns always 355
[wind0dir-dmin.0:--] => returns 0
[wind0dir-avg60.0:--] => returns meaninfull and correct data.

I need meaingfull information (the lowest winddirection <> 0, and the highest <> 355 ) for all three selectors:
* To display information like "Windirection between South and West, avereage 225 degrees" and
* To colorize the bands in the gauges,

Others
These are very interesting and often asked for, but I do not think that they can be easily implemented:
* Days with rain - this month and this year.
* Today hourly rain maximum and minimum.
* Days with no rain can be calculated if the "last rain occured" selector was available.

Wim

Wim, thanks for taking the time to explain your needs.

The 24 hour values are beyond the storage capabilities of the MR3020. To keep all data of a day is too much and it would also need some sort of persistency to survive reboots etc. Otherwise a reboot will wipe that data and it will take full 24 hours until this is filled up again. There might be a solution somewhere in 2016 but not on short term. sorry.

"Last rain" and sensor specific "last good data" is something that cold be done. I have to see how to make this permanent as currently this is not stored on the server. But this sounds like something that might be implemented in one of the next updates.

regarding "wind dir" I am not sure what ind of information you are looking for in case of dmin and dmax selectors. At the moment they don't have meaning for wind direction and should not be used.

Days with rain will be a challenge that needs some persistency solution, an hourly maxima over the course of the day is something also not covered by the way data is handled and stored. This needs more thinking from my side.