Wheelchair routing

From OpenStreetMap Wiki
(Redirected from Rollstuhlrouting)
Jump to: navigation, search
Available languages — Wheelchair routing
· Afrikaans · Alemannisch · aragonés · asturianu · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · Bân-lâm-gú · Basa Jawa · Baso Minangkabau · bosanski · brezhoneg · català · čeština · dansk · Deutsch · eesti · English · español · Esperanto · estremeñu · euskara · français · Frysk · Gaeilge · Gàidhlig · galego · Hausa · hrvatski · Igbo · interlingua · Interlingue · isiXhosa · isiZulu · íslenska · italiano · Kiswahili · Kreyòl ayisyen · kréyòl gwadloupéyen · Kurdî · latviešu · Lëtzebuergesch · lietuvių · magyar · Malagasy · Malti · Nederlands · Nedersaksies · norsk bokmål · norsk nynorsk · occitan · Oromoo · oʻzbekcha/ўзбекча · Plattdüütsch · polski · português · português do Brasil · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · Tiếng Việt · Türkçe · Vahcuengh · vèneto · Wolof · Yorùbá · Zazaki · српски / srpski · беларуская · български · қазақша · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · मराठी · हिन्दी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 吴语 · 粵語 · 中文(繁體)‎ · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް

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

News

Wheelchair Routing Portal Online

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

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

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:housenumber=* 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 sidewalk:left:PROPERTY. *
Sidewalk right sidewalk:right:PROPERTY. *

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


Example

name Key Values Example
Surfaces sidewalk next to sidewalk:left:surface=* paving_stones
Smoothness of pavement right sidewalk: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 sidewalk:left:sloped_curb:start=* 0.1
Curb height on the left end sidewalk: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

Download Mapping Documents

Track recording


Relevant map features


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 Cycleway-markings.jpg highway=cyclewayedit highway=cyclewayedit
highway=footway Dscf0487 600.jpg highway=footwayedit highway=footwayedit
highway=living_street Spielstrasse.jpg highway=living_streetedit highway=living_streetedit
highway=pedestrian Calle arenal.jpg highway=pedestrianedit highway=pedestrianedit
highway=residential Residential.jpg highway=residentialedit highway=residentialedit
highway=secondary Highway secondary-photo.jpg highway=secondaryedit highway=secondaryedit
highway=tertiary Highway tertiary-photo.jpg highway=tertiaryedit highway=tertiaryedit
highway=track Frühlingslandschft Aaretal Schweiz.jpg highway=trackedit highway=trackedit
highway=unclassified Highway unclassified-photo.jpg highway=unclassifiededit highway=unclassifiededit
foot=yes
Foot.png
foot=yesedit foot=yesedit
foot=no foot=noedit foot=noedit
sidewalk=left See also sidewalks and properties sidewalk=leftedit sidewalk=leftedit
sidewalk=right See also sidewalks and properties sidewalk=rightedit sidewalk=rightedit
sidewalk=both See also sidewalks and properties sidewalk=bothedit sidewalk=bothedit
sidewalk=none See also sidewalks and properties sidewalk=noneedit sidewalk=noneedit
Track Type=grade1 {Template:Grade1: desc.}
Surface grade1.jpg
tracktype=grade1edit tracktype=grade1edit
Track Type=grade2 Unpaved track; surface of gravel or densely packed dirt / sand
Surface grade2.jpg
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 gravel.jpg Dscf1582-800.jpg surface = graveledit surface = graveledit
surface=cobblestone Cobblestones Surface cobblestones.jpg Dscf1641-800.jpg cobblestone surface =edit cobblestone surface =edit
surface=ground Earth Dscf1760-800.jpg surface = groundedit surface = groundedit
surface=grass Grass surface Grassway.JPG bbox&description= bbox&description= edit bbox&description= bbox&description= edit
surface=asphalt Asphalt surface Surface asphalt.jpg surface = Asphaltedit surface = Asphaltedit
surface=sand Sand surface Dscf0220 600.jpg surface = sandedit surface = sandedit
surface=paving_stones Paving stones, foot plates Surface paving stones.jpg Dscf1620-800.jpg surface = paving_stonesedit surface = paving_stonesedit
surface=concrete_plates Concrete slabs surface = concrete_platesedit surface = concrete_platesedit
surface=grass_paver Grass pavers Dscf1611-800.jpg Dscf1614-800.jpg surface = grass_paveredit surface = grass_paveredit
Smoothness =* The key =* describes the surface smoothness of paths in terms of usability with vehicles.
smoothness=good Template:Description: smoothness Bus prumyslova.jpg smoothness = goodedit smoothness = goodedit
smoothness=intermediate Template:Description: smoothness Map feature ford.jpg intermediate smoothness =edit intermediate smoothness =edit
smoothness=bad Template:Description: smoothness Smoothnessverybad.jpg 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% Incline17.jpg inclineedit inclineedit
sloped_curb=*

sloped_curb:start=* sloped_curb:end=*

Curb height in general and curb height at the beginning or end of a road. Beginning and end are defined by the digitizing direction.

The values are given in meters and are with "." separately. (Example: 15 cm would be 0.15)

Since the routing can only read so far Ways to be with sloped_curb.start / end the lowered tagged curbs at road checkpoints.

-> See sidewalks and properties

Sloppedcurb.jpg way sloped_curb =|node =|relations =|bbox=7.0,50.7,7.2,50.8|description = sloped_curb}}

sloped_curb.startedit {Relation =||{osm-query|way sloped_curb:end =|node=|bbox=7.0,50.7,7.2,50.8|description = sloped_curb.end}}

sloped_curbedit

sloped_curb.startedit {Relation =||{osm-query|way sloped_curb:end =|node= |bbox=7.75,47.9,7.95,48.1|description = 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. -> See sidewalks and properties: sidewalk: left.wheelchair=*...

Wheelchairlogo.png


NOWheelchairlogo.png
wheelchairedit wheelchairedit

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.
sidewalk:left:surface=* sidewalk: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

sidewalk:left:smoothness=* sidewalk: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

sidewalk:left:width=* sidewalk: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

sidewalk:left:incline=* sidewalk: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

sidewalk:left:sloped_curb=* sidewalk: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

sidewalk:left:sloped_curb:start=* sidewalk:left:sloped_curb:end=*

sidewalk:right:sloped_curb:start=* sidewalk: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.

left startedit

left endedit

right startedit right endedit

left startedit

left endedit

right startedit right endedit

sidewalk:left:wheelchair=* sidewalk:right:wheelchair=* left:wheelchair=* right:wheelchair=* Suitability of the left / right sidewalk for wheelchair users.

-> See path properties, in general "wheelchair =*"

Example leftedit

Example rightedit

Example leftedit

Example rightedit

sidewalk:left:wheelchair:start=* sidewalk:left:wheelchair:end=*

sidewalk:right:wheelchair:start=* sidewalk: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 Steps.jpg
sevice Alley.jpg
access_ramp 1) Accessramp.jpg

1) Please note: The tag highway=access_ramp is rarely used and is under discussion, see http://gis.19327.n5.nabble.com/Question-reg-wheelchair-mapping-tp5864292.html

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

Tag / Value auf Node Foto
highway=crossing Zebra-crossing sm.jpg
highway=elevator
crossing=pedestrian
crossing=zebra
crossing=traffic_signals Ampel.jpg
crossing=uncontrolled
crossing=island
amenity=sloped_curb (better use sloped_curb=yes on crossings) Sloppedcurb.jpg
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)

Stroller yes.jpg

User Manual

Rollstuhlrouting.de/ruhr2010 - Hilfe

See Also

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.