Uh... my bad, I miss-read the details. You are right, it's a rainfall per hour rate.
I think a pre-filter script to convert your hourly rate back into a counter before feeding it to rrd would be the best option. A little python scripting would probably do it pretty easily. On 14 June 2017 at 09:07, Alex van den Bogaerdt <a...@vandenbogaerdt.nl> wrote: > > A far simpler solution is; it's just a counter that resets every hour. > > No it's not. > > >> > 011111244445678888889998767777765555553444335888889899987677 > >> > 010000120001121000121000012000110000010100012300011010001210 > ------------ > ------------ > > Look approximately halfway: 98767 > Then look below: 00012 > > The "counter" goes from 7 to 6, as a result of rainfall 1 being added and > 2 being removed from the window. > > If you treat this as a counter being reset every hour, you would get > negative rainfall, or counter overflow with the resulting huge flood, or > rates becoming unknown because of sanity checks. > > > > > > -- Donovan Baarda <a...@minkirri.apana.org.au>
_______________________________________________ rrd-users mailing list rrd-users@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users