Gwillim Law | 14 Jan 17:45 2015
Picon

[tz] Fwd: Quintana Roo change to EST?

My translation of the cited article:

"... the new time zone will come into effect at two o'clock on the first Sunday of February, when we will have to advance the clock one hour from its current time, ...

"Federal deputy Lizbeth Gamboa Song stated that a new change for the month of April is not considered as yet, given that only the State will advance to summer time.

"Nevertheless, the deputy noted that Summer Time has applied in Mexico since 1996, to which all entities of the federation adhere, advancing their clocks one hour. In addition, she noted that it is yet unknown whether Quintana Roo will participate in a further change, but if so, the authorities will officially publish that fact in due time."

My Spanish is not native level, but I think the article makes it clear that the decision about DST for Quintana Roo has not yet been made.

Gwillim Law

On Wed, Jan 14, 2015 at 10:43 AM, Steffen Thorsen <thorsen <at> timeanddate.com> wrote:
On 08/12/14 14:18 , Steffen Thorsen wrote:
The Mexican state of Quintana Roo will likely change to EST in 2015, by not
going back from DST in October 2015. Its a bit unclear if they will still observe
DST the years after.
According to this source, Quintana Roo will change to EST as soon as 1 February 2015 at 2am:
http://sipse.com/novedades/confirman-aplicacion-de-nueva-zona-horaria-para-quintana-roo-132331.html

Through Google Translate, it says "According to the authorities, the term of the new time zone start at two o'clock on the first Sunday of February, when we brought forward one hour actual[?] hours, so the clock will be three o'clock."

Also, the new zone will not use DST.


Best regards,
Steffen Thorsen - timeanddate.com


Matt Johnson | 8 Jan 05:14 2015
Picon

[tz] Arizona will consider adopting daylight saving time

Numerous sources are reporting that the Arizona State Legislature will be
considering a bill to enact daylight saving time.
http://blogs.phoenixnewtimes.com/valleyfever/2015/01/arizona_lawmakers_propo
se_adopting_daylight_savings_time.php
http://www.bizjournals.com/phoenix/news/2015/01/07/spring-ahead-law-proposes
-daylight-saving-time-for.html
http://www.abc15.com/news/state/new-bill-could-put-az-on-daylight-saving-tim
e

The official link to the bill is here:
http://www.azleg.gov/DocumentsForBill.asp?Session_ID=114&Bill_Number=HB2014

Tim Parenti | 7 Jan 22:19 2015

Re: [tz] Positive leap second on 2015-06-30.

Denis,

This error was present in the leap-seconds.3629404800 file as provided by NIST.  I have copied Judah Levine on this message so that it might be fixed in their next version.

On 7 January 2015 at 16:15, Denis Excoffier <iana <at> denis-excoffier.org> wrote:
On 2015-01-06 21:22, Tim Parenti wrote:

> +#    Some systems implement leap seconds by amortizing the leap second
> +#    over the last few minutes of the day. The frequency of the local
> +#    clock is decreased (or increased) to realize the positive (or
> +#    negative) leap second. This method removes the time step described
> +#    above. Although the long-term behavior of the time scale is correct
> +#    in this case, this method introduces an error during the adjustment
> +#    period both in time and in frequency with respect to the official
> +#    defintion of UTC.

s/defintion/definition/

Regards,

Denis Excoffier.



--
Tim Parenti
J-F Rivard | 6 Jan 01:26 2015
Picon

[tz] Time zone reference inconsistencies

To whom it may be of interest:

The time zone rule files referred to following locations that are not found in "zone1970.tab":

 America/Montreal
 America/Antigua
 America/Cayman
 Asia/Bahrain
 Asia/Kuwait
 Asia/Muscat
 Asia/Aden
 Pacific/Saipan
 Pacific/Midway

Note: some (if not all) of the above-listed locations are found in "zone.tab", but the documentation states that "zone1970.tab" should be used instead.

Thank you for your excellent (and much appreciated!) work. Happy new year 2015!

J-F Rivard


J-F Rivard | Consultant | T:450.653.2912 | C:438.495.2912
Tim Parenti | 6 Jan 21:27 2015

