MOS:DATEUNIFY

Template:MoS guideline
Template:Pp-move-indef
Template:Style

This page guides the presentation of numbers, dates, times, measurements, currencies, coordinates, and similar material in articles. Its aim is to promote clarity and cohesion; this is especially important *within* an article. The goal is to make the whole encyclopedia easier and more intuitive to use.

Where this manual provides options, consistency should be maintained within an article unless there is a good reason to do otherwise. The Arbitration Committee has ruled that editors should not change an article from one guideline-defined style to another without a substantial reason unrelated to mere choice of style, and that revert-warring over optional styles is unacceptable. If discussion cannot determine which style to use in an article, defer to the style used by the first major contributor.

## General notes

### Quotations, titles, etc.

*See also: WP:MOSQUOTE*
Quotations, titles of books and articles, and similar "imported" text should be faithfully reproduced, even if they employ formats or units inconsistent with these guidelines or with other formats in the same article. If necessary, clarify via [bracketed interpolation], article text, or footnotes.

* It is acceptable to change other date formats in the same article to provide consistency, so long as those changes would otherwise be acceptable.

### Non-breaking spaces

Guidance on the use of non-breaking spaces ("hard spaces") – `&nbsp;`, `{{nbsp}}`, `&thinsp;`, `{{thinsp}}` – is given in some sections below; `{{nowrap}}` may also be useful in controlling linebreaks in some situations. Not all situations in which hard spaces or `{{nowrap}}` may be appropriate are described.

## Chronological items

### Statements likely to become outdated

Shortcuts:
* MOS:DATED
* MOS:EPHEMERAL
* MOS:CURRENT

*See also: Wikipedia:Manual of Style/Words to watch#Relative time references, Wikipedia:As of*

Except on pages updated regularly (e.g. the "Current events" portal), terms such as Template:FormattingError, Template:FormattingError, Template:FormattingError, Template:FormattingError, Template:FormattingError, and Template:FormattingError should usually be avoided in favor of phrases such as Template:FormattingError, Template:FormattingError, and Template:FormattingError. For current and future events, use phrases like Template:FormattingError or Template:FormattingError to signal the time-dependence of the information.
However, do not replace Template:FormattingError with `{{as of|2005}}` because some information (the *beginning* of 2005) would be lost; in such circumstances, use advanced features of {{as of}} such as `{{as of|2005|alt=since the beginning of 2005}}`.

Relative-time expressions are acceptable for very long periods, such as geological epochs: Template:FormattingError

### Time of day

Shortcut:
* MOS:TIME

Context determines whether the 12- or 24-hour clock is used; in both, colons separate hours, minutes and seconds (e.g. Template:FormattingError or Template:FormattingError).

* **12-hour clock times** end with dotted or undotted lower-case Template:Xtn or Template:Xtn, or Template:Xtn or Template:Xtn, preceded by a non-breaking space, e.g. Template:FormattingError or Template:FormattingError (markup: `2:30{{nbsp}}p.m.` or `2:30{{nbsp}}pm`), not Template:FormattingError or Template:FormattingError. Hours should not have a leading zero (e.g. Template:FormattingError, not Template:FormattingError). Usually, use Template:FormattingError and Template:FormattingError rather than Template:FormattingError and Template:FormattingError; whether "midnight" refers to the start or the end of a date should be explicitly specified unless clear from the context.
* **24-hour clock times** have no a.m., p.m., noon or midnight suffix. Hours under 10 should have a leading zero (e.g. Template:FormattingError). The time Template:FormattingError refers to midnight at the start of a date, Template:FormattingError to noon, and Template:FormattingError to midnight at the end of a date, but Template:FormattingError should not be used for the first hour of the next day (e.g. use Template:FormattingError for ten minutes after midnight, not Template:FormattingError).

The numerical elements of times-of-day are figures (Template:FormattingError) rather than words (Template:FormattingError) though conventional terms such as Template:FormattingError and Template:FormattingError are acceptable (taking care, with the latter, to avoid possible date ambiguity in constructions such as Template:FormattingError).

#### Time zones

Shortcut:
* MOS:TIMEZONE
Give dates and times appropriate to the time zone where an event took place. For example, the date of the attack on Pearl Harbor should be December 7, 1941 (Hawaii time/Template:Zwspdate). Give priority to the place at which the event had its most significant effects; for example, if a hacker based in China attacked a Pentagon computer in the US, use the time zone for the Pentagon, where the attack had its effect. In some cases the best solution may be to add the date and time in Coordinated Universal Time (UTC). For example:

  •   Template:FormattingError
Alternatively, include just the UTC offset:

  •  Template:FormattingError
Rarely, the time zone in which a historical event took place has since changed; for example, China to 1949 was divided into five time zones, whereas all of modern China is UTC+8. Similarly, the term "UTC" is not appropriate for dates before this system was adopted in 1960; Universal Time (UT) is the appropriate term for the mean time at the prime meridian (Greenwich) when it is unnecessary to specify the precise definition of the time scale. Be sure to show the UTC or offset appropriate to the clock time in use at the time of the event, not the modern time zone, if they differ.

###  Dates, months and years

Shortcuts:
* MOS:DATEFORMAT
* MOS:DATEVAR

These requirements do not apply to dates in quotations or titles; .
Special rules apply to citations; .

#### Formats

Acceptable date formats

Shortcuts:
* MOS:UNLINKDATES
* MOS:BADDATE

* Dates should be linked only when they are germane to the subject .
* For issues related to dates in sortable tables, , or consider using `{{sort|2008-11-01|1 Nov 2008}}` or `{{dts|Nov 1, 2008}}`.
* Phrases such as Template:FormattingError (or Template:FormattingError, but not Template:FormattingError), Template:FormattingError, Template:FormattingError and Template:FormattingError are proper names, to which rules for dates do not apply (Template:FormattingError).

##### Consistency

Shortcut:
* **MOS:DATEUNIFY**

* **Dates in article body text** should all use the same format: Template:FormattingError, but not Template:FormattingError.
* **Publication dates** in an article's citations should all use the same format, which may be:

* the format used in the article body text,
* an abbreviated format from the "Acceptable date formats" table, provided the day and month elements are in the same order as in dates in the article body, or
* the format expected in the citation style being used (however, all-numeric date formats other than yyyy-mm-dd must still be avoided).

For example, a single article might contain one, but only one, of:
Template:FormattingError
Template:FormattingError
(among other possibilities).
* **Access and archive dates** in an article's citations should all use the same format, which may be:

* the format used for publication dates in the article;
* the format expected in the citation style adopted in the article (e.g. Template:FormattingError); or
* yyyy-mm-dd

For example, a single article's citations might contain either of the following:
Template:FormattingError
Template:FormattingError
When a citation style does not expect differing date formats, it is permissible to normalize publication dates to the article body text date format, and/or access/archive dates to either, with date consistency being preferred.
##### Strong national ties to a topic

