text:
Glass electrode

A glass electrode is a type of ion-selective electrode made of a doped glass membrane that is sensitive to a specific ion. The most common application of ion-selective glass electrodes is for the measurement of pH. The pH electrode is an example of a glass electrode that is sensitive to hydrogen ions. Glass electrodes play an important part in the instrumentation for chemical analysis, and physicochemical studies. The voltage of the glass electrode, relative to some reference value, is sensitive to changes in the activity of a certain type of ions.

History
The first studies of glass electrodes (GE) found different sensitivities of different glasses to change the medium's acidity (pH), due to the effects of the alkali metal ions.

In 1906, M. Cremer, the father of Erika Cremer, determined that the electric potential that arises between parts of the fluid, located on opposite sides of the glass membrane is proportional to the concentration of acid (hydrogen ion concentration).

In 1909, S. P. L. Sørensen introduced the concept of pH, and in the same year F. Haber and Z. Klemensiewicz reported results of their research on the glass electrode in The Society of Chemistry in Karlsruhe. In 1922, W. S. Hughes showed that the alkali-silicate glass electrodes are similar to hydrogen electrodes, reversible concerning H+.

In 1925, P. M. Tookey Kerridge developed the first glass electrode for analysis of blood samples and highlighted some of the practical problems with the equipment such as the high resistance of glass (50–150 MΩ). During her PhD, Kerridge developed a glass electrode aimed to measure small volume of solution. Her clever and careful design was a pioneering work in the making of glass electrodes.

Applications
Glass electrodes are commonly used for pH measurements. There are also specialized ion-sensitive glass electrodes used for the determination of the concentration of lithium, sodium, ammonium, and other ions.

Glass electrodes find a wide diversity of uses in a large range of applications including research labs, control of industrial processes, analysis of foods and cosmetics, monitoring of environmental pollution, or soil acidity measurements…. Micro-electrodes are specifically designed for pH measurements on very small volumes of fluid, or for direct measurements in geochemical micro-environments, or in biochemical studies such as for determining the electrical potential of cell membrane.

Heavy duty electrodes withstanding several tens of bar of hydraulic pressure also allow measurements in water wells in deep aquifers, or to directly determine in situ the pH of pore water in deep clay formations. For long-term in situ measurements, it is critical to minimize the KCl leak from the reference electrode compartment (Ag / AgCl / KCl 3 M), and to use glycerol-free electrodes to avoid fuelling microbial growth, and to prevent unexpected but severe perturbations related to bacterial activity (pH decrease due to sulfate-reducing bacteria, or even methanogen bacteria).

Types
All commercial electrodes respond to single-charged ions, such as H+, Na+, Ag+. The most common glass electrode is the pH-electrode. Only a few chalcogenide glass electrodes are presently known to be sensitive to double-charged ions, such as Pb2+, Cd2+, and some other divalent cations.

There are two main types of glass-forming systems:
 * 1) The most common one: a silicate matrix based on an amorphous molecular network of silicon dioxide (SiO2, the network former) with additions of other metal oxides (network modifiers), such as Na, K, Li, Al, B, Ca…, and;
 * 2) A less used one: a chalcogenide matrix based on a molecular network of AsS, AsSe, or AsTe.

Interfering ions
Because of the ion-exchange nature of the glass membrane, it is possible for some other ions to concurrently interact with ion-exchange sites of the glass, and distort the linear dependence of the measured electrode potential on pH or other electrode functions. In some cases, it is possible to change the electrode function from one ion to another. For example, some silicate pPNA electrodes can be changed to pAg function by soaking in a silver salt solution.

Interference effects are commonly described by the semi-empirical Nicolsky-Shultz-Eisenman equation (also known as Nikolsky-Shultz-Eisenman equation), an extension to the Nernst equation. It is given by:
 * $$E=E^0 + \frac{RT}{z_iF} \ln \left [ a_i + \sum_{j} \left ( k_{ij}a_j^{z_i/z_j} \right ) \right ]$$

where E is the electromotive force (emf), E0 the standard electrode potential, z the ionic valency including the sign, a the activity, i the ion of interest, j the interfering ions and kij is the selectivity coefficient quantifying the ion-exchange equilibrium between the ions i and j. The smaller the selectivity coefficient, the less is the interference by j.

To see the interfering effect of Na+ to a pH-electrode:
 * $$E=E^0 + \frac{RT}{F} \ln \left ( a_{\text{H}^+} + k_{\text{H}^+,\text{Na}^+}a_{\text{Na}^+} \right )$$

Range of a pH glass electrode
The pH range at constant concentration can be divided into 3 parts:
 * Undisturbed electrode function, where potential linearly depends on pH, realizing an ion-selective electrode for hydronium.
 * $$E=E^0 - \frac{2.303RT}{F} \text{pH}$$

where F is Faraday's constant (see Nernst equation). The effect is usually noticeable at pH > 12, and at concentrations of lithium or sodium ions of 0.1 mol/L or more. Potassium ions usually cause less error than sodium ions.
 * Alkali error range – at low concentration of hydrogen ions (high values of pH) contributions of interfering alkali metals ions (such as Li+, Na+, K+) are comparable with one of the hydrogen ions. In this situation dependence of the potential on pH become non-linear.
 * Acidic error range – at a very high concentration of hydrogen ions (low values of pH) the dependence of the electrode on pH becomes non-linear, and the influence of the anions in the solution also becomes noticeable. These effects usually become noticeable at pH < -1.

Special electrodes exist for working in extreme pH ranges.

Construction
A typical modern pH probe is a combination electrode, which combines both the glass and reference electrodes into one body. The combination electrode consists of the following parts (see the drawing):

 * 1) A sensing part of electrode, a bulb made from a specific glass.
 * 2) Internal electrode, usually silver chloride electrode or calomel electrode.
 * 3) Internal solution, usually a pH=7 buffered solution of 0.1 mol/L KCl for pH electrodes or 0.1 mol/L MCl for pM electrodes.
 * 4) When using the silver chloride electrode, a small amount of AgCl can precipitate inside the glass electrode.
 * 5) Reference electrode, usually the same type as 2.
 * 6) Reference internal solution, usually 3.0 mol/L KCl.
 * 7) Junction with studied solution, usually made from ceramics or capillary with asbestos or quartz fiber.
 * 8) Body of electrode, made from non-conductive glass or plastics.

The bottom of a pH electrode balloons out into a round thin glass bulb. The pH electrode is best thought of as a tube within a tube. The inner tube contains an unchanging 1×10−7 mol/L HCl solution. Also inside the inner tube is the cathode terminus of the reference probe. The anodic terminus wraps itself around the outside of the inner tube and ends with the same sort of reference probe as was on the inside of the inner tube. It is filled with a reference solution of KCl and has contact with the solution on the outside of the pH probe by way of a porous plug that serves as a salt bridge.

Galvanic cell schematic representation
This section describes the functioning of two distinct types of electrodes as one unit which combines both the glass electrode and the reference electrode into one body. It deserves some explanation.

This device is essentially a galvanic cell that can be schematically represented as:

 * Internal electrode | Internal buffer solution || Test Solution || Reference solution | Reference electrode
 * Ag(s) | AgCl(s) | 0.1 M KCl(aq), 1×10−7M H+ solution || Test Solution || KCl(aq) | AgCl(s) | Ag(s)

The double "pipe symbols" (||) indicate diffusive barriers – the glass membrane and the ceramic junction. The barriers prevent (glass membrane), or slow down (ceramic junction), the mixing of the different solutions.

In this schematic representation of the galvanic cell, one will note the symmetry between the left and the right members as seen from the center of the row occupied by the "Test Solution" (the solution whose pH must be measured). In other words, the glass membrane and the ceramic junction occupy both the same relative places in each electrode. By using the same electrodes on the left and right, any potentials generated at the interfaces cancel each other (in principle), resulting in the system voltage being dependent only on the interaction of the glass membrane and the test solution.

The measuring part of the electrode, the glass bulb on the bottom, is coated both inside and out with a ~10 nm layer of a hydrated gel. These two layers are separated by a layer of dry glass. The silica glass structure (that is, the conformation of its atomic structure) is shaped so that it allows Na+ ions some mobility. The metal cations (Na+) in the hydrated gel diffuse out of the glass and into solution while H+ from solution can diffuse into the hydrated gel. It is the hydrated gel which makes the pH electrode an ion-selective electrode.

H+ does not cross through the glass membrane of the pH electrode, it is the Na+ which crosses and leads to a change in free energy. When an ion diffuses from a region of activity to another region of activity, there is a free energy change and this is what the pH meter actually measures. The hydrated gel membrane is connected by Na+ transport and thus the concentration of H+ on the outside of the membrane is 'relayed' to the inside of the membrane by Na+.

All glass pH electrodes have extremely high electric resistance from 50 to 500 MΩ. Therefore, the glass electrode can be used only with a high input-impedance measuring device like a pH meter, or, more generically, a high input-impedance voltmeter which is called an electrometer.

Limitations
The glass electrode has some inherent limitations due to the nature of its construction. Acid and alkaline errors are discussed above. An important limitation results from the existence of asymmetry potentials that are present at glass/liquid interfaces. The existence of these phenomena means that glass electrodes must always be calibrated before use; a common method of calibration involves the use of standard buffer solutions. Also, there is a slow deterioration due to diffusion into and out of the internal solution. These effects are masked when the electrode is calibrated against buffer solutions but deviations from ideal response are easily observed by means of a Gran plot. Typically, the slope of the electrode response decreases over a period of months.

