Page 1 of 1

How to Fix Incorrect Record Data - a little hot at 70 C!

Posted: Mon Jun 29, 2009 7:09 pm
by AAMFlyer
I use WDL and have discovered that somehow Meteohub reported a temperature of 158F (70.0 C)to WDL and now that populates across all of my WDL records for month/year/all time and graphs.

I checked my RAW file and the data tab in meteohub and it is not recorded in the RAW file and it does not graph within meteohub graphs (so it is specific to WDL data) - so where do I correct that figure so that I can recalculate the records correctly.....I see it in the "hist-" files but not in the RAW file data - so I'm wondering where records are kept and or pulled from for WDL so that I can correct the error...

Do I need to stop data loging and correct the following files to fix it and then any new high temp records will fix it or is it deeper than that!

hist-alltime
hist-month1
hist-year1

Re:How to Fix Incorrect Record Data - a little hot at 70 C!

Posted: Mon Jun 29, 2009 10:49 pm
by skyewright
AAMFlyer wrote:Do I need to stop data loging and correct the following files to fix it and then any new high temp records will fix it or is it deeper than that!
If there is no problem in the raw data, then I presume a recomputation ought to rebuild the hist files with correct values?

Re:How to Fix Incorrect Record Data - a little hot at 70 C!

Posted: Mon Jun 29, 2009 11:05 pm
by AAMFlyer
That's what I thought - but no go - a recomputation didn't change anything.....or I'm reading the raw file incorrectly....

The record is 158F on 6/18/2009 at 20:43 which doesn't exist in the RAW File.

Here is the raw records between that time for th0:

From RAW
20090618204233 th0 237 27 0036
20090618204325 th0 237 29 0046
20090618204415 th0 237 31 0056
20090618204517 th0 237 31 0056
20090618204559 th0 237 28 0041

From HIST-MONTH1
month1_th0_tempmax_time 20090618204304
month1_th0_tempmax_c 70.0
month1_th0_tempmax_f 158.0

Thanks!

Re:How to Fix Incorrect Record Data - a little hot at 70 C!

Posted: Mon Jun 29, 2009 11:51 pm
by sevenless
Keep in mind that the raw data file timestamps are UTC, and the records and computed data is then adjusted for local time based on the time difference you enter in the administrative section.

Based on Colorado I'm guessing that you're UTC-7, so the incorrect raw data should have a time stamp of somewhere around 3:43am of 6/19/2009 (200906190343xx), assuming my math is correct.

Re:How to Fix Incorrect Record Data - a little hot at 70 C!

Posted: Tue Jun 30, 2009 11:58 pm
by AAMFlyer
Thanks - that was it - I found it.... I will get it deleted but not sure if I should do it manually of through the data tab within meteohub - will try meteo first... Thanks!