OK, I think I can see what happened here. if you look at the WU data for 21 August (tried to include an extract in a bit more readable format below) at 17:10:00 you can see a WeeWX 3.8.2 sourced record and thence every 10 minutes after. The net effect is that there are WeeWX sourced and 'Wunderground v.1.15' sourced interleaved records. I suspect the cause is that when Pete first started WeeWX it downloaded the loggers history and uploaded any archive records to WU, I'll bet at the time the oldest record in the logger was 21 August 2018 17:10:00. Because 21 August was a 'partial' day as far as WeeWX was concerned I imagine it had trouble getting a dayRain value to upload to WU, hence the WeeWX records break the integrity of the WU rain data (column with first entry 5.6). Consequently when wee_import was used to import the WU data it hoovered up everything, and I could see wee_import being easily tricked with the dayRain values going up and down within a day. Interestingly, if you look at subsequent days you still see the interleaved records but this time WeeWX has a full day of data so there is much more consistency in the dayRain data (still the odd error though)
2018-08-21 16:23:20 23.4 22.9 1010.4 East 100 1.6 3.2 97 1.3 5.6 56 Wunderground v.1.15 2018-08-21 20:23:20 2018-08-21 16:33:12 23.4 22.9 1010.4 East 90 1.6 3.2 97 1 5.6 49 Wunderground v.1.15 2018-08-21 20:33:12 2018-08-21 16:43:08 23.6 23.1 1010.4 SE 134 1.6 3.2 97 0 5.6 72 Wunderground v.1.15 2018-08-21 20:43:08 2018-08-21 16:53:04 23.7 23.2 1010.4 SE 132 3.2 4.8 97 0 5.6 148 Wunderground v.1.15 2018-08-21 20:53:04 2018-08-21 17:03:20 23.8 23.3 1010.4 SE 132 3.2 3.2 97 0 5.6 42 Wunderground v.1.15 2018-08-21 21:03:20 2018-08-21 17:10:00 23.7 23.1 1010.1 SE 135 1.6 9.7 96 0 0 54 weewx-3.8.2 2018-08-21 21:10:00 2018-08-21 17:13:12 23.7 23.1 1010 East 98 3.2 3.2 96 0 5.6 37 Wunderground v.1.15 2018-08-21 21:13:12 2018-08-21 17:20:00 23.7 23.2 1010 East 90 1.6 11.3 97 0 0 43 weewx-3.8.2 2018-08-21 21:20:00 2018-08-21 17:23:08 23.7 23.2 1010 East 99 1.6 1.6 97 0 5.6 37 Wunderground v.1.15 2018-08-21 21:23:08 2018-08-21 17:30:00 23.7 23.2 1010 East 90 1.6 6.4 97 0 0 43 weewx-3.8.2 2018-08-21 21:30:00 2018-08-21 17:33:04 23.7 23.2 1010 East 101 1.6 1.6 97 0 5.6 26 Wunderground v.1.15 2018-08-21 21:33:04 2018-08-21 17:40:00 23.7 23.2 1009.9 East 90 1.6 8 97 0 0 27 weewx-3.8.2 2018-08-21 21:40:00 2018-08-21 17:43:20 23.7 23.2 1010 ESE 104 1.6 4.8 97 0 5.6 14 Wunderground v.1.15 2018-08-21 21:43:20 2018-08-21 17:50:00 23.8 23.3 1009.8 ESE 112 3.2 11.3 97 0 0 16 weewx-3.8.2 2018-08-21 21:50:00 2018-08-21 17:53:12 23.8 23.3 1009.7 ESE 113 4.8 4.8 97 0 5.6 25 Wunderground v.1.15 2018-08-21 21:53:12 2018-08-21 18:00:00 23.9 23.4 1009.8 ESE 112 3.2 11.3 97 0 0 31 weewx-3.8.2 2018-08-21 22:00:00 2018-08-21 18:03:08 23.8 23.2 1009.7 SSE 151 3.2 3.2 96 0 5.6 44 Wunderground v.1.15 2018-08-21 22:03:08 2018-08-21 18:10:00 23.9 23.2 1009.8 SSE 158 1.6 6.4 96 0.8 0.8 36 weewx-3.8.2 2018-08-21 22:10:00 2018-08-21 18:13:04 23.8 23.2 1009.7 ESE 116 1.6 1.6 96 43.4 7.9 23 Wunderground v.1.15 2018-08-21 22:13:04 No point in trying to re-import the WU data. So the available fixes would be editing the WeeWX archive for 21 August 2018 then rebuilding the daily summaries for that day or importing the .wlk files via a third party app. You could delete the 'WeeWX sourced' records from the archive for 21 August (for that matter through until 8 September when WeeWX is the sole source of data) or you could delete the 'Wunderground v.1.15' records from 21 August 2018 17:10:00 to 8 September. I am sure a cunning query could be crafted to do it. One word of warning, if you use a graphical app to manipulate your data be careful as they can leave null strings in SQLite databases and that can causes issues. I guess hardening wee_import to these sorts of errors would be good, going to be pretty complex though and I just see a stack more issues being thrown up. 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.
