[Tagging] compressed_air=yes / no - adding to amenity=fuel

[Mateusz Konieczny]

Dec 13, 2021, 15:55 by miketho16 at gmail.com:

>
>
> On Mon, Dec 13, 2021 at 6:29 AM <> osm.tagging at thorsten.engler.id.au> > wrote:
>
>> I think it would be a good idea to generally follow the model established
>>  with sidewalks here.
>>  
>>  e.g.:
>>  compressed_air=separate
>>  bench=separate 
>>  ...
>>  
>>  And apply this pattern to any type of tag where a yes/no is used to indicate
>>  the presence of some associated feature.
>>  
>>  With "separate" meaning "yes, but it's also mapped as it's own object
>>  nearby".
>>
> +1 Otherwise there is a risk that data users will double count.
>  
>
I strongly disagree.

1) it is a widespread practice to use such =yes values to denote
"it has such associated feature which may be mapped separately or not"

Eben if we would declare that =yes means "is not mapped separately"
and =separate "is mapped separately" and bother mappers using it 
in other way - it would still take massive effort to change existing data

2) such resurvey is not really possible 

Even if many mappers would use =yes solely for "and is not mapped separately"
then existing =yes have unclear meaning and will have unclear meaning 
basically forever.

3) it would make much more complicated to do mapping - you would
need to look around whenever you add =yes/no and on adding any bench, atm,
bin and any other feature one would need to look around all objects and
flip =yes to =separate

That is not going to happen.

Overall, =separate is not viable and doomed to failure and likely to waste
plenty of time. Please, do not try doing it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20211214/877e5c0c/attachment.htm>