Shortcut:
* MOS:DATETIES

*See also: Wikipedia:Manual of Style#Strong national ties to a topic*

* Articles on topics with strong ties to a particular English-speaking country should generally use the date format most commonly used in that nation. For the United States this is (for example) Template:FormattingError; for most other English-speaking countries it is Template:FormattingError
* Articles related to Canada may use either format with (as always) consistency within each article.
* In some topic areas the customary format differs from the usual national one: for example, articles on the modern U.S. military use day-before-month, in accordance with U.S. military usage.

##### Retaining existing format

Shortcut:
* MOS:DATERET

*See also: Wikipedia:Manual of Style#Retaining the existing variety*

* If an article has evolved using predominantly one format, the whole article should conform to it, unless there are reasons for changing it based on strong national ties to the topic or consensus on the article's talk page.
* The date format chosen by the first major contributor in the early stages of an article should continue to be used, unless there is reason to change it based on strong national ties to the topic or consensus on the article's talk page.
* Where an article has shown no clear sign of which format is used, the first person to insert a date is equivalent to "the first major contributor".

#### Era style

Shortcuts:
* MOS:ERA
* MOS:BCE

* The default calendar era is the Western Dionysian era system, a year numbering system also known as the Western Christian era (represented by Template:FormattingError), or the Common Era (represented by Template:FormattingError).
	+ Template:Xtn and Template:Xtn are the traditional ways of designating eras. Template:Xtn and Template:Xtn are common in some scholarly texts and in certain topic areas. Either convention may be appropriate for use in Wikipedia articles.
		- Do not change the established era style in an article unless there are reasons specific to its content. Seek consensus on the talk page *before* making the change. Open the discussion under a subhead that uses the word "era". Briefly state why the style is inappropriate for the article in question. A personal or categorical preference for one era style over the other is not justification for making a change.
		- Template:Xtn and Template:Xtn or Template:Xtn and Template:Xtn are written in upper case, unspaced, without a period (full point, `.`), and separated from the numeric year by a space (Template:FormattingError, not Template:FormattingError). It is advisable to use a non-breaking space.
		- Template:Xtn may appear before or after a year (Template:FormattingError, Template:FormattingError); the other abbreviations appear only after (Template:FormattingError, Template:FormattingError, Template:FormattingError).
		- In general, do not use Template:Xtn or Template:Xtn unless required to avoid ambiguity (e.g. Template:FormattingError not Template:FormattingError nor Template:FormattingError) or awkwardness (Template:FormattingError not Template:FormattingError). On the other hand, Template:FormattingError will avoid unnecessary confusion. Also, in Template:FormattingError the era marker makes it clear that "55" does not refer to his age. Alternatively, Template:FormattingError If the era is shown for the initial date in a range, then use it for the final date as well: either Template:FormattingError or Template:FormattingError, but definitely Template:FormattingError. Template:See below
		- Use either the BC–AD or the BCE–CE notation consistently within the same article. Exception: do not change direct quotations, titles, etc.
* **Uncalibrated (bce) radiocarbon dates:** Calibrated and uncalibrated dates can diverge widely, and some sources distinguish the two only via Template:Xtn or Template:Xtn (for calibrated dates) versus Template:FormattingError, Template:Xtn or Template:Xtn (uncalibrated). Avoid giving uncalibrated dates except in direct quotations, and even then a footnote or square-bracketed note [like this] should note that the date is uncalibrated or (ideally) give the calibrated date.
* **BP**: In scientific and academic contexts, BP (before present) is often used. This is calibrated from January 1, 1950, not from the date of publication, though the latter introduces an insignificant error when the date is distant or an approximation (18,000 BP). BP years are given as Template:FormattingError or spelled out as Template:FormattingError (not Template:FormattingError, Template:FormattingError, Template:FormattingError, or similar). Do not convert other notations to or from BP unless you are certain of what you are doing; a safer and simpler alternative may be to use Template:FormattingError.Template:Explain
* **Other era systems** may be appropriate in an article. In such cases, dates should be followed by a conversion to Dionysian (or vice versa) and the first instance should be linked: Template:FormattingError, or Template:FormattingError.
	+ Astronomical year numbering follows the Common Era and does not require conversion, but the first instance of a non-positive year should still be linked: Template:FormattingError

#### Julian and Gregorian calendars

Shortcuts:
* MOS:OSNS
* MOS:JG

*See also: Old Style and New Style dates*

A date can be given in any appropriate calendar, as long as it is (at the minimum) given in the Julian calendar or the Gregorian calendar or both, as described below. For example, an article on the early history of Islam may give dates in both Islamic and Julian calendars. Where a calendar other than the Julian or Gregorian is used, the article must make this clear.

* Current events are dated using the Gregorian calendar.
* Dates of events in countries using the Gregorian calendar at that time are given in the Gregorian calendar. This includes some of the Continent of Europe from 1582, the British Empire from 14 September 1752, and Russia from 14 February 1918 .
* Dates before 15 October 1582 (when the Gregorian calendar was first adopted in some places) are normally given in the Julian calendar. The Julian day and month should not be converted to the Gregorian calendar, but the start of the Julian year should be assumed to be 1 January .
* Dates for Roman history before 45 BC are given in the Roman calendar, which was neither Julian nor Gregorian. When (rarely) the Julian equivalent is certain, it may be included.
* For dates in early Egyptian and Mesopotamian history, Julian or Gregorian equivalents are often uncertain. Follow the consensus of reliable sources, or indicate their divergence.

The dating method used should follow that used by reliable secondary sources (or if reliable sources disagree, that used most commonly, with an explanatory footnote).

At some places and times, the new year began on a date other than 1 January. For example, in England and its colonies until 1752, the year began on Annunciation Day, 25 March; . In writing about historical events, however, years should be assumed to have begun on 1 January ; if there is reason to use another start-of-year date, this should be noted.

If there is a need to mention Old or New Style dates in an article (as in the Glorious Revolution), a footnote should be provided on the first usage, stating whether the New Style refers to a start of year adjustment or to the Gregorian calendar (it can mean either).

#### Ranges

Shortcuts:
* MOS:DOB
* MOS:OTHERDATE
* MOS:DATERANGE

* A pure **year–year** range is written (as is any range) using an en dash (`&ndash;` or `{{ndash}}`) not a hyphen or slash; this dash is usually *unspaced* (that is, with no space on either side); and the range's end year is usually given in full:

  •   Template:FormattingError;  Template:FormattingError (not Template:FormattingError;  Template:FormattingError)
Template:Hanging indent
* The ending year in a range *may* be abbreviated to two digits (Template:FormattingError, but never Template:FormattingError or Template:FormattingError) in the case of **two consecutive years** and in **infoboxes and tables** where space is at a premium. (Use a single format consistently in any given table column, both for aesthetic reasons and so that data sorts properly.)
* Articles in **certain topic areas** may use two-digit ending years if there is a very good reason, such as matching the established convention of reliable sources in that topic area. Similarly, the slash notation (Template:FormattingError) may be used to signify a fiscal year or other special period, if that convention is used in reliable sources.

