[Tagging] Facts and opinions

[Mateusz Konieczny]

Jan 9, 2019, 11:59 PM by 61sundowner at gmail.com:

> On 10/01/19 05:27, Mateusz Konieczny      wrote:
>
>> Jan 8, 2019, 10:33 PM by >> graemefitz1 at gmail.com <mailto:graemefitz1 at gmail.com>>> :
>>
>>> On Tue, 8 Jan 2019 at 23:36, Simon Poole <>>> simon at poole.ch <mailto:simon at poole.ch>>>> >              wrote:
>>>
>>>>
>>>> I'm not convinced that we really want to model such a                  level of detail in the first place, 
>>>>
>>>>
>>> Agree with you there!
>>>
>>> If the place is a shop=tyres, isn't that really all              that OSM needs to say?
>>>
>> I am fine with tagging more        detailed info. But I would be equally fine with deleting any
>> outdated detailed info.
>>
>>
>>
>>>
>>> & where do we stop with extreme details?
>>>
>> At level        where mappers are unwilling to maintain up to date information.
>>
>>
>>
>
> Some time ago I came across a section of road that, in OSM, used an    old bridge.
>  That bridge had not been there for quite some time, the new one was    evident in imagery. 
>  
>  Should that section of road be deleted because 'no one is    maintaining it'??? 
>
No, I was answering "where do we stop with extreme details".
 

>  It is a section of main highway in Australia. I think it needs to    stay, even if the detail is wrong .. there will still be a highway    through that area. 
>
but detail may be deleted (for example if old bridge was 3D mapped it is fine to delete it and
map new one without 3D tagging)

>  
>  Shops too may come and go .. but physically the 'shop' structure    remains. 
>  So what happens when 'no one is maintaining it'? It may get out of    date .. have incorrect information .. and when someone finds it they    can update it. 
>
And during update they are free to delete outdated detail rather than updating it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20190110/3f29e2c7/attachment-0001.html>