tz database

The tz database partitions the world into regions where local clocks all show the same time. This map was made by combining version 2023d of theList of tz database time zoneswithOpenStreetMapdata, using open source software.

Thetz databaseis a collaborative compilation of information about the world'stime zonesand rules for observingdaylight saving time,primarily intended for use with computer programs and operating systems.Paul Eggert has been its editor and maintainer since 2005,with the organizational backing ofICANN.The tz database is also known astzdata,thezoneinfo databaseor theIANA time zone database(after theInternet Assigned Numbers Authority), and occasionally as theOlson database,referring to the founding contributor, Arthur David Olson.

Its uniform naming convention for entries in the database, such asAmerica/New_YorkandEurope/Paris,was designed by Paul Eggert.The database attempts to record historical time zones and all civil changes since 1970, theUnix timeepoch.It also recordsleap seconds.

The database, as well as some referencesource code,is in thepublic domain.New editions of the database and code are published as changes warrant, usually several times per year.

Data structure

Definition of a timezone

Within the tz database, atimezoneis any national region where local clocks have all agreed since 1970.This definition concerns itself first with geographic areas which have had consistent local clocks. A timezone is different from a region with a particularstandard timeoffset from UTC,which is often referred to as a "time zone". Therefore, each of the timezones defined by the tz database may use multiple offsets from UTC, such as offsets for standard time anddaylight saving time.

File formats

The tz database is published as a set oftext fileswhich list the rules and zone transitions in a human-readable format. For use, these text files arecompiledinto a set of platform-independentbinary files—one per timezone. The reference source code includes such a compiler calledzic(zone information compiler), as well as code to read those files and use them in standardAPIssuch aslocaltime()andmktime().

Timezones

Each timezone has one or more "zone lines" in one of the tz database text files. The first zone line for a timezone gives the name of the timezone; any subsequent zone lines for that timezone leave the name blank, indicating that they apply to the same zone as the previous line. Each zone line for a zone specifies, for a range of date and time, theoffset to UTCfor standard time, the name of the set of rules that governdaylight saving time(or a hyphen if standard time always applies), the format for time zone abbreviations, and, for all but the last zone line, the date and time at which the range of date and time governed by that line ends.

Daylight saving time (DST) rules

The rules fordaylight saving timeare specified in named rule sets. Each rule set has one or more rule lines in the text files. A rule line contains the name of the rule set to which it belongs, the first year in which the rule applies, the last year in which the rule applies (or "only" if it applies only in one year or "max" if it is the rule then in effect), the type of year to which the rule applies ( "-" if it applies to all years in the specified range, which is almost always the case, otherwise a name used as an argument to a script that indicates whether the year is of the specified type), the month in which the rule takes effect, the day on which the rule takes effect (which could either be a specific day or a specification such as "the last Sunday of the month" ), the time of day at which the rule takes effect, the amount of time to add to theoffset to UTCwhen the rule is in effect, and the letter or letters to use in the time zone abbreviation (for example, "S" if the rule governs standard time and "D" if it governs daylight saving time).

Names of timezones

The timezones have unique names in the form "Area/Location",e.g." America/New_York ". A choice was also made to use English names or equivalents, and to omit punctuation and common suffixes. The underscore character is used in place of spaces. Hyphens are used where they appear in the name of a location. TheAreaandLocationnames have a maximum length of 14 characters.

Area

Areais the name of acontinent,anocean,or "Etc". The continents and oceans used areAfrica,America,Antarctica,Arctic,Asia,Atlantic,Australia,Europe,Indian,andPacific.

The oceans are included since some islands are hard to connect to a certain continent. Some are geographically connected to one continent and politically to another. See alsoBoundaries between continents.

The special area of "Etc" is used for some administrative zones, particularly for "Etc/UTC" which representsCoordinated Universal Time.In order to conform with thePOSIXstyle, those zone names beginning with "Etc/GMT" have their sign reversed from the standardISO 8601convention. In the "Etc" area, zones west of GMT have a positive sign and those east have a negative sign in their name (e.g "Etc/GMT-14" is 14 hours ahead of GMT).

