[Accessibility] Mapping complex road junctions with pedestrian crossings

Barbeau, Sean barbeau at cutr.usf.edu
Mon Feb 13 15:44:02 GMT 2012


Hi all,
We've looked at general accessibility issues in OpenTripPlanner (OTP) and OpenStreetMap as part of a research project at USF (http://www.locationaware.usf.edu/ongoing-research/projects/open-transit-data/), and we would strongly suggest that micro-mapping of intersections in OpenStreetMap be done according to the "Sidewalk as a separate way" (http://wiki.openstreetmap.org/wiki/Proposed_features/Sidewalk_as_separate_way) convention that Flaimo mentions.  This convention seems like the best method to fully support detailed accessibility routing for intersections that aren't perfectly symmetrical.

There are two distinct categories for intersection mapping:  implicit, in which it is assumed that an intersection is perfectly symmetrical (e.g., curb cuts/tactile strips are universal to all sidewalk/road) unless exceptions are stated, and explicit, in which the detail for the entire intersection is coded.  For dense, well-established pedestrian environments like New York or Washington, D.C., the implicit code might be preferred due to less effort by OSM users when coding data.  However, for suburban/rural areas in which pedestrian infrastructure isn't as dense and sidewalks aren't universal the explicit coding seems to be the preferred method.  There is still an open area of work for how routing is handled in transitions between implicitly and explicitly coded areas, and to my knowledge OpenTripPlanner hasn't tackled this yet.  We've coded OSM data according to explicit "Sidewalk as a separate way" method and tested it in OTP on the USF campus in our OTP deployment (http://opentripplanner.usf.edu/), and this method works best for our suburban campus.

More details about "Sidewalk as a separate way" OSM coding in context of OpenTripPlanner is available in a presentation here (http://goo.gl/1xltp) starting on slide 6, and in a final report here (http://goo.gl/k3Uiy) starting on page 47.

I should mention that our research team that worked on this is sighted, and we would welcome any additional insight into this problem from anyone with visual impairments, or anyone with differing opinions.

Thanks,
Sean

Sean Barbeau
Research Associate
Center for Urban Transportation Research
University of South Florida

-----Original Message-----
From: accessibility-request at openstreetmap.org [mailto:accessibility-request at openstreetmap.org] 
Sent: Sunday, February 12, 2012 7:00 AM
To: accessibility at openstreetmap.org
Subject: Accessibility Digest, Vol 29, Issue 6

Send Accessibility mailing list submissions to
	accessibility at openstreetmap.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.openstreetmap.org/listinfo/accessibility
or, via email, send a message with subject or body 'help' to
	accessibility-request at openstreetmap.org

You can reach the person managing the list at
	accessibility-owner at openstreetmap.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Accessibility digest..."


Today's Topics:

   1. Re: Mapping complex road junctions with pedestrian	crossings
      (Flaimo)


----------------------------------------------------------------------

Message: 1
Date: Sat, 11 Feb 2012 13:21:25 +0100
From: Flaimo <flaimo at gmail.com>
To: accessibility at openstreetmap.org
Subject: Re: [Accessibility] Mapping complex road junctions with
	pedestrian	crossings
Message-ID:
	<CAM9eaZLXBJ+kLGgVg9+B39=6D1=YDgXXCFtORz4r50v_yb4GLg at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

there already is an approved proposal for footway=crossing/sidewalk which also introduced sloped kerbs:
http://wiki.openstreetmap.org/wiki/Proposed_features/Sidewalk_as_separate_way
. footway=crossing has been used over 16000 times so far; footway=sidewalk 30000 times. i started tagging those, as soon as the proposal was approved. for example at this junction:
http://osm.org/go/0JhM2ot0J--

regards,
flaimo

On Sat, Feb 11, 2012 at 13:00,  <accessibility-request at openstreetmap.org> wrote:
> ------------------------------
>
> Message: 2
> Date: Fri, 10 Feb 2012 14:58:08 +0100
> From: Peter Wendorff <wendorff at uni-paderborn.de>
> To: accessibility at openstreetmap.org
> Subject: Re: [Accessibility] Mapping complex road junctions with ? ? ? 
> ?pedestrian crossings
> Message-ID: <4F352270.1030700 at uni-paderborn.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi John.
> Welcome on this list.
> I'm sighted too, but working on the Look-and-Listen-Map currently and 
> did my bachelor thesis about navigation for the blind.
> In the thesis I proposed a tagging scheme similar to what you propose here:
> A way cutting the street, where the common nodes are tagged as 
> highway=crossing, crossing=* and a node between the middle node and 
> the "border" node tagged with sloped_curb=* and tactile_paving=*.
> I did not tag the way itself different than any footway, but yes, that 
> may be a good idea.



------------------------------

_______________________________________________
Accessibility mailing list
Accessibility at openstreetmap.org
http://lists.openstreetmap.org/listinfo/accessibility

To unsubscribe from this mailing list send an empty email to accessibility-unsubscribe at openstreetmap.org



End of Accessibility Digest, Vol 29, Issue 6
********************************************



More information about the Accessibility mailing list