Could you clarify *exactly *how you derived your table, in terms of the IANA data? If you look at https://nodatime.org/tzvalidate/generate?version=2019c&zone=Europe/Istanbul - which is generated from IANA data - it shows DST changes stopping in September 2016, just as you said. Likewise if you look at the current source data <https://github.com/eggert/tz/blob/1a27ec76bc436a64070461bbbf28e0511c7cf3b8/e...>, you'll see the same result. I suspect this is a problem of data interpretation rather than anything else. Jon On Mon, 2 Dec 2019 at 17:32, Benjamin Weiser <Benjamin.Weiser@inrix.com> wrote:
Hello,
I’d like to report your downloads for the following Time Zones from this URL on your site are out of date: https://www.iana.org/time-zones
For instance Europe/Istanbul moved to UTC 3 permanently in September of 2016 and no longer follow DST.
I will place the correct times first, and then the incorrect IANA times second. Highlighted in orange have the incorrect time zone information (0 means there is no DST, 1 means they follow DST)
TimeZone
UTC Offset
ObservesDST
IANA_UTC_offset:
IANA_ObservesDST:
America/Campo_Grande
-4
0
-4
1
America/Sao_Paulo
-3
0
-3
1
America/St_Johns
-3.5
1
-3
1
Asia/Sakhalin
11
0
10
0
Australia/Adelaide
9.5
1
9
1
Australia/Darwin
9.5
0
9
0
Australia/Lord_Howe
10.5
1
10
1
Europe/Istanbul
3
0
2
1
Indian/Cocos
6.5
0
6
0
Pacific/Chatham
12.75
1
12
1
Thanks.