<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Jan 12, 2021, 11:04 by stefan.tauner@gmx.at:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On Tue, 12 Jan 2021 10:38:05 +0100 (CET)<br></div><div>Mateusz Konieczny via Tagging <tagging@openstreetmap.org> wrote:<br></div><blockquote><div>The problem is that there is not even plan to how handle over half million<br></div><div>just redefined shelter=yes, many of them retroactively made incorrect<br></div></blockquote><div><br></div><div>I see your point.<br></div><blockquote><div>In this case I see no reason to redefine existing tag and introduce more work for <br></div><div>mappers.<br></div></blockquote><div><br></div><div>Well, eventually we have to go through them all anyway (or have this<br></div><div>tag redundantly remain for backwards compatibility) but I am with you.<br></div><div>The change makes the situation worse.<br></div><div><br></div><div>Still, the hint to the relation should be added ;)<br></div></blockquote><div>Which relation?<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>And we should discuss if we should introduce something like separated<br></div><div>but without changing the meaning of =yes. There should be a way to<br></div><div>distinguish the legacy/current meaning "yes, there is a shelter<br></div><div>associated with this stop - either tagged separately or not" and "yes,<br></div><div>there is one but it is separately mapped (and part of the<br></div><div>public_transport=stop_area relation)".<br></div><div>We could re-use the "separate" value for that and verify the bunch of<br></div><div>existing usages.<br></div></blockquote><div>Yes, shelter=separate would make a bit more sense if there would<br></div><div>be some way to distinguish =yes from<br></div><div>"using it in standard way, shelter may exist or not" from<br></div><div>"shelter is definitely not mapped as a separate "<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>And apparently that is what you have already decided during our<br></div><div>discussion here? That previous change was in July. Thanks for fixing it<br></div><div>but I don't really appreciate doing this while it is being discussed...<br></div></blockquote><div>If it is wrong/controversial it may be easily reverted or changed.<br></div><div><br></div><div>Note that if changes to Wiki cannot be made during discussion<br></div><div>then it strongly discourages asking for feedback on tagging<br></div><div>mailing list.<br></div><div><br></div><div>I would need to setup some reminder system<br></div><div>and keep checking whatever discussion continues and <br></div><div>only after that reread entire discussion again...<br></div><div><br></div><div>And I spend more time on editing OSM Wiki than I should<br></div><div>but I am not so motivated.<br></div><div><br></div><div>What is wrong with adding what seems consensus based<br></div><div>on early comments and later editing it further?<br></div><div><br></div><div>OSM Wiki is not set in stone and for parts where there is<br></div><div>agreement it makes sense to update it, rather than starting<br></div><div>long discussion, not documenting anything and repeating<br></div><div>it say year later<br></div><div><br></div><div>It is really surprising to me that people extremely rarely<br></div><div>update wiki based on what become clear in discussion<br></div><div>- tagging mailing comments/thread are hard to find<br></div><div>and basically always will be forgotten.<br></div> </body>
</html>