|Used to mark that a specific feature is a general area (only used for closed way objects, not used for nodes, open ways and relations).|
|Used on these elements|
|Tools for this tag|
The area=yes tag is required for some closed ways when used to define an Area (polygon); however, for closed ways with other tags there is an assumption that the way defines an area. In some circumstances a closed way may define both a closed polyline and also an area.
If the assumption that a closed way together with other tags defines an area is misleading, area=no can be used to clarify the situation. E.g., leisure=track, sport=running, area=no is just a closed running way.
Used on these elements explained with symbols
for nodes the key area is not used
for open ways the key area is not used
for closed ways the key area can be used. A closed way without key area or with tag area=no it will demonstrate a , otherwise if a closed way has the tag area=yes it will be demonstrate a area
for relations area is not used
The following closed ways should be treated as linear features:
- barrier=*, for thicker hedges or walls or detailed mapping defined using an area add area=yes
- highway=*, see 'Highway areas' below for more details
- This list is probably incomplete - please add other cases
Closed ways are assumed to be areas in most other situations, including:
- aeroway=*, avoid using closed ways for aeroway=taxiway or it will be shown as an area
Note that mappers frequently use multiple tags on the same closed way. This can result in the way being used to define both, an area and also a polyline at the outline of this area. For example a closed way tagged landuse=grass and barrier=fence can be interpreted as a fence enclosing an area of grass.
Where a road crosses a pedestrian area then a linear way tagged in the usual way should be overlaid across the square. This linear way should shares nodes with the pedestrian area at its entrance and exit from the square.
In the context of roads, area=yes indicates that an area has no street lines within it (i.e., there is no given direction on the area).
Note: There is currently no clear agreement on how highway tag values other than pedestrian should be treated when also tagged with area=yes.
Note: Most pedestrian routing algorithms do not currently route (correctly) across area features, tending to route around the edge or not at all (especially in case of multipolygons). Do not alter your mapping to accommodate such routers.
- Proposed features/area:highway for defining the carriageway of a road as areas (in addition to mapping them as lines) and as an alternative to describing pedestrian areas.