Mapping Sidewalks with iD a HowTo
How to Manually Map Sidewalks as Separate Ways
This guide will help you map your cities sidewalks as separate ways using the iD editor. My previous post was mapping sidewalks using JOSM.
The goal is to build a network of routable sidewalks, especially for people with limited mobility. AccessMap.io show the power of OSM to help people navigate their city on foot or in a wheelchair.
While I have you here, I want to give a shoutout to the University of Washington’s Taskar Center for Accessible Technology . The director, Anat Caspi and project lead, Nick Bolton, were the ones that convinced me that we need to change how we map pedestrian ways. They developed the OpenSidewalk Project and AccessMap.io. They are the inspiration behind mapping sidewalks in OSM.
Tools you’ll need
- iD - personnally I like JOSM for editing but iD is well suited to mapping sidewalks.
- Tasking Manager to help break the area into manageable chunks.
- Good satellite imagery
- Street level imagery which can be Bing StreetSide, OpenStreetCam or Mapillary. The last two allow you to capture the street level imagery from your car, bike and even walking.
- Tasking Manager to break the collections into small chunks
- See my previous article on how to evaluate the sidewalk network.
- footway. What we call sidewalks in the US is called a footway in England where OSM got it start. A footway is a pedestrian path between any two points.
- sidewalks. A sidewalk is a footway that run parallel to a street.
highway=footway + footway=sidewalk
- crossing. A street crossing is either a marked or unmarked crossing of a street.
highway=footway + footway=crossing + crossing=marked|unmarked
- Marked/Unmarked Any crossing that is marked on the street should be tagged as
crossing=marked. The marking can be just two parallel lines, stripping, or even intricate patterns. This interpretation differs from the wiki which is confusing.
- crossing islands. Crossing island are small places usually between two lanes of traffic. Tag the short way as
- curbs. In British English its kerb. There are many flavors of kerbs. Here are some of the common ones you’ll likely see:
- Lowered A lowered curb cut should be wide enough for a wheelchair to use. There should be no more than a 1 inch difference between the street and the curb. also referred to as a sloped curb or curb ramp.
- Incline An attempt to create a lowered curb. Using JOSM to measure the length and estimate the height of the curb to determine incline. Most curbs are 6” high but not all. Split the way at the end of the regular sidewalk. Draw the way to indicate movement upward.
- Flushed A flush curb is level with the pavement
- None If there is no curb, tagging the end of the footway with
- Raised A curb with more than a 1 inch difference with the street.
- Rolled Rolled curbs still provide a gutter for water while being traversable by large wheeled vehicles, such as cars and bicycles, but not wheelchairs
kerb=rolledNo image available
A good place to start is to map sidewalks in city blocks around one intersection before adding the crossings. If the imagery is sufficiently sharp you should be able to easily add the sidewalks. Occasionally you’ll need to consult street level imagery to see below tree and other blocked views.
The next logical step would be to add curbs. This is where street side imagery is needed. iD has integrated the three street side packages into the editor.
Determine if a curb ramp exists and if so, what type and is there a tactile pad. Adding the tactile pad is important for people with vision impairments. Adding a short footway between the curb with a ramp and the sidewalk would be a good idea. I don’t, basically because marking a curb ramp in the footway doesn’t impact routing for people with limited mobility and since most curb ramps extend into the way, it’s a good signal to someone with vision impairments that they reached a curb ramp.
Next add the crosswalks. Use
crossing=marked when the intersection is marked for pedestrians or
crossing=unmarked when the crossing isn’t marked. Include a pedestrian crossing node where the street intersects with the crosswalk. It’s purpose is to notify vehicles of the crosswalk. While you are there, check for stop signs and traffic lights to add to OSM.
If there is a island between lanes of traffic, add a way,
This is a special case where there is a wheelchair ramp, usually to a business. It should be mapped as
incline=x%. Use JOSM to measure the length of the way and estimate the height to calculate the percent incline.
- Mark sidewalks that end without access to the street as
- Mark sidewalks that end in the yard with
- If the sidewalk has a raised curb, add an extension to the sidewalk otherwise the router will thing their is a raised curb preventing wheelchair routing.
- Remove any existing footway that connects directly to the road without a crossing. Remember, we are trying to keep pedestrians on the sidewalk.
- Include steps and ramps
- Indicate obstruction areas that block wheelchair access with
- Add surface=* especially if the surface is gravel or other material that would impair or prohibit wheelchair access.
- If working from Tasking Manager, pick a strategy, such as working blocks from south to north and east to west. This will help you not miss intersections.