Key:tactile paving

A tactile paving is a line of different stones/shaping on a footway that has an easy to detect surface, often more rough than the surrounding ground.

• 
  Tactile paving on a sidewalk. Line tile means go and dot tile means attention.
• 
  Tactile paving (white) at a bus stop in Germany.
• 
  Tactile paving warning about a lowered kerb.
• 
  Australian bus stop showing two different tactile patterns.
• 
  Japanese zebra crossing with tactile paving.
• 
  tactile_paving=incorrect - The paving is not where you walk - You don't find the door.
• 
  tactile_paving=incorrect - The paving is not where you walk - You run into the poles. The paving to the door is missing / there are tactile elements used for decoration.

Common values

• tactile_paving=contrasted Where there are a tactile_paving wich contrast is at least 70% the colour of the ground (withe if the ground is black and vice-versa).
• tactile_paving=yes
• tactile_paving=no
• tactile_paving=primitive Where any water drain or decorative tactile element can be used for orientation accidentally, but no typical tactile ground elements are used.
• tactile_paving=incorrect Where tactile paving is used but not in a sensible way, e.g. if the paving is symmetric for visual pleasure but on one of the sides it leads to nothing, or if only one sloped kerb at a crossing has tactile paving. It may be sensible if tactile paving leads to a building wall, because the way continues next to the wall and it can be used for orientation with a white cane.

Note: There is no default value. tactile_paving=no can be tagged explicitly if discovered.

Use

Use on nodes

In general: Use precise coordinates or add FIXME=position estimated!

• For dangerous spots
  • When a footway next to a road ends at a crossing with a lowered kerb sloped kerb, tactile_paving is often used to indicate the dangerous spot tactile_paving=yes. This is set separately for each side of the road, because it can be different! Use in the same way on traffic islands. please note the "kerb" and not "curb" should be used (BE vs. AE).
  • When a bus stop is mapped as a node highway=bus_stop and there is one or more lines of tactile_paging at that bus stop, the bus_stop node gets tactile_paving=yes
  • highway=elevator, when there is a tactile paving at the entrance of an elevator ON EACH LEVEL!

• 
  Tactile paving (white) at a bus stop in Germany. Correct use of tactile paving on node.
• 
  Tactile paving warning about a lowered kerb. Correct use of tactile paving on node.
• 
  Australian bus stop showing two different tactile patterns. Correct use of tactile paving on node.

Use on ways

• On a pedestrian crossing highway=crossing, when the tactile paving is used in a line all across the crossing. Do not use tactile_paving on the way when only the two spots where the footway ends are paved differently.

• 
  Tactile paving on a sidewalk. This is correct use of tactile paving on a way.
• 
  Japanese zebra crossing with tactile paving. This is correct use of tactile paving on a way.

• On footways, when there is a line all the way on the footway highway=footway.
• On platforms, highway=platform or man_made=pier. If the platform or pier is mapped as an area, only if you draw a separate way for the tactile lines. If the platform or pier is small and mapped as a way, add tactile_paving=yes to the way.
  • Use on the way highway=steps (some of which have escalator=yes) of steps, even if there is only a spot with tactile paving at each end. The stairs themselves are sufficiant tactile objects to detect with a white cane.

Use on areas

• tactile_paving=yes is not used on areas. If you have a large area (like a market place) with indicator lines across, draw separate ways for the tactile paving and map on ways.
• tactile_paving=no can be used on border polygons to indicate that a community is not aware at all of the requirements of blind persons.

Use on relations

• tactile_paving=yes can be used on route/tram relations for instance, when all vehicles in use are equipped with tactile indicators at the doors or similar. Please add blind:description:en=* to tell about the details.

Typical combinations

• OSM for the blind
• blind:description:en=* See DisabilityDescription.
• traffic_signals:sound=yes/no
• traffic_signals:vibration=yes/no
• traffic_signals:floor_vibration=yes/no
• traffic_signals:arrow=yes/no
• traffic_signals:minimap=yes/no

Rendering

Tactile paving does not need to be rendered on visual maps by default. It will be used for tactile maps and acoustic routing software for pedestrians.

There is a visual map for features for the blind: blindmap.

^{[ dead link ]}

(link dead since 29/11/2013)

^{[ dead link ]}

(link dead since 29/11/2013)

• HaptoRender - Tactile OSmaps for the blind.
• LoroDux - Pedestrian navigation software for the blind
• Loadstone - GPS tool for the blind, able to import OSM POIs and crossings.

See also

• tourism=information with information=tactile_map
• Category:Visual Impairment
• OSM for the blind
• LoroDux - Pedestrian routing software for the blind
• HaptoRender - Haptic (tactile) maps for the blind
• Original Proposal: Proposed features/Tactile paving