Whether you are from, Saint-Louis-du-Ha! Ha!, Springfield or Ea names are important. They help us identify where we are, where we are from and where we want to go to.
Almost everything has a name and OpenStreetMap volunteers have mapped 115 million names.
Local name of features on www.openstreetmap.org
In OpenStreetMap, the verbal identifier with which people refer to something is documented by the name=
tag. This usually is the most common name in the local language and is the most obvious name of the feature. For example, if you are in France and map a road called “Rue des Beaux-Arts”, you add name=Rue des Beaux-Arts
so that everyone knows what that road is called.
There are many map styles based on OpenStreetMap data. On www.openstreetmap.org, we display “osm-carto” style by default, with a layer switcher for many others.
There are a few simple rules that the OpenStreetMap community follows, including:
name=
is typically the commonly used name in the local language. A street in Paris has asname=
its French name, not the name in English.name=
should be verifiable.name=
should be a proper name – not a description or a reference id.
The recording of names is a complex issue, but these are the main rules we use.
The OpenStreetMap community tries to ensure that the name=
tags in the OpenStreetMap database are correct, for mapped features with names such as shops, places, streets, lakes or even oceans.
Additional names of features on www.openstreetmap.org
In addition to the local name, set by name=
, objects in OpenStreetMap very often have one or more names. Such additional names are classified by their function – how they are used in contrast to the local name, or what purpose they serve for data users. We can store old names, local names, official names, and alternative names.
Both local and other name keys can also be suffixed with a language code. If you want to add a name in another language, you use a separate tag like name:en=
for English or name:fr=
for French, and leave the name=
tag in the local language. The ISO language code system we use allows more details, such as the writing system used, or even the region and dialect. The English spoke in Britain isn’t the same as that spoken in Australia.
Therefore, the OpenStreetMap database contains features with multiple names.
On the default layer of the www.openstreetmap.org website (osm-carto) we don’t show different names based on where you are, this means everyone will see the name of the feature in the local language. It’s important that the website has a layer where this is the case. This is mostly a technical reason.
While only name=
is displayed on the default layer of www.openstreetmap.org, there are additional layers on the website and there is ongoing work on the new Vector layer to show names in your local language, but more about that in a later post. There are other map styles showing names only in German, or only in English.
One database – unlimited maps: create the map you want
It is important to note that OpenStreetMap data is offered to everyone for free, under the ODbL licence, and used for any purpose – including commercial usage.
It is possible to produce your own maps which, for example, show only a subset of the mapped names or features. The www.openstreetmap.org website’s main purpose is to facilitate OpenStreetMap mappers and not to be a single map for every use. OpenStreetMap data is used by individuals, big companies, game companies, grassroot organisations, governmental agencies, humanitarian groups and many others and the data can be used to create unlimited maps and for other purposes.
What about official names?
Mostly the official name will match the commonly used name of a feature. Sometimes people will continue to use the original name, so our name
tag will stay. We can store the official names of mapped features when different, in the official_name=
tag
In cases like the executive order related to Lake Ontario, it’s not unusual that there will be a community discussion and in this case the tag official_name:en-US=Lake America
has been added to the lake on OpenStreetMap, to record the new official en-US name. The primary name of the lake remains the same. Since a lot of people still use the name “Lake Ontario” we keep it as name
. The addition of the official_name:en-US=Lake America
name means that anyone searching for Lake America on www.openstreetmap.org and apps/services using OpenStreetMap data which have all the feature names, will find Lake Ontario.
The Name of the Game
OpenStreetMap’s flexible data model means that if you want to show a map, with certain names, or certain langauges, we provide a world-wide freely-usable database for you to use. Just adjust your map style to prefer one name
tag over another, and you’ll automatically get the map you want.
OpenStreetMap’s community base, and non-commerical freedom, international project structure, and “on the ground rule” means that if you use the name
tag, then the names on the map will be based on what people are actually using.
When it comes to maps, OpenStreetMap is the only name in town!
> name= should be a proper name.
this seems to be not accurate? https://en.wikipedia.org/wiki/Proper_name_(philosophy is about something else, though may be related.
“is a name which ordinarily is taken to uniquely identify its referent in the world” – but many valid name= are in fact not unique across world or even across a city. Especially branded shops.
But even street names can occasionally manage to not be unique within a single city. And some, say “Main Street” can appear multiple times across world.
and yes, street names not unique within city is silly – but it happened in some cases and this is not making name= tags invalid there
Great piece — I love that OSM’s answer to naming is “reflect local usage and hold multiple perspectives” rather than crowning one official truth (the Lake Ontario / Lake America example says it all).
That same spirit raises a bigger question for *continents*. Unlike a name that just varies by language, here even the *count* is contested:
• In much of the Global South, *America is one continent*; in the US model it’s two (North + South) — and where does Central America go?
• Is it *Europe*, or part of *Eurasia*? Why is Europe a continent but South Asia is not?
• The five Olympic rings encode yet another model: Africa, America, Asia, Europe, Oceania.
So `place=continent` isn’t a neutral fact — it quietly picks one worldview. It’s exactly the kind of thing this post argues OSM should hold plurally, instead of forcing a single “correct” answer. Maybe the interesting question isn’t *which* model is right, but *why we assume there’s only one*.
Curious how others see it — how many continents were you taught?
Facts Only
* OpenStreetMap volunteers have mapped 115 million names.
* The `name=` tag documents the most common identifier in the local language.
* OSM data is released for free under the ODbL license.
* Language-specific names are stored using ISO language codes (e.g., `name:en` or `name:fr`).
* The `officialname=` tag is used when the official name differs from the commonly used name.
* The default map style on www.openstreetmap.org is "osm-carto."
* Official naming for Lake Ontario includes the tag `officialname:en-US=Lake America`.
* Map styles can be adjusted to prefer specific name tags over others.
* The `name=` tag is intended to be a proper name and verifiable.
* Data is used by governmental agencies, humanitarian groups, and private companies.
Executive Summary
OpenStreetMap (OSM) utilizes a flexible tagging system to document geographic features, prioritizing the most common local name via the `name=` tag. To maintain a comprehensive database, the system allows for additional tags to capture official names (`officialname=`), alternative names, and language-specific variations (e.g., `name:en=` for English), ensuring that data remains verifiable and reflects actual usage on the ground.
While the default website display typically shows only the local name for technical consistency, the underlying database supports diverse map styles tailored to specific languages or user needs. This data is provided free of charge under the ODbL license for both commercial and non-commercial use. This approach allows the community to resolve naming conflicts—such as the discrepancy between "Lake Ontario" and "Lake America"—by recording multiple perspectives rather than enforcing a single official truth.
Full Take
SKEPTICAL MODE:
The strongest version of this narrative is that OpenStreetMap is a democratic, pluralistic alternative to top-down cartography, where "truth" is defined by local usage rather than state decree. By separating "common name" from "official name," it preserves historical and cultural memory while remaining functionally useful for navigation.
The narrative relies on a gentle Appeal to Popularity, suggesting that because "people are actually using" certain names, those names are inherently the most "correct" for the database. However, this is a transparent operational choice rather than a manipulative one; the flexibility of the ODbL license and the multi-tag system provides a technical hedge against the very rigidity it criticizes.
Patterns detected: none
The driving paradigm is "bottom-up" epistemic authority. It assumes that the collective experience of residents is more valuable than the administrative record of a government. This echoes the broader open-source movement's shift from centralized authority to distributed verification.
The implication for human agency is significant: it allows marginalized communities to assert their own naming conventions on a global stage. The cost is a lack of "single-source truth," which may complicate official administrative tasks but increases the map's resilience to political erasure.
Bridge Questions:
1. If local usage and official decrees conflict violently, how does the community decide which tag takes precedence in a search query?
2. In regions with no dominant "local" language or contested sovereignty, who defines the "common" name?
Counterstrike Scan:
A coordinated influence campaign would use this "local usage" logic to systematically erase official names of disputed territories to create a new geopolitical reality. This content does not match that pattern; it explicitly provides a mechanism (`officialname`) to preserve the official record alongside the local one.
Sentinel — Human
The text functions effectively as a bridge, using the technical framework of OpenStreetMap naming conventions to launch a deeper critique of how geopolitical concepts like 'continent' are defined and asserted.