* Other "pure" ranges use an *unspaced* en dash as well:

* **day–day**: Template:FormattingError;  Template:FormattingError;  Template:FormattingError
* **month–month**: Template:FormattingError;  Template:FormattingError;  (but Template:FormattingError uses a *spaced* en dash; )

* If at least one of the items on either side of the en dash is in a mixed format (containing two or more of day, month, year); carries a modifier such as Template:Circa; or otherwise contains a space; then a *spaced* en dash (`{{snd}}`) is used:

* **between specific dates in different months**: Template:FormattingError;  Template:FormattingError
* **between dates in different years**:

Template:FormattingError
Template:Hanging indent
Template:FormattingError
* **between months in different years**: Template:FormattingError;  Template:FormattingError

Template:Hanging indent
* Constructions such as Template:FormattingError (with unspaced ndash), Template:FormattingError (spaced ndash), or Template:FormattingError (spaced ndash) may be used where appropriate, but other constructions may be more appropriate in prose . In tables, infoboxes, and so on, *pres.* may be used to conserve horizontal space (Template:FormattingError). Do not use incomplete-looking constructions such as Template:FormattingError and Template:FormattingError .
* For a person still living: Template:FormattingError, not Template:FormattingError or Template:FormattingError
* Where birthdate is unknown: Template:FormattingError or Template:FormattingError
* An overnight period may be expressed using a slash between two contiguous dates: Template:FormattingError or Template:FormattingError.

Or use an en dash: (unspaced) Template:FormattingError;  (spaced) Template:FormattingError.
* Use a dash, or a word such as Template:Xtn or Template:Xtn, but not both: Template:FormattingError (not Template:FormattingError);  Template:FormattingError (not Template:FormattingError)
* The `{{Age}}` template can keep ages current in infoboxes and so on:

  •  `{{age|1989|7|23}}` returns: Template:FormattingError
  •  `{{age|1989|7|23}}-year-old` returns: Template:FormattingError
  •  `{{age|1989|7|23}} years old` returns: Template:FormattingError
* Date mathematics templates are available for other age calculations.

#### Uncertain, incomplete, or approximate dates

Shortcut:
* MOS:APPROXDATE

* To indicate "around", "approximately", or "about", the use of the spaced, unitalicised form Template:FormattingError (or the `{{circa}}` template) is preferred over Template:FormattingError, Template:FormattingError, Template:FormattingError, Template:FormattingError, or Template:FormattingError:

  •   Template:FormattingError
  •   Template:FormattingError
  •   Template:FormattingError
* Where both endpoints of a range are approximate, c. should appear before each date:

  •   Template:FormattingError (not Template:FormattingError)
  •   Template:FormattingError (not Template:FormattingError)
* Where birth/death limits have been inferred from known dates of activity:

  •   Template:FormattingError
  •   Template:FormattingError
  •   Template:FormattingError
* When a person is known to have been active ("flourishing") during certain years, Template:FormattingError, `[[Floruit|fl.]]`, or `{{fl.}}` may be used:

  •   Template:FormattingError
The linked forms should not be used on disambiguation pages, and "active" followed by the range is a better alternative for artists, soldiers and other persons with an occupation.
* When a date is known to be either of two years (e.g. from a regnal or AH year conversion, or a known age at death):

  •   Template:FormattingError
* Other forms of uncertainty should be expressed in words, either in article text or in a footnote: Template:FormattingError. Do not use a question mark (Template:FormattingError), because it fails to communicate the nature of the uncertainty.
* Ranges in which Template:FormattingError, Template:FormattingError, Template:FormattingError or similar forms appearTemplate:Mdashbwhether on one or both sidesTemplate:Mdashbemploy a *spaced* endash (`{{snd}}`) and ideally a nonbreaking space should follow very short modifiers such as Template:FormattingError and Template:FormattingError. *Markup:* `1896{{snd}}after 1954`, `{{c.}}{{nbsp}}470{{snd}}{{c.}}{{nbsp}}540`

### Other

#### Days of the week

* Days of the week are capitalized (Template:FormattingError, Template:FormattingError).

#### Seasons

Shortcut:
* MOS:SEASON

* Seasons are uncapitalized (Template:FormattingError) except when personified: Template:FormattingError; Template:FormattingError.
* Using seasons to refer to a particular time of year (Template:FormattingError) is ambiguous for two reasons:
	+ the same names are used for both northern hemisphere and southern hemisphere seasons, which occur six months apart, and;
	+ areas near the equator have only wet and dry seasons.

Unambiguous alternatives include Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError.
* Referring to a season by name is appropriate when it is part of a formal or conventional name or designation (Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError).

#### Decades

Shortcut:
* MOS:DECADE

* To refer to a decade as a chronological period *per se* (not with reference to a social era or cultural phenomenon) always use four digits (Template:FormattingError, but not Template:FormattingError or Template:FormattingError, and *definitely* not Template:FormattingError).

* Prefixes should be hyphenated (Template:FormattingError;  Template:FormattingError).

* For a social era or cultural phenomenon associated with a particular decade:

* Two digits (with a preceding apostrophe) may be used as an alternative to four digits, *but only if this is a well-established phrase seen in reliable sources* (Template:FormattingError,  Template:FormattingError,  Template:FormattingError, but Template:FormattingError, and do not write Template:FormattingError;  Template:FormattingError;  or Template:FormattingError).
* A third alternative (where seen in reliable sources) is to spell the decade out, capitalized: Template:FormattingError

#### Centuries and millennia

Shortcuts:
* MOS:CENTURY
* MOS:MILLENNIUM

* Treat the 1st century AD as years 1–100, the 17th century as 1601–1700, and the second millennium as 1001–2000; similarly, the 1st century BC/BCE was 100–1 BC/BCE, the 17th century was 1700–1601 BC/BCE, and the second millennium 2000–1001 BC/BCE.
	+ The 18th century (1701–1800) and the 1700s (1700–1799) are not the same period.
	+ When using forms such as Template:FormattingError ensure there is no ambiguity as to whether e.g. 1700–1709 or 1700–1799, is meant.
	+ Note that the sequence of years runs Template:FormattingError – there is no "year 0".
* Centuries and millennia are identified using either figures (Template:FormattingError, not Template:FormattingError) or words (Template:FormattingError). When used adjectivally they contain a hyphen (Template:FormattingError or Template:FormattingError). Do not capitalize (Template:FormattingError;  Template:FormattingError).

#### Long periods of time

