The danger of averages

Historically, we should have gotten an average of 5.5 inches of rain in and around our property in the month of January.  Actual total?  1.7″ image of rain

Given my prior modeling calcuations for rain catchment (360 ft^2*.5ft*7.5gal/ft^3) I should have been able to capture 1300 gallons of water.  In reality, we would have only captured 340 gallons.  Given our modeling around having enough water to last through the dry summer months, it now becomes clear that unless February exceeds it’s average goals, we may not be able to capture enough water to last the weekends we are anticipating to be up there this summer.

And on top of that, this all assumed a 2 person event, but given the interest in helping, even if it’s just for one weekend, we’re going to need access to quite a bit more water anyway.

Luckily our neighbor will help us out with some water (he runs his well from a generator though, so from an environmental perspective, it’s _VERY_ expensive water).  The other solution is that we could drive out to a local spring (there are a few near by) and collect water that way. This is also expensive, as we still have an overhead fuel cost which we might be able to mitigate if we can find a spring on the way, rather than out of the way.

This leads me back to the idea of providing a larger water catchment area in order to accelerate our time to cistern filling, which I believe is one of the more sensible solutions to this, as it continues to leverage the free water that does arrive, while also better dealing with the fact that averages can easily be deceiving.

Oh, and December was 1.5″ over average. And we still don’t have a catchment up and running, so this is all conjecture anyway.

Comments are closed.