|place = locality|
|A named place that has no population.|
|Used on these elements|
|Tools for this tag|
The place=locality tag is used to name an unpopulated location for which there is no extant feature to which the tag could be associated.
How to map
Place a node at the appropriate location and add a place=locality tag together with name=*. wikipedia=*, note=*, source=*, and similar tags are strongly encouraged to explain the use of place=locality.
Examples of use
place=locality is used in the United States to describe locations of former human settlements for which all taggable features are gone, but which still see use (and/or have value) as named locations. This is most frequent in the case of former hamlets, or for historical railroad stations or railroad junction locations. There may or may not be contemporary road signs which indicate the existence of the location. There may be other named and taggable elements near its location, such as a cemetery. GNIS is a common source of such locations, as are USGS topo maps and historical plat maps.
- Consider using abandoned:place=* for formerly inhabited places that still have some physical traces, eg abandoned buildings
- Consider using railway=junction for railway junctions and junction=yes for highway junctions
In French-speaking regions, this tag is often used for Lieu-dit, eg a vineyard, a meadow, field, part of a woodland, or several hills. Many of these could instead be mapped with a specific natural feature. Examples:
- a vineyard = landuse=vineyard
- a crossroads = junction=yes
- a field = landuse=farmland or landuse=meadow
- hills = natural=ridge or natural=peak or natural=hills
- a wood = natural=wood
This tag sometimes is used in addition to rarely used or unusual tagging scheme (for example natural=dune + place=locality + name=*), as an example of tagging for the renderer.
When not to use this tag
To define any feature that already has a suitable tag schema in OpenStreetMap. For example:
- landuse=forest or natural=wood
For some of these tags, however, there exist possible exceptions:
- A continuous, named, wooded area can be broken up into multiple connected areas tagged landuse=forest or natural=wood. One then has to choose between three options with different tradeoffs:
- If the continuous area is small enough, it can be tempting to create a single overlapping multipolygon, covering the full wooded area, in order to tag it with name=*. One can then choose to tag the area either as:
- For larger areas, on may use as of yet unsupported group or cluster relations.
- The same issue occurs for wetlands with subdivisions.
- ...and for subdivided reservoirs, like Lake Mead.
For populated places, including farms and isolated dwellings, see place=*. For a name that is associated with a natural or physical feature it is better to add a name=* to the element that describes that feature.
Also consider creating a new tag if you would like to map a specific feature that does not yet have an established tag. Searching Taginfo is a good way to find tags that may be in use but not yet documented on this wiki. If you have the time, you can document your idea for a new tag with a Proposal page.
If a name isn't rendered for the populated place or named feature, this is a problem with the map renderer itself, as described below.
Don't use place=locality just to force a name to appear on a feature
Although place=locality will always show a locality's name in Openstreetmap-carto, this does not justify tagging for the renderer when a taggable feature doesn't show its name on the map. In these cases, the renderers themselves should be fixed/upgraded, along lines of "please render the name=* on this tagged feature".
Examples, current and former
- Dark Peak (mountain area)
- Hartland Point → natural=cape
- Raven's Ait → place=island
- Lulworth Cove → natural=bay
- Persian Gulf → place=sea
- Sognefjord → prob. natural=bay
- Seven Sisters, Sussex → natural=cliff with a relation