I know the discussion here is going away from using an externally created/updated database, but for the sake of others who might consider such a path there is one other issue to keep in mind; the daily summaries. As Tom said an externally updated database should present no problems for weeWX to generate reports against as long as a suitable binding is defined and it has the key fields dateTime, usUnits and interval (and of course the data). Such a setup would support $current, $latest, $span and a few other tags as normal, but the longer period aggregates such as $month and $year (and heaven forbid $alltime if you implemented it) would use the archive instead of the daily summaries and there woudl potentially be a big performance hit for large databases. Creating/updating the daily summaries is far more onerous than creating/updating the archive and I have yet to see any non-weeWX solutions that do this (we use a separate database for weeWX-WD data but that database uses a sub-classed StdArchive service to to manage the data going into the database and so has the daily summaries available). In my opinion using the weeWX machinery to take care of the archive and daily summaries is by far the best and safest way to manage a database with daily summaries.
Gary -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