Storage
Between measurements any glass and membrane electrodes should be kept in a solution of its own ion. It is necessary to prevent the glass membrane from drying out because the performance is dependent on the existence of a hydrated layer, which forms slowly.

title: Glass electrode


text:
Goran Svilanović

Goran Svilanović (Горан Свилановић; born 22 October 1963) is a Serbian politician and diplomat who was the Secretary General of the Regional Cooperation Council (RCC), from 1 January 2013 until 31 December 2018, following the appointment by the South-East European Cooperation Process (SEECP) Foreign Ministers in Belgrade, Serbia on 14 June 2012.

Career
Svilanović has been active in politics since 1993. He became president of the Civic Alliance of Serbia (Građanski Savez Srbije) in 1999 and held this position until 2004, when he resigned. From 2000 to 2004, he was Minister of Foreign Affairs of the Federal Republic of Yugoslavia, which was renamed Serbia and Montenegro in 2003. After years of negotiations, disagreements and delays he signed the Agreement on Succession Issues of the Former Socialist Federal Republic of Yugoslavia on behalf of Federal Republic of Yugoslavia. He served from November 2004 until the end of 2007 as the chairman of Working Table I (democratization and human rights) of the Stability Pact for South Eastern Europe. He was also a member of the Senior Review Group of the Stability Pact, which proposed the transformation of the Stability Pact into the Regional Co-operation Council. He served as coordinator of the OSCE Economic and Environmental Activities (2008–2012).

Since 2008, Svilanović has been assistant professor of law at Union University in Belgrade. He has also been engaged and worked with a number of organizations and committees, such as the Centre for Antiwar Action (1995–1999), the International Commission on the Balkans (2004–2006) and the Belgrade Centre for Human Rights (2007–2008). He is a Senior Network Member at the European Leadership Network (ELN).

Currently he is serving as the advisor of the cabinet of Zdravko Krivokapić for economic reforms and European integration.

Education
Svilanović holds a PhD from the Union University in Belgrade, Masters and undergraduate law degrees from the University of Belgrade Faculty of Law. He has also studied at the Institute for Human Rights in Strasbourg, France, the University of Saarland, Germany, and the European University Center for Peace Studies in Staadtschlaining, Austria.

Personal life
The Svilanović family moved from Gnjilane to Belgrade when Goran was seven. His father Tihomir held a doctoral degree in agricultural science and his mother Stavrula was an accountant. Svilanović is married and has two children. He speaks Serbian and English. He recognizes the independence of Kosovo.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Goran Svilanović


text: Category:Ardèche

title: Category:Ardèche


text:
Talk:Streptococcus salivarius

google says it is pathogenic. Mikkalai 09:05, 13 Feb 2005 (UTC)
 * No, Google says it's used in yogurt manufacturing. I removed the dispute tag. — Brim 10:19, Feb 13, 2005 (UTC)
 * No, google says it is pathogenic as well. Accuracy tag placed. This is not the same as "dispute". I am not disputing what is written. I am saying that This pathogenicity is  too important issue, so that the article becomes inaccurate. In the present form the article is like saying that hydrocyanic acid is the thingy that makes the cherry wine so tasty. Mikkalai 18:59, 13 Feb 2005 (UTC)
 * Could you be so kind as to provide a link to article that says S. salivarius is pathogenic? Everything that I've come across says that it's a part of the normal human oropharyngeal flora and is used in the manufacture of yogurt. — Brim 00:14, Feb 14, 2005 (UTC)

http://www.phac-aspc.gc.ca/msds-ftss/msds149e.html

SECTION II - HEALTH HAZARD

PATHOGENICITY: Organisms colonize upper respiratory tract within first few hours after birth and are normal inhabitant of oral cavity, oropharynx and upper respiratory tract; infrequently pathogenic; Viridans streptococci species cause most dental caries and are the most frequent cause of subacute native valve bacterial endocarditis, typically associated with dental procedures; S. salivarius may cause septicemia in neutropenic patients

EPIDEMIOLOGY: World wide; Dental caries common; persons with previously damaged heart valves are susceptible

HOST RANGE: Humans

INFECTIOUS DOSE: Not known

MODE OF TRANSMISSION: Normal inhabitant of upper respiratory tract - trauma (dental work, brushing teeth, etc.) results in organisms entering into the blood stream

INCUBATION PERIOD: Not known

COMMUNICABILITY: Not transferred from person-to-person

General Internet USER Response: GUYS Brim is probably more 'right' than you are Mikkalai. Salivarius is NATURAL to the human mouth cavity and is [practically] the exclusive lactobacilli found in the human mouth soon after birth and prior to the 1st teething of the child. Once the child teeths other bactrial flora start to dominate (S.Mutans, Acidophilus, Thermophilus, etc.). While I'm not disputing the Salivarius has been found in Heart Valves, the pathogenity is still in question. You should be made aware the S. Salivarius is the LIVE active ingredient in a mouthwash approved by regulators in the EU, UK, Australia and New Zealand for NON-PRESCRIPTION daily use. This particular mouthwash is being marketed for fighting Chronic Halitosis by using Salivarius bacteria to kill and starve the Anaerobic Sulfurous Gas producing bacteria that cause halitosis. If this bacteria was such a pathogen, Mikkalai, then regulators would not allow it be available freely and without a prescription.

Nonetheless Mikkalai has got a legitmate point about this particular bacterial species being implicated in Heart Valve infections. Anybody (professional researcher hopefully), that could shed light on the heart valve issue would be helpful. Please remember that many 'benign' microoganisms that exist in our bodies can become pathogenic under certain circumstances, that does not make these organisms pathogenic in general, and heart valves are not natural structures in our bodies. Quite frankly, we don't know if a flaw in the design of those heart valves may have contributed to the Salivirius colonies taking hold in the valves.

I Added some health information and removed the accuracy tag. Bunchofgrapes 20:26, 5 October 2005 (UTC)

D.Roy: Streptococcus thermophilus is now considered a full-fledge species and is no longer considered a subspecies of S. thermophilus. there are at least 3 complete genome of S. thermophilus out there (see ncbi pubmed) and it was shown that Thermophilus as no intact gene associated with pathogenicity.

On another subject, S. salvarius is NOT implicated with tooth decay, S. mutans is respnsible for that. furthermore, Streptococcus is not a lactobacilli... its a streptococcus, i.e. a coccus, or roud shaped bacteria in short chain (hence the "strepto") lactobacilli are rod shaped bacteria. Finally, S. salivarius is an opportunistic pathogen, i.e. by itself it wont do much but given the chance (immunodeficient patient) it may do some harm.

D.Roy (2006/02/01): S. salivarius is not involved in tooth decay, S. mutans is, so I changed that information in the article. Furthermore, I strongly believe that S. themophilus and S. salivarius should be splitted in two different article, since both are very different organism.

I also changed the statement where it was said that S. salivarius is used in cheese and yogurt production, Its the work of S. thermophilus.

Foor those who know how to do it... S. thermophilus should be erased from this section and added to its own section titled Streptococcus thermophilus... D. Roy

Copyright Violation
I've reverted material copied from http://microbewiki.kenyon.edu/index.php/Streptococcus_salivarius because of the copyright notice (http://microbewiki.kenyon.edu/index.php?title=Streptococcus_salivarius&action=history) indicating personal use only. Note that the material on the microbewiki was added before the material was added here based on comparin article histories. -- Whpq (talk) 17:33, 15 May 2008 (UTC)

title: Talk:Streptococcus salivarius


text:
Wikipedia talk:WikiProject Norway

Women in Green's 5th Edit-a-thon
 Hello WikiProject Norway:

WikiProject Women in Green is holding a  month-long Good Article Edit-a-thon event in October 2023!

Running from October 1 to 31, 2023, WikiProject Women in Green (WiG) is hosting a Good Article (GA) edit-a-thon event with the theme Around the World in 31 Days! All experience levels welcome. Never worked on a GA project before? We'll teach you how to get started. Or maybe you're an old hand at GAs – we'd love to have you involved! Participants are invited to work on nominating and/or reviewing GA submissions related to women and women's works (e.g., books, films) during the event period. We hope to collectively cover article subjects from at least 31 countries (or broader international articles) by month's end. GA resources and one-on-one support will be provided by experienced GA editors, and participants will have the opportunity to earn a special WiG barnstar for their efforts.

We hope to see you there! Grnrchst (talk) 13:32, 21 September 2023 (UTC)

Good article reassessment for Bergen Light Rail
Bergen Light Rail has been nominated for a good article reassessment. If you are interested in the discussion, please participate by adding your comments to the reassessment page. If concerns are not addressed during the review period, the good article status may be removed from the article. GeorgR (de) (talk) 15:31, 25 September 2023 (UTC)

Requested move at Talk:Sparebank
There is a requested move discussion at Talk:Sparebank that may be of interest to members of this WikiProject. ModernDayTrilobite (talk • contribs) 14:45, 13 October 2023 (UTC)

RfC of interest
(non-automated message) Greetings to all members of WP:NORWAY! I have opened an RfC on WT:ROYALTY that may be of interest to users of this WikiProject! You are encouraged to contribute to this discussion here! Hurricane Andrew (444) 22:59, 23 November 2023 (UTC)

