Tag:highway=footway

From OpenStreetMap Wiki
(Redirected from Footway)
Jump to navigation Jump to search
Public-images-osm logo.svg highway = footway
A designated footpath.jpg
Description
A path mainly or exclusively for pedestrians. Show/edit corresponding data item.
Rendering in OSM Carto
Rendering-highway footway.png
Group: highways
Used on these elements
should not be used on nodesmay be used on waysmay be used on areas (and multipolygon relations)should not be used on relations (except multipolygon relations)
Implies
Useful combination
Status: de facto

The tag highway=footway is used for mapping minor pathways which are used mainly or exclusively by pedestrians.

When to use

Footways tend to be constructed and either paved or with smooth surface (compacted, wood or similar). The elderly and small children and quite often also wheelchair users can use them with ease. They tend to be in urban settings, but not always. Access is primarily for pedestrians, which is often specified by street signs (or implied by local law).

  • Paths kept mainly by the fact of people walking on them or paths that are only minimally constructed are usually tagged as highway=path. Their surface might be uneven (typically ground) and one might need to be physically fit and situationally aware to use them. They tend to be located outside of urban enviromnent. Hiking trails are a typical example and sac_scale=*, trail_visibility=*, surface=* and access=* are useful. However, in some countries like the UK or others, this distinction does not hold and highway=footway can be used for these too.
  • For ways used mainly or exclusively by cyclists, use highway=cycleway.
  • For ways used mainly or exclusively by horses, use highway=bridleway.
  • For ways used mainly or exclusively for motorcycles, use highway=path + motorcycle=yes or motorcycle=designated.
  • For ways closed to cars but open to motorcycles, cyclists, horses or other users without clear primary user, use highway=path with appropriate access tags.
  • For wider pedestrianised streets, typically lined with shops or commercial buildings, use the highway=pedestrian.
  • For ways designated for pedestrians, but which also allows bicycles, use either highway=footway and bicycle=yes or highway=path, foot=designated and bicycle=yes.
  • For roads for cars used to access land for mostly agricultural or forestry purposes, use highway=track.
  • For sidewalks that span a road, see Sidewalks.

How to map

Linear ways

To map a footway nothing else than a simple way is required. Add the highway=footway tag to it and add a name=* if appropriate.

Add access=* restriction tags if appropriate. See default access restrictions.

If the footway is associated with a road, then add the footway=sidewalk tag.

The way footway=* or highway=footway should join with another kind of way for routing porposes. For motivation, see Beginners Guide step 5, or Editing Standards and Conventions.

Example photos Example tracking Referring tag Comment
Footway in Stowupland - geograph.org.uk - 1044849.jpg
JOSM hgw barr foot cross.png
Sidewalk referenced by the letter S on the image in the “Example tracking” column.

+highway=footway (defines the way).
++surface=* (defines paving).
++name=* (if known).
++wheelchair=no (if not well accessible to wheelchair users, not the case in the picture).
++access=* (what are the legal rules of use).

In case of footway not immediately adjacent to a highway=* and that is wide enough, for example in a park, consider highway=pedestrian.
Fence on the sidewalk.JPG
JOSM hgw barr foot cross.png
Sidewalk referenced by the letter S on the image in the “Example tracking” column.

+highway=footway (defines the way).
++footway=sidewalk (specific for sidewalk).
++surface=* (defines paving).
++access=* (what are the legal rules of use).
++cycleway=* (if there is a cyclepath integrated to the road – this is not present on the picture ).

Reference B letter


If there is a barrier such as a fence between the street and the sidewalk, map a way tagged as barrier=*, or if there is grass between highway=footway and the highway=*, see landuse=*.

Ephrata - MainSt at LincolnAve.jpg
JOSM hgw foot cross.png
Referenced by the letters S – C – C1 – C2 on the image in the “Example tracking” column.

+highway=footway (defines the way).
++footway=sidewalk (specific for sidewalk).
++surface=* (defines paving).
++access=* (what are the legal rules of use).
+highway=footway (C – crosswalk).
++crossing=* (C – details about the pedestrian crossing, for example, if it is controlled by traffic lights).
++crossing_ref=* (C – defines the design of crossing, for example, stripes).
+highway=crossing (C1 – put on the node that the street shares with the pedestrian crossing).
+barrier=kerb (C2 – put on the first and last node of the crossing).

Areas

There is no clear consensus on this topic – see the talk page for more information.

There are two main approaches to mapping the area of a highway=footway, and which to use is dependent upon the context of the area you're mapping. If you are mapping the area of a footway simply to describe the area it covers (e.g., rather than using width=*, perhaps because the width is variable) then it is recommended to use the area:highway=footway tag.

If, however, you are mapping the area of a footway because this provides non-linear routing —for example, large sidewalk areas— then you can map the area as highway=footway and area=yes. This tagging scheme is similar to the well-established highway=pedestrian + area=yes tagging scheme used when mapping pedestrian areas such as plazas and squares. However, there is a clear distinction between highway=footway and highway=pedestrian, and so we should not conflate these two types of highways.

When mapping a highway area, the area should be connected via a node to at least one way. Some mappers chose to continue the way through the area, to enable routers to pick the most straightforward route through the area, but this way should still share nodes with the area (e.g., in the places where it enters and exists the area).

Tags used in combination

See also