* When the term is frequent, combine Template:Xtn (years) or Template:Xtn (years ago) with Template:Xtn (thousand): Template:Xtn, Template:Xtn; Template:Xtn (million): Template:Xtn, Template:Xtn; and Template:Xtn (short-scale billion): Template:Xtn, Template:Xtn.
* In academic contexts, SI annus-based units are often used: Template:Xtn (kiloannus), Template:Xtn (megaannus), and Template:Xtn (gigaannus).
* Show the meaning parenthetically, and consider linking to the appropriate section of the Year article  on first occurrence and where the use is a standalone topic of interest. In source quotations, use square brackets: Template:FormattingError

## Numbers

### Numbers as figures or words

Shortcuts:
* WP:NUMERAL
* MOS:NUMERAL
* WP:SPELL09
* MOS:SPELL09

Generally, in article text:

* Integers from zero to nine are spelled out in words.
* Integers greater than nine *expressible in one or two words* may be expressed either in numerals or in words (Template:FormattingError or Template:FormattingError, Template:FormattingError or Template:FormattingError, Template:FormattingError or Template:FormattingError). In spelling out numbers, components from 21 to 99 are hyphenated; larger ones are not (Template:FormattingError, Template:FormattingError).
* Other numbers are given in numerals (Template:FormattingError, Template:FormattingError) or in forms such as Template:FormattingError. Markup: `21{{nbsp}}million`

* "billion" and "trillion" are understood to represent their short-scale values of 109 (1,000,000,000) and 1012 (1,000,000,000,000), respectively. Keep this in mind when translating articles from non-English Wikipedias, or using material from non-English sources.
* Template:FormattingError (unspaced) or Template:FormattingError (unspaced) respectively may be used for "million" or "billion" after a number, when the word has been spelled out at the first occurrence (e.g., Template:FormattingError).
* SI prefixes and symbols, such as Template:Xtn (Template:Xtn) and Template:Xtn (Template:Xtn), should be restricted to scientific, engineering, and technical uses.
* Sometimes, the variety of English used in an article may necessitate the use of a numbering system other than the Western thousands-based system. For example, the South Asian numbering system is conventionally used in South Asian English. In those situations, link the first spelled-out instance of each quantity (e.g. `[[crore]]`, which yields crore). (If no instances are spelled out, provide a note after the first instance directing the reader to the article about the numbering system.) Also, provide a conversion to Western numbers for the first instance of each quantity, and provide conversions for subsequent instances if they do not overwhelm the content of the article. For example, write Template:FormattingError. Group digits in Western thousands-based style (e.g., Template:FormattingError; not Template:FormattingError); . (Note that the variety of English does not uniquely determine the method of numbering in an article. Other considerations, such as conventions used in mathematics, science and engineering, may also apply, and the choice and order of formats and conversions is a matter of editorial discretion and consensus.)

Shortcut:
* WP:NUMNOTES

Notes and exceptions:

* In tables and infoboxes, quantities are expressed in figures (Template:FormattingError); but numbers within a table's explanatory text and comments follow the general rule.
* Numbers in mathematical formulae are never spelled out (Template:FormattingError, not Template:FormattingError).
* Comparable quantities should be all spelled out or all in figures:

  •  Template:FormattingError, not Template:FormattingError.
  •  Template:FormattingError, not Template:FormattingError
  •  Template:FormattingError, even though *3* would normally be given as *three*; or Template:FormattingError (or *two hundred and six* in British English), even though *two hundred six* would normally be given as *206*); but not Template:FormattingError.
* But adjacent quantities not comparable should usually be in *different formats:* Template:FormattingError or Template:FormattingError, not Template:FormattingError or Template:FormattingError.

* Avoid awkward juxtapositions: Template:FormattingError, not Template:FormattingError.

* Personal ages are typically stated in figures (Template:FormattingError) except for large, approximate values (Template:FormattingError).
* Sometimes figures and words carry different meanings; for example Template:FormattingError implies there is a single exception (without specifying which), while Template:FormattingError means that only locker number 1 was not searched.
* Proper names, technical terms, and the like are never altered: Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError

* Avoid beginning a sentence with figures:

  •   Not Template:FormattingError,

      but Template:FormattingError or Template:FormattingError.
  •   Not Template:FormattingError (nor Template:FormattingError – because comparable numbers should be both written in words or both in figures) but Template:FormattingError
* Exception: Where a proper name, technical term, etc., itself beginning with a numeral, opens the sentence (Template:FormattingError) although this can usually be avoided by rewording (Template:FormattingError).

Shortcuts:
* MOS:ORDINAL
* WP:ORDINAL

### Ordinals

* Ordinal suffixes (Template:FormattingError, Template:FormattingError, Template:FormattingError, Template:FormattingError) are not superscripted (Template:FormattingError and Template:FormattingError, not Template:FormattingError nor Template:FormattingError).
* Regnal numbers are normally written with roman numerals (without suffix, e.g. Template:FormattingError not Template:FormattingError).
* Do not use a dot (Template:FormattingError) or the ordinal mark (Template:FormattingError) to indicate ordinals.

### Singular versus plural

* Nouns following simple fractions are singular (Template:FormattingError;  Template:FormattingError;  Template:FormattingError).
* Nouns following mixed numbers are plural (Template:FormattingError;  Template:FormattingError).
* Nouns following the lone, unsigned digit 1 are singular, but those following other decimal numbers (i.e. base-10 numbers not involving fractions) are plural (Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError but Template:FormattingError;  Template:FormattingError;  Template:FormattingError).
* The same rules apply to numbers given in words (Template:FormattingError;  Template:FormattingError;  Template:FormattingError;  Template:FormattingError).

### Fractions and ratios

Shortcuts:
* MOS:FRAC
* MOS:RATIO

* Spelled-out fractions are hyphenated: Template:FormattingError.
* Where numerator and denominator can each be expressed in one word, a fraction is usually spelled out (e.g. Template:FormattingError;  Template:FormattingError); use figures if a fraction appears with a symbol (e.g. Template:FormattingError – markup: ``{{frac|1|4}}`&nbsp;mi`, not Template:FormattingError or Template:FormattingError).
* Mixed numbers are usually given in figures, unspaced (not Template:FormattingError or Template:FormattingError but Template:FormattingError – markup: `{{frac|8|1|2}}`). In any case the integer and fractional parts should be consistent (not Template:FormattingError).
* Metric (SI) measurements generally use decimals, not fractions (Template:FormattingError, not Template:FormattingError).
* Non-metric (imperial and US customary) measurements may use fractions or decimals (Template:FormattingError; Template:FormattingError); the practice of reliable sources should be followed, and within-article consistency is desirable.
* In science and mathematics articles mixed numbers are rarely used (not Template:FormattingError, but Template:FormattingError) and use of `{{frac}}` is discouraged in favor of one of these styles:

1
2

{\displaystyle \textstyle\frac{1}{2}}

 – markup: `<math>\textstyle\frac{1}{2}</math>`
  •   Template:FormattingError – markup: `{{sfrac|2}}`
  •   Template:FormattingError – markup: `1/2`