Good article reassessment for Architecture of Norway
Architecture of Norway has been nominated for a good article reassessment. If you are interested in the discussion, please participate by adding your comments to the reassessment page. If concerns are not addressed during the review period, the good article status may be removed from the article. AirshipJungleman29 (talk) 19:59, 8 December 2023 (UTC)

Requested move at Talk:National Museum of Art, Architecture and Design
There is a requested move discussion at Talk:National Museum of Art, Architecture and Design that may be of interest to members of this WikiProject. Vanderwaalforces (talk) 17:56, 9 January 2024 (UTC)

Requested move at Talk:Capitalist Party
There is a requested move discussion at Talk:Capitalist Party that may be of interest to members of this WikiProject. Vanderwaalforces (talk) 01:05, 12 January 2024 (UTC)

Good article reassessment for Bergen Line
Bergen Line has been nominated for a good article reassessment. If you are interested in the discussion, please participate by adding your comments to the reassessment page. If concerns are not addressed during the review period, the good article status may be removed from the article. ~~ AirshipJungleman29 (talk) 02:29, 3 March 2024 (UTC)

how to talk 2003:E8:DF38:2C00:F98F:99FB:3CCB:2D90 (talk) 18:34, 6 March 2024 (UTC)

Andrée's Arctic balloon expedition
I have nominated Andrée's Arctic balloon expedition for a featured article review here. Please join the discussion on whether this article meets the featured article criteria. Articles are typically reviewed for two weeks. If substantial concerns are not addressed during the review period, the article will be moved to the Featured Article Removal Candidates list for a further period, where editors may declare "Keep" or "Delist" in regards to the article's featured status. The instructions for the review process are here. Z1720 (talk) 22:41, 12 July 2024 (UTC)

title: Wikipedia talk:WikiProject Norway


text:
Wikipedia talk:WikiProject Norway/to do

Create Norway-related articles

Requested articles: more…
 * Great Seal of the Realm,
 * Jacob Christian Bie
 * Johan Bertrand Narvesen
 * Olaf Gulbrandsson
 * Samuel Conrad Schwach
 * Agathon Bartholomæus Hansteen
 * Jan Erik Aalbu
 * Terje Kalheim
 * Ebba Wergeland
 * Hilde Bojer
 * Wenche Fossen
 * Sjelens Sang-Offer
 * Sennalandet
 * Vælern
 * Sørsamer
 * Many villages and small islands in Norway are absent from Wikipedia in English.
 * Many villages and small islands in Norway are absent from Wikipedia in English.
 * Many villages and small islands in Norway are absent from Wikipedia in English.
 * Many villages and small islands in Norway are absent from Wikipedia in English.
 * Many villages and small islands in Norway are absent from Wikipedia in English.
 * Many villages and small islands in Norway are absent from Wikipedia in English.

Building and structure stubs, Company stubs, Football club stubs, Geography stubs, History stubs, Musical group stubs, People stubs, more...
 * Stubs:

Egil Børre Johnsen, Larkollen, Olav Nordrå, Reinsvoll, Segalstad bru, Kaj Skagen, Johan Bernhard Hjort, more...
 * Translation request from Norwegian:

Jan Frode Andersen, Jan Eggum, Arve Moen Bergset, Gro Schibsted Sandvik, Egil Hegerberg, more...
 * Unreferenced biographies of living persons:

 * Tag the talk pages of Norway-related articles with the WikiProject Norway banner. See this page for newly created articles related to Norway.

 * Rate the Unassessed Norway articles. There are currently unassessed articles.

 * Populate the hierarchy Category:Disestablishments in Norway by year

title: Wikipedia talk:WikiProject Norway/to do


text:
List of universities and colleges in Macau

Macau is a city of tourism with a multicultural blend which provides a broad sense and international perspective for its college students. The free academic atmosphere and its profound and unique foundation in culture have also created favorable conditions for higher education. Most of the curricula, teachers and the general quality of teaching have reached an internationally accepted level.

Mainly English or Chinese (or both) are the languages of instruction in universities; some courses or programs are conducted in Portuguese.

The following is a list of universities, polytechnics and other advanced level (higher) education and research institutions in Macau.


text: Category:Islands of Singapore

title: Category:Islands of Singapore


text:
Edward R. Roybal Learning Center

Edward R. Roybal Learning Center (formerly known as Belmont Learning Center, Vista Hermosa Learning Center, and Central Los Angeles High School 11), is a secondary school located in the Westlake area of Los Angeles, California. Built to alleviate overcrowding at the nearby Belmont High School, the school's construction was met with controversy surrounding its cost and the discoveries of harmful gases and an earthquake fault, leading to a temporary suspension in 1999 that wasn't lifted until 2003. While development began in 1988, the school did not open until 20 years later on September 3, 2008.

History

Early planning and construction of a new school called the Belmont Learning Center began in 1988 as an effort to reduce overcrowding at the nearby Belmont High School, with some of the land previously used for the Los Angeles City Oil Field. The school received some pushback due to the cost and how it would be financed. It was designed by McLarand Vasquez & Partners, with the construction beginning in 1997. However, this was halted in 1999 after tests revealed methane and hydrogen sulfide gases within the land, stemming from the oil field. Two years later, with the construction stalled, it was revealed that the land was also situated on a major earthquake fault.

After the project was temporarily suspended in 2002, WWCOT took over from McLarand Vasquez & Partners in 2003 with the backing of new Superintendent Roy Romer and the LAUSD Board of Education. In 2004, more than half of the buildings were demolished in light of the earthquake fault. Construction was restarted in 2006, necessitating the demolition of some of the already completed classroom buildings and administration building. The total cost for the school was estimated to be around $400 million.

On March 25, 2008, the LAUSD Board of Education voted to rename the Vista Hermosa Learning Center to the Edward R. Roybal Learning Center, honoring former city councilman and Congressman Edward R. Roybal, who represented the area where the school is situated. On July 19, 2008, Vista Hermosa Park opened its doors before the fall opening of Roybal Learning Center, with an opening-day celebration that featured Mayor Antonio Villaraigosa and Supervisor Gloria Molina. On September 3, 2008, Roybal Learning Center opened for 2,400 students, with a ribbon-cutting ceremony held the day before.

Academics and programs
The Roybal Learning Center opened with four small learning communities—the International School of Languages (ISL), the Activists for Educational Empowerment (AEE), the Business and Finance Academy (BFA), and the Computer Science Academy (CSA)—as well as two independent pilot schools—Civitas School of Leadership and the School for Visual Arts and Humanities. The school later replaced ISL with the Academy for Social Work and Child Development (SWCD) and renamed the Activists for Educational Empowerment to Academy of Educational Empowerment. Each Academy has its own purpose and different techniques of teaching: BFA is more about involving students with the business atmosphere; SWCD trains students for jobs in the fields of social work and child development; CSA is about involving students with the computer atmosphere; and AEE provides their students with a sense of empowerment and helps them get involved.

In 2021, a new magnet school called the Roybal School of Film and Television Production opened on campus, with the support of high-profile celebrities such as George Clooney, Mindy Kaling, Kerry Washington, Eva Longoria and Don Cheadle.

Current schools

 * Downtown Magnets High School (2022–present)
 * Roybal School of Film and Television Production Magnet (2022–present)

Former schools

 * Civitas School of Leadership (2008–2014)
 * School for the Visual Arts and Humanities (2008–2015)
 * Los Angeles Academy of Art and Enterprise (2016–2021)

title: Edward R. Roybal Learning Center


text:
Wikipedia:Assume good faith/Vote

Voting has closed on this proposal.

Voting
This is to take this policy and make it official, rather than semi-official. Voting ends March 1, 2005 at 23:59 UTC. Please vote below. One vote per user is allowed; anonymous votes will be ignored. Comments regarding votes can be left below or on the vote Talk page. Discussion of the policy in general should be left on the parent article's Talk page.

For

 * 1)  AllyUnion (talk) 08:45, 13 Feb 2005 (UTC)
 * 2) Thryduulf 11:01, 13 Feb 2005 (UTC)
 * 3) utcursch 11:59, Feb 13, 2005 (UTC)
 * 4) Tsuyoshikentsu 06:02, 14 Feb 2005 (UTC)
 * 5) CheeseDreams 19:27, 14 Feb 2005 (UTC)
 * 6) Beta m (talk) 18:15, 2005 Feb 15 (UTC)
 * 7) Hyacinth 03:02, 2 Mar 2005 (UTC)
 * 8) 80.255 18:37, 9 Mar 2005 (UTC)

