[Tagging] Is shelter=separate wanted? What is the meaning of shelter=yes

[Mateusz Konieczny]

Jan 12, 2021, 10:33 by stefan.tauner at gmx.at:

> On Tue, 12 Jan 2021 10:16:05 +0100 (CET)
> Mateusz Konieczny via Tagging <tagging at openstreetmap.org> wrote:
>
>> shelter=separate was recently added to page documenting shelter key
>>
>> See https://wiki.openstreetmap.org/w/index.php?title=Key:shelter&diff=2012123&oldid=1990179
>>
>> It effectively redefined shelter=yes from "this bus stop has shelter" to 
>> "this bus stop has shelter that is not separately mapped"
>>
>> https://taginfo.openstreetmap.org/keys/shelter#values 
>> shelter=yes has 557 951 uses
>> shelter=separate has 245 uses
>>
>> I want to explicitly describe shelter=yes as "it means that given object has shelter. It may
>> or may be not mapped as a separate amenity=shelter object"
>>
>> And describe shelter=separate as unwanted value that should not be used
>>
>
> I think the point of shelter=separate is to allow data users to
> determine if the stop has a shelter even if it is separately mapped
> without the need to do an additional search around the stop for it.
> That intention is good IMHO but I guess it would be better to do this
> in a relation and there should be a clear hint on the shelter page to do
> that with https://wiki.openstreetmap.org/wiki/Tag:public_transport%3Dstop_area
>

The problem is that there is not even plan to how handle over half million
just redefined shelter=yes, many of them retroactively made incorrect

And looking for nearby amenity=shelter seems relatively straightforward to me,
unlike sidewalks where finding matching separately mapped sidewalk is nasty
- even if footway=* and sidewalk=separate tags were used

In this case I see no reason to redefine existing tag and introduce more work for 
mappers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20210112/d7be2d61/attachment.htm>