<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 01/06/14 18:03, Joris Van den Bogaert wrote:
<blockquote cite="mid:F642B7C4065B46F1B0E62FDC8F05F3F1@WhizzitPC"
type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div dir="ltr">
<div style="font-size: 10pt; font-family: 'Arial'; color: rgb(0,
0, 0);">
<div>
<div style="FONT-SIZE: small; TEXT-DECORATION: none;
FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal;
COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline"><font
face="Arial" size="2">Hi Angel,</font></div>
</div>
<div>
<div style="FONT-SIZE: small; TEXT-DECORATION: none;
FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal;
COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline"> </div>
</div>
<div>
<div style="FONT-SIZE: small; TEXT-DECORATION: none;
FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal;
COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline"><font
face="Arial" size="2">> </font>Matching geo data to
a timezone is a bit fuzzy. On the <br>
> other hand, you state that correct calculation is
critical.<br>
</div>
</div>
<div>
<div style="FONT-SIZE: small; TEXT-DECORATION: none;
FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal;
COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline"><font
face="Arial" size="2">We’re working with old protocols
that don’t include TZ information in the data that is
sent to us, so we have to get thet TZ info through geo
mapping tables.</font></div>
</div>
<div>
<div style="FONT-SIZE: small; TEXT-DECORATION: none;
FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal;
COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline"><font
face="Arial" size="2">We’ve been looking at
geopostcodes.com. </font></div>
</div>
</div>
</div>
</blockquote>
I would evaluate switching the software to start reporting in UTC
after some epoch (2015-01-01? 2014-07-01?).<br>
<br>
<blockquote cite="mid:F642B7C4065B46F1B0E62FDC8F05F3F1@WhizzitPC"
type="cite">
<div dir="ltr">
<div style="font-size: 10pt; font-family: 'Arial'; color: rgb(0,
0, 0);">
<div>
<div style="FONT-SIZE: small; TEXT-DECORATION: none;
FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal;
COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline"><font
face="Arial" size="2">We’d like it to be as correct as
possible, but realize it’s not possible to cover
everything. </font></div>
</div>
<div>
</div>
<div>
<div style="FONT-SIZE: small; TEXT-DECORATION: none;
FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal;
COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline"><font
face="Arial" size="2">Eg. 2014-10-26T02:05:00 may refer
to 2014-10-26T02:05:00.000+02:00 or
2014-10-26T02:05:00.000+01:00</font></div>
</div>
</div>
</div>
</blockquote>
Right. Tha local time alone is ambiguous.<br>
Although I was thinking in cases of "We are not sure if this Valley
uses the timezone of the town 10 Km North or the one 8 Km South"<br>
As you now clarified that you are dealing with «recent» events,
that's unlikely to happen. Actually, you may be able to tag each
source with the tzid.<br>
<br>
<br>
<blockquote cite="mid:F642B7C4065B46F1B0E62FDC8F05F3F1@WhizzitPC"
type="cite">
<div dir="ltr">
<div style="font-size: 10pt; font-family: 'Arial'; color: rgb(0,
0, 0);">
<div>
<div> > Now I'm thinking that perhaps you aren't working
on historic <br>
> records but with future ones, in which case it's very
likely that<br>
> tz will be right (but in that case why not store them
in UTC directly?)<br>
</div>
<div>Our data is all about real-time events, but when
reports need to be regenerated for some reason in the
future, they will be historic. Hence the questions about
tz versions.</div>
</div>
</div>
</div>
</blockquote>
If you convert them properly to UTC today, then you won't need them
regenerated in the future. There is a big difference between
processing what happened 40 years ago and what is happening right
now. Nowadays, you can easily know your offset.<br>
<br>
Cheers<br>
<br>
</body>
</html>