The downside of using `wheelchair=no` is that there are many conditions
that will prevent some, but not all, wheelchair users from using the
infrastructure. For example: some wheelchair users don't care about curb
ramp info at all because they're comfortable finding driveways and going in
the street (`kerb=raised` does not imply `wheelchair=no`), while others
absolutely require proper infrastructure (most powered wheelchair users,
`kerb=raised` implies `wheelchair=no`). I recommend tagging specific,
on-the-ground conditions that can be interpreted later, like `kerb`,
`barrier`, `width`, `surface`.

Another thing is that you probably want this info to be immediately useful,
but I'm not aware of any existing routers that can use sidewalk=* subtags,
as the sidewalk=* on a street model has to be expanded to a new graph (and
the vast majority of routers don't do that). OpenTripPlanner is attempting
to develop this, but it's unreleased. That doesn't mean you shouldn't tag,
but it's a segue for my next recommendation: consider mapping sidewalks as
separate footways. More or less, you describe sidewalks as
`highway=footway` `footway=sidewalk`, connect them via `highway=footway`
`footway=crossing` ways, and ensure that those crossings intersect and
share a node with streets.  While this involves more ways, it makes it much
easier to organize and use the kinds of subtags you're interested in using,
and can be used directly in most routers. For example, you wouldn't have to
make an executive decision about `sidewalk:width` vs `width:sidewalk` -
just use the widely-documented `width` tag.

Feel free to email me directly if you'd be interested in setting up a
wheelchair mapping effort in your area with separate ways. We (
www.opensidewalks.com) have some in-development tools that can assist with
mapping, but currently need to be explained in-person / via emails.

Best,

Nick

On Sun, Dec 10, 2017 at 9:56 AM Volker Schmidt <vosc...@gmail.com> wrote:

> The other common reason is the sidewalk is too narrow.
>>
>
> Yes.
> I suppose that could taken care of by:
>
>    - width:sidewalk=<value>
>    - width:sidewalk:left|right=<value>
>
> The wheelchair routing could evaluate this.
>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>  Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#m_-6089876021245349881_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> _______________________________________________
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to