Against

 * 1) Charles Stewart 14:14, 13 Feb 2005 (UTC)
 * 2) Maurreen 20:21, 13 Feb 2005 (UTC)
 * 3) Carnildo 20:40, 13 Feb 2005 (UTC)
 * 4) Philip Baird Shearer 20:53, 13 Feb 2005 (UTC)
 * 5) —Charles P. (Mirv) 22:07, 13 Feb 2005 (UTC) See comments.
 * 6) Jmabel | Talk 01:00, Feb 14, 2005 (UTC) See comments.
 * 7) --Rje 03:39, Feb 14, 2005 (UTC)
 * 8) RickK 05:52, Feb 14, 2005 (UTC)
 * 9) Cyrius|✎ 06:10, 14 Feb 2005 (UTC)
 * 10) —  Stevie is the man!  Talk 11:26, 14 Feb 2005 (UTC)  See comments.
 * 11) Mgm|(talk) 12:16, Feb 14, 2005 (UTC)
 * 12) Jwrosenzweig 21:52, 14 Feb 2005 (UTC) (I'm opposed to even voting on making this "policy" -- doesn't make sense.  I don't see that this vote does anything but make a great piece of advice into an unnecessarily legalistic set of handcuffs.)
 * 13) This a principle, but not appropriate as a policy. -- Netoholic @ 02:07, 2005 Feb 15 (UTC)
 * 14) What they said.   — mark ✎ 02:09, 15 Feb 2005 (UTC)
 * 15) foobaz·✐ 02:30, 15 Feb 2005 (UTC)
 * 16) Chris 73 Talk 11:12, Feb 15, 2005 (UTC) Way to fuzzy, and not needed.
 * 17) r3m0t 17:10, 15 Feb 2005 (UTC) although I follow this myself and want other people to.
 * 18) llywrch 22:02, 15 Feb 2005 (UTC)
 * 19) Should remain a guideline. Tony Sidaway|Talk 12:52, 16 Feb 2005 (UTC)
 * 20) Theo  (Talk) 02:13, 26 Feb 2005 (UTC) Unenforcable.
 * 21) Chamaeleon 13:59, 26 Feb 2005 (UTC)
 * 22) SlimVirgin 13:28, Feb 27, 2005 (UTC)
 * 23) ral315 22:53, Feb 27, 2005 (UTC)
 * 24) --User:Boothy443 | comhrÚ 07:43, 1 Mar 2005 (UTC)
 * 25) If you need a policy to tell you to assume good faith, you shouldn't be part of a wiki. Dr Zen 06:28, 10 Mar 2005 (UTC)
 * 26) Wincoote 03:05, 13 Mar 2005 (UTC) This is a proposal to make unconditional naivety mandatory. I think that is absurd. People should be allowed to judge for themselves. It is obvious that there is a good deal of bad faith on Wikipedia and telling people to stick their heads in the sand won't change that. Wincoote 03:05, 13 Mar 2005 (UTC)

Neutral

 * 1)  AllyUnion (talk) 23:28, 14 Feb 2005 (UTC)

Comments

 * Seems like a good idea, however some editors (over a period of time) have demonstrated that they are not editing in good faith. An ammendment that clarifies this would be a good idea, IMO. - Ta bu shi da yu 09:45, 13 Feb 2005 (UTC)
 * I'm echoing Ta bu shi da yu's criticism, except I am rather pessimistic about the abusability of this rather Panglossian rule. For an example, if a series of POV edits appear on David Irving, eulogising his skills as a historian and putting down his court defeats as part of the global left-wing conspiracy, I am not going to assume good faith, and I will not appreciate well-meant Wikipedia rules directing me to do so, particularly if, say, the edits are from an IP address listed on various anti-fascist blacklists.  Be civil might be the name of a constructive policy, but policies telling me how to think are not constructive.  Charles Stewart 14:23, 13 Feb 2005 (UTC)
 * I agree with TBSDY and Charles. Further: How could such a policy be enforced? How can anyone assume to know what is someone else is thinking? And why no discussion before this poll? Maurreen 20:25, 13 Feb 2005 (UTC)
 * What is enforcable about this policy? --Carnildo 20:37, 13 Feb 2005 (UTC)
 * I've always thought this Wikipedia text should emphasize that one does always begin with the assumption of good faith. Then one soon learns through experience. I cringe every time I see this language brandished (and even linked! how self-righteous is that!) in heated discussion, used as a stick, often by the least collegial editors (I'm only selectively collegial myself, I know) to beat their current opponents who identified specific acts of furtiveness or manipulation. In another aspect, I have found that if I find an anon. edit has been reverted and look at the page history, I often find a history of vandalism. The corollary of "Assume Good Faith" is always "...but Expect more of the Same." --Wetman 21:56, 13 Feb 2005 (UTC)
 * I don't think we'd be served by making this an official policy. I think most editors already assume good faith until they have reason to do otherwise, and if they don't, how are we to tell? Then, too, it's sometimes appropriate not to assume good faith, if you have ample reason to believe otherwise. Making this an official policy would just give those who are acting in bad faith another screen for their behavior; as the MeatBallWiki page from which this is derived says:
 * Note that it is bordering on offensive to repeatedly shrill "You must AssumeGoodFaith, stop asking me questions!" whenever challenged - that is, to hide behind this social convention. In fact, we will assume you are not acting in good faith instead. It's better to obviously act in good faith than demand people read that into your actions.
 * —Charles P. (Mirv) 22:08, 13 Feb 2005 (UTC)
 * While I generally assume good faith, and think people should do so, there are people to whom I no longer grant this boon. There comes a point where it becomes clear that someone is acting in bad faith, beyond which I see no reason to continue to assume good faith. At some point that becomes just a license to troll. -- Jmabel | Talk 01:02, Feb 14, 2005 (UTC)
 * I agree with much which has already been said. I think this policy is unenforcable, and besides I think that most people do assume good faith for the most part anyway, apart from for a few persistant trolls/vandals etc. This kind of thing has to be taken on a case by case basis. Rje 03:44, Feb 14, 2005 (UTC)
 * I really don't understand how this can be a policy. So, what do we do if somebody doesn't follow it?  Ban them, because they assume somebody is behaving badly?  This is thought police stuff.  RickK 05:52, Feb 14, 2005 (UTC)
 * You have to assume good faith simply because this Wikipedia would be nonexistant without it. All right, that's a bit of an overstatement of fact, but if you want a NPOV article, you have to have edits by many biased people, which means allowing biased people to make edits, and then editing that.  There are two sides to every story, and within those two sides a combination of points of each are true.  So if a biased person makes an edit, another removes the untrue points and adds several of his own, and the first biased person removes the second's untrue points, you end up eith an unbiased, true article.Tsuyoshikentsu 06:22, 14 Feb 2005 (UTC)
 * I had held off on voting against this for a while. It left me feeling vaguely unsettled, and I just realized why. Making "assume good faith" official policy is contradictory. By saying "YOU MUST ASSUME GOOD FAITH", we fail to assume good faith. "Assume good faith" is a guideline to behavior, not a rule that can be dictated and enforced. -- Cyrius|✎ 06:16, 14 Feb 2005 (UTC)
 * In my reading through the Talk pages on the Wikipedia (for both articles and User pages), and looking through current and archived disputes (RfC, RfM, and RfAr), it is obvious that there are too many problems on the Wikipedia that start, or escalate, because one side or both sides started out by not assuming good faith. On the other hand, this does sound like an attempt to legislate thought rather than behavior. I think that it may be best for now to leave this as semi-policy that can still be cited by the Arbitration Committee in those cases where the behavior of an editor has been in flagrant violations of the policy. Blank Verse   ∅   11:22, 14 Feb 2005 (UTC)
 * You know what "they" say about assuming, right? Besides, I regularly run into editors who are trying to advertise things or inject material they should know to be incorrect, not just POV.  Therefore, I find this concept we're voting on to be Pollyanna-ish. —  Stevie is the man!  Talk 11:29, 14 Feb 2005 (UTC)
 * Policies should be enforceble and this one isn't unless it's clearly defined, when bad faith is evident. Mgm|(talk) 12:18, Feb 14, 2005 (UTC)
 * I agree with Jmabel above. Making this a policy will create far more problems than it would solve. (This proposal reminds of a passage from the Tao Te Ching, to the effect that if we must make "assume good faith" a policy, then we no longer have it.) -- llywrch 22:02, 15 Feb 2005 (UTC)
 * I've been recently having problems with a turd who quotes "assume good faith" whenever I point out the bad-faith actions he engages in. If this policy remains, it should make clearer that although initially assuming good faith is nice, continuing to believe in good faith against all evidence is foolish. Chamaeleon 14:02, 26 Feb 2005 (UTC)

Motion to make this a guideline

 * I motion to make this a guideline, rather than policy. -- AllyUnion (talk) 23:29, 14 Feb 2005 (UTC)
 * Since that's what it already was... I guess I support that. Wikipedia is getting too legalistic. Isomorphic 16:40, 15 Feb 2005 (UTC)

Suggested improvements

 * "Assume good faith, but don't be a sucker." -- Cyrius|✎ 22:07, 13 Feb 2005 (UTC)
 * "Assume good faith in others, if you want them to assume good faith in yourself." Blank Verse   ∅   11:27, 14 Feb 2005 (UTC)
 * "Assume an axe to grind." This would seem a lot more realistic. :) —  Stevie is the man!  Talk 14:38, 14 Feb 2005 (UTC)
 * "Don't assume bad faith. Wait for it to announce its presence." - Nunh-huh 02:25, 15 Feb 2005 (UTC)
 * "Assume good faith, but do not ignore bad faith when it announces itself." -- Cyrius|✎ 14:48, 16 Feb 2005 (UTC)

Voting is evil
Whoever started this vote, consider yourself flogged with a wet noodle. There's no reason to vote on this. It isn't a procedural matter, like how VfD should run, or when people should be blocked. It's not enforceable and not intended to be. There isn't really a difference between "official policy" and "semi-policy" anyway; on Wikipedia, "policy" is just a word meaning "what we do". Formalizing for its own sake just misses the point.

