Rich, Ok, good to hear. Let us know how you go importing your Weatherlink data when the time comes.
Gary On Thursday, 1 February 2018 11:03:02 UTC+10, rich T wrote: > > Gary > > Update: All records are fine and the NOAA reports are fully populated. > Here is what I did > > 1. Deleted all of the months causing the issue; > 2. Imported each month separately (oldest to newest) then verified that > the data imported correctly > 3. Deleted all of the NOAA Reports and allowed them to regenerate. > > Thanks > Rich > > On Tuesday, January 30, 2018 at 5:40:26 PM UTC-5, gjr80 wrote: >> >> Thanks Rich, that suits just fine. >> >> Gary >> >> On Wednesday, 31 January 2018 08:11:40 UTC+10, rich T wrote: >>> >>> Gary >>> >>> When I find the weatherlink data, it will be no problem to provide it. >>> It is not a top priority right now, other projects going on, but will be >>> looking in a few weeks. >>> >>> Rich >>> >>> On Tuesday, January 30, 2018 at 5:30:03 AM UTC-5, gjr80 wrote: >>>> >>>> Rich, >>>> >>>> First of all, thank you for the time you put in looking at this issue. >>>>> Sometime copying and pasting does not work either...learned the hard way. >>>>> It will take a few days, but I will delete the months that are causing >>>>> the >>>>> issue and re-import them. If all else fails, will delete a records from >>>>> August 2014 to October 2017 and re-import them into the database. Will >>>>> provide an update on how the process went. >>>> >>>> >>>> No problems, I had a big hand in wee_import so I like to make sure it >>>> works properly. >>>> >>>> >>>>> Another question: I am in the process of locating additional 5 to 6 >>>>> years (2009 through early 2014) worth of data, stored on one of many >>>>> spare >>>>> hard drives, which the data is in Weatherlink format. Would there an >>>>> issues in populating the database. >>>>> >>>> >>>> Hmm, I knew the Weatherlink question would come back again one day. I >>>> did start looking at adding a Weatherlink module to wee_import but >>>> like many things it did not go too far. To solve your problem now there >>>> may >>>> be a couple of alternatives. Being a Cumulus user this thread >>>> <https://groups.google.com/d/topic/weewx-user/Fvu9I3upv44/discussion> >>>> may be of some use, unfortunately we never heard back from the OP. This >>>> thread >>>> <https://groups.google.com/d/topic/weewx-user/BdHqIpIAUnc/discussion> >>>> takes what appears to be a more cumbersome approach, plus it is quite >>>> dated, again did not hear anything more though the last issue seemed to be >>>> one of deleting some bad data. >>>> >>>> I would like to tackle adding Weatherlink support to wee_import again, >>>> but I suspect I won't have anything for a few weeks at best, at least when >>>> we wrote wee_import we structured it in a manner that makes its fairly >>>> simple to extend, all we need do is work out to decode the source data and >>>> the rest is fairly much done. I understand Weatherlink uses more of a >>>> database format rather than CSV like Cumulus monthly logs, if it's easy >>>> enough to do would you be prepared to share some of your Weatherlink data >>>> to allow me to develop a Weatherlink front end to wee_import? >>>> >>>> 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.
