Wheelchair routing

Contents 1 Goal: building a routing portal for wheelchair users 1.1 Covered Area 2 News 2.1 Wheelchair Routing Portal Online 2.2 Project Ruhr 2010-barrier-free 2.3 Disabled toilets 2.4 Looking for helpers 2.5 Project Wheelmap.org 2.6 Routing portal goes online 2.7 Mapping Party Bonn 3 Requirements for Wheelchair Accessible Routes 4 Test Areas 4.1 Desired test areas 5 Rolli Mapping 5.1 Tagging 5.1.1 Properties 5.1.2 Sidewalks 5.1.3 Curb heights 5.2 Device 5.3 Download Mapping Documents 6 Tags for routing 6.1 General way types 6.2 Path properties, in general 6.3 Sidewalks and properties 6.4 Obstacles/Accessibility 7 Important, not previously evaluated for the routing tags (because of Nodes) 8 Profile 9 User Manual 10 See Also 11 Sources und Links

Goal: building a routing portal for wheelchair users

Based on OSM data, develop a route planner especially for wheelchair users. But the existing one is OpenRouteService of the Geoinformatics Department, Institute of Geography University of Heidelberg (Formerly Cartography of the University of Bonn) expanded. University of Heidelberg GIScience (Geoinformatics) Research Group ([1])

GIScience Research Group (Geoinformatics)

University of Heidelberg

http://giscience.uni-hd.de

Zipf@uni-heidelberg.de

To this end, a web portal is set up, looking over the users goals in their environment, and the best way to display the wheelchair.

The difficulty of the way is made clear. Hazards or difficult passages be marked with symbols. In addition to the slope are given.

To enable routing, the routes must be labeled "accessible to wheelchairs" and meet specific requirements.

Covered Area

• Germany only.

News

Wheelchair Routing Portal Online

The wheelchair routing portal is available for testing online. It can be accessed at the following address:

• http://www.rollstuhlrouting.de

On 15.09.2009 (and 19.09.2009) ran the article "Maps make life easier. OpenStreetMap Wheelchair." The contribution can also be viewed at:

• Routing wheelchair at Quarks & Co.

Project Ruhr 2010-barrier-free

In 2010, Essen and the Ruhr European Culture Capital, at www.ruhr2010-barrierefrei.de is a lot of information on accessibility of venues, attractions, lodging, restaurants, pubs, car parks and toilets available. This information is then transferred to the OSM database. It would be nice if the OSM community could help it. This information will be analyzed for the mobility routing.

The new OSM tags for this purpose are described later on this page. - BlackBike 10:04, 6 February 2010 (UTC)

Disabled toilets

In the city of Bonn is an urgent need for disabled toilets to be tagged. For some it is a so-called "Euro-key (default is in Germany, all City Toilets Wall AG and many, especially newer, motorway toilets so equipped. All disabled toilets on motorway parking areas without any further development with buildings can be assumed almost always from € key ability. Furthermore, such facilities are often found in public buildings.). This enables physically impaired people to gain access to the disabled toilets. Therefore, this tagging as follows:

Name	Key	Value
Toilet	amenity=*	Toilets
Fitness for wheelchair users	wheelchair=*	Yes
"Eurokey"	centralkey=*	Eurokey
Opening times	opening_hours=*	Times
Address Street	addr: street=*	Name of road
Address house number	addr: house number=*	Number

Looking for helpers

It is still important to find mappers and wheelchair users, record the data for this project. Only with sufficient data, the test area from Bonn to a larger area to be expanded.
Who participates in data collection may appear in the category of helpers.
Enter any questions you used to me: Astrid

I would like to get involved, certainly not in Bonn. How about extending the area of the map first time to offer an incentive? The Wheelchairmap On the one see so well that disabled-related tags are used worldwide. Right now you get not even a sensible error message when you try to use the card outside Bonn. I'm at least not with a yardstick to the pavement, without that I can try out the result soon after! - Lulu-Ann 12:10, 15 January 2010 (UTC)

Project Wheelmap.org

The project Wheelmap the association social heroes eV would cooperate. OSM makes the technique (until now work with a Google Map), social hero makes the advertising, to move to non-OSMler to submit the wheelchair-accessible facilities. - Lulu-Ann 15:37, 20 October 2009 (UTC)

Routing portal goes online

No later than the 1.9 is the first prototype of the wheelchair-routing portal "online. The Internet address is http://www.RollstuhlRouting.de Feedback welcome! http://www.geog.uni-heidelberg.de/giscience.html