Speaking of missing the point, have some of you forgotten that this is a wiki? If the page is unclear or has problems, fix it. I can't believe Wetmen cringes every time he sees the page, and hasn't done anything about it. The principle is important, but the words on the page aren't sacred; I wrote much of it myself a few months ago. Isomorphic 19:41, 14 Feb 2005 (UTC)

 * There is a difference between policy and a guideline. I saw it was marked as semi-official, rather than official. -- AllyUnion (talk) 22:56, 14 Feb 2005 (UTC)
 * I never liked the semi-policy category much, since it created a distinction where there had been none before. When I showed up, pretty much everything was just a guideline.  The idea that things have to be "official policy" is pretty new, and I'm not a fan. Isomorphic 16:48, 15 Feb 2005 (UTC)

title: Wikipedia:Assume good faith/Vote


text: Category:Roads in Singapore

title: Category:Roads in Singapore


text:
Wikipedia:Non-admin protection/Vote

Voting
This is to move the policy to official policy. Voting ends on March 1, 2005 at 23:59 UTC. Please vote below. One vote per user is allowed; anonymous votes will be ignored. Comments regarding votes can be left below or on the vote Talk page. Discussion of the policy in general should be left on the parent article's Talk page.

Yes

 * 1)  AllyUnion (talk) 08:39, 13 Feb 2005 (UTC)
 * 2) Thryduulf 11:04, 13 Feb 2005 (UTC)
 * 3)   -- Scott  eiπ + 1 = 0  23:10, Feb 14, 2005 (UTC)
 * 4) Beta m (talk) 18:19, 2005 Feb 15 (UTC)

No

 * 1) Don't think it's a good idea. Ta bu shi da yu 09:43, 13 Feb 2005 (UTC)
 * 2) What about this page are we saying needs to be policy?  -- Netoholic @ 02:10, 2005 Feb 15 (UTC)
 * 3) A) I can't see the point and B) the last thing we need is more stuff like this in the article namespaceGeni 02:33, 15 Feb 2005 (UTC)
 * 4) If an editor wants to stop editing, s/he can stop editing. S/he doesn't need a tag to do it. Gamaliel 18:22, 15 Feb 2005 (UTC)
 * 5) Making this policy seems to be unnecessary. Other than cluttering the article namespace, what will this tag do that can't be done now? Carrp | Talk 18:28, 15 Feb 2005 (UTC)
 * 6) If edit warriors are going to stop, they will. I think this will just be used to claim the moral highground. Rje 18:57, Feb 15, 2005 (UTC)
 * 7) What will this do? As I said in Comments, the main purpose will be for one editor to claim moral high ground. If he does it after his own reversion, it's bordering on insulting. If he does it after someone else's reversion, why does he need the template? The whole idea is pointless, and, more so, it makes no sense for it to be "official policy" as it isn't prescribing any action. — Asbestos |  Talk  23:47, 15 Feb 2005 (UTC)
 * 8) Wide open to abuse by editors who want a tool with which to stop the page being edited further. --Tony Sidaway|Talk 12:51, 16 Feb 2005 (UTC)
 * 9) If someone wants to stop, he can. We have multitude dispute-resolution tags for use then. As Laozi put it: "laws are issued when good customs aren't followed". If there is no such goodwill to make peace without outward praise, we can't expect that this one will be used with good intent. Agree with Asbestos - vandals and POV-pushers will use it as an tool to stiffen efforts to remove their rubbish. And Wikipedia has already poor achievements at defusing fanatics. Forseti 11:04, 18 Feb 2005 (UTC)
 * 10) Ceasefires should be agreed on the talk page, not inside the article namespace. Angela. 15:50, Feb 20, 2005 (UTC)
 * 11) Oppose poorly-written poll.  You can't sensibly have a poll about whether or not to "move the policy to official policy" when you don't even specify the exact wording of the proposed policy.  —AlanBarrett 10:17, 25 Feb 2005 (UTC)
 * 12) utcursch | talk 12:25, Mar 4, 2005 (UTC)
 * 13) Circeus 04:31, Mar 6, 2005 (UTC) Unfortunately, I do not believe this would work.

Neutral

 * 1) What will it mean for this to become "official policy"? — Asbestos | Talk 10:12, 15 Feb 2005 (UTC) Vote moved to "No"

Comments

 * 1) I don't understand: what precisely is being proposed here?  Wouldn't it be sufficient to point out that the ceasefire template is available for use by anyone willing to do their share to de-escalate an edit skirmish? The harmonious editing club in particular might be interested. Unless I'm missing something, the proposed policy doesn't say that use of the new template is in any way mandatory.  If no new obligations arise as the result of this proposal, what is there to vote on? I mean aside from the fact that de-escalation is obviously a good idea. --MarkSweep 06:57, 15 Feb 2005 (UTC)
 * 2) As it is right now, I think that it is open to abuse. I expect that a very common senario during edit wars will be one editor reverting back to his own version and then sticking the notice up. At that point if the other editor reverts, the first can claim the moral high-ground because he tried to stop the edit war. I think that the idea is good, but that it should be an explicit guideline within the use of the template that you ought not to stick it up after your own reversion. I realize that the whole thing is voluntary, but I worry that without that guideline being made explicit too many editors will use it as a method of taking the moral high-ground. — Asbestos | Talk 10:09, 15 Feb 2005 (UTC)

Suggested changes

 * Rename the policy, as suggested by Deco -- AllyUnion (talk) 08:39, 13 Feb 2005 (UTC)
 * I agree that Deco's suggested renaming should be implemented. Thryduulf 11:07, 13 Feb 2005 (UTC)
 * Neutral on the policy, but I agree that "Ceasefire" is probably a better name, since there is no actual protection given. -- Jmabel | Talk 00:59, Feb 14, 2005 (UTC)

title: Wikipedia:Non-admin protection/Vote


text:
Wikipedia:Deletion of useless stub templates and stub categories/Vote

Voting
I am placing this policy to a vote. Voting ends on March 1, 2005 at 23:59 UTC. Please vote below. One vote per user is allowed; anonymous votes will be ignored. Comments regarding votes can be left below or on the vote Talk page. Discussion of the policy in general should be left on the parent article's Talk page.

Approve

 * 1)  AllyUnion (talk) 08:55, 13 Feb 2005 (UTC)

Oppose

 * 1) This is way too complicated. Stub template and category deletions have yet to be a major problem at either templates or categories for deletion. -Aranel (" Sarah  ") 22:23, 13 Feb 2005 (UTC)
 * 2) The policy would grant too many rights to the WSS. If every project did the same, no one could edit anything here unless it was in-line with whatever project's criteria. --jag123 18:34, 14 Feb 2005 (UTC)
 * 3) Don't see what's wrong with VfD. --Tony Sidaway|Talk 12:54, 16 Feb 2005 (UTC)
 * 4) I don't think this is a major issue at the present time, certainly not one that merits such a complicated process. I don't see too much problem with VfD for sorting stub templates out at the moment. Rje 19:46, Feb 18, 2005 (UTC)
 * 5) It's a big solution to a small problem.  ral315 22:52, Feb 27, 2005 (UTC)
 * 6) WP:TFD isn't so overworked that it can't handle these.  -Sean Curtin 16:20, Mar 1, 2005 (UTC)

Neutral

 * 1) Only because of the "Notification has been given to Wikipedia talk:WikiProject Stub sorting" clauses for TfD, CfD, etc; I oppose giving any sub-group of these items any special treatment on those pages, as this precedent could overwhelm them in red tape if others followed suit. Other than that, I support. Now that that wording has been changed, I no longer oppose. Seems a bit complex to me, which is why I'm only moving to neutral. Noel (talk)

Comments

 * 1) I would suggest an addition to the 10-day discussion requirement that during that 10 days a running tally of the contents of the stub-template category be kept so that if there's a sudden spike in additional stubs (such as one of the users deciding that indeed this isn't a stub category to lose) it will be obvious and communicated obviously.  I'm sure that we would all catch it as part of the ongoing discussion, but it would be nice to have that as a cap on the process if, as expected, a statement could be made like "deletion was initiated because the category was empty, and no activity in the category was detected during the 10-day discussion period".  Courtland 17:45, 2005 Feb 13 (UTC)
 * 2) I agree with Jag123 in the comment on the discussion section of this article: deletion of "unapproved" stubs without voting isn't a good idea.  I think that someone who has gone to the trouble of making a new stub template & category and, as Jag123 suggests, isn't aware of the mechanics of Wikipedia maintenance shouldn't be penalized for ignorance; consider it a blessing if someone puts up a later approved stub and sorts things into it.  On the flip (curse) side, it does open the door to all manner of special interests and their special stubs ... but that would happen with or without this section of the policy and would be covered under the vandalism/inappropriate content policies (again as Jag123 suggested).  Courtland 18:20, 2005 Feb 13 (UTC)
 * 3) This is an unnecessary complication. There has yet to be a major problem with massive numbers of stub templates and categories being created and I see no clear reason to treat stub templates and categories any differently than other templates with associated categories. -Aranel (" Sarah  ") 22:23, 13 Feb 2005 (UTC)
 * 4) Please note: The policy is still a draft, and will be re-written again, if it fails to pass. -- AllyUnion (talk) 23:03, 15 Feb 2005 (UTC)

Suggested changes

 * 10-day activity log (see Comment 1)
 * drop policy to delete unapproved stub templates & categories (see Comment 2)


