Gary, Vince, thanks for the replies. Somehow I was able to subscribe to this group with a non-Google email address (and in fact got a copy of my own post) but never got any of the replies and can't even figure out how to reply to this thread with my original non-Google account. So I didn't see the replies until I checked with the web interface just now. Sorry!
I did anticipate some issues with CoCoRaHS data being on a much different schedule than typically WeeWX data, so thanks for providing thoughts on that. I'm not as interested in inserting multi-day reports, only the daily reports which are a bit more regular (ideally 7:00 AM). But I do get what you're saying about archive records and daily summaries. One of my goals is to make my CoCoRaHS data available on my weather site alongside my other WeeWX data. I'm currently testing the Belchertown skin, which has very nice graphing capabilities, and wanted to avoid writing something completely separate for snow data. Vince, I think your suggestion of creating a separate WeeWX compatible database to start with is a good one; it seems like I could get a skin to use this second datasource when I get that far along. At any rate, what I have right now is a few simple scripts that run from cron to pull down my daily CoCoRaHS data, transform the XML a little bit, and do some basic aggregation and reporting on it. So that part is good enough to build on to get the data into a database (I use MySQL with WeeWX so will just create another schema there). I currently use the CoCoRaHS website to submit my observations since the Android app is broken for me (password not being escaped correctly). -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/2f97bd61-325e-4479-ad0a-1a0204393fdan%40googlegroups.com.