Location

Locationis the name of a specific location within the area – usually a city or small island.

Country names are not normally used in this scheme, primarily because they would not be robust, owing to frequent political and boundary changes. The names of large cities tend to be more permanent.Usually the most populous city in a region is chosen to represent the entire timezone, although another city may be selected if it is more widely known, and another location, including a location other than a city, may be used if it results in a less ambiguous name.In the event that the name of the location used to represent the timezone changes, the convention is to create an aliasin future editions so that both the old and new names refer to the same database entry.

In some cases theLocationis itself represented as a compound name, for example the timezone "America/Indiana/Indianapolis". Three-level names include those under "America/Argentina/...", "America/Kentucky/...", "America/Indiana/...", and "America/North_Dakota/...".

The location selected is representative for the entire area. However, if there were differences within the area before 1970, the time zone rules only apply in the named location.

Examples

Name	Explanation
America/Costa_Rica	name of country used because the name of the largest city (and capital city)San Joséisambiguous
America/New_York	Space replaced with underscore
Asia/Kolkata	name of city ofKolkataused, because it was the most populous city in the zone at the time the zone was set up, though this is no longer true
Asia/Sakhalin	name of island used, because largest city,Yuzhno-Sakhalinsk,has more than 14 characters
America/Bahia_Banderas	"de" removed fromBahia de Banderas,because correct name has more than 14 characters
Antarctica/DumontDUrville	the apostrophe is removed. The space would normally be replaced with "_", but the name would then exceed 14 characters.

Example zone and rule lines

These are rule lines for the standard United States daylight saving time rules, rule lines for the daylight saving time rules in effect in the USEastern Time Zone(called "NYC" asNew York Cityis the city representing that zone) in some years, and zone lines for the America/New_York timezone, as of release versiontzdata2011nof the time zone database. The zone and rule lines reflect thehistory of DST in the United States.

# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
Rule US 1918 1919 - Mar lastSun 2:00 1:00 D
Rule US 1918 1919 - Oct lastSun 2:00 0 S
Rule US 1942 only - Feb 9 2:00 1:00 W # War
Rule US 1945 only - Aug 14 23:00u 1:00 P # Peace
Rule US 1945 only - Sep 30 2:00 0 S
Rule US 1967 2006 - Oct lastSun 2:00 0 S
Rule US 1967 1973 - Apr lastSun 2:00 1:00 D
Rule US 1974 only - Jan 6 2:00 1:00 D
Rule US 1975 only - Feb 23 2:00 1:00 D
Rule US 1976 1986 - Apr lastSun 2:00 1:00 D
Rule US 1987 2006 - Apr Sun>=1 2:00 1:00 D
Rule US 2007 max - Mar Sun>=8 2:00 1:00 D
Rule US 2007 max - Nov Sun>=1 2:00 0 S
....
# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER
Rule NYC 1920 only - Mar lastSun 2:00 1:00 D
Rule NYC 1920 only - Oct lastSun 2:00 0 S
Rule NYC 1921 1966 - Apr lastSun 2:00 1:00 D
Rule NYC 1921 1954 - Sep lastSun 2:00 0 S
Rule NYC 1955 1966 - Oct lastSun 2:00 0 S
# Zone NAME GMTOFF RULES FORMAT [UNTIL]
Zone America/New_York -4:56:02 - LMT 1883 November 18, 12:03:58
-5:00 US E%sT 1920
-5:00 NYC E%sT 1942
-5:00 US E%sT 1946
-5:00 NYC E%sT 1967
-5:00 US E%sT

Data stored for each zone

For each timezone that has multiple offsets (usually due to daylight saving time), the tz database records the exact moment of transition. The format can accommodate changes in the dates and times of transitions as well. Zones may have historical rule changes going back many decades (as shown in the example above).

Zone.tab