text:
Wikipedia:WikiProject Geographical coordinates

WikiProject Geographical coordinates aims to better organize location information in articles containing a set of numbers that identifies location on and relative to the Earth. In particular, we aim to establish a standard for uniform handling of latitude and longitude coordinates as given in various Wikipedia articles, somewhat analogous to how ISBN numbers are handled.

NOTE: This is a concept currently under development, so this is subject to change.

Related WikiProjects
WikiProject Council includes this WikiProject in its Geographical directory. This WikiProject is an offshoot of WikiProject Maps:

 * WikiProject Geography
 * WikiProject Maps
 * WikiProject Geographical coordinates

...and is the parent project of:

 * Wikipedia-World

Other WikiProjects that make use of geographical coordinates include:

 * Meta:Category:Wikimaps
 * WikiProject Cities
 * WikiProject Countries
 * WikiProject Glaciers
 * WikiProject Lakes
 * WikiProject Microformats Geo
 * WikiProject Mountains
 * WikiProject OpenStreetMap
 * WikiProject Protected areas
 * WikiProject Rivers
 * WikiProject U.S. counties
 * WikiProject United States

Associated Portals
The AtlasPortal is associated with WikiProject Geography.

The Geography Portal is associated with WikiProject Geography.

Participants
This list has been moved to its own page.

Goals

 * 1) Undcstrmrc.png Should provide a uniform markup for all geographic coordinates
 * 2) Undcstrmrc.png Should provide a user-preferred appearance for all geographic coordinates
 * 3) Greentree.jpg Markup should be easy and natural to use
 * 4) Check mark.svg Undcstrmrc.png Should be able to have a uniform, extensible way of accessing all types of map resources, avoiding having direct external links to maps in articles
 * 5) Check mark.svg Clicking on a reference navigates directly to a page with external pointers to various resources, with coordinates automatically embedded where possible. The resources can be maps of various kinds, topological charts, satellite photos and others.
 * 6) Check mark.svg Create a database of points, enabling generation of navigatable maps with a clickable icon appearing for every location for which there is a Wikipedia article. This has been implemented for NASA World Wind, Google Earth (see below) and Google maps (see below).
 * 7) Check mark.svg Serve as a tool for finding Wikipedia articles describing nearby locations. See also Wikipediatlas.
 * 8) Question dropshade.png Adhere to existing Internet standards for geographic coordinates as far as possible such as using WGS84 for terrestrial coordinates

Usage guidelines

 * See also MOS:COORDS

In general, coordinates should be added to any article about a location, structure, or geographic feature that is more or less fixed in one place. Such items can vary in size from a single tree (or smaller) to entire oceans or continents. Coordinates should also be added to articles about events that are associated with a single location, for example, the Ufa train disaster. Guidelines for less obvious situations are given below.

Coordinates are appropriate for the top articles or within infoboxes of the following types of articles:
 * Businesses/organizations with a single location (even if they are defunct)
 * Demolished buildings/structures
 * Buildings/structures that have been proposed, but not yet built (if there is a reliable source for the location)
 * Permanently docked ships (and shipwrecks)

Do not add coordinates to the following types of articles:
 * Biographies of living people
 * Works of art (other than permanent outdoor statues, installations or murals)
 * Sports teams (add to the stadium article instead)
 * Businesses with multiple locations (although listing coords for individual locations in a table may be appropriate)
 * Ships that are not permanently docked or sunk

Other types of articles may be decided on a case-by-case basis.

Which coordinates to use
National mapping agencies such as the Geographic Names Information System (GNIS), Ordnance Survey (OS), and Geographical Names Board of Canada (GNBC) are usually reliable sources for coordinates. The GEOnet Names Server (GNS) database is not reliable. Always double check the coordinates on an internet mapping service. For other locations, the following points should be considered:
 * For villages, towns, communities, etc., use the current centre. Where this is difficult, choose the earliest known settlement of that name. Be aware that the GNIS coordinates may be an arbitrarily chosen civic feature, as that was the usual rule.
 * For military and industrial establishments (e.g., castles, barracks, dockyards, car plants) use the main gate.
 * For administrative districts, use the head office.
 * For geographical features with an area, such as lakes, reservoirs, and islands, use a point reasonably in the center of the feature. (Remember not to specify too much precision; see Precision guidelines below.)
 * For linear features, see WikiProject Geographical coordinates/Linear. Be aware that the GNIS primary coordinates will usually be of the feature "mouth" and thus may differ.

Markup
The practical usage of coordinate markup in Wikipedia is described in the style guide for geographical coordinates. For use on maps and other services, parameters may also be required.

A complete entry could for example be:

See also: Obtaining coordinates

Marking project-related pages on Talk page
The template   may be added to relevant Talk pages. This adds the page to several categories and displays as:

Coordinate templates
There are two ways of specifying coordinates:

 * 1)  – Accepts multiple data formats and supports a style sheet preference for display format, plus a Geo microformat.   may be placed anywhere in the article source text, inline, with prose text. For example " ", which displays as "Mount Everest is at 27.98778°N, 86.94444°W". To display coordinates at the page's top, near the article's title, in a skin-dependent way, use   (see example at Krasnoyarsk hydroelectric dam). To display both inline and top, use.
 * 2) Infoboxes – Many infobox templates for places have a parameter, typically coordinates, for specifying a place's coordinates. The template internally uses coord and may therefore also display in the title area. See Template:Infobox Settlement and Template:Infobox Mountain for documentation, or, usage examples at Los Angeles and Mount Everest.

(Before September 2008, there was a widely-used family of templates of the form coor .... These are deprecated and have been replaced by coord. For an overview of choices: WikiProject Geographical coordinates/comparison.)

Parameters
Following the geographical coordinate, further parameters can optionally be supplied, separated by underscores. This helps display suitable map resources (see Template:GeoTemplate), and will help Wikimaps become fully functional.

For example:
 * displays 61.1631°N, -149.9721°W

It has
 * type:landmark
 * globe:earth
 * region:US-AK
 * scale:150000
 * source:gnis

Name
coord takes

If an article contains several display=inline coordinates, each of these may be supplied with a unique name. This name will be used to display the coordinate on the WikiMiniAtlas, and will cause the template to emit an hCard microformat using that name, even if used within an existing hCard. Do not use when the name is that of a person (e.g for a gravesite), as the generated hCard would be invalid. Also, do not use square brackets in names.

Format

 * will reformat the coordinates to decimal degrees for all readers.
 * will reformat the coordinates to degrees | minutes | seconds (dms) format for all readers.

Creating new templates
When creating new templates or infoboxes, use coord. Unless a template uses the coordinate data in another way, the coord template should be the field value. For example, infobox lake accepts.

If coordinate data are used directly by a template, use the following parameter names for coordinates:

A provision for accepting decimal coordinates is recommended. For example, allow  and omission of the remaining parameters.

Where the United Kingdom's Ordnance Survey grid references are used as the coordinates, use.

For articles which have no coordinates, but need them, use.

Linear features
For draft guidance on, and examples of, coordinates for linear features (rivers, roads, bridges, tunnels, etc.), see WikiProject Geographical coordinates/Linear.

How to obtain geographical coordinates
See Obtaining geographic coordinates

See also: Category:Articles needing coordinates, Maybe-Checker

Geodetic system
All coordinates specified through coord must be referenced to WGS84, or an equivalent datum. WGS84 is required for some of the conversions done by the geohack extension.

British national grid references of the Ordnance Survey use its own OSGB36 datum, which is correct for use in national grid references; the correct transformations will automatically be applied when national grid coordinates are used in oscoor tags. However, OSGB36 latitude/longitude coordinates should not be used anywhere in Wikipedia; please use WGS84 lat/long instead.

Precision guidelines
Regardless of how coordinates are obtained, consider the precision specified in a Wikipedia article. Reliable secondary sources exist for some locations. Without a reliable source, the larger the object being mapped, the less precise the coordinates need to be. Cities must be specified with a precision of degrees, minutes and seconds to respect historical norms. When the guideline is used, degrees, minutes and seconds or d.dddd are the default. To specify a particular point in the city, such as a building, generally requires precision down to degrees-minutes-seconds or d.dddd° if decimal degrees are used. In the case of objects such as fountains or statues, it may be necessary to use d°m's.s" or d.ddddd°. Higher precisions should be avoided, as they greatly exceed the accuracy of civilian GPS and online mapping services. (Using 4 m accuracy as an estimate for civilian GPS: Depending on the coordinates format and the latitude, the next-higher precisions exceed the accuracy by a factor of somewhere between 13 and 72.)

A general rule is to give precisions approximately one-tenth the size of the object, unless there is a clear reason for additional precision. Overly precise coordinates can be misleading by implying that the object is smaller than it truly is.

There is no set way to determine object size, and the boundaries of many geographical objects are not clearly defined or not readily available. The difference rarely affects the suggested coordinates precision, so a rough size estimate is usually adequate. However, it should be noted that object size is always linear (one-dimensional), not an area measurement.

In the two most-used coordinate representations, degrees-minutes-seconds and decimal degrees, precision is, as a useful approximation,

Conversions: 1 km, 1 m, 1 cm; 1 mi, 1 ft, 1 in

