Time zone

A time zone is a region of the  that has adopted the same, usually referred to as the local time. Most adjacent time zones are exactly one hour apart, and by convention compute their local time as an offset from (see also ). Standard time zones can be defined by geometrically subdividing the Earth's into 24  (wedge-shaped sections), bordered by  each 15° of  apart. The local time in neighbouring zones would differ by one hour. However, political and geographical practicalities can result in irregularly-shaped zones that follow political boundaries or that change their time seasonally (as with ), as well as being subject to occasional redefinition as political conditions change.

There are variations of the definitions of time zone which generally fall into two meanings: a time zone can represent a region where the local time is some fixed offset from a global reference (usually UTC), or a time zone can represent a region throughout which the local time is always consistent even though the offset may fluctuate seasonally.

Before the adoption of time zones, people used local (originally apparent solar time, as with a ; and, later, mean solar time). Mean solar time is the average over a year of apparent solar time. Its difference from apparent solar time is the.

This became increasingly awkward as and s improved, because clocks differed between places by an amount corresponding to the difference in their geographical longitude, which was usually not a convenient number. This problem could be solved by synchronizing the clocks in all localities, but then in many places the local time would differ markedly from the solar time to which people are accustomed. Time zones are thus a compromise, relaxing the complex geographic dependence while still allowing local time to approximate the mean solar time. There has been a general trend to push the boundaries of time zones further west of their designated meridians in order to create a permanent daylight saving time effect. The increase in worldwide communication has further increased the need for interacting parties to communicate mutually comprehensible time references to one another.

Standard time zones
Earlier, time zones based their time on Greenwich Mean Time (GMT, also called ), the mean solar time at longitude 0° (the ). But as a mean solar time, GMT is defined by the rotation of the Earth, which is not constant in rate. So, the rate of s was annually changed or steered to closely match GMT. But on, it became fixed, using predefined s instead of rate changes. This new time system is (UTC). Leap seconds are inserted to keep UTC within 0.9 seconds of UT1. In this way, local times continue to correspond approximately to mean solar time, while the effects of variations in Earth's rotation rate are confined to simple step changes that can be easily subtracted if a uniform ( or TAI) is desired. With the implementation of UTC, nations began to use it in the definition of their time zones instead of GMT. As of 2005, most but not all nations have altered the definition of local time in this way (though many media outlets fail to make a distinction between GMT and UTC). Further change to the basis of time zones may occur if proposals to abandon leap seconds succeed.

Due to, UTC is local time at the only between 01:00 UTC on the last Sunday in October and 01:00 UTC on the last Sunday in March. For the rest of the year, local time there is, known in the as  (BST). Similar circumstances apply in many places.

The definition for time zones can be written in short form as UTC±n (or GMT±n), where n is the offset in hours. These examples give the local time at various locations at 12:00 UTC when daylight saving time (or summer time, etc.) is not in effect:
 * ,, : ; 04:00
 * , : ; 08:00
 * ,, : ; 07:00
 * , : ; 13:00
 * , : ; 14:00
 * ,, : UTC+5:30; 17:30
 * , : ; 21:00
 * , : ; 22:00

Where the adjustment for time zones results in a time at the other side of midnight from UTC, then the date at the location is one day later or earlier. Some examples when UTC is 23:00 on Monday when daylight saving time is not in effect: Some examples when UTC is 02:00 on Tuesday when daylight saving time is not in effect:
 * , : UTC+2; 01:00 on Tuesday
 * , : ; 11:00 on Tuesday
 * ,, United States: ; 21:00 on Monday
 * ,, United States: ; 16:00 on Monday

The time-zone adjustment for a specific location may vary because of Daylight Saving Time. For example New Zealand, which is usually, observes a one-hour daylight saving time adjustment during the summer, resulting in a local time of.

See also.

History
(GMT) was established in 1675, when the was built, as an aid to determine longitude at sea by mariners. The first time zone in the world was established by British on,  — with GMT hand-carried on s. About , , time signals were first transmitted by telegraph from the. Even though 98% of 's public clocks were using GMT by 1855, it was not made Britain's legal time until,. Some old clocks from this period have two minute hands &mdash; one for the local time, one for GMT. This only applied to the island of Great Britain, and not to the island of.

On, , (then a British colony) officially adopted a standard time to be observed throughout the colony, and was perhaps the first country to do so. It was based on the longitude 172° 30' East of, that is 11 hours 30 minutes ahead of GMT. This standard was known as.

Timekeeping on the American railroads in the mid nineteenth century was somewhat confused. Each railroad used its own standard time, usually based on the local time of its headquarters or most important terminus, and the railroad's train schedules were published using its own time. Some major railroad junctions served by several different railroads had a separate clock for each railroad, each showing a different time; the main station in, , for example, kept six different times. The confusion for travelers making a long journey involving several changes of train can be imagined.

