Changes between Initial Version and Version 1 of Ticket #21705, comment 12


Ignore:
Timestamp:
2022-01-02T19:16:07+01:00 (4 years ago)
Author:
Famlam

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21705, comment 12

    initial v1  
    44> Without consider `access=unknown` as acceptable for tagging cases where access is unknown to mapper it would encourage guessing and make things worse.
    55
    6 It could be an info-level warning that Klumbumbus suggests. There are so many warnings that I typically ignore while mapping, unless I'm certain about something, simply because I don't know. However, I'd not add `lit=unknown`, `access=unknown`, `surface=unknown`, `maxspeed=unknown`, ... even though all of those tags will affect data consumers somehow. So definitely a downvote from me for adding (or even accepting) `anything=unknown`
     6It could be an info-level warning that Klumbumbus suggests, if you're concerned about this. There are so many warnings that I typically ignore while mapping, unless I'm certain about something, simply because I don't know. However, I'd not add `lit=unknown`, `access=unknown`, `surface=unknown`, `maxspeed=unknown`, ... even though all of those tags will affect data consumers somehow. So definitely a downvote from me for adding (or even accepting) `anything=unknown`