The values in the table give distances in the east-west direction corresponding to a small change in longitude, at different latitudes. You can take the equator columns of the table as a rough guide to distances in the north-south direction that correspond to a small change in latitude, since they vary only a little bit at different latitudes. For simplicity, however, the latitude precision is commonly copied from that of the longitude.

Precision tables
The following tables show suggested coordinates precisions for various object sizes and latitudes. Refer to the preceding section for more information about coordinates precision. To use these tables:
 * Choose one of the tables depending on whether you want degrees-minutes-seconds format or decimal degrees format
 * Find the column that is closest to the latitude of your object
 * Find the row that is closest to the size of your object
 * Note the coordinates precision at the intersection of your row and column

Example: You want coordinates, in decimal degrees format, for Yosemite National Park, California, U.S. To solve: (This is a good example of a borderline case, as the latitude is quite close to 37.5°, the midpoint between 30° and 45°. If the Park were a mere 25 miles to the south, you would use the 30° column instead, yielding a different precision: d.dd°. You could opt for that precision instead, giving 37.85, −119.56. That's your call. But the table shows that more than two decimal positions would definitely be too precise for this case.)
 * The size of the object is roughly 70 km
 * GNIS query gives the Park's location, in decimal degrees, as: 37.8483188 (north latitude), −119.5571434 (west longitude)
 * Choose the Decimal degrees format table
 * Find the 45° column; 37.8483188 is (slightly) closer to 45° than to 30°
 * Find the 50 km row; 70 km is closer to 50 km than to 100 km
 * Note the precision at the intersection of row and column: d.d°
 * Round to the selected precision: 37.8, −119.6

 * 1) The tables are derived from the precision data at, above. As suggested there, they use a target resolution of one-tenth of the object size.
 * 2) The tables are not perfect. Some cases will yield a precision that is different from what you would get by doing the math (including trigonometry) for that specific case. This is because it is impossible to represent all cases correctly in a usable tabular format. The tables provide the correct precision for a majority of cases. Any error should be limited to one level of precision (e.g., d° m' vs. d° m' s", or d.ddd° vs. d.dddd°), which is acceptable for the purposes of Wikipedia coordinates.
 * 3) d.ddddd° is roughly three times more precise than d° m' s.s".

Mathematical formulas
You can also calculate the kilometers per degree of longitude, k, using one of the following formulas (θ is the latitude, 6378.14 km is the equatorial radius, and 6356.8 km is the polar radius):

Accurate, assuming a spheroid:
 * $$k = \frac{\pi}{180}\cos(\theta)\sqrt{\frac{(6378.14^2\cos\theta)^2+(6356.8^2\sin\theta)^2}{(6378.14\cos\theta)^2+(6356.8\sin\theta)^2}}$$

Approximate:
 * $$k = 111.3\cos\theta\,$$ Equator to latitude 25° (north or south)
 * $$k = 111.2\cos\theta\,$$ Latitude 30° to 40°
 * $$k = 111.1\cos\theta\,$$ Latitude 45° to pole

Tools and applications based on coordinates from Wikipedia
Articles (and coordinates) can be found through the pages using the templates in Category:Coordinates templates

All coordinates are available for download in Wikipedia database dumps. To get the coordinates from the XML format dump of all articles (enwiki-latest-pages-articles.xml.bz2, 4 GB), the dump needs to be parsed for pages containing coordinates in the entry formats listed above. Most articles in Wikipedia conform to these formats and coordinates are easy to parse from the wikitext with regular expressions for simple character sequences. As all coordinates link to the same PHP tool, they may also be found from the SQL format table of external links (enwiki-latest-externallinks.sql.gz, 725MB). This second method will however not include all available information about the coordinates, such as their position between the article body and the title area.

There may exist some groups of articles that generate the coordinate data dynamically and are not in any of the standard entry formats, as some editors may have wished to facilitate entry of common coordinate related information, while only keeping the output similar with the existing templates. To get all such coordinates, all the articles in the database dump need to be run through a wikitext parser (such as the PHP one in MediaWiki) to expand all the templates, and the result parsed for coordinates. Alternatively, it is also possible to download the HTML generated from all the article and expanded template content (wikipedia-en-html.tar.7z, 14 GB).

Note that mass downloading individual pages from the live Wikipedia site is strongly discouraged and may lead to discontinued access.

NASA World Wind Samples
All examples use NASA World Wind, with the Wikipedia overlay. This is purely meant as an example of using a coordinated concept for geographical coordinates.

View Wikipedia in Google Earth
Project Wikipedia-World scan 11 Dumps (ca,cs,de,en,eo,es,fi,fr,nl,pt,ru) and provides:
 * dynamic Google-Earth layers in 21 languages. For instance: english Layer, español Layer
 * static Google-Earth layers in 10 language with different folders (Castles, Parks,...), Download at webkuehn.de
 * SQL-Data of all scanned coordinates

Copernix.io - View and search Wikipedia Articles on a map
Copernix.io is a geographical search engine allowing users to search places and information from Wikipedia on a map. Users can leave the search bar empty to see all pages within an area or type a query to get subject specific information.

Some useful examples can be found at: The main search page is at:
 * Copernix examples and about
 * Copernix.io

Visualization of Wikipedia articles with Google Maps

 * www.geonames.org over 800,000 Wikipedia articles in 230 languages on Google maps. The placemarks include short descriptions of the displayed items, extracted from the Wikipedia articles. Webservices for full text search and reverse geocoding of Wikipedia articles.

WikiMiniAtlas JavaScript plugin
WikiMiniAtlas is a JavaScript to add to your monobook.js. It adds a draggable and zoomable (just like GoogleMaps) map to all geo-coded articles. Clickable labels with links to other geocoded articles are placed on the map to allow spatial browsing of Wikipedia. Map layers include satellite images (using Landsat7 data) with zoomlevels down to a resolution <100m, and daily updated MODIS satellite data.

WikiMiniAtlas is currently enabled on Wikipedia (by clicking on the globe beside the coordinates).

All geodata in SQL file format

 * Project Wikipedia-World, provides the complete database for download in SQL-file format.

Export multiple coordinates
Kmlexport tool: Pages marked with multiple coordinates or categories of articles with coordinates can be exported as KML (for use in Google Earth, for example). This tool and some alternatives can be found on clicking the coordinates or by applying the GeoGroup template on a page.

The Kmlexport can be used directly or through Google Maps; see for example Colmar Pocket or Category:Capitals in Europe. Export from articles is real-time, export from categories is based on stored extractions (may be several weeks old).

KML may be converted in other formats, suitable as Points of Interest (POI) for GPS systems.

Other sources:
 * Wikitude provides coordinates as KML or TomTom POI format.

Coordinates search tool
~dispenser/cgi-bin/geosearch.py allows for regular expression searching on the GeoHack links in the external links table. This has the advantages of near real time information and powerful pattern matching. The following are some example queries created as a demonstration of the flexibility of the system.


text:
Putney Lower Common

Putney Lower Common is an open parkland space in the London Borough of Wandsworth between the town centres of Putney and Barnes. It is part of Wimbledon and Putney Commons, lying 1.5 miles from the rest of the common area.

Geography
The common has an area 13.22 ha, it borders with Barn Elms and Beverley Brook on the north, the residential Commondale and Horne Way areas on the west with Lower Common South road on the south, and with Barnes Common on the west side; the Lower Richmond road and Queen's ride run across the common.

History
The land was enclosed from the 15th century, in 1871 the Wimbledon and Putney Commons act entrusted the land from the Spencer family, to the Wimbledon and Putney Commons Conservators (WPCC), who have been responsible for managing the land ever since.

Features
The Oasis Academy Putney primary school lies on the east side of the common, on the site of the former Putney Hospital, construction of the school involved the loss of commons land so that a new access road could be laid.

The Spencer pub is on the south side of the Lower Richmond road, and often expands its seating area onto the common in the summer, under licence with WPCC. All Saints is a Grade II* listed church on the south east corner of the common, it has a churchyard and features windows designed by William Morris. Transport for London's number 22 bus, run by London General for the Go-Ahead Group, terminates at Putney Common, with buses parking between the Spencer pub and All Saints church, before maintenance at the nearby Putney bus garage on Chelverton road.

Putney Lower Common Cemetery lies on the west side of the common on the Lower Richmond road, bordering with Barnes Common, it features several notable graves.

Funfairs visit the common on bank holidays, and the Santus circus have visited the common in late summer.

Wildlife
The common is predominantly neutral grassland, it is a Site of Special Scientific Interest (SSSI), a Special Area of Conservation (SAC), and within the London Borough of Wandsworth is a designated site of borough importance.

The common is part of a wider habitat network that includes the WWT London Wetland Centre, Barnes Common, with the wildlife corridor of Putney Park Lane up to Putney Heath, Wimbledon Common and Richmond Park.

In 2019 the People's Trust for Endangered Species found that the site is a hotspot in London for hedgehogs, Greenspace Information for Greater London records show that stag beetles have been recorded on the common, as well as Hobbies, Kestrels and Kingfishers.

Several invasive species have been found on the common, Oak Processionary moth was first recorded in 2011 and the WPCC try to control its numbers with regular surveys, caterpillar removal, and application of the biocontrol agent Bacillus thuringiensis; Japanese knotweed and Himalayan balsam have also been recorded and removed.

The common has regularly won the London in Bloom gold award in the Common of the Year category, for management to improve the local environment.

Sports grounds