The filezone.tabis in the public domain and lists the zones. Columns and row sorting are described in the comments of the file, as follows:

# This file contains a table with the following columns:
# 1.ISO 3166 2-character country code.See the file `iso3166.tab'.
# 2. Latitude and longitude of the zone's principal location
# inISO 6709sign-degrees-minutes-seconds format,
# either +-DDMM+-DDDMM or +-DDMMSS+-DDDMMSS,
# first latitude (+ is north), then longitude (+ is east).
# 3. Zone name used in value of TZ environment variable.
# 4. Comments; present if and only if the country has multiple rows.
#
# Columns are separated by a single tab.
# The table is sorted first by country, then an order within the country that
# (1) makes some geographical sense, and
# (2) puts the most populous zones first, where that does not contradict (1).

Data before 1970

Data before 1970 aims to be correct for the city identifying the region, but is not necessarily correct for the entire region. This is because new regions are created only as required to distinguish clocks since 1970.

For example, between 1963-10-23 and 1963-12-09 in Brazil only the states ofMinas Gerais,Espirito Santo,Rio de Janeiro,andSão Paulohad summer time. However, a requested split fromAmerica/Sao_Paulowas rejected in 2010 with the reasoning that, since 1970, the clocks were the same in the whole region.

Time in Germany,which is represented byEurope/Berlin,is incorrect for the year 1945 when theTrizoneused daylight saving time rules different from Berlin's.

Coverage

Zones covering multiple post-1970 countries

There are two zones that cover an area that was covered by two countries after 1970. The database follows the definitions of countries as perISO 3166-1,whose predecessor, ISO 3166, was first published in 1974.

• Asia/Aden– two countries until 1990:North Yemen(ISO 3166-1:YE; capital Sana'a) andSouth Yemen(People's Republic, ISO 3166-1: YD,ISO 3166-3:YDYE; capital: Aden).
• Europe/Berlin– two countries until1990:East Germany(ISO 3166-1: DD, ISO 3166-3: DDDE) andWest Germany(ISO 3166-1: DE)

Maintenance

The tz reference code and database is maintained by a group of volunteers. Arthur David Olson makes most of the changes to the tz reference code. Paul Eggert makes most of the changes to the tz database. Proposed changes are sent to the tz mailing list, which is gatewayed to the comp.time.tzUsenet newsgroup.Source files are distributed via the IANA FTP server. Typically, these files are taken by a software distributor likeDebian,compiled, and then the source and binaries are packaged as part of that distribution. End users can either rely on their software distribution's update procedures, which may entail some delay, or obtain the source directly and build the binary files themselves. TheIETFhas publishedRFC6557,"Procedures for Maintaining the Time Zone Database" documenting best practices based on similar principles.

Unix-like systems

The standard path for the timezone database is/usr/share/zoneinfo/in Linux distributions,macOS,and some otherUnix-likesystems.

Usage and extensions

Boundaries of timezones

Geographical boundaries in the form of coordinate sets are not part of the tz database, but boundaries are published by Evan SirokyinGeoJSONandshapefileformats.

Use in other standards

The UnicodeCommon Locale Data Repository(CLDR) refers to zones in the tz database. However, as the name for a zone can change from one tz database release to another, the CLDR assigns theUN/LOCODEfor the city used in the name for the zone, or an internally-assigned code if there is no such city for the zone, to a tzdb zone.

Use in software systems

The tz database is used for time zone processing and conversions in many computer software systems, including:

