I wonder how to tag a pool lift, that is a device with a seat to lower an raise a person in and out of water at a pool or pier, as an accessibility tool for persons with movement limitations (including, but not exlusive to wheelchair users.)
I found platform_lift, which is specific for platforms, not applicable here.
Tagging should not be specific to wheelchairs. First, use of the lifts is not limited to wheelchair users, and second, it’s used by sitting on a chair, not in the wheelchair.
I’d see this kind of equipment as “man_made” object. There are a couple of man_made=lift tags already according to taginfo.
As micromapping becomes more and more popular I am sure we will see more of these objects in the database soon. Only few day ago a saw a similar permanently installed lift, not used for people, but to lift equipment out of an inspection shaft.
Considering this I would appreciate to group such equipment under a generic main tag, like
man_made=lift
lift_type=pool_lift
plus further appropriate tags like access, fee etc.
Looking at taginfo for man_made=lift, this is not really used. I also do not like it because it does not relate to anything: man_made fits too much without describing anything. If I would make up a tag, I’d rather put it to amenity, for being helpful in every day life, or in something related to accessability.
If the platform lift is not attached to any stairs or steps, treat the platform lift as highway=elevator and indicate its restrictions and limitations by adding wheelchair=designated and capacity=1.
I will go with capacity=1 and something for the seat.
I do not consider this as micromapping, but rather detail mapping.
For me, mapping of all this details make OpenStreetMap outstanding and one of the most important aspects of OSM. For people that need special infrastructure, this is crucial! Ever searched for drinking water? Which map will provide you this information.
This has been done for a long time now, nothing new here.
Micromapping in the sense of marking every flowerpot and seat on a restaurant terasse is a different thing. May be nice, but sometime I do not see the value of it.
Just a matter of definition, I do not have any problem with either the one or the other. Fact is that more and more details and minor objects are entered into the database which I understand as a normal process.
I think that man_made is a good approach for such objects and agree that “crane” might be some kind of overkill. That is why I would favour “lift” instead but I do not have a problem with highway=elevator as well.
This is as much as an elevator as a platform_lift . They don’t accommodate you on merely an exposed seat. On the other hand, this is still associated with the landing steps on the left. chairlift (considering aerialway=chair_lift ; or maybe seat_lift ) was already asked @OPENER_next@wielandb during the proposal . It’s only excluded from the lack of public examples, and possible want to be focused. chairlift= can similarly be =vertical vs =inclined to distinguish from stair-attached ones, or even =crane as this isn’t vertical only. Proposal talk:Wheelchair lifts and ramps on platforms - OpenStreetMap Wiki
Nice! This is the thing I would like to connect it to.
One year too late for the discussion and voting, I will think about how to extend the tagging properly without a proposal. It should be so compatible that the ‘pool lifts’ show up on maps for accessibility.
It’s only excluded from the lack of public examples.
Where I found it we got more than a dozen over the last couple years, and it’s a advertised feature in the tourism information. That means I can locate them without visiting all the spots. And we have pictures, also with usable license.
For documentation and continuity, I’d like to add this information to the discussion. @Kovoschiz do you think this is ok?
To me it seems like an important (you could say defining) part of platform_lift=* is that does, in fact, have a platform and is intended to be used with a wheelchair.
The proposal is clear about this being a key feature of platform lifts.
We decided against naming the tag stair_lift=* for platform lifts. Stair lifts allow people to sit on a chair to be lifted up the stairs on which the lift is mounted. Therefore they only transport people without a wheelchair or mobility scooter.
I was also wondering about mapping those, but didn’t find anything fitting… So I’d appreciate if some conclusion was reached and documeented.
I’ve temporarily mapped it as Node: 12081927060 | OpenStreetMap until I find something better (but except perhaps description, those are all lacking / murky)
Mapping this as a crane doesn’t just seem like overkill, I’d argue it’s a completely incorrect tag. Just because both are related to ‘lifting’ things doesn’t mean they serve anywhere near the same purpose. Tagging them as such just because man_made=crane is already in use is not a good reason and is ultimately detrimental for the usability of data for both these accessibility lifts and cranes.
What’s wrong with just creating a new tag for these accessibility lifts?
You don’t necessarily need a proposal to create a new tag and a new dedicated tag even without a proposal is still better than an existing one that doesn’t fit.
Mammi71
(One feature, Six mappers and still More ways to map it)
14
Diese Lifte können zwar auch von anderen bewegungseingeschränkten Personen genutzt werden, in erster Linie sind diese Lifte aber natürlich für Rollstuhlfahrer gedacht. Und natürlich wird nicht der ganze Rollstuhl ins Wasser gehievt, sondern der Rollstuhlfahrer vom Rollstuhl in den Lift umgesetzt. Von daher sehe ich hier ein wheelchair-Tagging als angebracht und richtig.
PS: dass dies für Rollstuhlfahrer gedacht ist, ergibt sich bereits aus der Beschilderung.
However, one should be aware though that without discussion (either like the one provided by formal proposal process or at least informal one like discussing in this thread things like:
what would be the best tag / in what namespace should it be / exact key=value
what its documentation should cover and how it would be defined
what similar uses make sense
what subtags more clearly define it
etc.
one can unfortunately easily create a tag which creates even more mess and confusion and ambiguity and duplication than a more properly discussed and documented solution would.
While proposal process might be a little more work, it does tend to create better quality solutions, as it codifies important things in a checklist-alike form and more eyes means more problems are uncovered and corrected before the tag starts being used.
Source
)