dmfilipenko / timezones.json Goto Github PK

A lot of the Russian time zones are out of date. The UTC offsets are for their 2011 to 2014 DST-365 rules. They are now standard time 365, so each of those time zones is one hour off in its offset.

There are two timezones with the same value "GMT Standard Time"

• change to summer time.

The file currently state 'CUT' as the abbreviation for Coordinate Universal Time, while the consensus is to abbreviate it as UTC. I have not yet seen any systems using 'CUT'.

Also, could you clarify the source for this data or how it is collected?

Incorrect offset or abbr

    "value": "Alaskan Standard Time",
    "abbr": "AKDT",
    "offset": -8,
    "isdst": true,
    "text": "(UTC-09:00) Alaska"

AKDT is Alaska Daylight Time with offset equal to UTC -8
AKST is Alaska Standard Time with offset equal to UTC -9

Suggest splitting this item in timezones array to two different items for AKDT and AKST

The following timezones are missing the utc property:

Mid-Atlantic Standard Time

E. Europe Standard Time

Kaliningrad has UTC+2 instead of UTC+3

i am using this timezone json file to find the short name for any time zone like IST for India Standard Time.

I get the 'New Zealand Standerd Time' from the JavaScript function before March. But now JavaScript return 'New Zealand Daylight Time' which is not there in Json and this is same for all other timezone which are now in 'Daylight' time

"ADT", "AST", "BST", "CAST", "CDT", "CEDT", "CST", "EAST", "GDT", "JST", "KST", "MDT", "MST", "NST", "PDT", "SAST", "TST", "U", "VST", "WAST"

It looks like for many of the timezones, the value and text properties reflect the values for standard time, whereas the abbr and offset properties refect the values for DST.

For example, for Eastern Standard Time, value === 'Eastern Standard Time' and text has an offset of UTC-05:00, which are the correct values for standard time. However, offset === -4, and abbr === 'EDT', which stands for Eastern Daylight Time.

Hello,
In timezone json we are not maintaining old IANA equivalents e.g. "Asia/Calcutta" is old IANA name for Indian standard time and the new name is "Asia/Kolkata" but library like moment.js and luxon maintaining old and new both IANA names and also it provides old zone name value in their datetime obj which lead us mismatching data between timezones.json and moment zoneNames because timezones.json not maintaining old IANA equivalents so is it possible to keep both new and old IANA equivalents in timezones.json?

AEDT is the DST for the likes of Australia/Sydney.

https://en.m.wikipedia.org/wiki/Daylight_saving_time_in_Australia
https://www.timeanddate.com/time/zone/australia/sydney

London is GMT, so it should have an offset of 0.

I can only guess that any item listed "isdst": true is also doubling for when it is "isdst": false please confirm that this is how you intended.

Operating system do not use Greenwich Mean Time. They use GMT Standard Time specially windows OS. https://support.microsoft.com/en-us/help/973627/microsoft-time-zone-index-values. This is causing application to break-down in various other operating systems as well.

#30

Since when is EST Egypt Standard Time? Isn't is Eastern Standard Time?

Hello,

Loking into the values you have stored here, I found that some of them are deprecated (non canonicals). What is the plan for getting those values updated?

The abbreviations concerning "Central European Time" (CET) (UTC+01:00) and "Central European SUMMER Time" (CEST) (UTC+02:00) are wrong in your list. Never seen anybody refer to it as Romance Standard Time (RST)!

https://en.wikipedia.org/wiki/Central_European_Time

Also many longform codes are missing like "Europe/Vienna".

https://github.com/dmfilipenko/timezones.json/blame/f7a689832fab3c230cf2948899a6b05fac0d1332/timezones.json#L625C16-L625C16

I have noticed that whatever time zone I place in the request parameters, the time remains the same (local time in Morocco).

Example: https://www.prayertimes.mahmoud.ma/api/80/today?timezone=Pacific/Midway
Test date: Sat, 18. Sept 2021 - 12:02 pm
Result: {"fajr":"05:47","sunrise":"07:13","dohr":"13:30","asr":"16:54","maghreb":"19:37","ichaa":"20:51"}

Any ideas where the issue resides?

You need to publish the version 1.0.0 to NPM. The package there is missing the index.js file.

It should be Asia/Kathmandu not Asia/Katmandu

For example in the (UTC-06:00) Guadalajara, Mexico City, Monterrey case, those properties has differents values, I mean has the next values below:

name: (UTC-06:00) Guadalajara, Mexico City, Monterrey
offset: -5

The correct offset property value should be: -6 as we can see in the name property.

Could you help me adding the correct values please?

49 different timezones has duplicated abbreviated timezones but has different offsets.
The list includes: ['ADT', 'AST', 'BST', 'CAST', 'CST', 'EAST', 'EST', 'GDT', 'JST', 'KST', 'MDT', 'MST', 'NST', 'SAST', 'TST', 'U', 'VST', 'WAST']
Also a lot of DST timezones aren't updated.

Mexico City just cancel summer time this year

Your timezone "UTC+4". But Moscow timezone "UTC+3"

For example:

 "value": "Eastern Standard Time",
    "abbr": "EDT",
    "offset": -4,
    "isdst": true,
    "text": "(UTC-05:00) Eastern Time (US & Canada)",

The offset -4 is correct for daylight time, but the text displays (UTC-5:00). Furthermore, EDT stands for Eastern Daylight Time not Eastern Standard Time. I see there are a lot of mismatches between offset and what is displayed in the text, so I don't think the data is correct.

Some of the places in the json file are placed in different timezones. Most of them are European places. One such instance is:

{
    "value": "Greenwich Mean Time",
    "abbr": "GMT",
    "offset": 0,
    "isdst": false,
    "text": "(UTC) Edinburgh, London",
    "utc": [
      "Europe/Isle_of_Man",
      "Europe/Guernsey",
      "Europe/Jersey",
      "Europe/London"
    ]
  },
  {
    "value": "British Summer Time",
    "abbr": "BST",
    "offset": 1,
    "isdst": true,
    "text": "(UTC+01:00) Edinburgh, London",
    "utc": [
      "Europe/Isle_of_Man",
      "Europe/Guernsey",
      "Europe/Jersey",
      "Europe/London"
    ]
  }

Is this intentional? Because that is breaking in UI, when I am trying to map to dropdown.

I’m wondering why CDT is not in the list.

as in the title