• BSD-derived systems, includingFreeBSD,NetBSD,OpenBSD,DragonFly BSD,macOS,andiOS(they also use the reference TZ database processing code as their TZ POSIX API implementation);
• theGNU C Libraryand systems that use it, includingGNU,mostLinux distributions,BeOS,Haiku,Nexenta OS,andCygwin;
• System V Release 4-derived systems, such asSolarisandUnixWare;
• AIX6.1 and later(earlier versions of AIX, starting with AIX 5.2, include zoneinfo,for support of third-party applications such asMySQL,but do not use it themselves);
• Android
• several otherUnixsystems, includingIRIX,Tru64,SunOS4.x,andUNICOS/mp;
• OpenVMS;
• theJava Runtime Environmentsince release 1.8 (2014), seejava.time.ZoneId
• thePerlmodulesDateTime::TimeZoneandDateTime::LeapSecondsince 2003;
• PHPreleases since 5.1.0 (2005);
• theRubyGemTZInfo;
• thePythonstandard libraryzoneinfomodule, and the third-partypytzpackage;
• theJavaScriptlanguage specification for Internationalization explicitly specifies the usage of IANA Time Zone names for API, and recommends the usage of the time zone data as well.
  • Numerous libraries also available:timezone-js,BigEasy/TimeZone,WallTime-jsandmoment-timezone;
• the Pandas (Python) modulepandas – Python Data Analysis Library;
• the.NET FrameworklibrariesNodaTime,TZ4NetandzoneinfoArchived24 December 2017 at theWayback Machine;
• theHaskelllibrariestimezone-seriesandtimezone-olson;
• theErlangmoduleezic;
• TheGostandard librarytimepackage;
• TheRustcratechrono-tz;
• TheSqueakSmalltalktimepackage;
• TheC++librariesBoostandQt,andC++20chrono standard library'sstd::chrono::tzdb;
• TheDelphiandFree PascallibraryTZDB;
• TheFree PascallibraryPascalTZ;
• TheTool Command Languagehas aclock commandusing tzdata;
• Oraclereleases since 10g (2004);
• PostgreSQLsince release 8.0 (2005);
• theMicrosoft SQL ServerlibrarySQL Server Time Zone Support
• MongoDBsince release 3.6;
• theDart/FlutterTimezone package in pub;
• embedded software such as the firmware used in IP clocks.

The Olson timezone IDs are also used by the UnicodeCommon Locale Data Repository(CLDR) andInternational Components for Unicode(ICU). For example, the CLDR Windows–Tzid table maps Microsoft Windows time zone IDs to the standard Olson names, although such a mapping cannot be perfect because the number of time zones in Windows systems is significantly lower than in the IANA TZ database.

History

The project's origins go back to 1986 or earlier.

2011 lawsuit

On 30 September 2011, a lawsuit,Astrolabe, Inc. v. Olson et al.,was filed concerningcopyrightin the database.As a result, on 6 October 2011, the database's mailing list andFTPsite were shut down.The case revolved around the database maintainers' use ofThe American Atlas,byThomas G. Shanks,andThe International Atlas,by Thomas G. Shanks and Rique Pottenger. It complained of unauthorised reproduction of atlas data in the timezone mailing list archive and in some auxiliary link collections maintained with the database, though it did not actually point at the database itself. The complaint related only to the compilation of historical timezone data, and did not cover extant tzdata world timezone tables.

This lawsuit was resolved on 22 February 2012 after the involvement of theElectronic Frontier Foundation,when Astrolabe voluntarilymoved to dismissthe lawsuit without having everservedthe defendants and agreed to a covenant not to sue in the future.

Move to ICANN

ICANNtook responsibility for the maintenance of the database on 14 October 2011.The full database and a description of plans for its maintenance are available online fromIANA.

See also

• List of tz database time zones
• Time zone
• Daylight saving time

External links

General

• Legal time(PDF),ITU, 2015.
• The tz database home page,UCLA(deprecated, see Official IANA sources below)
• The tz mailing list archive,Gmane, archived fromthe originalon 3 February 2008.
• tz(archive)(mailing list).
• tz mailing list at ICANN
• "A literary appreciation of the Olson/Zoneinfo/tz database"byJon Udell

Official IANA sources

• Home page
• FTP
• rsync,at rsync://rsync.iana.org/tz/

Man pages

• zic(8)–LinuxAdministration and Privileged CommandsManual(gives the syntax of source files for the tz database)
• tzfile(5)–LinuxFile FormatsManual(gives the format of compiled tz database files)