Putney Cricket Club have a cricket pitch on the south side of the common, between Queens ride and Lower common South. There is an established walking trail that takes the common and Barnes common, with a distance of 3.4km. The Putney Town Bowling Club have a bowling green and clubhouse on the west side of the common, next to the Oasis Academy.

In popular culture
Jilly Cooper's book, The Common Years (1984), is a diary about Cooper's life living near the Common.

Transport
There are parking spaces on Mill Hill road by the cemetery, the Common is served by Transport for London buses 22, 265 and 284 which stop at Commondale on the Lower Richmond road, Barnes railway station (Southwestern Railway) is a 10 minute walk.

title: Putney Lower Common


text:
User:CatherineMunro/CJB

This anonymous user uses several different IP adresses.

Duran Duran - http://duranduran.cjb.net/
User has inserted a link to "DURANMANIA -Duran Duran & James Bond 007" repeatedly into the Duran Duran article. The link was originally inserted on August 13, 2004], and remained on the site unchallenged until November, when I began preparing the article as a featured article candidate. I investigated the link and found it to be a low-traffic discussion forum (less than 60 users, less than 400 total posts), and removed it.

 * 1) Revision as of 14:54, 7 Dec 2004 - User:24.18.230.100 - add link
 * 2) Revision as of 02:23, 24 Dec 2004 - User:67.170.66.135 - add link
 * 3) Revision as of 16:07, 25 Dec 2004 - User:67.170.66.135 - add link
 * 4) Revision as of 19:38, 28 Dec 2004 - User:24.19.234.106 - add link
 * 5) Revision as of 20:23, 1 Jan 2005 - User:24.19.234.106 - move link up list
 * 6) Revision as of 15:23, 3 Jan 2005 - User:24.19.234.106 - rm legit links, rm "fansites" section, move link up list
 * 7) Revision as of 16:31, 7 Jan 2005 - User:24.19.234.106 - rm "fansites" section, rm other fansite, move link up list
 * 8) Revision as of 04:53, 27 Jan 2005 - User:68.99.212.163 - edit text of link display
 * 9) Revision as of 14:13, 6 Feb 2005 - User:68.99.212.163 - add link
 * 10) Revision as of 23:44, 10 Feb 2005 - User:172.132.221.56 - add link
 * 11) Revision as of 13:05, 11 Feb 2005 - User:172.131.34.77 - add link
 * 12) Revision as of 20:45, 11 Feb 2005 - User:172.131.34.77 - add link
 * 13) Revision as of 14:37, 12 Feb 2005 - User:172.133.179.253 - add link
 * 14) Revision as of 23:50, 12 Feb 2005 - User:172.138.145.225 - add link
 * 15) Revision as of 23:52, 12 Feb 2005 - User:172.138.145.225 - edit text of link display
 * 16) Revision as of 04:07, 13 Feb 2005 - User:68.99.212.163 - add link
 * 17) Revision as of 02:45, 14 Feb 2005 - User:68.99.212.163 - add link

Kajagoogoo - http://kajagoogoomania.proboards33.com/
User inserts "Kajamania Kajagoogoo & Limahl Worldwide News & Info Board" (98 members, <500 posts) to Kajagoogoo
 * 1) Revision as of 16:31, 13 Aug 2004 - User:67.180.197.54 - add link
 * 2) Revision as of 16:34, 13 Aug 2004 - User:67.180.197.54 - edit text of link display
 * 3) Revision as of 16:34, 13 Aug 2004 - User:67.180.197.54 - rm official UK site
 * 4) Revision as of 18:16, 29 Aug 2004 - User:66.27.201.219 - add link
 * 5) Revision as of 18:16, 29 Aug 2004 - User:66.27.201.219 - edit text of link display
 * 6) Revision as of 16:47, 22 Oct 2004 - User:67.180.190.154 - edit text of link display
 * 7) Revision as of 16:48, 22 Oct 2004 - User:67.180.190.154 - edit text of link display
 * 8) Revision as of 16:40, 24 Dec 2004 - User:67.170.66.135 - add add'l official site, edit text of link display
 * 9) Revision as of 14:14, 23 Jan 2005 - User:68.99.212.163 - add link
 * 10) Revision as of 03:11, 24 Jan 2005 - User:68.99.212.163 - add link
 * 11) Revision as of 12:58, 24 Jan 2005 - User:68.99.212.163 - add link
 * 12) Revision as of 21:28, 24 Jan 2005 - User:172.173.41.231 - add link
 * 13) Revision as of 18:03, 25 Jan 2005 - User:172.200.209.241 - add link
 * 14) Revision as of 18:05, 25 Jan 2005 - User:172.200.209.241 - edit text of link display
 * 15) Revision as of 14:20, 26 Jan 2005 - User:68.99.212.163 - add link
 * 16) Revision as of 16:21, 26 Jan 2005 - User:172.161.250.225 - add link
 * 17) Revision as of 01:35, 27 Jan 2005 - User:172.161.250.225 - add link
 * 18) Revision as of 12:33, 27 Jan 2005 - User:172.133.96.154 - add link
 * 19) Revision as of 18:01, 27 Jan 2005 - User:172.136.89.115 - add link
 * 20) Revision as of 00:21, 28 Jan 2005 - User:172.136.89.115 - add link
 * 21) Revision as of 04:18, 28 Jan 2005 - User:68.99.212.163 - add link
 * 22) Revision as of 11:39, 28 Jan 2005 - User:68.99.212.163 - add link
 * 23) Revision as of 13:08, 29 Jan 2005 - User:172.142.55.127 - replace rival fansite link with own
 * 24) Revision as of 13:09, 29 Jan 2005 - User:172.142.55.127 - edit text of link display
 * 25) Revision as of 21:06, 29 Jan 2005 - User:172.142.55.127 - replace rival fansite link with own
 * 26) *(page protected for three days)
 * 27) Revision as of 04:10, 7 Feb 2005 - User:68.99.212.163 - add link
 * 28) Revision as of 04:09, 8 Feb 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 29) Revision as of 23:47, 12 Feb 2005 - User:172.138.145.225 - replace rival fansite site link with own
 * 30) Revision as of 04:14, 13 Feb 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 31) Revision as of 04:15, 13 Feb 2005 - User:68.99.212.163 - edit text of link display

Limahl - http://kajagoogoomania.proboards33.com/
What's sad is that this article has had a POV tag on it this whole time, and neither of these "fans" has done a thing to improve the article....
 * 1) Revision as of 16:37, 24 Dec 2004 - User:67.170.66.135 - add several links (apparently copied from Kajagoogoo article)
 * 2) Revision as of 16:38, 24 Dec 2004 - User:67.170.66.135 - add links
 * 3) Revision as of 18:34, 6 Jan 2005 - User:24.19.234.106 - move rival fansite to bottom
 * 4) *Note rival (User:84.133.119.104) reverts and inserts almost as often
 * 5) Revision as of 15:48, 13 Jan 2005 - User:24.19.234.106 - move rival fansite to bottom
 * 6) Revision as of 07:33, 14 Jan 2005 - User:24.19.234.106 - move rival fansite to bottom
 * 7) Revision as of 00:07, 15 Jan 2005 - User:24.19.234.106 - rm rival fansite
 * 8) Revision as of 15:55, 15 Jan 2005 - User:24.19.234.106 - replace rival fansite site link with own
 * 9) Revision as of 17:59, 16 Jan 2005 - User:24.19.234.106 - replace rival fansite site link with own
 * 10) Revision as of 14:58, 18 Jan 2005 - User:24.24.242.135 - replace rival fansite site link with own
 * 11) Revision as of 14:59, 20 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 12) Revision as of 18:26, 21 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 13) Revision as of 12:26, 22 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 14) Revision as of 16:08, 22 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 15) Revision as of 14:11, 23 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 16) Revision as of 03:10, 24 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 17) Revision as of 12:58, 24 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 18) Revision as of 21:27, 24 Jan 2005 - User:172.173.41.231 - replace rival fansite site link with own
 * 19) Revision as of 17:59, 25 Jan 2005 - User:172.200.209.241 - replace rival fansite site link with own
 * 20) Revision as of 14:19, 26 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 21) Revision as of 16:18, 26 Jan 2005 - User:172.161.250.225 - replace rival fansite site link with own
 * 22) Revision as of 01:34, 27 Jan 2005 - User:172.161.250.225 - replace rival fansite site link with own
 * 23) Revision as of 12:31, 27 Jan 2005 - User:172.133.96.154 - replace rival fansite site link with own
 * 24) Revision as of 17:57, 27 Jan 2005 - User:172.136.89.115 - replace rival fansite site link with own
 * 25) Revision as of 00:17, 28 Jan 2005 - User:172.136.89.115 - replace rival fansite site link with own
 * 26) Revision as of 04:16, 28 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 27) Revision as of 11:36, 28 Jan 2005 - User:68.99.212.163 - replace rival fansite site link with own
 * 28) Revision as of 04:11, 7 Feb 2005 - User:68.99.212.163 - add link

Others

 * Nick Beggs
 * Steve Askew
 * Michael Jackson

Other actions
Reverted notice on talk page: And again:

title: User:CatherineMunro/CJB


text: User talk:212.100.250.213

title: User talk:212.100.250.213


text:
Vitré

Vitré may refer to communes in France:

 * Vitré, Ille-et-Vilaine
 * Vitré, Deux-Sèvres

title: Vitré