[tz] Positive leap second on 2015-06-30.

Per IERS Bulletin C49 (2015-01-05), a positive leap second will be 
observed on 2015-06-30. The attached patch updates leap-seconds.list 
from NIST, retrieved from <ftp://time.nist.gov/pub/leap-seconds.3629404800>.

-- 
Tim Parenti

From d6003a7c91eb5267e60cb28e96e31be24b6eab57 Mon Sep 17 00:00:00 2001
From: Tim Parenti <tim <at> timtimeonline.com>
Date: Tue, 6 Jan 2015 15:22:41 -0500
Subject: Positive leap second on 2015-06-30.

* leap-seconds.list: Per IERS Bulletin C49 (2015-01-05), a positive leap
second will be inserted into the UTC time scale at the end of
2015-06-30.  Update file from NIST, retrieved from
<ftp://time.nist.gov/pub/leap-seconds.3629404800>.
---
 leap-seconds.list | 24 +++++++++++++++++-------
 1 file changed, 17 insertions(+), 7 deletions(-)
 mode change 100644 => 100755 leap-seconds.list

diff --git a/leap-seconds.list b/leap-seconds.list
old mode 100644
new mode 100755
index 0980e7b..17c0466
--- a/leap-seconds.list
+++ b/leap-seconds.list
 <at>  <at>  -47,7 +47,7  <at>  <at> 
 #	and can be ignored for many purposes. These differences
 #	are tabulated in Circular T, which is published monthly
 #	by the International Bureau of Weights and Measures
-#	(BIPM). See www.bipm.fr for more information.
+#	(BIPM). See www.bipm.org for more information.
 #
 #	3. The current definition of the relationship between UTC
 #	and TAI dates from 1 January 1972. A number of different
 <at>  <at>  -127,6 +127,15  <at>  <at> 
 #	with, since the difficulty of unambiguously representing the epoch
 #	during the leap second does not arise.
 #
+#	Some systems implement leap seconds by amortizing the leap second
+#	over the last few minutes of the day. The frequency of the local
+#	clock is decreased (or increased) to realize the positive (or
+#	negative) leap second. This method removes the time step described
+#	above. Although the long-term behavior of the time scale is correct 
+#	in this case, this method introduces an error during the adjustment 
+#	period both in time and in frequency with respect to the official 
+#	defintion of UTC.
+#
 #	Questions or comments to:
 #		Judah Levine
 #		Time and Frequency Division
 <at>  <at>  -134,7 +143,7  <at>  <at> 
 #		Boulder, Colorado
 #		Judah.Levine <at> nist.gov
 #
-#	Last Update of leap second values:   11 January 2012
+#	Last Update of leap second values:   5 January 2015
 #
 #	The following line shows this last update date in NTP timestamp
 #	format. This is the date on which the most recent change to
 <at>  <at>  -142,7 +151,7  <at>  <at> 
 #	be identified by the unique pair of characters in the first two
 #	columns as shown below.
 #
-#$	 3535228800
+#$	 3629404800
 #
 #	The NTP timestamps are in units of seconds since the NTP epoch,
 #	which is 1 January 1900, 00:00:00. The Modified Julian Day number
 <at>  <at>  -190,10 +199,10  <at>  <at> 
 #	current -- the update time stamp, the data and the name of the file
 #	will not change.
 #
-#	Updated through IERS Bulletin C48
-#	File expires on:  28 June 2015
+#	Updated through IERS Bulletin C49
+#	File expires on:  28 December 2015
 #
-# <at> 	3644438400
+# <at> 	3660249600
 #
 2272060800	10	# 1 Jan 1972
 2287785600	11	# 1 Jul 1972
 <at>  <at>  -221,6 +230,7  <at>  <at> 
 3345062400	33	# 1 Jan 2006
 3439756800	34	# 1 Jan 2009
 3550089600	35	# 1 Jul 2012
+3644697600	36	# 1 Jul 2015
 #
 #	the following special comment contains the
 #	hash value of the data in this file computed
 <at>  <at>  -236,4 +246,4  <at>  <at> 
 #	the hash line is also ignored in the
 #	computation.
 #
