                    Possible NEW FEATURES

possibly implement averaging rainRate calculation instead of the
current near-instantaneous implementation in fousb

Offer tags to support JSON. In particular, vectors.

Make record generation from the accumulators into a separate service, allowing 
easier customization. This would also make calculation of extensive quantities
easier.

The Davis console could intercept new archive record events and add rxcheckpercent
and rain to software generated records.

Consider breaking the rule that reporting can only be done through the 
databases and, instead, offer up the last record when the reporting thread
starts.

New observation types would have their unit group attached as a suffix.
E.g., _energy.

Move to a "plugin" architecture.

Support the WU "RapidFire" protocol.

Offer out-of-the-box support for "last 24 hours", "last 7 days", and "last 28 days"
statistics.

Use the tagged stats classes for the archive database as well, thus unifying
the two databases.

Offer "cumulative" as an aggregation type.

Allow rain-to-date to be added to a partial rainyear.

ET appears only at the top of the hour in an archive record. So, it's effective
archive interval is 60 minutes. Does this carry through?

Fix scaling for aggregate interval of a week, so it starts on a Sunday.

More dynamic access to the database. Check out
Werkzeug. http://werkzeug.pocoo.org

Dynamic web updates, using AJAX.

Port to Windows.
