[Tagging] Use of highway=track vs highway=service cemeteries, parks, allotment gardens, golf courses, and recreation areas

Yves ycai at mailbox.org
Fri Mar 5 18:54:21 UTC 2021

Not to mention the other nightmare : unpaved + concrete + horrible or whatever fancy combination you can imagine. I'd also let the more general classification to the data user. 

Le 5 mars 2021 18:42:01 GMT+01:00, Paul Norman via Tagging <tagging at openstreetmap.org> a écrit :
>On 2021-03-05 1:50 a.m., Richard Fairhurst wrote:
>> Graeme Fitzpatrick wrote:
>> > Could consideration be made to move to a two tier system of
>> > surface=paved, unpaved and then surface:paved=* and
>> > surface:unpaved=* ? Coupling this with smoothness would
>> > make the data easier to digest
>> No it wouldn't!
>> This is over-complicating things and really, really unnecessary.
>> If surface=gravel then it's unpaved, because... it's gravel. If 
>> surface=ground it's unpaved, because... it's ground. And so on. You 
>> really do not need two keys to express this.
>> It does not make it easier to digest. It makes it harder. Trust me. I 
>> probably do more complex surface parsing for cycle.travel than any 
>> other data consumer and this would be no help whatsoever, it would 
>> just be yet more code I have to write.
>I agree with this. The proposal would not make data easier to digest.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20210305/e62f4cfa/attachment-0001.htm>

More information about the Tagging mailing list