wee_import is going through a bit of a change at the moment. I have added a QC capability that applies the weewx.conf StdQC min/max settings to imported data the same way the StdQC service works on incoming data. I would expect this will get rid of the nonsense WU data. Will have to wait to see if the QC capabilty is accepted when I push it up.
On Wednesday, 7 September 2016 10:01:00 UTC+10, Andrew Milner wrote: > > I found similar things Liz when I imported 2yrs of data from WU - and > found that many of the negative values were a result of either -- or 9999 > values in the WU data. > I have not seen any -- values returned from a WU WXDailyHistory query, only obviously wrong large numbers. When processing imported fields if wee_import cannot convert an imported field to a number (float) it looks to see if the field is just whitespace, in which case it treats it as None, otherwise wee_import raises an exception which causes the import to halt. A -- would cause such an exception. WU may well display -- in place of a missing value on the nicely formatted, tabulated daily history display page but I don't believe they are actually including -- in any of the numeric observation fileds in WXDailyHistory query results. 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.