Mapping Party Bonn

Details of the mapping party on wheelchair Routing in Bonn can be found here: Mapping Party Bonn

Requirements for Wheelchair Accessible Routes

Parameters	request and recommendation to DIN 18024-1
Road surface	Fixed Low vibration Increased volumes in the surface max. 5 mm No rough, deep sand or gravel No grass No strong rooting Not very rocky or muddy etc. Not very uneven
The light path width	Main route: min 150 cm 200 cm Byway: min 90 cm, 100 cm more
Longitudinal slope	3% 3% - 6%: Verweilplatz every 10 m (wheelchair user manual)
Cross slope	2%
Columns	Column max. 3 cm across the Route Columns parallel to Route with more than 3 cm in length: max. 0.5 cm wide (for example, grid)
Thresholds curb height	Max. 3 cm
Ramp	Max. 6% slope Min. 120 cm between the wheel deflector ramp From 600 cm length: 150 cm x 150 cm Verweilplätze with max. 3% slope

Test Areas

As a test regions, the urban areas of Bonn and serve Freiburg im Breisgau .

A city with very many well-tagged stairs (with highway=steps and step_count=*) is Pforzheim. Another area with lots of stairs and slopes in the district is Hamburg Blankenese.

Desired test areas

I would like to test in the Hanover region, please complete the range. - Lulu-Ann 19:07, 20 January 2010 (UTC)

We want to Rostock to work with 2 schools and inspire them with your service for a data migration. - i! 17:13, 20 February 2010 (UTC)

Rolli Mapping

Tagging

Important for mapping for wheelchair users are tags that describe the properties of paths and especially the properties of pavements.

Properties

Name	Key	Value (example)
Smoothness	smoothness=*	Good / intermediate / bad
Surfaces	surface=*	Paving_stones
Width / m	width=*	2.5
Slope	incline=*	3% -2.5%
Curb height / m	sloped_curb=*	0.03

More detailed information about the individual tags can be found at tags for routing

Sidewalks

name	Key	Values Example
Sidewalk next to	footway:left.PROPERTY.	*
Sidewalk right	footway:right.PROPERTY.	*

Note: "left" and "right" refer to the digitizing direction!

Example

name	Key	Values Example
Surfaces sidewalk next to	footway:left.surface=*	paving_stones
Smoothness of pavement right	footway:right.smoothness=*	good

Curb heights

The routing algorithm can only tags that belong to the line elements (ways), evaluate. Therefore, the property lowered curb "a way to attach. To define the point at which is located on the lowering of the Way, the key is the extra information "start" and "end" is added:

name	Key	Values Example
Curb height left start	footway:left.sloped_curb.start=*	0.1
Curb height on the left end	footway:left.sloped_curb.end=*	0.03

Device

In addition to GPS the following devices are strongly recommended:

• Yardstick for measuring the curb heights
• Protractor or Level for measuring the slope

• Measuring Pitch
• 

  Digital Level with% - and ° - ad.

• 

  protractor, available for a few euros in the construction market.

Download Mapping Documents

Track recording

• track recording

Relevant map features

• Characteristics of roads and sidewalks: properties
• Trail type: path-types

Tags for routing

The above-mentioned requirements on the way to the hitherto existing in OSM tags (attributes) are mapped inaccurately. However, it is tested with the available options, a first routing.

Since the routing algorithm currently only tags that belong to evaluate the line elements (ways), it can, only that in the following table are listed. Tags, such as highway = crossing "can not therefore be considered first. At a later stage, they will be able to be installed. Therefore, these tags are "Important not yet usable tags" also listed.

General way types

Tag / Value	Description	Photo	Bonn	Freiburg
highway=cycleway			highway=cyclewayedit	highway=cyclewayedit
highway=footway			highway=footwayedit	highway=footwayedit
highway=living_street			highway=living_streetedit	highway=living_streetedit
highway=pedestrian			highway=pedestrianedit	highway=pedestrianedit
highway=residential			highway=residentialedit	highway=residentialedit
highway=secondary			highway=secondaryedit	highway=secondaryedit
highway=tertiary			highway=tertiaryedit	highway=tertiaryedit
highway=track			highway=trackedit	highway=trackedit
highway=unclassified			highway=unclassifiededit	highway=unclassifiededit
foot=yes			foot=yesedit	foot=yesedit
foot=no			foot=noedit	foot=noedit
footway=left	See also sidewalks and properties		footway=leftedit	footway=leftedit
footway=right	See also sidewalks and properties		footway=rightedit	footway=rightedit
footway=both	See also sidewalks and properties		footway=bothedit	footway=bothedit
footway=none	See also sidewalks and properties		footway=noneedit	footway=noneedit
Track Type=grade1	{Template:Grade1: desc.}		tracktype=grade1edit	tracktype=grade1edit
Track Type=grade2	Unpaved track; surface of gravel or densely packed dirt / sand		tracktype=grade2edit	tracktype=grade2edit

