<div dir="ltr">I'd mostly agree with Greg's description of issues, with the additional caveat that the better we can describe the obstacles, the more plausible it would be for someone to be informed about what they'd be facing. One of my high-school classmates is parapalegic but also athletic (he was actually on the US Disabled Ski Team for a number of years), and especially with a little bit of help, he could get into and around a lot of places that were anywhere close to meeting ADA specs. At the same time, it was incredibly helpful to know what level of barriers were involved, especially when weighing options (i.e. shaving three minutes off a metro ride was most definitely not worth it if it was going to take 10 extra minutes to get out of the station). As it happens, the same info is helpful to a lot of other people (parents with strollers, for example).<div><br></div><div>With that said, the suggestion he made—something similar to sac_scale, ideally adopting something from existing organizations working in that space—is probably a good target until / unless we can get to the level of micromapping every curb, step, ramp (with steepness), etc.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 12, 2021 at 7:11 AM Greg Troxel <<a href="mailto:gdt@lexort.com">gdt@lexort.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
I'm starting to map a new (ish) nature reserve which has permissive<br>
access footpaths (that bit is easy), and some of those footpaths are<br>
suitable for wheelchair users.<br>
<br>
I have been mapping trails and starting to think about this issue too.<br>
<br>
I think it's really important to separate physical suitability from what<br>
we put in the access tag. My impression about access for the US<br>
matches another commenter's, expanded to:<br>
<br>
Wheelchairs and mobility scooters are replacements for pedestrian<br>
access. They don't really have anything to do with bicycles, although<br>
that aspect is debatable.<br>
<br>
It is pretty much unthinkable to have someplace that allows<br>
pedestrians but not wheelchairs. There is essentially never<br>
controversy about this.<br>
<br>
Mobility scooter use by the disabled (perhaps certified disabled) is<br>
sort of allowed whereever pedestrians are allowed, but with<br>
limitations. This is slightly controversial as there are many "no<br>
motorized vehicle" places, and scooters are heavier and capable of<br>
faster speeds. An example policy, picked because I was able to find<br>
it, but a tagging scheme should be able to cope with a large number of<br>
such policies:<br>
<a href="http://www.middlesexcountynj.gov/Government/Departments/IM/Documents/Parks%20and%20Rec/Reservations/Trails%20Mobility%20Policy%202021%205.11.21.pdf" rel="noreferrer" target="_blank">http://www.middlesexcountynj.gov/Government/Departments/IM/Documents/Parks%20and%20Rec/Reservations/Trails%20Mobility%20Policy%202021%205.11.21.pdf</a><br>
<br>
A summary of the policy is that wheelchairs (unpowered) are allowed,<br>
period, and that powered devices have a presumption of being allowed<br>
except where it wouldn't be safe and there are rules per trail.<br>
<br>
So I conclude that at top level we have to represent three things<br>
(specific tags are to explain, not really proposals):<br>
<br>
wheelchair=yes -- a wheelchair can physically travel<br>
<br>
wheelchair:access=no -- wheelchairs are prohibited (but pedestrians<br>
are allowed). I don't think we need this, until there's a non-trivial<br>
exmmple.<br>
<br>
mobility_scooter:physical=yes -- a mobility_scooter can physically travel<br>
<br>
mobility_scooter:access=no -- mobility scooters are prohibited, even<br>
though foot traffic and wheelchairs are allowed<br>
<br>
<br>
Then there is the issue of grades of wheelchair suitability. I have<br>
known multiple people using wheelchairs, and the difference in ability<br>
to travel among individuals is significant. Consider a 90 year old who<br>
is generally not able to do much, with a traditional wheelchair, and<br>
someone who is 18 with strong arms but can't use their legs to walk,<br>
with a carbon-fiber sport wheelchair.<br>
<br>
The existing key<br>
<a href="https://wiki.openstreetmap.org/wiki/Key:wheelchair" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Key:wheelchair</a><br>
is to me very clearly about physical access.<br>
<br>
It says that for the US, wheelchair=yes means meeting ADA requirements.<br>
Those are pretty strict, and there are many places that don't meet them<br>
exactly but that most wheelchair users can in practice go. Then there<br>
are things that are walking paths, trails, that become more difficult.<br>
<br>
So I think we need something like sac_scale, to indicate<br>
<br>
ADA compliance (or the equivalent?), which is about max slope, curbs,<br>
resting areas, and a bunch of other technical design requirements<br>
<br>
suitable for someone in a heavy regular wheelchair who can't deal with<br>
too much<br>
<br>
suitable for someone with more arm strength who is willing to put up<br>
with bumps<br>
<br>
suitable for sport wheelchair use<br>
<br>
I don't presume to have gotten that right, and I'm basically certain I<br>
didn't -- but it's an example of how complicated this might be. I<br>
would think there are disability organizations that have some<br>
definitions used in guides, and we really should figure that out and<br>
adopt their labels rather than making our own (hence the sac_scale<br>
reference).<br>
<br>
Greg<br>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Kevin Broderick</div><div><a href="mailto:ktb@kevinbroderick.com" target="_blank">ktb@kevinbroderick.com</a></div></div></div>