-#h	a4862ccd c6f43c6 964f3604 85944a26 b5cfad4e
+#h	45e70fa7 a9df2033 f4a49ab0 ec648273 7b6c22c
--

-- 
2.1.1

Arthur David Olson | 1 Jan 00:52 2015
Picon

[tz] Time zones in the news

(The article covers the traditional 24 time zones rather than those of TZDB.)

    <at> dashdashado


Paul Eggert | 17 Dec 19:11 2014

Re: [tz] [Tzdist] Getting to closure Re: [tzdist] #31 (service): Include leap seconds?

On 12/17/2014 06:55 AM, Martin Burnicki wrote:
>
> 2.) We have the leap second file from TZ DB. This file has a different 
> format than the NIST file, but as far as I can see is simply generated 
> from a file in NIST format by a script which is part of the TZ DB 
> package. Unfortunately the expiration date is *not* migrated into the 
> TZ DB's leap second file, so some important information is lost.
>

Thanks for reporting this.  I have installed the attached fix in the 
experimental tz sources on github and it should appear in the next tz 
release.  I am cc'ing the tz mailing list to give them a heads-up.

> 3.) We have a leap second file from IERS, which is once more in a 
> different format than the ones mentioned above.
>
> In my opinion the IERS should be the authoritative source for a leap 
> second file (or table) since this is the institution deciding whether 
> a leap second is to be scheduled,

I would prefer this also.  However, the IERS file is copyrighted. That 
is why the tz database reproduces the NIST file (the NIST file is public 
domain).  Other distributors of the IERS file might want to keep this in 
mind.

Amusingly enough, the NIST file's expiration date disagrees with the 
IERS's.  As a practical matter the NIST's date is more conservative and 
is a better choice for applications like tz and tzdist and this is 
another argument for using the NIST file.

Perhaps someday the IERS will address these two concerns.
Naveed Shakur | 16 Dec 06:58 2014

[tz] Info regarding TZ database

Good day
My name is Naveed and I have some query regarding the TZ database, is it possible to query the timezone database maintained by IANA or any other possible solution to have a local copy of the same at our own premises, we have to integrate with our in-house application with timezone information.
 
Best Regards and Thank You
Naveed Shakur.
 
Ken Murchison | 12 Dec 14:50 2014
Picon

[tz] US Sep 30, 1945

All,

I'm wondering why the US rule for Sep 30, 1945 uses an explicit date 
rather than lastSun, where it would dovetail nicely into the existing 
rules for America/New_York, Chicago, Indiana/Indianapolis (and maybe 
others) which cover 1946-1954.

The only reason that I care is because when converting the TZ data into 
iCalendar VTIMEZONEs with vzic, the dst->std transition for 1945 doesn't 
get coalesced into the recurrence rule for 1946-1954. I won't bother 
going into the reason for how/why vzic isn't able to coalesce these, but 
I'm pretty sure that it would take a non-trivial amount of 
work/logic/code to fix it.

--

-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University

John Madziarczyk | 10 Dec 23:01 2014
Picon

[tz] U.S. 1946-1966 dst

Hi, 

I apologize is this question has been asked many times before, but is there any publication out there that lists all the observances and non-observances of Daylight Savings Time in the U.S. in the years between the end of World War II and the Uniform Time Act? 

John Madziarczyk
Steffen Thorsen | 8 Dec 14:18 2014

[tz] Quintana Roo change to EST?

The Mexican state of Quintana Roo will likely change to EST in 2015, by not
going back from DST in October 2015. Its a bit unclear if they will 
still observe
DST the years after.

Some sources in Spanish:
http://sipse.com/novedades/reconocen-el-trabajo-de-empresarios-con-cambio-de-huso-horario-126236.html
http://www.unioncancun.mx/articulo/2014/12/04/medio-ambiente/congreso-aprueba-una-hora-mas-de-sol-en-qroo

We have summed up the info in English here:
http://www.timeanddate.com/news/time/mexico-quintana-roo-time-zone.html

Best regards,
Steffen Thorsen - timeanddate.com


Gmane