Can you check my site

[DaveNZ]

Hi, can you guys check this page http://howickweather.info/graphs_.php
I need to know if the times on the graphs are correct for timezones different than the NZ timezone. The last point should say 20:00, as should the first point. Note this is a static test page, and not the updating graphs page.
Thanks!

[henkg]

Netherlands (UTC+01:00):

[DaveNZ]

Thanks. The time it's giving you is 12 hrs behind what it should say. Similarly you are 12 hrs behind the NZ timezone. If others have similar results I'll know what to do to fix it...

[steve]

It shows 0700 for me, I'm on UTC.

[DaveNZ]

Alright I have tried to fix things, does it display 20:00 as the last point now?

[steve]

It does for me, yes.

[mcrossley]

Working for me on UTC, but your daily reports page looks a bit sick
(http://howickweather.info/dailyreports.php)

Fatal error: Uncaught exception 'Exception' with message 'DateTime::__construct() [<a href='datetime.--construct'>datetime.--construct</a>]: Failed to parse time string (--) at position 0 (-): Unexpected character' in /virtual/users/e17018-18566/web/dailyreports.php:120 Stack trace: #0 /virtual/users/e17018-18566/web/dailyreports.php(120): DateTime->__construct('--', Object(DateTimeZone)) #1 {main} thrown in /virtual/users/e17018-18566/web/dailyreports.php on line 120

[DaveNZ]

Working for me on UTC, but your daily reports page looks a bit sick

Fixed now. As for the graphs, I will assume the timestamps are showing OK now unless someone else posts otherwise

[serowe]

Axis doesn't show the start and end time points - first time point for Melb is 21:00 and last point shown is 18:00. Pop ups/floy outs on graphs though now show 20:00 as start and end points - just the axis that is missing times.

[serowe]

OK query/anomaly on your live data page.

The page - when entered - states 'Updates paused.' and provides a Resume Updates (which, from the way the page is shown, appears to be the default state ie you can't have the page 'stay live' by itself.

But, what is disconcerting, if you press 'Resume Updates' the display updates, some of the values change colour (randomly assigned colours???) but then, about 1-2 seconds later, these new colopurs are removed and you are left wondering 'WTH did the screen flash at me?'. I am presuming the coloursindicated changed values but why remove them so quickly?

And then - if this is a 'live weather data page' is the default a static page?

Next point

On your Monthly/Yearly reports and Daily Reports pages you show years 2009 through 2012 - screen is blank until you have selected year, month and day. Why not default to the current data so at least the screen shows data, highlights the currently selected date and gives the user the impression that there is actually data available. I know you say at the top 'First select a year, .....' but the average user will come to that page, and just see....nothing

It appears to take 'ages' (figuratively speaking) whilst date is collected and graphs drawn so appears nothing is happening when you do make a selection.

[DaveNZ]

Axis doesn't show the start and end time points - first time point for Melb is 21:00 and last point shown is 18:00. Pop ups/floy outs on graphs though now show 20:00 as start and end points - just the axis that is missing times.

Hi, that is what should show for everyone. This is the way the graphs library displays the times. I don't think it is too much of an issue because the tooltips give the times.

[DaveNZ]

OK query/anomaly on your live data page.

The page - when entered - states 'Updates paused.' and provides a Resume Updates (which, from the way the page is shown, appears to be the default state ie you can't have the page 'stay live' by itself.

But, what is disconcerting, if you press 'Resume Updates' the display updates, some of the values change colour (randomly assigned colours???) but then, about 1-2 seconds later, these new colopurs are removed and you are left wondering 'WTH did the screen flash at me?'. I am presuming the coloursindicated changed values but why remove them so quickly?

And then - if this is a 'live weather data page' is the default a static page?

Next point

On your Monthly/Yearly reports and Daily Reports pages you show years 2009 through 2012 - screen is blank until you have selected year, month and day. Why not default to the current data so at least the screen shows data, highlights the currently selected date and gives the user the impression that there is actually data available. I know you say at the top 'First select a year, .....' but the average user will come to that page, and just see....nothing

It appears to take 'ages' (figuratively speaking) whilst date is collected and graphs drawn so appears nothing is happening when you do make a selection.

Thanks for the comments, what browser are you using? I have tested the live page in all the main browsers and there have been no issues...
The colours change to indicate changed values, yes. I assume when most people see the flash they know this means changing/updating values.

I may change the daily reports page to display the most recent daily report (yesterday's). But the loading of new data & graphs is pretty quick for me, maybe your internet was running a little slow?

[serowe]

Using IE9.

The problem with the 'flash' is that it is so quick. If you aren't looking at the screen, and have good retention for what you see, more than one or two changed items would give the user no chance to remember/recall all the highlighted items. Personally I would keep the highlighted colours until the next update.

And as for slow internet? No - I'm on cable and I have exactly the same problem when I test my page updates. Here, whether local or on my internal or external web servers, generating a daily report from 2.5+ million records is very quick BUT when I go to anyone elese house, whether they are on cable or ADSL, the updates take a lotttt longer. Still haven't worked out why, but it is something I have noticed quite often. (my cable connection today si qorking at full speed - just checked, so there isn't an issue getting access 'over the pond'....)