Another, perhaps simpler, approach just occurred to me.  On the snow depth 
RPi run apache with php and have a function that returns the snow depth 
value upon a web request.  On the weewx machine, write a custom service 
that makes the web request, parses the returned value and stores it.  Then 
I could use all the suggestions in the documentation for a 2nd data 
source.  I'd just have to anticipate error conditions and figure out how to 
deal with them.

On Thursday, December 14, 2017 at 10:53:30 AM UTC-8, Joe Percival 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.

Reply via email to