Path properties, in general

The tag Smoothness is initially of little significance, since according to Tagwatch and because of controversial discussion on its application so far is little or no spread consensus on its use was achieved in OSM. He could, however, in the rare case of its presence serve as exclusion criteria. For the wheelchair-routing is the day smoothness in the pilot regions is not explicitly tagged.

Tag / Value of Way or Area	Description	Photo	Bonn	Freiburg
Surface =*	The key =* surface describes the surface layer of roads and paths
surface=paved	Secured paved		surface = pavededit	surface = pavededit
surface=unpaved	Unpaved		surface = unpavededit	surface = unpavededit
surface=gravel	Gravel, crushed stone		surface = graveledit	surface = graveledit
surface=cobblestone	Cobblestones		[2]edit cobblestone surface =	[3]edit cobblestone surface =
surface=ground	Earth		surface = groundedit	surface = groundedit
surface=grass	Grass surface		[4]edit	[5]edit
surface=asphalt	Asphalt surface		surface = Asphaltedit	surface = Asphaltedit
surface=sand	Sand surface		surface = sandedit	surface = sandedit
surface=paving_stones	Paving stones, foot plates		way paving_stones = surface =|node =|relations =|description = surface = paving_stones}|bbox = 7.0,50.7,7.2,50.8}	way paving_stones = surface =|node =|relations =|description = surface = paving_stones}|bbox = 7.75,47.9,7.95,48.1}
surface=concrete_plates	Concrete slabs		way concrete_plates = surface =|node =|relations =|description = surface = concrete_plates}|bbox = 7.0,50.7,7.2,50.8}	way concrete_plates = surface =|node =|= relation|description = surface = concrete_plates}|bbox = 7.75,47.9,7.95,48.1}
surface=grass_paver	Grass pavers		way grass_paver = surface =|node =|relations =|description = surface = grass_paver}|bbox = 7.0,50.7,7.2,50.8}	way grass_paver = surface =|node =|relations =|description = surface = grass_paver}|bbox = 7.75,47.9,7.95,48.1}
Smoothness =*	The key =* describes the surface smoothness of paths in terms of usability with vehicles.
smoothness=good	Template:Description: smoothness		smoothness = goodedit	smoothness = goodedit
smoothness=intermediate	Template:Description: smoothness		intermediate smoothness =edit	intermediate smoothness =edit
smoothness=bad	Template:Description: smoothness		smoothness = badedit	smoothness = badedit
width=*	Width of the road in meters. Information is given with a dot. Example: 2.5, 1.5 ....		widthedit	widthedit
incline=*	Xy%		[6]edit sloped_curb.end
wheelchair=yes wheelchair=* Template:Tag limited	Suitability of the path for wheelchair users. This day only to be set if one is absolutely sure. -> Seesidewalks and properties: footway: left.wheelchair=*...		[7]edit wheelchair	[8]edit wheelchair

Sidewalks and properties

The following tags are not the usual process of Vote go through and should be avoided for now! This is particularly controversial in this case, since there are several competing proposals are, addressing the issue of additional tracks that run next to and / or right along a main road. To illustrate the problem, the table was added to a second variant of the tagging.

Day on Way or Area	Alternative	Description	Photo	Bonn	Freiburg
	left: highway=* right: Highway=* left2: highway=* right2: Highway=*	A prefix key in allowing the use of all available tags to detect features / usage / status / permission for a track. Furthermore, there is no limit, which relates the number of left or right or running paths along a "real" covered path.