proposed a system of one-hour standard time zones for American railroads about 1863, although he published nothing on the matter at that time and did not consult railroad officials until 1869. In 1870, he proposed four ideal time zones (having north–south borders), the first centered on, but by 1872 the first was centered 75°W of Greenwich, with geographic borders (for example, sections of the ). Dowd's system was never accepted by American railroads. Instead, U.S. and Canadian railroads implemented a version proposed William F. Allen, the editor of the Traveler's Official Railway Guide. The borders of its time zones ran through railroad stations, often in major cities. For example, the border between its Eastern and Central time zones ran through, , , , and. It was adopted on Sunday,, , also called "The Day of Two Noons", when each railroad station clock was reset as standard-time noon was reached within each time zone. The zones were named Intercolonial, Eastern, Central, Mountain, and Pacific. Within one year, 85% of all cities with populations over 10,000, about 200 cities, were using standard time. A notable exception was Detroit (which is about half-way between the meridians of eastern time and central time), which kept local time until 1900, then tried Central Standard Time,, and before a May 1915 ordinance settled on EST and was ratified by popular vote in August 1916. This hodgepodge ended when Standard zone time was formally adopted by the on   as the Standard Time Act.

Time zones were first proposed for the entire world by 's Sir in 1876 as an appendage to the single 24-hour clock he proposed for the entire world (located at the center of the Earth and not linked to any surface meridian). In 1879 he specified that his universal day would begin at the anti-meridian of Greenwich (now called 180°), while conceding that hourly time zones might have some limited local use. He continued to advocate his system at subsequent international conferences. In October 1884, the did not adopt his time zones because they were not within its purview. The conference did adopt a universal day of 24 hours beginning at Greenwich midnight, but specified that it "shall not interfere with the use of local or standard time where desirable".

Nevertheless, most major countries had adopted hourly time zones by 1929. Today, all nations use standard time zones for secular purposes, but they do not all apply the concept as originally conceived. , India, Iran, Afghanistan, Burma, the, as well as parts of Australia use half-hour deviations from standard time, and some nations, such as , and some provinces, such as the , use quarter-hour deviations.

Nautical time zones
Since the 1920s a system has been in operation for ships on the. Nautical time zones are an ideal form of the terrestrial time zone system. Under the system, a time change of one hour is required for each change of by 15°. The 15° gore that is offset from or  (not ) by twelve hours is bisected by the nautical date line into two 7.5° gores that differ from GMT by ±12 hours. A nautical date line is implied but not explicitly drawn on time zone maps. It follows the except where it is interrupted by  adjacent to land, forming gaps: it is a pole-to-pole dashed line.

A ship within the of any nation would use that nation's standard time, but would revert to nautical standard time upon leaving its territorial waters. The captain was permitted to change his ship's clocks at a time of his choice following his ship's entry into another time zone—he often chose midnight.

For airplanes, similar principles apply.

Skewing of zones
Ideal time zones, such as nautical time zones, are based on the mean solar time of a particular meridian located in the middle of that zone with boundaries located 7.5 degrees east and west of the meridian. In practice, zone boundaries are often drawn much farther to the west with often irregular boundaries, and some locations base their time on meridians located far to the east.

For example, even though the Prime Meridian (0°) passes through and, they use the mean solar time of 15 degrees east  rather than 0 degrees. France previously used GMT, but it was switched to CET during the German Occupation and did not switch back after the war.

There is a tendency to draw time zone boundaries far to the west of their meridians. Many of these locations also use daylight saving time which means that solar noon could occur later than 14:00 by the clock.

In a more extreme example, is at 165°24′W longitude, which is just west of center of the idealized  (165°W). Nevertheless, Nome observes  (135°W) with DST so it is slightly more than two hours ahead of the sun in winter and over three in summer.

Also, extends as far west as 73°34′E, but all parts of it use  (120°E), so noon can occur as late as 1:30 p.m.

Daylight saving time
Many countries, or even parts only of countries, adopt during part of the year. This typically involves advancing s by an near the start of  and adjusting back in. Some countries also use backward daylight saving over the winter period. Modern DST was first proposed in 1907 and was widespread use in 1916 as a measure aimed at. Despite controversy, many countries have used it since then; and change occasionally.

