davidg666 wrote:Any chance of making the graphs aware of the time zone for the places they're reporting on? Here in Ireland (and in the UK too) we're on UTC in the winter, UTC+1 in the summer - an hour behind most of Europe - so the activity graph for Dublin is showing that it's already about 1825, but it's still just 1725 here...

Please keep the graphs simple and make everything UTC, irrespectively of the country of the graph, the country of the viewer or the daylight savings. It's gonna be a mess when you start getting countries with multiple timezones, and many other issues. Whoever is looking at the graphs should know how to convert UTC into localtime.

foxitrot wrote:The base idea is good. What about the data gaps/overlaps because of Daylight Saving Time jumps twice a year, interpolate? Or let's ignore DST changes and use the base time zone shift (usually during the winter time)? Neither option is ideal.

I agree that neither option is ideal, but even if you stay with a single timezone, the graphs will be offset by an hour when DST kicks in for the summer - so there'll be either a one hour gap in the data or an hour's worth of data with hour on the clock to put it.

I suggest dropping the hour's worth of extra data when DST ends at the end of the year, and inserting a gap in the graph (or even just a straight line) when DST starts and the clock moves forward.

In any case, the DST problem is a separate problem to supporting multiple timezones - unless you tie all the graphs to UTC (and avoid DST changes completely).

++David \ davidg666

Country manager and local champ for IrelandAM for Dublin, Wicklow, Kilkenny, Wexford, Graiguenamanagh and Enniscorthy

davidg666 wrote:Any chance of making the graphs aware of the time zone for the places they're reporting on? Here in Ireland (and in the UK too) we're on UTC in the winter, UTC+1 in the summer - an hour behind most of Europe - so the activity graph for Dublin is showing that it's already about 1825, but it's still just 1725 here...

Yes, it's posible but the images are static, so the only option would be to set local timezone of the city, not the user watching the website. Added to my to-do list but will be difficult to re-write my scripts generating daily data after the midnight.

Oh yes - I meant that the graphs should show the local time of the city for each graph, not that they should adjust the time for the user looking at the graph - who could be anywhere anyway.

That way, it would be easier to compare graphs for different cities in different time zones - it looks a little awkward when a city outside your timezone appears to have its evening rush between 1800 and 2000 instead of 1700 and 1900. I expect this will become more important if you add more cities that are further apart.

++David \ davidg666

Country manager and local champ for IrelandAM for Dublin, Wicklow, Kilkenny, Wexford, Graiguenamanagh and Enniscorthy