footway: left.surface=* footway: right.surface=*	left: surface=* right: surface=*	Surface layer of the left / right sidewalk in relation to the direction of digitization. The values (Values) entspechen those of surface=*. -> See path properties, in general "surface =*"		Example leftedit Example rightedit	Example leftedit Example rightedit
footway: left.smoothness=* footway: right.smoothness=*	left: smoothness=* right: smoothness=*	Smoothness of the left / right sidewalk. The smoothness refers to the usefulness of vehicles. The values (Values) entspechen those of smoothness=*. -> See path properties, in general "smoothness =*"		Example leftedit Example rightedit	Example leftedit Example rightedit
footway: left.width=* footway: right.width=*	left: width=* right: width=*	Width of the left / right sidewalk in meters. The values (Values) entspechen those of width=*. The values are given in meters and are with "." separately. (Example: 1.5) -> See path properties, in general "width =*"		Example leftedit Example rightedit	Example leftedit Example rightedit
footway: left.incline=* footway: right.incline=*	left: incline=* right: incline=*	Slope of the left / right sidewalk. The values (Values) entspechen those of incline=*. The values are given in% (eg 6%) -> See path properties, in general, "incline =*"		Example leftedit Example rightedit	Example leftedit Example rightedit
footway: left.sloped_curb=* footway: right.sloped_curb=*	left: sloped_curb=* right: sloped_curb=*	Curb height of the left / right sidewalk. The values are given in meters and are with "." separately. (Example: 15 cm would be 0.15) -> See path properties, in general, "sloped_curb =*"		Example leftedit Example rightedit	Example leftedit Example rightedit
footway: left.sloped_curb.start=* footway: left.sloped_curb.end=* footway: right.sloped_curb.start=* footway: right.sloped_curb.end=*	left: sloped_curb.start=* left: sloped_curb.end=* right: sloped_curb.start=* right: sloped_curb.end=*	Curb height of the sidewalk at the beginning and end of the Ways. Beginning and end are defined by the digitizing direction. Because the routing node can not read yet, hereby Lowered be tagged curbs at road checkpoints.		leftedit start left endedit right startedit right endedit	leftedit start left endedit right startedit right endedit
footway: left.wheelchair=* footway: right.wheelchair=*	left: wheelchair=* right: wheelchair=*	Suitability of the left / right sidewalk for wheelchair users. -> Seepath properties, in general "wheelchair =*"		Example leftedit Example rightedit	Example leftedit Example rightedit
footway:left.wheelchair.start=* footway:left.wheelchair.end=* footway:right.wheelchair.start=* footway:right.wheelchair.end=*	left:wheelchair.start=* left:wheelchair.end=* right:wheelchair.start=* right:wheelchair.end=*	Eignung des Bürgersteigs für Rollstuhlfahrer am Anfang/ Ende des Weges. Hiermit kann die Eignung von Straßenübergängen getaggt werden.		left startedit left endedit right startedit right endedit	left startedit left endedit right startedit right endedit

Obstacles/Accessibility

Key	Value	Foto
access	designated
	restricted
highway	steps
	sevice
	access_ramp

Important, not previously evaluated for the routing tags (because of Nodes)

Tag / Value auf Node	Foto
highway=crossing
highway=elevator
crossing=pedestrian
crossing=zebra
crossing=traffic_signals
crossing=uncontrolled
crossing=island
amenity=sloped_curb (better use sloped_curb=yes on crossings)
elevator=*
amenity=parking
disabled_spaces=NumberOfParkingSpacescapacity:disabled=NumberOfParkingSpaces
barrier=*
amenity=toilets
wheelchair=yes/no/limited/only

Profile

• E-Wheelchair
• Manual Wheelchair
• Pushed Wheelchair
• Stroller/Child's wheelchair (short, two parallel slants) established: stroller=yes/(no)

User Manual

Rollstuhlrouting.de/ruhr2010 - Hilfe

See Also

• Wheelchair Map: Wheelchairmap NEW! Now, not only nodes but also ways!
• Pages that link to this page

Sources und Links

• Friedrich, Juliane. 2005: FreiRaum. Planning guidelines for the accessible design of hiking trails. Institute of Transport and Urban Planning. Fachhochschule Erfurt.
• Natur für alle: Planning Guidance on Accessibility.
• nullbarriere.de- Website Accessible to the field of Planning, Building and Housing
• Fernsehbeitrag "OpenStreetMap für Rollstuhlfahrer" in Quarks & Co. (WDR)
• Zusatzinformationen from Quarks & Co. Beitrag
• Müller, A., Neis, P. Zipf, A. (2010): Route planning for wheelchair users based on OpenStreetMap data. Design, implementation and perspectives, AGIT 2010. Symposium on Applied Geoinformatics, Salzburg, Austria.