* Do not use special characters such as "½" (deprecated markup: ~~`&frac12;`~~ or ~~`&#189;`~~).
* Ordinal suffixes such as Template:Xtn should not be used with fractions expressed in figures (not Template:FormattingError;  Template:FormattingError, but Template:FormattingError;  Template:FormattingError;  Template:FormattingError).
* Dimensionless ratios (i.e. those not incorporating units) are given using numerals and a colon, or numbers-as-words and *to*: Template:FormattingError or Template:FormattingError, but not Template:FormattingError or Template:FormattingError. Use a "spaced" colon when a decimal point is present (Template:FormattingError – markup: `a 3.5&nbsp;:&nbsp;1 ratio`). Do not use the colon form where units are involved (Template:FormattingError)Template:Mdashbinstead see *ratios* section of table at § Unit names and symbols, below.

### Decimals

Shortcuts:
* WP:DECIMAL
* MOS:DECIMAL

* A period/full point (`.`), *never* a comma, is used as the decimal point (Template:FormattingError, not Template:FormattingError).
* Numbers between −1 and +1 require a leading zero (Template:FormattingError, not Template:FormattingError); exceptions are sporting performance averages (Template:FormattingError) and commonly used terms such as Template:FormattingError.
* Indicate repeating digits with an overbar e.g. `14.31{{overline|28}}` gives Template:FormattingError. (Consider explaining this notation on first use.) Do not write e.g. Template:FormattingError because it resembles notations for § Uncertainty.

#### Grouping of digits

Shortcuts:
* WP:DIGITS
* MOS:DIGITS

* Digits should be grouped and separated either by commas or narrow gaps (*never* a period/full point).

Grouping with commas
* Left of the decimal point, five or more digits are grouped into threes separated by commas (e.g.  Template:FormattingError,  Template:FormattingError,  Template:FormattingError,  Template:FormattingError).
* Numbers with exactly four digits left of the decimal point may optionally be grouped (either  Template:FormattingError  or  Template:FormattingError), provided that this is consistent within each article.
* When commas are used left of the decimal point, digits right of the decimal point are not grouped (i.e. should be given as an unbroken string).
* Markup: `{{formatnum:}}` produces this formatting.

Grouping with narrow gaps
* Digits are grouped both sides of the decimal point (e.g.  Template:FormattingError,  Template:FormattingError,  Template:FormattingError).
* Digits are generally grouped into threes. Right of the decimal point, *usual* practice is to have a final group of four instead of a lone digit (e.g.  Template:FormattingError  or  Template:FormattingError). In mathematics-oriented articles long strings may be grouped into fives (e.g.  Template:FormattingError).
* This style is especially recommended for articles related to science, technology, engineering or mathematics.
* Markup: Templates `{{val}}` or `{{gaps}}` may be used to produce this formatting. Note that use of *any* space character in numbers, including non-breaking space, is problematic for screen readers.  Screen readers read out each *group* of digits as separate numbers (e.g.  `30&thinsp;000`  is read as "thirty zero zero zero".)

* Delimiting style should be consistent throughout a given article.

* Either use commas or narrow gaps, but not both in the same article.
* Either group the thousands in a four-digit number or do not, but not mixed use in the same article.
* However, grouping by threes and fives may coexist.

* An exception is made for four-digit page numbers or four-digit calendar years. These should never be grouped (not  Template:FormattingError,  though  Template:FormattingError  or  Template:FormattingError).

### Percentages

Shortcuts:
* MOS:PERCENT
* WP:PERCENT
* WP:%

* In the body of non-scientific/non-technical articles, Template:Xtn (American English) or Template:Xtn (British English) are commonly used: Template:FormattingError; Template:FormattingError; Template:FormattingError. Ranges are written Template:FormattingError or Template:FormattingError, not Template:FormattingError or Template:FormattingError.
* In the body of scientific/Template:Zwsptechnical articles, and in *tables and infoboxes* of any article, the symbol `%` (unspaced) is more common: Template:FormattingError, not Template:FormattingError or Template:FormattingError. Ranges: Template:FormattingError, not Template:FormattingError or Template:FormattingError.
* When expressing the difference between two percentages, do not confuse a percentage change with a change in percentage points.

### Scientific and engineering notation

* Scientific notation always has a single nonzero digit to the left of the point: not Template:FormattingError, but Template:FormattingError.
* Engineering notation is similar, but adjusted so that the exponent is a multiple of three: Template:FormattingError.
* Avoid mixing scientific and engineering notations (Template:FormattingError).
* In a table column (or other presentation) in which all values can be expressed with a single power of 10, consider giving e.g. Template:FormattingError once in the column header, and omitting it in the individual entries. (Markup: `{{e|7}}`)
* In both notations, the number of digits indicates the precision. For example, Template:FormattingError means rounded to the nearest thousand; Template:FormattingError to the nearest hundred; Template:FormattingError to the nearest ten; and Template:FormattingError to the nearest unit.

Markup: `{{val}}` and `{{e}}` may be used to format exponential notation.

### Uncertainty and rounding

Shortcuts:
* MOS:UNCERTAINTY
* MOS:LARGENUM

* Where explicit uncertainty information (such as a margin of error) is available and appropriate for inclusion, it may be written in various ways:

  •  Template:FormattingError
  •  Template:FormattingError (not used with scientific notation)
  •  Template:FormattingError
  •  Template:FormattingError (equivalent to Template:FormattingError)
  •  Template:FormattingError
