MOS:DATEUNIFY

<!-- PLEASE MAKE MINOR CHANGES TO THIS TEXT ALSO TO THE EQUIVALENT TEXT AT MOS. MORE SIGNIFICANT CHANGES, ESPECIALLY TO THE ACTUAL STYLE RECOMMENDATIONS, NEED TO BE FLAGGED AT THE WT:MOS TALK PAGE BEFORE IMPLEMENTATION HERE AND AT MOS, UNLESS THEY INVOLVE SECTIONS HERE THAT HAVE NO EQUIVALENT AT MOS (e.g. GEOGRAPHICAL COORDINATES).

FORMATTING: This page makes heavy and very particular use of a lot of specific formatting. To avoid confusion concerning the proper formatting of units, symbols, values, variables, code, etc., please observe the following markup conventions on this page: - Use to mark up positive examples or required text. - Use to mark up negative examples or deprecated items. - Use to mark up items than may or may not be applied depending on context. - Use to mark up items that are very rarely applied – dubious, deprecated, disputed, only used in one context (this template may not be needed on this page but is available). - Use double quotes to mark up words-as-words,"scare-quoting", and quoted sources, but not for unusual purposes. Italics are used heavily on this page for many other things, so do not use them for words-as-words. - Use to mark up emphasis. - Reserve plain italic only for conventional stylistic, non-semantic use of italics (e.g. for titles of major published works, foreign phrases, etc.; see above about words-as-words). - Use bold to mark up inline headers. - Use to mark up strong emphasis (rarely needed;  will usually suffice). - Use  (or   if needed) to mark up code examples, including individual special characters. Do not use ; this element no longer exists in HTML5. - Use to mark up variables and variable input, not, ..., or other markup. - Use to illustrate or name templates (or use undefined if nested inside  ). - Use ... in running prose to indicate editor input choices for templates (not necessary in actual code examples inside ) - Use ... in running prose to indicate example code output that should be monospaced, if the need arises. - Use spaced en dashes, not run-together em dashes, especially with markup examples, so the dash cannot be confused as being part of the example. - Use for cross-references to other sections or pages. This produces consistent formatting, and helps identify cross-references in the code for periodic checking against "advice forking". - Avoid italicization other than as specified above. - Avoid - in or near examples; should probably only be used inside tables, when width is a concern. - Do not markup mention of units and the like outside the context of advice about their use; example: 'Use m for "minute" only where there is no danger of confusion with meter' ["meter" is not marked up here per this convention; "m" is marked up with for conditional use; "minute" is double-quoted for words-as-words use]. -->

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 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.

Quotations, titles, etc.
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") –, ,  ,  – is given in some sections below;  may also be useful in controlling linebreaks in some situations. Not all situations in which hard spaces or may be appropriate are described.

Statements likely to become outdated
Except on pages updated regularly (e.g. the "Current events" portal), terms such as now, currently, to date, so far, soon, and recently should usually be avoided in favor of phrases such as during the 1990s, since 2010, and in August 1969. For current and future events, use phrases like as of August 2024 or since the beginning of 2024 to signal the time-dependence of the information. Using will produce the text  and adds the article to a category flagging it for periodic review. A full date is specified with. However, do not replace since the beginning of 2005 with because some information (the  of 2005) would be lost; in such circumstances, use advanced features of as of such as.

Relative-time expressions are acceptable for very long periods, such as geological epochs: Humans diverged from other primates long ago, but only recently developed state legislatures.

Time of day
Context determines whether the 12- or 24-hour clock is used; in both, colons separate hours, minutes and seconds (e.g. 1:38:09pm or 13:38:09).
 * 12-hour clock times end with dotted or undotted lower-case a.m. or p.m., or am or pm, preceded by a non-breaking space, e.g. 2:30p.m. or 2:30pm (markup:  or  ), not 2:30p.m. or 2:30pm. Hours should not have a leading zero (e.g. 2:30p.m., not 02:30p.m.). Usually, use noon and midnight rather than 12 pm and 12 am; 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. 08:15). The time 00:00 refers to midnight at the start of a date, 12:00 to noon, and 24:00 to midnight at the end of a date, but 24 should not be used for the first hour of the next day (e.g. use 00:10 for ten minutes after midnight, not 24:10).

