Key:tactile_indicator
| Description |
|---|
| A tactile indicator (tactile paving, a deliberate change of material or a followable edge) and what it tells a blind or visually impaired pedestrian |
| Group: accessibility |
| Used on these elements |
| Useful combination |
| See also |
|
| Status: in use |
| Tools for this tag |
| Note: This key is in use but not approved. A proposal with RFC is planned for late November 2026. |
tactile_indicator=* maps tactile indicators (tactile paving, studs, an intentional change of material, or an edge that can be followed) by what they tell a potentially blind or visually impaired pedestrian: follow, turn, stop or keep off.
It is designed as the successor to tactile_paving=*. Everything that tactile_paving can say still has an equivalent here (see below), and it adds what tactile_paving is missing: what the indicator is for, what it feels like and exactly where it lies. Until this tag has reached a reasonable level of adoption, please keep existing tactile_paving tags and add the tactile_indicator alongside them.
Map the indicator as its own node, way or area where you can (recommended). If you want the simpler option, add it to the feature the indicator belongs to (a kerb, a sidewalk, a train platform). The tags are the same either way.
Values
The values loosely build on the attention and guiding indicators of ISO 23599, and add locating and boundary.
| Value | Tells the pedestrian | Typical examples |
|---|---|---|
tactile_indicator=guide |
Follow this line. | Guide strips in stations and on sidewalks, for example a kerb that can be followed with a cane (kerbs towards the road don't count) |
tactile_indicator=locating |
Something is to the side, follow this to it. Runs across the full width of the walkway and ends at a crossing, stop, door, etc. | A strip across the sidewalk which leads to a crossing or bus stop |
tactile_indicator=attention |
Stop and check, then continue. | Domes at a curb ramp, edges of a platform, top and bottom of stairs, junctions between guide strips, boarding fields at stops |
tactile_indicator=boundary |
Don't go past this. | Separation from a bike lane, the edge of a pool |
Attention or boundary? If people are meant to continue past it eventually (cross the street, board the train), it is attention. If it should not be crossed, it is boundary.
Guide or locating? If it runs across the full width of the walkway and ends at a target beside it, it's locating. If it runs along the route, or crosses it but continues, or branches off a guide strip, it's guide.
New values should only be added for a new instruction to the pedestrian. A typical branching field, for example, is attention where guide strips meet.
Only to be tagged on the feature the indicator belongs to:
tactile_indicator=yes: present, function unknowntactile_indicator=no: nonetactile_indicator=separate: mapped as its own feature
For several functions, use the semicolon approach, e.g. tactile_indicator=attention;locating on a kerb node that has tactile tiles and a locating strip leading up to it. Any additional tags then apply to all of them. If they differ, for example a sett strip leading to tactile tiles, please map each indicator separately.
Additional tags
| Key | Values | If missing | Meaning |
|---|---|---|---|
tactile_indicator:pattern=* |
no, yes, domes, bars | unknown | Any value other than no means proper, purpose-made tactile tiles. domes / bars: the type of relief. yes: type unknown. no: no raised pattern, only a change of material. |
tactile_indicator:surface=* |
any surface=* value |
unknown | The material of the indicator, e.g. sett or metal. Mostly useful with pattern=no. |
tactile_indicator:contrast=* |
yes, no | unknown | Clearly visually distinguishable from its surroundings |
tactile_indicator:colour=* |
any colour | unknown | |
tactile_indicator:pattern:orientation=* |
parallel, perpendicular | unknown | Only on ways, with pattern=bars: whether the bars run parallel or perpendicular to the way the tag is on. |
Missing tags mean unknown. This is so they never claim anything that wasn't mapped, which is safer for someone relying on that information. Please add a pattern to strips and fields whenever you can: no for a change of material, yes or the type for tactile tiles. Add tactile_indicator:contrast=yes when they stand out clearly.
How to map
Simple: on the feature it belongs to
Add the tags to an existing feature. Depending on the feature, they carry a different meaning:
- Kerb node or other node: at this point
- Special note: On a kerb node, the tags describe an indicator at the kerb, most commonly an attention field. The kerb itself is not an indicator, because
kerb=*already describes it. - Crossing (node or way): at both kerbs. A guide strip running across is mapped as it's own way
- Steps: at the top and bottom
- Footway, platform, etc: along it (see sidedness a few lines below)
- Bus stop or station: somewhere on it
- Stop area relation: somewhere in the stop area
- Kerb drawn as a way: the kerb edge itself
- Sidewalk tagged on the road: use
sidewalk:left:tactile_indicator,sidewalk:right:tactile_indicatororsidewalk:both:tactile_indicator
On ways, you can specify which side the indicator runs along. This should be a clear side though, meaning the edge. For example: tactile_indicator:left, tactile_indicator:right or tactile_indicator:both. This is always relative to the direction the way is drawn. Additional tags then follow that side, e.g. tactile_indicator:right:pattern=bars. When no side is specified, it's unknown which side the indicator is on. Sides are only used on ways the indicator belongs to, when no indicator is mapped separately.
If you have the time and motivation, please map the indicator separately (see below). Otherwise you can still improve precision by tagging each kerb node, or the top and bottom nodes of the steps, instead of the crossing or step way.
Detailed (recommended): as its own feature
Draw the indicator where it lies:
- Point: for attention fields only
- Line: along the middle of the strip; needed for guide, locating and boundary
- Area: a closed way with the tag
area=yesfor the full area. A closed way without the area tag is a ring-shaped strip.
Where an indicator line crosses or ends on a footway or another indicator, make sure to share the node. If it runs along a footway, make sure to map it as a separate way so it doesn't share nodes along the footway.
If only the pattern changes along an indicator (common for locating strips), including the orientation of its bars, split the way and keep the same value. If the instruction changes at a spot, for example a field in a guide strip where you should stop, that section gets its own value. The simplest question to ask yourself is, again: what does this section tell the pedestrian?
If you map an indicator as its own feature, tag the feature it belongs to with tactile_indicator=separate.
Examples
Proper tactile paving
| Photo | Situation | Mapped as | Tags |
|---|---|---|---|
| White strip with domes across the sidewalk, leading to a crossing | Line across the sidewalk, sharing a node with the sidewalk way, and ending at the kerb. Split the way if there's a change in pattern. | tactile_indicator=locatingtactile_indicator:pattern=domestactile_indicator:colour=whitetactile_indicator:contrast=yes
| |
| Guide strip running parallel to a sidewalk | The strip gets its own way, the sidewalk way gets tactile_indicator=separate (alternative: omit the separate way and tag it all on the sidewalk) |
tactile_indicator=guidetactile_indicator:pattern=barstactile_indicator:contrast=yes
| |
| Curb ramp with yellow domes | Own way along the strip of domes, and sharing a node at the intersection with the crossing way. The kerb node gets tactile_indicator=separate (alternative: omit the separate way and tag everything on kerb node) |
tactile_indicator=attentiontactile_indicator:pattern=domestactile_indicator:colour=yellowtactile_indicator:contrast=yes
| |
| Yellow strip of domes along a rail platform edge | Line along the edge | tactile_indicator=attentiontactile_indicator:pattern=domestactile_indicator:colour=yellowtactile_indicator:contrast=yes
| |
| Ribbed strip along a platform at a safe distance from the edge (common in Germany) (it does also serve a safety function, but guide is the actual, primary instruction) |
Way along the strip | tactile_indicator=guidetactile_indicator:pattern=bars
| |
| Guide strips meeting at a field | Lines for the strips, and one node where they meet | Strips: tactile_indicator=guide + tactile_indicator:pattern=barsJunction: tactile_indicator=attention + tactile_indicator:pattern=domesBoth: tactile_indicator:colour=yellow + tactile_indicator:contrast=yes
|
Material changes and edges
| Photo | Situation | Mapped as | Tags |
|---|---|---|---|
| Sett strip across a paved sidewalk, leading to a crossing. No proper tactile tiles. | Line across the sidewalk, terminated at the kerb | tactile_indicator=locatingtactile_indicator:pattern=notactile_indicator:surface=sett
| |
| Kerb between the sidewalk and a grass verge that can be followed with a cane | On the kerb way | barrier=kerbtactile_indicator=guide
| |
| Kerb between the sidewalk and a cycle track | On the kerb way | barrier=kerbtactile_indicator=boundary
| |
| Walkable crossing island intentionally paved with sett | On the island area | area:highway=traffic_islandtactile_indicator=attentiontactile_indicator:pattern=notactile_indicator:surface=sett
|
Simple vs. detailed mapping
While you're at it, please consider using the detailed approach if possible. Thank you.
| Situation | Simple | Detailed |
|---|---|---|
| Bus stop with a locating strip and boarding field | On the stop: highway=bus_stop + tactile_indicator=locating;attention + tactile_indicator:pattern=bars |
Indicator strip as a line, boarding field as a node (depending on the size), bus stop tagged tactile_indicator=separate
|
| Stairs with tactile fields at the top and bottom | On the steps way: tactile_indicator=attention + tactile_indicator:pattern=yes |
The same tags on the steps top and bottom nodes |
| Guide strip along the building side of a sidewalk | On the sidewalk way: tactile_indicator:right=guide + tactile_indicator:right:pattern=bars |
As its own line, where it runs |
| Guide strip along a sidewalk that is only tagged on the road | On the road: sidewalk:right:tactile_indicator=guide + sidewalk:right:tactile_indicator:pattern=bars |
On the separately mapped sidewalk way, or as its own line |
Successor to tactile_paving
tactile_paving=* really only records whether a feature has tactile paving. The problem is, it mixes several things into one value (primitive, contrasted, incorrect). This new tag separates them and can describe each indicator on its own.
Why a new key at all? Extending tactile_paving=* with subkeys, such as tactile_paving:function=*, would keep its yes/no main value, which many existing applications rely on. If we then built newer detailed indicators on top, they would either be misread or contradict that value. An example is a feature with tactile_paving=yes and a pattern of no.
This is exactly why an entirely new key is needed, so older applications ignore it, and tactile_indicator can use its main value for the function.
Most values of the tactile_paving tag have a direct equivalent:
| tactile_paving | tactile_indicator |
|---|---|
| yes on a kerb, crossing node, steps or elevator | tactile_indicator=attention + tactile_indicator:pattern=yes
|
| yes on a crossing way | Check on the ground. tactile_paving documents this as a line across the crossing (tactile_indicator=guide), but it's often used for the kerb fields (tactile_indicator=attention)
|
| yes on a footway or path | tactile_indicator=guide + tactile_indicator:pattern=yes
|
| yes on a bus stop, platform or other feature | tactile_indicator=yes + tactile_indicator:pattern=yes
|
| no | tactile_indicator=no
|
| contrasted | As yes above, plus tactile_indicator:contrast=yes
|
tactile_paving:colour=* |
tactile_indicator:colour=*
|
| primitive, incorrect, partial | Doesn't have a direct equivalent, because they mix several things with insufficient detail. Check on the ground, or if you're confident using imagery, then use the tactile indicator values with pattern and surface. |
tactile_paving:type=* |
Just the main value of tactile_indicator, by what it tells the pedestrian, e.g. attention_block → tactile_indicator=attention
|
tactile_paving:surface=* |
tactile_indicator:surface=*
|
| tactile_paving:markings=yes (when there's contrasting markings around the indicator) | tactile_indicator:contrast=yes
|
Please keep tactile_paving tags while apps still rely on them. Don't convert existing data automatically without following the Automated Edits code of conduct.
Notes to data consumers
A locating strip usually terminates on an attention indicator. You can link each strip to the nearest feature from that end node or the feature already sharing a node with the attention indicator, such as the kerb. That feature will often be tagged separate. If both ends touch the same attention area, use the end closer to the feature.
Indicators form their own network, and are connected to the walking network wherever they meet. Apps for blind or visually impaired persons can use it for routing directly. For them, those indicators, mainly guide strips, are the path, not the footways for sighted people.
Extending this scheme
To keep this key scheme from turning into a patchwork, every tag should answer exactly one question:
- What does it tell the pedestrian? The main value
- How does it feel?
tactile_indicator:pattern=* - What is the indicator made of?
tactile_indicator:surface=* - How does it look?
tactile_indicator:contrast=*,tactile_indicator:colour=*
A new subkey should only answer one of these questions (or a new one), and not repeat what another tag already says. For example, tactile_indicator:pattern:orientation=* describes the feeling of the indicator, so it goes under pattern.
See also
- Key:tactile_paving
- The current discussion about this key (German)
- Proposal:Detailed tactile paving: an earlier draft whose pattern ideas this builds on
- DELFI Attribute - Barrierefreiheit im Öffentlichen Personenverkehr
- Forum discussion on sett as tactile paving (Dresden)
- ISO 23599: Tactile walking surface indicators
