Trixology

WeatherCat => WeatherCat General Discussion => Topic started by: xairbusdriver on May 26, 2016, 01:15:49 AM

Title: STAT$...:MAX:YESTERDAY:TIME$ vs Emailed report from WC
Post by: xairbusdriver on May 26, 2016, 01:15:49 AM
On my Statistics page, I have some simple tables reporting maximum and minimum items. The "Yesterday" item in question is:
Code: [Select]
<td class="right">High Temp:</td>
<td class="left">STAT$TEMPERATURE:MAX:YESTERDAY$TEMPUNITS$ at STAT$TEMPERATURE:MAX:YESTERDAY:TIME$</td>
The similar item in the "This Week" section is:
Code: [Select]
<td class="right">High Temp:</td>
<td class="left">STAT$TEMPERATURE:MAX:THISWEEK$TEMPUNITS$ on STAT$TEMPERATURE:MAX:THISWEEK:TIME$</td>
Likewise, there's a similar "This Month" section with ":THISWEEK:" replaced with ":THISMONTH:".  :o

Here are the displayed values on the page:Howsomeever, the Admin email I got was:
Quote
New Annual High Temperature Record for Houston Levee Trace Wx Station! Previous high was 88.11?F on 2016-05-11 14:07:00 -0500. New high is 88.40?F

Message from WeatherCat! 2.2.1

WeatherCat TimeStamp: 16:07:34 24-May-16
Is it safe to assume (if it ever is!) that the "4:01 PM" is the actual time WC received the data, while the email time ( 16:07:34 ) is simply the time the email was sent?

If so, can that received time be added to the email in some revision of the app? Perhaps I've simply missed the location for adding that bit of info? I'll now go check The Manual...  [banghead]

I'm so easily confused! But I doubt that you can fix that, no matter how much you improve WC. [blush]
Title: Re: STAT$...:MAX:YESTERDAY:TIME$ vs Emailed report from WC
Post by: WCDev on May 26, 2016, 11:15:39 PM
Is it safe to assume (if it ever is!) that the "4:01 PM" is the actual time WC received the data, while the email time ( 16:07:34 ) is simply the time the email was sent?

Yes, the timestamp is the time WeatherCat generated the email, not the time of the new record.

Every three hours WeatherCat checks for new records, so the time of the event will be sometime in the last three hours. We can add this in the future.


 
Title: Re: STAT$...:MAX:YESTERDAY:TIME$ vs Emailed report from WC
Post by: xairbusdriver on May 27, 2016, 02:02:52 AM
Quote
the time of the event will be sometime in the last three hours
Thanks for the info!
However, in that case, there's not much of a reason to make the time any more specific in the email.

I suppose the time, within a minute, is the "T" value in the M_WeatherCatData.cat file?
[removed link to the now castly photobucket.com site]  It also appears to be Centigradesius, wish the "civilized" parts of the World would return to the proper way of measuring things...   [banghead] [lol]

Maybe something I can use for practicing some php scripting... reading only, of course. ;)

Actually, no need to bother/touch/read/upload the M_WeatherCatData.cat file [banghead], WC is already reporting the 'current' temp every two minutes. That's certainly close enough for government work! All I need to do is keep track of the highest temp for the day (and any other min/max value I want). It's actually already being recorded by WC:
Code: [Select]
STAT$TEMPERATURE:MAX:TODAY$TEMPUNITS$
STAT$TEMPERATURE:MIN:TODAY$TEMPUNITS$
STAT$WINDSPEED:MAX:TODAY$ WINDSPEEDUNITS$
etc.
Probably just need to add the ":TIME$" bit then save/display it anywhere I want!
Once again, Stu has already thought about what we might need/want!  [cheer]  [removed link to the now castly photobucket.com site]