No reason why this shouldn't work. Just use a 2nd binding to your "other" database.
If the two databases are using different archive intervals and are not synchronized in time, that should not be a problem. Just ask for the "latest" value (tag $latest) rather than current ($current) value. That's what it's there for. -tk On Thu, Dec 14, 2017 at 12:53 PM, Joe Percival <[email protected]> wrote: > I am going to have a network accessible database which holds a single > parameter, snowDepth, as well as dateTime (and usUnits and interval if > necessary). > I've read the customization documentation about using more than one > database but the assumption there was both databases were using the weewx > schema and that they were both being populated by instances of weewx. For > the project I have in mind, this second, network accessible, database will > be populated at different intervals than weewx would do (maybe). > Can I just create a new schema for the new database and then use the new > parameters in templates for statistics and graphics as described for two > weewx databases in the documentation? > for example: > > schema = [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'), > ('usUnits', 'INTEGER NOT NULL'), > ('interval', 'INTEGER NOT NULL'), > ('snowDepth', 'REAL')] > > Thanks! > joe > > > -- > 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. > -- 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.