Additional info

 * has the largest number of time zones: eleven, including on the . In terms of distinct time zones, Canada and the United States are tied for second with six, while Australia has seven time zones that always overlap to some degree. See:
 * If the possessions of the, the and  are included it increases the number of time zones in each. Taking into account overseas territories and possessions, France has the most, with at least twelve time zones, followed by Australia with ten, the United States with nine and the United Kingdom with at least eight.
 * In terms of area, China is the largest country with only one time zone . Before the Communist control of the mainland in 1949 during the, China was separated into five time zones. China also has the widest spanning time zone. See:
 * Stations in generally keep the time of their supply bases, thus both the  (U.S.) and  (U.S.) use  time ( southern winter,  southern summer).
 * The 27° N latitude passes back and forth across time zones in South Asia. Pakistan: +5, India +5:30, Nepal +5:45, India +5:30, China +8:00, Bhutan +6:00, India  +5:30, Myanmar +6:30. This switching was more odd in 2002, when  enabled Daylight Saving Time. Thus from west to east, time zones were: +6:00, +5:30, +5:45, +5:30, +8:00, +6:00, +5:30 and +6:30.
 * Because the earliest and latest time zones are 26 hours apart, any given calendar date exists at some point on the globe for 50 hours. For example, begins in time zone  at 10:00 UTC, and ends in time zone  at 12:00 UTC.
 * There are numerous places where several time zones meet, for instance at the tri-country border of Finland, Norway and Russia.
 * There are about 39 time zones instead of 24 (as popularly believed). This is due to fractional hour offsets and zones with offsets larger than 12 hours near the . Some s may use offsets that are not recognized by all authorities.
 * The largest time gap along a political border is the 3.5 hour gap along the border of (UTC +8) and  (UTC+4:30).
 * One of the most unusual time zones is the Australian Central Western Time zone (CWST), which is a small strip of from the border of  west to E125.5°, just before .  It is 8¾ hours ahead of UTC (UTC+8:45) and covers an area of about 35,000 km², larger than Belgium, but has a population of about 200.  Although unofficial, it is universally respected in the area--as without it, the time gap in standard time at E129° (the WA/SA border) would be 1.5 hours. See.

Internet and computer systems
is used on the Internet for meetings (i.e. chats, news, shows and so on).

The format is based in the Note "datetime". On the other hand, most modern computer s include information about time zones, including the capability to automatically change the local time when daylight saving starts and finishes (see the article on for more details on this aspect).

NTP
The protocol used the most to synchronize time with multiple sources across the internet is (NTP). It operates across multiple platforms and there are a wide array of public servers available on the internet to synchronize with. Every server is normally kept updated with an belonging to the standards institution of each country. Normally a large organization has an internal server to keep time with one of the public NTP servers on the internet, and then this server acts as a proxy and becomes the official timekeeper for all organization machines. NTP is so popular now that virtually all -capable devices implement some degree of NTP client software.

Unix
Most systems, including  and, keep system time as UTC. Rather than having a single timezone set for the whole computer, timezone offsets can vary for different processes. Standard library routines are used to calculate the local time based on the current timezone, normally supplied to processes through the TZ. This allows users in multiple timezones to use the same computer, with their respective local times displayed correctly to each user. Timezone information is most commonly stored in a timezone database known as (or sometimes tz or Olson format). In fact, many systems, including anything using the, can make use of this database.

Microsoft Windows
based computer systems normally keep system time as local time in a particular time zone. A system database of timezone information includes the offset from UTC and rules that indicate the start and end dates for daylight saving in each zone. Application software is able to calculate the time in various zones, but there is no standard way for users from multiple zones to use a single server and have their own local time presented to them.

Smalltalk
Each dialect comes with its own built-in classes for dates, times and timestamps, only a few of which implement the DateAndTime and Duration classes as specified by the ANSI Smalltalk Standard. provides a TimeZone class that supports up to 2 annually-recurring offset transitions, which are assumed to apply to all years (same behavior as Windows time zones.)  provides a Timezone class that does not support any offset transitions. does not support time zones at all.

For full support of the  in a Smalltalk application (including support for any number of annually-recurring offset transitions, and support for different intra-year offset transition rules in different years) the third-party, open-source, ANSI-Smalltalk-compliant Chronos Date/Time Library is available for use with any of the following Smalltalk dialects: VisualWorks, Squeak or Dolphin.

Java
While most application software will use the underlying operating system for timezone information,, from version 1.3.1, has maintained its own timezone database. This database (as well as the operating system database) will need to be updated whenever timezone rules change.

One unfortunate problem is that the date of the start of daylight saving time was altered by the government for year 2000 to accommodate the. This altered date was included with the Sun.

Python
The standard module stores and operates on the timezone information class. The third party pytz module provides access to the full zoneinfo database.

Databases
Some s allow storage of a datetime type having time zone information. The standard defines two standard time data types:


 * TIMESTAMP WITH TIME ZONE
 * TIMESTAMP WITHOUT TIME ZONE

However the standard has a somewhat naive understanding of time zones. It generally assumes a time zone can be specified by a simple offset from GMT. This causes problems when trying to do arithmetic on dates which span daylight savings time transitions or which span political changes in time zone rules.

Oracle
Oracle Database is configured with a database time zone, and connecting clients are configured with session time zones. Oracle Database uses two data types to store time zone information:
 * TIMESTAMP WITH TIME ZONE : Stores date and time information with the offset from UTC
 * TIMESTAMP WITH LOCAL TIME ZONE : Stores date and time information with respect to the dbtimezone (which cannot be changed so long as there is a column in the db of this type), automatically adjusting the date and time from the stored time zone to the client's session time zone.

PostgreSQL
uses the standard data types but tries to impose an interpretation which avoids the problems described above.


 * TIMESTAMP WITH TIME ZONE : Stores date and time in UTC and converts to the client's local time zone (which could be different for each client) for display purposes.


 * TIMESTAMP WITHOUT TIME ZONE : Stores date and time without any conversion on input or output.