Markup: `{{+-}}`, `{{su}}`, and `{{val}}` may be used to format uncertainties.
* Where explicit *uncertainty is unavailable* (or is unimportant for the article's purposes) round to an appropriate number of significant digits; the precision presented should usually be conservative. Precise values (often given in sources for formal or matter-of-record reasons) should be used only where stable and appropriate to the context, or significant in themselves for some special reason.

  •   Template:FormattingError
*but* Template:FormattingError
  •   Template:FormattingError (not Template:FormattingError – an official figure unlikely to be accurate at full precision)
*but* Template:FormattingError (unusual case in which the full-precision official population figure is helpful to readers)
  •   Template:FormattingError (likely that accurate and precise figures were determined)
  •   Template:FormattingError (unlikely that any precise number can be accurate, even if an official figure is issued)
*or* Template:FormattingError (in reporting conflicting information, give detail sufficient to make the contrast intelligible)
  •   Template:FormattingError (where the actual figure was $8,462,247.63) Template:FormattingError
* The number of decimal places should be consistent within a list or context (Template:FormattingError, not Template:FormattingError), unless different precisions are actually intended.
* It may sometimes be appropriate to note the *lack* of uncertainty information, especially where such information is normally provided and necessary for full interpretation of the figures supplied.

  •   Template:FormattingError
* The `{{undue precision}}` template may be added to figures appearing to be overprecise.

* Avoid using "approximately", "about", and similar terms with figures that have merely been approximated or rounded in a normal and expected way, unless the reader might otherwise be misled.

  •   Template:FormattingError (not Template:FormattingError – heights are conventionally reported only to the nearest inch, even though greater precision may be available in principle)
*but* Template:FormattingError ("about" because here the precise value is unknown, with substantial uncertainty)
* The reader may be assumed to interpret large round numbers (Template:FormattingError) as approximations. Writing a quantity in words (Template:FormattingError) can further emphasize its approximate nature.

### Non-base-10 notations

Shortcuts:
* MOS:BASE
* MOS:RADIX
* MOS:BINARY
* MOS:HEX

* In computer-related articles, use the C programming language prefixes `0x` (zero-ex) for hexadecimal and `0` (zero) for octal. For binary, use `0b`. Explain these prefixes in the article's introduction or on first use.
* In all other articles, use `<sub>` to create subscripts: Template:FormattingError, Template:FormattingError. Markup: Template:FormattingError, Template:FormattingError
* For bases above 10, use symbols conventional for that base (as seen in reliable sources) e.g. for base 16 use 0–9 and A–F.

## Units of measurement

Shortcuts:
* WP:UNIT
* WP:UNITS
* WP:METRIC
* WP:MEASUREMENT

### Unit choice and order

Quantities are typically expressed using an appropriate "primary unit", displayed first, followed, when appropriate, by a conversion in parentheses e.g. Template:FormattingError. For details on when and how to provide a conversion, see the section § Unit conversions. The choice of primary units depends on the circumstances, and should respect the principle of "strong national ties", where applicable:

* In **non-scientific articles relating to the United States**, the primary units are US customary, e.g. Template:FormattingError.
* In **non-scientific articles relating to the United Kingdom**, the primary units for most quantities are metric or other internationally used units, except that:
	+ UK engineering-related articles, including those on bridges and tunnels, generally use the system of units that the topic was drawn up in (but road distances are given in imperial units, with a metric conversion – see next bullet);
	+ the primary units for distance/Template:Zwsplength, speed and fuel consumption are miles, miles per hour, and miles per imperial gallon (except for short distances or lengths, where miles are too large for practical use);
	+ the primary units for personal height and weight are feetTemplate:Zwsp/inches and stones/Template:Zwsppounds;
	+ imperial pints are used for quantities of draught beer/Template:Zwspcider and bottled milk;
* In **all other articles**, the primary units chosen will be SI units, non-SI units officially accepted for use with the SI, or such other units as are conventional in reliable-source discussions of the article topic (such as revolutions per minute (rpm) for angular speed, hands for heights of horses, et cetera).

*Special considerations:*

* Quantities set via definition (as opposed to measured quantities) should be given first in the units used in the definition, even if this makes the structure of presentation inconsistent: Template:FormattingError.
	+ This may benefit from a slightly non-standard structure, such as Template:FormattingError. In this sort of case, using Template:Xtn can help make clear which is the statutory, exact value.
* Nominal quantities (e.g. Template:FormattingError) require consideration of whether the article is concerned with the item's actual dimensions or merely with its function. In some cases only the nominal quantity may suffice; in others it may be necessary to give the nominal size (often in non-SI units), the actual size in non-SI units, and the actual size in SI units.
* Whenever a conversion is used, ensure that the precision of the converted quantity in the article is comparable to the precision of the value given by the source .

### Unit names and symbols

*Definitions:*
* Examples of **unit names**: foot, meter, kilometer.
* Examples of **unit symbols**: ft, m, km.

* Unit names and symbols should follow the practice of reliable sources.
* In prose, unit names should be given in full if used only a few times, but symbols may be used when a unit (especially one with a long name) is used repeatedly, after spelling out the first use (e.g. Template:FormattingError).

* Exception: Certain units are generally represented by their symbols (e.g. Template:FormattingError rather than Template:FormattingError) even on first use, though their unit names may be used for emphasis or clarity (Template:FormattingError).
* Exception: Consider using *inches* in place of *in* where the latter might be misread as a prepositionTemplate:Mdashbbut not where the value is followed by a parenthesized conversion e.g. Template:FormattingError, or is part of such a conversion (Template:FormattingError).

* Where space is limited, such as in tables, infoboxes, parenthetical notes, and mathematical formulas, unit symbols are preferred.
* Units unfamiliar to general readers should be presented as a name–symbol pair on first use, linking the unit name (Template:FormattingError).
* Ranges use unspaced en dash (`{{ndash}}`) if only one unit symbol is used at the end (e.g. Template:FormattingError), and spaced en dash (`{{snd}}`) if two symbols are used (e.g. Template:FormattingError); ranges in prose may be specified using either unit symbol or unit names, and units may be stated either after both numerical values or after the last (e.g. Template:FormattingError, Template:FormattingError, Template:FormattingError and Template:FormattingError are all acceptable).
* Length–width, length–width–height and similar dimensions may be separated by the multiplication sign (`×`) or the word Template:Xtn.
	+ With the multiplication sign, each number should be followed by a unit name or symbol (if appropriate):

  •  Template:FormattingError, not  Template:FormattingError , Template:FormattingError nor  Template:FormattingError
  •  Template:FormattingError
  •  Template:FormattingError
* With Template:Xtn, the unit need be given only once:  Template:FormattingError  or  Template:FormattingError
* The unspaced letter Template:FormattingError may be used in common terms such as Template:FormattingError.

*Note to table:*

1. ↑ Only use this format if it is clear from the context whether this means hours and minutes (H:MM) or minutes and seconds (M:SS).

### Specific units

* The following table lists only units that need special attention.
* The SI Brochure should be consulted for guidance on use of other SI and non-SI units.

#### Quantities of bytes and bits

Shortcut:
* WP:COMPUNITS

In quantities of bits and bytes, the prefixes Template:Xtn (symbol Template:Xtn or Template:Xtn), Template:Xtn (Template:Xtn), Template:Xtn (Template:Xtn), Template:Xtn (Template:Xtn), etc., are ambiguous. They may be based on a decimal system (like the standard SI prefixes), meaning 103, 106, 109, 1012, etc., or they may be based on a binary system, meaning 210, 220, 230, 240, etc. The binary meanings are more commonly used in relation to solid-state memory (such as RAM), while the decimal meanings are more common for data transmission rates, disk storage and in theoretical calculations in modern academic textbooks.
Template:Bit and byte prefixes
Follow these recommendations when using these prefixes in Wikipedia articles:

* Following the SI standard, a lower-case Template:FormattingError should be used for "kilo-" whenever it means 1000 in computing contexts, whereas a capital Template:FormattingError should be used instead to indicate the binary prefix for 1024 according to JEDEC. (If, under the exceptions detailed further below, the article otherwise uses IEC prefixes for binary units, use Template:FormattingError instead).
* Do not assume that the binary or decimal meaning of prefixes will be obvious to everyone. Explicitly specify the meaning of k and K as well as the primary meaning of M, G, T, etc. in an article (`{{BDprefix}}` is a convenient helper). Consistency within each article is desirable, but the need for consistency may be balanced with other considerations.
* The definition most relevant to the article should be chosen as primary for that article, e.g. specify a binary definition in an article on RAM, decimal definition in an article on hard drives, bit rates, and a binary definition for Windows file sizes, despite files usually being stored on hard drives.
* Where consistency is not possible, specify wherever there is a deviation from the primary definition.
* Disambiguation should be shown in bytes or bits, with clear indication of whether in binary or decimal base. There is no preference in the way to indicate the number of bytes and bits, but the notation style should be consistent within an article. Acceptable examples include:

  •  Template:FormattingError
  •  Template:FormattingError
  •  Template:FormattingError
* Avoid inconsistent combinations such as Template:FormattingError. Footnotes, such as those seen in Power Macintosh 5500, may be used for disambiguation.
* Unless explicitly stated otherwise, one byte is eight bits .

The IEC prefixes Template:Xtn (symbol Template:Xtn), Template:Xtn (Template:Xtn), Template:Xtn (Template:Xtn), etc., are generally not to be used except:

* when the majority of cited sources on the article topic use IEC prefixes;
* in a direct quote using the IEC prefixes;
* when explicitly discussing the IEC prefixes; or
* in articles in which both types of prefix are used with neither clearly primary, or in which converting all quantities to one or the other type would be misleading or lose necessary precision, or declaring the actual meaning of a unit on each use would be impractical.

### Unit conversions

Shortcuts:
* MOS:CONVERSIONS
* WP:MOSCONVERSIONS

Where English-speaking countries use different units for the same quantity, follow the "primary" quantity with a conversion in parentheses: Template:FormattingError; Template:FormattingError. In science-related articles, however, supplying such conversion is not required unless there is some special reason to do so.

* Generally, conversions to and from metric units and US or imperial units should be provided, except:
	+ When inserting a conversion would make a common or linked expression awkward (Template:FormattingError).
	+ When units are part of the subject of a topic – nautical miles in articles about the history of nautical law (Template:FormattingError), SI units in scientific articles (Template:FormattingError), yards in articles about American football – it can be excessive to provide conversions every time a unit occurs. It might be best to note that this topic will use the units (possibly giving the conversion factor to another familiar unit in a parenthetical note or a footnote), and link the first occurrence of each unit but not give a conversion every time it occurs.
* Converted quantity values should use a *level of precision* similar to that of the source quantity value, so Template:FormattingError, not Template:FormattingError. Small numbers may need to be converted to a range where rounding would cause a significant distortion, so Template:FormattingError, not Template:FormattingError. Be careful especially when your source has already converted from the units you're now converting back to. This may be evidenced by multiples of common conversion factors in the data, such as 160 km (from 100 miles).
* **Conversion templates** can be used to convert and format many common units, including `{{convert}}`, which includes non-breaking spaces.
* In a **direct quotation**, always retain the source units. Any conversions can be supplied either in the quote itself (in square brackets, following the original measurement) or in a footnote.
* `{{Units attention}}` may be added to articles needing general attention regarding choice of units and unit conversions.

## Currencies and monetary values

Shortcuts:
* WP:$
* WP:£
* WP:€
* MOS:CURRENCY

*See also: Wikipedia:WikiProject Numismatics/Style#Article titles*

### Choice of currency

* In **country-specific articles**, such as Economy of Australia, use the currency of the subject country.
* In **non-country-specific articles** such as Wealth, use US dollars (Template:FormattingError), euros (Template:FormattingError), or pounds sterling (Template:FormattingError).

### Currency names

* Do not capitalize the names or denominations of currencies, currency subdivisions, coins and banknotes: not Template:FormattingError but Template:FormattingError. *Exception:* where otherwise required, as at the start of a sentence or in such forms as Template:FormattingError.
* To pluralize Template:Xtn use the standard English plurals (Template:FormattingError), not the invariant plurals used for European Union legislation and banknotes (Template:FormattingError). For the adjectival form, use a hyphenated singular: (Template:FormattingError).
* Link the first occurrence of lesser-known currencies (Template:FormattingError).

### Currency symbols

* In general, the first mention of a particular currency should use its full, unambiguous signifier (e.g. Template:FormattingError), with subsequent references using just the appropriate symbol (e.g. Template:FormattingError), unless this would be unclear. *Exceptions:*

* In an article referring to multiple currencies represented by the same symbol (e.g. the dollars of the US, Canada, Australia, New Zealand, and other countries – ) use the full signifier (e.g. Template:FormattingError, Template:FormattingError) each time, except (possibly) where a particular context makes this both unnecessary and undesirable.
* In articles entirely on EU-, UK- and/or US-related topics, all occurrences may be shortened (Template:FormattingError, Template:FormattingError or Template:FormattingError), unless this would be unclear.

* The pound sterling is represented by the Template:FormattingError symbol, with one horizontal bar. The double-barred Template:FormattingError symbol is ambiguous, as it has also been used for the Italian lira and other currencies. For non-British currencies that use pounds or a pound symbol (e.g. the Irish pound, IR£) use the symbol conventionally preferred for that currency.
* If there is no common English abbreviation or symbol, follow the ISO 4217 standard.

### Formatting

* A period (full point, `.`) is used as the decimal point – never a comma (Template:FormattingError, not Template:FormattingError).
* Do not place a currency symbol *after* the accompanying numeric figures (e.g. Template:FormattingError, Template:FormattingError, Template:FormattingError) unless that is the normal convention for that currency when writing in English.Template:Clarify Never use forms such as Template:FormattingError or Template:FormattingError.
* Currency abbreviations that come before the numeric value are *unspaced* if they consist of a nonalphabetic symbol only, or end in a symbol (Template:FormattingError;   Template:FormattingError); but *spaced* if alphabetic (Template:FormattingError).
* Ranges should be expressed giving the currency signifier just once: Template:FormattingError, not Template:FormattingError.
* Template:FormattingError and Template:FormattingError should be spelled out on first use, and (optionally) abbreviated Template:FormattingError or Template:FormattingError (both unspaced) thereafter: Template:FormattingError; Template:FormattingError.
* In general, a currency symbol should be accompanied by a numeric amount e.g. not Template:FormattingError but Template:FormattingError or Template:FormattingError.

* Exceptions may occur in tables and infoboxes where space is limited e.g. Template:FormattingError. It may be appropriate to wikilink such uses, or add an explanatory note.

### Conversions

* Conversions of *less-familiar currencies* may be provided in terms of more familiar currencies – such as the US dollar, euro or pound sterling – using an appropriate rate (which is often *not* the current exchange rate). Conversions should be in parentheses after the original currency, rounding to avoid false precision (two significant digits is usually sufficient, as most exchange rates fluctuate significantly), with at least the year given as a rough point of conversion rate reference; e.g. Template:FormattingError, not Template:FormattingError.
* For *obsolete currencies*, provide an equivalent (formatted as a conversion) if possible, in the modern replacement currency (e.g. decimal pounds for historical pre-decimal pounds-and-shillings), or a US-dollar equivalent where there is no modern equivalent.
* In some cases it may be appropriate to provide a conversion accounting for inflation or deflation over time.

## Common mathematical symbols

Shortcuts:
* WP:COMMONMATH
* MOS:MINUS

*See also: Wikipedia:Manual of Style/Mathematics*

* The *Insert* menu below the editing window gives a more complete list of math symbols, and allows symbols to be inserted without the HTML encoding (e.g. `&divide;`) shown here.
* Spaces are placed to left and right when a symbol is used with two operands, but no space with one operand.
* Use `{{var}}` or `<var>...</var>` for variable names: `{{var|base}} + {{var|ht}}` and `<var>base</var> + <var>ht</var>` both produce base + ht.
* The `{{nbsp}}` and `{{nowrap}}` templates may be used to prevent awkward linebreaks.

## Geographical coordinates

Shortcuts:
* MOS:COORDS
* WP:COORDINATES

**Quick guide**:
Template:Coord how-to

Geographical coordinates on Earth should be entered using a template to standardise the format and to provide a link to maps of the coordinates. As long as the templates are adhered to, a robot performs the functions automatically.

First, obtain the coordinates. Avoid excessive precision.

Two types of template are available:

* `{{coord}}` offers users a choice of display format through user styles, emits a Geo microformat, and is recognised (in the *title* position) by the "nearby" feature of Wikipedia's mobile apps and by external service providers such as Google Maps and Google Earth, and Yahoo.
* Infoboxes such as `{{Infobox settlement}}`, which automatically emit `{{Coord}}`.

The following formats are available.

where:

* dd, mm, ss are the degrees, minutes and seconds, respectively;
* N/S is either `N` for northern or `S` for southern latitudes;
* E/W is either `E` for eastern or `W` for western longitudes;
* negative values may be used in lieu of `S` and `W` to denote Southern and Western Hemispheres

For example:

For the city of Oslo, located at 59° 55′ N, 10° 44′ E:

For a country, like Botswana, less precision is appropriate:

Higher levels of precision are obtained by using seconds:

Coordinates can be entered as decimal values

Increasing or decreasing the number of decimal places controls the precision. Trailing zeros should be used as needed to ensure that both values have the same level of precision.

London Heathrow Airport, Amsterdam, Jan Mayen and Mount Baker are examples of articles that contain geographical coordinates.

Generally, the larger the object being mapped, the *'less precise* the coordinates should be. For example, if just giving the location of a city, precision greater than 100 meters is not needed unless specifying a particular point in the city, for example the central administrative building. Specific buildings or other objects of similar size would justify precisions down to 10 meters or even one meter in some cases (1′′ ~15 m to 30 m, 0.0001° ~5.6 m to 10 m).

The final field, following the E/W, is available for attributes such as `type:`, `region:`, or `scale: `.````

```When adding coordinates, please remove the `{{coord missing}}` tag from the article, if present.```

``Templates other than `{{coord}}` should use the following variable names for coordinates: lat\_d, lat\_m, lat\_s, lat\_NS, long\_d, long\_m, long\_s, long\_EW.``

``See also
--------````* Wikipedia:Naming conventions (numbers and dates)
* Wikipedia:Date formattings
* m:Help:Date formatting feature at Meta
* m:Help:Calculation § Displaying numbers and numeric expressions at Meta````Template:Math templates````Notes and references
--------------------````1. ↑ Wikipedia:Requests for arbitration/Jguk § Principles, Wikipedia:Requests for arbitration/jguk 2 § Principles, and Wikipedia:Requests for arbitration/Sortan § Principles
2. ↑  (2009-06-02) *CCTF/09-32: Coordinated Universal Time (UTC)*. BIPM, 3. Retrieved on 2015-08-20. “This coordination began on January 1, 1960, and the resulting time scale began to be called informally 'Coordinated Universal Time.' ”
3. ↑ Only certain citation styles use abbreviated date formats.
5. ↑ All-numeric yyyy-mm-dd dates might be assumed to follow the ISO 8601 standard, which mandates the Gregorian calendar. Also, technically all must be four-digit years, but Wikipedia is unlikely to ever need to format a far-future date beyond the year 9999.
6. ↑ The routine linking of dates is deprecated. This change was made August 24, 2008, on the basis of this archived discussion. It was ratified in two December 2008 RfCs Wikipedia:Manual of Style/Dates and numbers/Three proposals for change to MOSNUM and Wikipedia:Manual of Style/Dates and numbers/Date Linking RFC
7. ↑ Wikipedia talk:Manual of Style/Archive 151 § RFC: Month abbreviations
8. ↑ These formats cannot, in general, be distinguished on sight, because there are usages in which 03-04-2007 represents March 4, and other usages in which it represents April 3. In contrast there is no common usage in which 2007-04-03 represents anything other than April 3.
9. ↑ The number in parentheses is the numerical value of the standard uncertainty referred to the corresponding last digits of the quoted result – .
10. ↑ If there is disagreement about the primary units used in a UK-related article, discuss the matter on the article talk-page, at MOSNUM talk, or both. If consensus cannot be reached, refer to historically stable versions of the article and retain the units used in these as the primary units. Also note the style guides of British publications such as *The Times* (see archived version, under "Metric").
11. ↑ 11.0 11.1 11.2  (2014) *SI Brochure: The International System of Units (SI)*, 8th, BIPM. Retrieved on 2015-08-20.  Tables 6, 7, 8, and 9 give additional guidance on non-SI units.
12. ↑ These definitions are consistent with all units of measure mentioned in the SI Brochure  and with all units of measure catalogued in EU directive 80/181/EEC [1].
13. ↑ Resolution B2 on the re-definition of the astronomical unit of length  (2012).
14. ↑ Wikipedia follows common practice regarding bytes and other data traditionally quantified using binary prefixes (e.g. Template:Xtn and Template:Xtn, meaning 220 and 210 respectively) and their unit symbols (e.g. Template:Xtn and Template:Xtn) for RAM and decimal prefixes for most other uses. Despite the IEC's 1998 international standard creating several new binary prefixes (e.g. mebi-, kibi-) to distinguish the meaning of the decimal SI prefixes (e.g. Template:Xtn and Template:Xtn, meaning 106 and 103 respectively) from the binary ones, and the subsequent incorporation of these IEC prefixes into the ISO/IEC 80000, consensus on Wikipedia in computing-related contexts currently favours the retention of the more familiar but ambiguous units Template:Xtn, Template:Xtn, Template:Xtn, Template:Xtn, Template:Xtn, Template:Xtn, etc. over use of unambiguous IEC binary prefixes.````Template:Style wide``