The numerical elements of times-of-day are figures (12:45p.m.) rather than words (twelve forty-five p.m.) though conventional terms such as noon and midnight are acceptable (taking care, with the latter, to avoid possible date ambiguity in constructions such as midnight on July 17).

Time zones
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 December7, 1941 (Hawaii time/ date). 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:
 * &bull;  8p.m. Eastern Standard Time on January15, 2001 (01:00UTC, January16)

Alternatively, include just the UTC offset:
 * &bull; 21:00British Summer Time (UTC+1) on 27July 2012

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
These requirements do not apply to dates in quotations or titles;. Special rules apply to citations;.

Formats

 * Dates should be linked only when they are germane to the subject.
 * For issues related to dates in sortable tables,, or consider using or.
 * Phrases such as Fourth of July (or JulyFourth, but not July4th), Cinco de Mayo, Seventh of March Speech and Sete de Setembro are proper names, to which rules for dates do not apply (Any decent Fourth of July celebration includes fireworks).

Consistency

 * Dates in article body text should all use the same format: She fell ill on 25June 2005 and died on 28June, but not She fell ill on 25June 2005 and died on June28.
 * 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:
 * Jones, J. (20September 2008)
 * Jones, J. (September20, 2008)
 * (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. 20Sep 2008); or
 * yyyy-mm-dd
 * For example, a single article's citations might contain either of the following:
 * Jones, J. (20Sep 2008)... Retrieved 5Feb 2009.
 * Jones, J. (20Sep 2008)... Retrieved 2009-02-05.
 * 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

 * 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) July 4, 1976; for most other English-speaking countries it is 4 July 1976
 * 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

 * 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

 * The default calendar era is the Western Dionysian era system, a year numbering system also known as the Western Christian era (represented by BC and AD), or the Common Era (represented by BCE and CE).
 * BC and AD are the traditional ways of designating eras. BCE and CE 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 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.
 * BCE and CE or BC and AD are written in upper case, unspaced, without a period (full point, ), and separated from the numeric year by a space (5BC, not 5BC). It is advisable to use a non-breaking space.
 * AD may appear before or after a year (AD106, 106AD); the other abbreviations appear only after (106CE, 3700BCE, 3700BC).
 * In general, do not use CE or AD unless required to avoid ambiguity (e.g. The Norman Conquest took place in 1066 not 1066CE nor AD1066) or awkwardness (January 1, 1AD not January 1, 1). On the other hand, Plotinus was a philosopher living at the end of the 3rd century AD will avoid unnecessary confusion. Also, in He did not become king until 55CE the era marker makes it clear that "55" does not refer to his age. Alternatively, He did not become king until the year 55. If the era is shown for the initial date in a range, then use it for the final date as well: either from 450 to 200 BCE or from 450 BCE to 200 BCE, but definitely from 100 BCE to 200 CE.
 * 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 BCE or BC (for calibrated dates) versus bce, bc or b.c. (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,000BP). BP years are given as 18,000BP or spelled out as 18,000years before present (not 18,000YBP, 18,000 before present, 18,000 years before the present, 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 ya (years ago).
 * 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: Qasr-al-Khalifa was built in 221AH (836CE), or in 836AD (221AH).
 * 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: The March equinox passed into Pisces in year−67.

Julian and Gregorian calendars
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 14September 1752, and Russia from 14February 1918.
 * Dates before 15October 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 1January.
 * Dates for Roman history before 45BC 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 1January. For example, in England and its colonies until 1752, the year began on Annunciation Day, 25March;. In writing about historical events, however, years should be assumed to have begun on 1January ; 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

 * A pure year–year range is written (as is any range) using an en dash ( or ) not a hyphen or slash; this dash is usually  (that is, with no space on either side); and the range's end year is usually given in full:
 * &bull;  1881–1886; 1881–1992 (not 1881–86; 1881 – 1886)
 * The ending year in a range may be abbreviated to two digits (1881–82, but never 1881–882 or 1881–2) 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 (2005/2006) may be used to signify a fiscal year or other special period, if that convention is used in reliable sources.
 * 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 (2005/2006) 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 en dash as well:
 * day–day: 5–7January 1979; January5–7, 1979; elections were held March 5–8
 * month–month: the 1940 peak period was May–July; the peak period was May–July1940; (but the peak period was May 1940 – July 1940 uses a 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 c. ; or otherwise contains a space; then a en dash  is used:
 * between specific dates in different months: They travelled June3 – August18, 1952; They travelled 3June – 18August 1952
 * between dates in different years:
 * Charles Robert Darwin (12February 1809 – 19April 1882) was an English naturalist...
 * Abraham Lincoln (February12, 1809 – April15, 1865) was the 16th President of...
 * between months in different years: The exception was in force August 1892 – January 1903; The Ghent Incursion (March 1822 – January1, 1823) was ended by the New Year's Treaty
 * between months in different years: The exception was in force August 1892 – January 1903; The Ghent Incursion (March 1822 – January1, 1823) was ended by the New Year's Treaty


 * Constructions such as 1982–present (with unspaced ndash), January 1, 2011 – present (spaced ndash), or January 2011 – present (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 (1982–pres.). Do not use incomplete-looking constructions such as 1982– and 1982–....
 * For a person still living: Serena Williams (born September26, 1981) is a..., not (September26, 1981 – ) or (born on September26, 1981)
 * Where birthdate is unknown: John Smith (died May1, 1622)... or John Smith (died 1622)...
 * An overnight period may be expressed using a slash between two contiguous dates: the night raids of 30/31May 1942 or raids of 31May/ 1June 1942.
 * Or use an en dash: (unspaced) raids of 30–31May 1942; (spaced) raids of 31May – 1June 1942.


 * Use a dash, or a word such as from or between, but not both: from 1881 to 1886 (not from 1881–86); between June1 and July3 (not between June1 – July3)
 * The template can keep ages current in infoboxes and so on:
 * &bull;   returns: 35
 * &bull;   returns: 35-year-old
 * &bull;   returns: 35 years old


 * Date mathematics templates are available for other age calculations.

Uncertain, incomplete, or approximate dates

 * To indicate "around", "approximately", or "about", the use of the spaced, unitalicised form c.1291 (or the template) is preferred over circa, ca, ca., approximately, or approx.:
 * &bull;  At the birth of Roger Bacon (c. 1214)...
 * &bull;  John Sayer (c. 1750 – 2October 1818)...
 * &bull;  the Igehalkid dynasty of Elam, c. 1400BC...


 * Where both endpoints of a range are approximate, c. should appear before each date:
 * &bull;  Dionysius Exiguus (c. 470 – c.  540)... (not Dionysius Exiguus (c. 470 – 540)...)
 * &bull;  Rameses III (reigned c. 1180 – c.  1150BCE)... (not Rameses III (reigned c. 1180 – 1150BCE)...)


 * Where birth/death limits have been inferred from known dates of activity:
 * &bull;  Offa of Mercia (before 734 – 26July 796)...
 * &bull;  Robert Menli Lyon (1789 – after 1863)...
 * &bull;  Ambrose Gwinnett Bierce (June 24, 1842 – after December 26, 1913)...


 * When a person is known to have been active ("flourishing") during certain years, fl.,, or  may be used:
 * &bull;  Jacobus Flori (fl. 1571 – 1588) ...
 * 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):
 * &bull;  Anne Smith (born 1912 or 1913; died 2013)...


 * Other forms of uncertainty should be expressed in words, either in article text or in a footnote: April14, 1224 (unattested date). Do not use a question mark (1291?), because it fails to communicate the nature of the uncertainty.
 * Ranges in which c., after, fl. or similar forms appear—‌whether on one or both sides—‌employ a spaced endash and ideally a nonbreaking space should follow very short modifiers such as c. and fl.. Markup: ,

Days of the week

 * Days of the week are capitalized (Sunday, Wednesday).

Seasons

 * Seasons are uncapitalized (a hot summer) except when personified: Soon Spring will show her colors; Old Man Winter.
 * Using seasons to refer to a particular time of year (winter 1995) 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 early 1995; the first quarter of 1995; January to March 1995; spent the southern summer in Antarctica.


 * Referring to a season by name is appropriate when it is part of a formal or conventional name or designation (annual mid-winter festival; the autumn harvest; 2018 Winter Olympics; Times Fall Books Supplement; Details appeared in Quarterly Review, Summer 2015, pp. 5–7; The Court's winter term).

Decades

 * 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 (the1980s, but not the1980's or the1980ies, and not the1980s').
 * Prefixes should be hyphenated (themid1980s; pre1960s social attitudes).


 * 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, (theRoaring'20s, theGay'90s, condemning the '60s counterculture, but grew up in 1960s Boston, moving to Dallas in1971, and do not write the90's; the90s; or the90s').
 * A third alternative (where seen in reliable sources) is to spell the decade out, capitalized: changing attitudes of the Sixties

Centuries and millennia

 * 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 the 1700s ensure there is no ambiguity as to whether e.g. 1700–1709 or 1700–1799, is meant.
 * Note that the sequence of years runs ...2BC, 1BC, 1AD, 2AD... – there is no "year 0".
 * Centuries and millennia are identified using either figures (the 18th century, not XVIIIcentury) or words (the second millennium). When used adjectivally they contain a hyphen (nineteenth-century painting or 19th-century painting). Do not capitalize (the best Nineteenth-century paintings; during the Nineteenth Century).

Long periods of time

 * When the term is frequent, combine yr(years) or ya(years ago) with k(thousand): kya, kyr; M(million): Mya, Myr; and b(short-scale billion): bya, byr.
 * In academic contexts, SI annus-based units are often used: ka(kiloannus), Ma(megaannus), and Ga(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: "a measured Libby radiocarbon date of 35.1mya [million years ago] required calibration ..."

Numbers as figures or words
Generally, in article text:
 * Integers from zero to nine are spelled out in words.
 * Integers greater than nine may be expressed either in numerals or in words (16 or sixteen, 84 or eighty-four, 200 or two hundred). In spelling out numbers, components from 21 to 99 are hyphenated; larger ones are not (fifty-six, five hundred).
 * Other numbers are given in numerals (3.75, 544) or in forms such as 21million. Markup:
 * "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.
 * M (unspaced) or bn (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., She received &pound;70million and her son &pound;10M).
 * SI prefixes and symbols, such as giga-(G) and tera-(T), 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., 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 three crore (thirty million). Group digits in Western thousands-based style (e.g., 30,000,000; not 3,00,00,000); . (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.)

Notes and exceptions:


 * In tables and infoboxes, quantities are expressed in figures (Years in office:5); but numbers within a table's explanatory text and comments follow the general rule.
 * Numbers in mathematical formulae are never spelled out (3<π<22/7, not three < π < 22 sevenths).
 * Comparable quantities should be all spelled out or all in figures:
 * &bull; five cats and thirty-two dogs, not five cats and 32 dogs.
 * &bull; 86men and 103women, not eighty-six men and 103 women
 * &bull; There were 3 deaths and 206 injuries, even though 3 would normally be given as three; or Three died and two hundred six were injured (or two hundred and six in British English), even though two hundred six would normally be given as 206); but not There were three deaths and 206 injuries.


 * But adjacent quantities not comparable should usually be in twelve 90-minute volumes or 12 ninety-minute volumes, not 12 90-minute volumes or twelve ninety-minute volumes.
 * Avoid awkward juxtapositions: On April 28, 2006, thirty-one more died, not On April 28, 2006, 31 more died.


 * Personal ages are typically stated in figures (8-year-old child) except for large, approximate values (69-million-year-old fossil).
 * Sometimes figures and words carry different meanings; for example Every locker except one was searched implies there is a single exception (without specifying which), while Every locker except1 was searched means that only locker number1 was not searched.
 * Proper names, technical terms, and the like are never altered: Seven Samurai; The Sixth Sense; 5Channel Street; Channel5; Chanel No.5; Fourth Estate; The Third Man; Second Judicial District; First Amendment; Zero Hour!; Less Than Zero


 * Avoid beginning a sentence with figures:
 * &bull;  Not There were many attacks. 23 men were killed,
 * but There were many attacks; 23men were killed or There were many attacks. Twenty-three men were killed.
 * &bull;  Not 1945 and 1950 saw crucial elections (nor Nineteen forty-five and 1950 saw crucial elections – because comparable numbers should be both written in words or both in figures) but The elections of 1945 and 1950 were crucial.
 * Exception: Where a proper name, technical term, etc., itself beginning with a numeral, opens the sentence (1-Naphthylamine is typically synthesized via the Feldenshlager–Glockenspiel process) although this can usually be avoided by rewording (Feldenshlager–Glockenspiel is the process typically used in the synthesis of 1-naphthylamine).

Ordinals

 * Ordinal suffixes (-st, -nd, -rd, -th) are not superscripted (123rd and 496th, not 123rd nor 496th).
 * Regnal numbers are normally written with roman [sic] numerals (without suffix, e.g. Elizabeth II not Elizabeth IInd).
 * Do not use a dot (.) or the ordinal mark (&#186;) to indicate ordinals.

Singular versus plural

 * Nouns following simple fractions are singular (He took $1/undefined$ dose; net change in score was &minus;$1/undefined$ point; $3/2$ dose).
 * Nouns following mixed numbers are plural (suicide victim knew even 1$1/2$ doses could be fatal; continued another 4$3/4$ miles).
 * 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 (increased 0.7 percentage points; 365.25 days; paid 5 dollars per work hour, 1 dollar per travel hour, 0 dollars per standby hour; increased by 1 point but net change +1 points; net change &minus;1 points; net change 1.0 points).
 * The same rules apply to numbers given in words (one dose; one and one-half doses; zero dollars; net change negative one points).

Fractions and ratios

 * Spelled-out fractions are hyphenated: seven-eighths.
 * Where numerator and denominator can each be expressed in one word, a fraction is usually spelled out (e.g. a two-thirds majority; moved one-quarter mile); use figures if a fraction appears with a symbol (e.g. $1/4$mi – markup:, not a quarter of a mi or one-quarter mi).
 * Mixed numbers are usually given in figures, unspaced (not Fellini's film 8$1/2$ or 8-$1/2$ but Fellini's film $8 1/2$ – markup:  ). In any case the integer and fractional parts should be consistent (not nine and$8 1/2$).
 * Metric (SI) measurements generally use decimals, not fractions (5.25mm, not 5$1/2$mm).
 * Non-metric (imperial and US customary) measurements may use fractions or decimals (5$1/4$inches;5.25inches); 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 1$1/4$ times the original voltage, but 4/3 the original) and use of is discouraged in favor of one of these styles:
 * &bull;  $$\textstyle\frac{1}{2}$$ – markup:
 * &bull;  $1/3$ – markup:
 * &bull;  1/2 – markup:


 * Do not use special characters such as "&frac12;" (deprecated markup: or  ).
 * Ordinal suffixes such as -th should not be used with fractions expressed in figures (not each US state has 1/50th of the Senate's votes; 1/8th mile, but one-fiftieth of the Senate's votes;  1/8 mile;  one-eighth mile).
 * Dimensionless ratios (i.e. those not incorporating units) are given using numerals and a colon, or numbers-as-words and to: favored by a 3:1 ratio or a three-to-one ratio, but not a 3/1 ratio or a 3–1 ratio. Use a "spaced" colon when a decimal point is present (a 3.5 : 1 ratio – markup: ). Do not use the colon form where units are involved (dissolve using a 3 ml:1 g ratio)—‌instead see ratios section of table at § Unit names and symbols, below. 

Decimals

 * A period/full point, a comma, is used as the decimal point (6.57, not 6,57).
 * Numbers between −1 and +1 require a leading zero (0.02, not .02); exceptions are sporting performance averages (.430 batting average) and commonly used terms such as .22caliber.
 * Indicate repeating digits with an overbar e.g. gives 14.31$1⁄2$. (Consider explaining this notation on first use.) Do not write e.g. 14.31(28) because it resembles notations for.

 Grouping of digits

 * Digits should be grouped and separated either by commas or narrow gaps ( 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. 12,200,  255,200 km,  8,274,527th,  $\overline{28}$).
 * Numbers with exactly four digits left of the decimal point may optionally be grouped (either 1,250  or  1250), 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: produces this formatting.
 * Grouping with narrow gaps
 * Digits are grouped both sides of the decimal point (e.g. $\overline{28}$,  $1/undefined$,  $6,543,210.123$).
 * Digits are generally grouped into threes. Right of the decimal point, practice is to have a final group of four instead of a lone digit (e.g.  $520.012 degC$  or  99.123 456  7). In mathematics-oriented articles long strings may be grouped into fives (e.g.  3.14159 26535  89793  23846  ...).
 * This style is especially recommended for articles related to science, technology, engineering or mathematics.
 * Markup: Templates or  may be used to produce this formatting. Note that use of  space character in numbers, including non-breaking space, is problematic for screen readers.   Screen readers read out each  of digits as separate numbers (e.g.     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  sailed in 1,492,  though  dynasty collapsed around 10,400 BC  or  by $101,325⁄760$, Vega will be the northern pole star).

Percentages

 * In the body of non-scientific/non-technical articles, percent (American English) or per cent (British English) are commonly used: 10 percent; ten percent; 4.5 per cent. Ranges are written ten to twelve per cent or ten to twelve percent, not ten–twelve per cent or ten to twelve %.
 * In the body of scientific/ technical articles, and in of any article, the symbol   (unspaced) is more common: 71%, not 71 % or three %. Ranges: 10–12%, not 10%–12% or 10 to 12%.
 * 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 $99.123$, but $13,727 AD$.
 * Engineering notation is similar, but adjusted so that the exponent is a multiple of three: $60.22$.
 * Avoid mixing scientific and engineering notations (A $6.022$ region covered by $602.2$).
 * In a table column (or other presentation) in which all values can be expressed with a single power of 10, consider giving e.g. once in the column header, and omitting it in the individual entries. (Markup:  )
 * In both notations, the number of digits indicates the precision. For example, $2.23 m2$ means rounded to the nearest thousand; $234 grains of sand$ to the nearest hundred; $5$ to the nearest ten; and $5$ to the nearest unit.

Markup: and  may be used to format exponential notation.

Uncertainty and rounding

 * Where explicit uncertainty information (such as a margin of error) is available and appropriate for inclusion, it may be written in various ways:
 * &bull; (1.534 ± 0.035) × 1023 m
 * &bull; 12.34m2 ± 5% (not used with scientific notation)
 * &bull; 15.34 $5$ × 1023 m
 * &bull; 1.604(48) × 10−4 J (equivalent to (1.604 ± 0.048) × 10−4 J)
 * &bull; Polls estimated Jones's share of the vote would be 55 percent, give or take about 3 percent
 * Markup:, , and may be used to format uncertainties.


 * Where explicit (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.
 * &bull;  The speed of light is defined to be 299,792,458m/s
 * Particle velocities eventually reached almost two-thirds the 300-million-metre-per-second speed of light
 * &bull;  The city's 1920 population was 667,000 (not population was 666,666 – an official figure unlikely to be accurate at full precision)
 * The town was ineligible because its official census figure (9,996) fell short of the statutory minimum of ten thousand (unusual case in which the full-precision official population figure is helpful to readers)
 * &bull;  The accident killed 337 passengers and crew, and three airport workers (likely that accurate and precise figures were determined)
 * &bull;  At least 800 persons died in the ensuing mudslides (unlikely that any precise number can be accurate, even if an official figure is issued)
 * Officials listed 835 deaths, but the Red Cross said dozens more may have gone unreported (in reporting conflicting information, give detail sufficient to make the contrast intelligible)
 * &bull;  The jury's award was $8.5million... (where the actual figure was $8,462,247.63) ... – reduced on appeal to $3,000,001 (one dollar in actual damages, the remainder in punitive damages)


 * The number of decimal places should be consistent within a list or context (The response rates were 41.0 and 47.4 percent, respectively, not 41 and 47.4 percent), unless different precisions are actually intended.
 * It may sometimes be appropriate to note the of uncertainty information, especially where such information is normally provided and necessary for full interpretation of the figures supplied.
 * &bull;  A local newspaper poll predicted 52 percent of the vote would go to Smith, but did not publish information on the uncertainty of this estimate


 * The 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.
 * &bull;  The tallest player was 6 feet 3 inches (not ... about 6 feet 3 inches – heights are conventionally reported only to the nearest inch, even though greater precision may be available in principle)
 * The witness said the assailant was about 5 feet 8 inches tall ("about" because here the precise value is unknown, with substantial uncertainty)


 * The reader may be assumed to interpret large round numbers (100,000 troops) as approximations. Writing a quantity in words (one hundred thousand troops) can further emphasize its approximate nature.



Non-base-10 notations

 * In computer-related articles, use the C programming language prefixes  (zero-ex) for hexadecimal and   (zero) for octal.  For binary, use  .  Explain these prefixes in the article's introduction or on first use.
 * In all other articles, use  to create subscripts: 1379, 2013. Markup: 137 9, 201 3
 * 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.

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. 200 km. For details on when and how to provide a conversion, see the section. 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. 97pounds (44kg).
 * 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/ length, 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 feet /inches and stones/ pounds;
 * imperial pints are used for quantities of draught beer/ cider 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).


 * 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: During metrification, the speed limit was changed from 30miles per hour (48kilometers per hour) to 50km/h (31mph).
 * This may benefit from a slightly non-standard structure, such as ...from 30miles per hour (about 48kilometers per hour) to 50km/h (about 31mph). In this sort of case, using about can help make clear which is the statutory, exact value.
 * Nominal quantities (e.g. 2 &times; 4 lumber) 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.
 * Where the article's primary units differ from the units given in the source, the template's   flag can be used; this causes the  unit to be shown as secondary in the article, and the  unit to be shown as primary:   &rarr; The two cities are 200 mi apart.

Unit names and symbols

 * Examples of unit names: foot, meter, kilometer.
 * Examples of unit symbols: ft, m, km.
 * 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. Up to 15 kilograms of filler is used for a batch of 250kg).
 * Exception: Certain units are generally represented by their symbols (e.g. &deg;C rather than degrees Celsius) even on first use, though their unit names may be used for emphasis or clarity (automatic conversion of degrees Celsius to degrees Fahrenheit).
 * Exception: Consider using inches in place of in where the latter might be misread as a preposition—‌but not where the value is followed by a parenthesized conversion e.g. bolts 5 in (12.7 cm) long, or is part of such a conversion (bolts 12.7 cm (5 in) long).


 * 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 (Energies were originally 2.3 megaelectronvolts (MeV), but were eventually 6MeV).
 * Ranges use unspaced en dash if only one unit symbol is used at the end (e.g. 5.9–6.3kg), and spaced en dash  if two symbols are used (e.g. 3μm – 1mm); 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. from 5.9 to 6.3 kilograms, from 5.9 kilograms to 6.3 kilograms, from 5.9 to 6.3kg and from 5.9kg to 6.3kg are all acceptable).
 * Length–width, length–width–height and similar dimensions may be separated by the multiplication sign or the word by.
 * With the multiplication sign, each number should be followed by a unit name or symbol (if appropriate):
 * &bull; 1m &times; 3m &times; 6m, not 1 &times; 3 &times; 6 m, (1 &times; 3 &times; 6)m nor 1 &times; 3 &times; 6m3
 * &bull; a metal plate 1ft &times; 3ft &times; 0.25in
 * &bull; a railroad easement 10ft &times; 2.5mi
 * With by, the unit need be given only once: 1 by 3 by 6 metres or 1 by 3 by 6 m
 * The unspaced letter x may be used in common terms such as 4x4.

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
In quantities of bits and bytes, the prefixes kilo- (symbol k or K), mega- (M), giga- (G), tera- (T), 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.

Follow these recommendations when using these prefixes in Wikipedia articles:


 * Following the SI standard, a lower-case k should be used for "kilo-" whenever it means 1000 in computing contexts, whereas a capital K 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 Ki 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 ( 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:
 * &bull; A 64MB (64 &times; 10242-byte) video card and a 100GB (100 &times; 10003-byte) hard drive
 * &bull; A 64MB (64 &times; 220-byte) video card and a 100GB (100 &times; 109-byte) hard drive
 * &bull; A 64MB (67,108,864-byte) video card and a 100GB (100,000,000,000-byte) hard drive


 * Avoid inconsistent combinations such as A 64MB (67,108,864-byte) video card and a 100GB (100 &times; 10003-byte) hard drive. Footnotes, such as those seen in [//en.wikipedia.org/w/index.php?title=Power_Macintosh_5500&oldid=218088888 Power Macintosh 5500], may be used for disambiguation.
 * Unless explicitly stated otherwise, one byte is eight bits.

The IEC prefixes kibi- (symbol Ki), mebi- (Mi), gibi- (Gi), 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
Where English-speaking countries use different units for the same quantity, follow the "primary" quantity with a conversion in parentheses: the Mississippi River is 2320 mi long; the Murray River is 2508 km long. In science-related articles, however, supplying such conversion is not required unless there is some special reason to do so.
 * Where an imperial unit is not part of the US customary system, or vice-versa – and in particular, where those systems give a single term different definitions – a double conversion may be appropriate: Rosie weighed 80 kg (markup: ); The car had a fuel economy of 5 L/100km (markup:  ).
 * 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 (The four-minute mile).
 * When units are part of the subject of a topic – nautical miles in articles about the history of nautical law (5 nautical miles), SI units in scientific articles (a 600-kilometer asteroid), 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 similar to that of the source quantity value, so the Moon is 380,000kilometres (240,000mi) from Earth, not (236,121mi). Small numbers may need to be converted to a range where rounding would cause a significant distortion, so one mile (1–2km), not one mile (2km).  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, 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.
 * may be added to articles needing general attention regarding choice of units and unit conversions.

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 ($123), euros (&euro;123), or pounds sterling (&pound;123).

Currency names

 * Do not capitalize the names or denominations of currencies, currency subdivisions, coins and banknotes: not a Five-Dollar bill, four Quarters, and one Penny total six Dollars one Cent but a five-dollar bill, four quarters, and one penny total six dollars one cent. Exception: where otherwise required, as at the start of a sentence or in such forms as Australian dollar.
 * To pluralize euro use the standard English plurals (ten euros and fifty cents), not the invariant plurals used for European Union legislation and banknotes (ten euro and fifty cent). For the adjectival form, use a hyphenated singular: (a two-euro pen and a ten-cent coin).
 * Link the first occurrence of lesser-known currencies (Mongolian tögrögs).

Currency symbols

 * In general, the first mention of a particular currency should use its full, unambiguous signifier (e.g. A$52), with subsequent references using just the appropriate symbol (e.g. $88), unless this would be unclear.
 * 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. US$, A$) 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 (&euro;26, &pound;22 or $34), unless this would be unclear.


 * The pound sterling is represented by the &pound; symbol, with one horizontal bar. The double-barred &#8356; 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&pound;) 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 ($6.57, not $6,57).
 * Do not place a currency symbol the accompanying numeric figures (e.g. 123$, 123&pound;, 123&euro;) unless that is the normal convention for that currency when writing in English. Never use forms such as $US123 or $123 (US).
 * Currency abbreviations that come before the numeric value are if they consist of a nonalphabetic symbol only, or end in a symbol (&pound;123; &euro;123); but  if alphabetic (R75).
 * Ranges should be expressed giving the currency signifier just once: $250–300, not $250–$300.
 * million and billion should be spelled out on first use, and (optionally) abbreviated M or bn (both unspaced) thereafter: She received &pound;70 million and her son &pound;10M; the school's share was $250–300 million, and the charity's $400–450M.
 * In general, a currency symbol should be accompanied by a numeric amount e.g. not He converted his US$ to A$ but He converted his US dollars to Australian dollars or He exchanged the US$100 note for Australian dollars.
 * Exceptions may occur in tables and infoboxes where space is limited e.g. Currencies accepted for deposit: US$, SFr, GB&pound;, &euro;. It may be appropriate to wikilink such uses, or add an explanatory note.
 * Exceptions may occur in tables and infoboxes where space is limited e.g. Currencies accepted for deposit: US$, SFr, GB&pound;, &euro;. It may be appropriate to wikilink such uses, or add an explanatory note.

Conversions

 * Conversions of 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  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. Since 2001 the grant has been 10,000,000 Swedish kronor ($1.4M, &euro;1.0M, or &pound;800k ), not ($1,390,570, &euro;971,673 or &pound;848,646).
 * For, 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

 * 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. ) shown here.
 * Spaces are placed to left and right when a symbol is used with two operands, but no space with one operand.
 * Use or  for variable names:   and   both produce base + ht.
 * The and  templates may be used to prevent awkward linebreaks.

Geographical coordinates



 * Quick guide:

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:
 * offers users a choice of display format through user styles, emits a Geo microformat, and is recognised (in the 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, which automatically emit.

The following formats are available.
 * For degrees only (including decimal values):
 * For degrees/minutes:
 * For degrees/minutes/seconds:

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&prime; N, 10° 44&prime; E:
 * – which becomes 59.91667°N, 10.73333°W

For a country, like Botswana, less precision is appropriate:
 * – which becomes -22°N, 24°W

Higher levels of precision are obtained by using seconds:
 * – which becomes 33.94°N, -118.4°W

Coordinates can be entered as decimal values
 * – which becomes -33.94°N, -118.4°W

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 the coordinates should be. For example, if just giving the location of a city, precision greater than 100meters 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 10meters or even one meter in some cases (1′′ ~15m to 30m, 0.0001° ~5.6m to 10m).

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

When adding coordinates, please remove the tag from the article, if present.

Templates other than should use the following variable names for coordinates: lat_d, lat_m, lat_s, lat_NS, long_d, long_m, long_s, long_EW.