<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 18/5/23 04:48, Mateusz Konieczny via
talk wrote:<br>
</div>
<blockquote type="cite" cite="mid:NVf1kqP--3-9@tutanota.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>May 16, 2023, 19:22 by <a class="moz-txt-link-abbreviated" href="mailto:ajt1047@gmail.com">ajt1047@gmail.com</a>:<br>
</div>
<blockquote class="tutanota_quote" style="border-left: 1px solid
#93A3B8; padding-left: 10px; margin-left: 5px;">
<div class="">On 24/04/2023 16:57, Mateusz Konieczny via talk
wrote:<br>
</div>
<blockquote type="cite">
<div><br>
</div>
<div><br>
</div>
<div>Apr 22, 2023, 14:10 by <a class="moz-txt-link-freetext"
href="mailto:ajt1047@gmail.com" rel="noopener noreferrer"
target="_blank" moz-do-not-send="true">ajt1047@gmail.com</a>:<br>
</div>
<div><br>
</div>
<blockquote style="border-left: 1px solid #93A3B8;
padding-left: 10px; margin-left: 5px;"
class="tutanota_quote">
<div>More generally, anyone with half a brain consuming OSM
shop data (or actually, _any_ external data from
_anywhere_) will look at the values contained in it***.<br>
</div>
</blockquote>
<div dir="auto">And that is exactly what lead to proposing
this edits - I was writing code to handle OSM<br>
</div>
<div dir="auto">data and researched tagging situation. And one
of[1] effects was discovering numerous<br>
</div>
<div dir="auto">cases of tags that seem to be exact duplicates
of more standard ones, and retagging<br>
</div>
<div dir="auto">them seems to clearly improve OSM data as far
as I can see<br>
</div>
<div dir="auto"><br>
</div>
</blockquote>
<p>Your continued tagfiddling here is making it much harder for
local mappers to find problem values in OSM data.<br>
</p>
<p>No-one's going to complain about you changing "shop=shoe" to
"shop=shoes" - they clearly have the same meaning, so changing
the less common form to the more common form is a net benefit.<br>
</p>
<p>However, your recent changes have gone much further than
this, included changing shops with values you don't understand
into "shop=yes". <br>
</p>
</blockquote>
<div dir="auto">For start: no such changes will be made, if
requested I can revert changes<br>
</div>
<div dir="auto">of shop=fixme to shop=yes if it is disputed.<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">-----------<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">But I do not really agree with some claims made
here and want to explain why.<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">For start there is a long list of shop values
which meaning I do not understand<br>
</div>
<div dir="auto">(for example, from start of list of exactly such
values:<br>
</div>
<div dir="auto">shop=grossery, shop=towing, shop=showroom,
shop=salon, shop=garage,<br>
</div>
<div dir="auto">shop=pond, shop=consignment...)<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">This change was made because it was carrying no
real info and was obscure value<br>
</div>
<div dir="auto">unlikely to be found and handled by mappers.<br>
</div>
<blockquote class="tutanota_quote" style="border-left: 1px solid
#93A3B8; padding-left: 10px; margin-left: 5px;">
<div dir="auto">As an example, consider <a
href="https://www.openstreetmap.org/way/353944525"
class="moz-txt-link-freetext" rel="noopener noreferrer"
target="_blank" moz-do-not-send="true">https://www.openstreetmap.org/way/353944525</a>
. It was previously "shop=retail", an unusual and rare tag
that would likely flag up the interest of a passing local
mapper. You changed it to "shop=yes", of which there are
180,000 of in OSM. <br>
</div>
</blockquote>
<div dir="auto">Except people using JOSM validator*, iD,
StreetComplete and other tools with special<br>
</div>
<div dir="auto">support for shop=yes as feature tag. Note that
this tools are more or less proactive<br>
</div>
<div dir="auto">while shop with unusual values will be spotted
solely by manual checks<br>
</div>
<div dir="auto">(as listing all unusual shop values is far from
helpful and requires a long<br>
</div>
<div dir="auto">filtering to skip undocumented values, aliases,
confusing values carrying some info)<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">*and therefore also Osmose, though I would not
recommend this QA tool<br>
</div>
<div dir="auto">
<blockquote class="tutanota_quote" style="border-left: 1px solid
#93A3B8; padding-left: 10px; margin-left: 5px;">
<div dir="auto">No-one is going to spot that as an "unusual"
shop at all. <br>
</div>
</blockquote>
<div>Thousands/tens of thousands were fixed already, at least 10
000 would be <br>
</div>
<div dir="auto">definitely not spotted and not fixed if they
would be just one of 10237 rare shop values.<br>
</div>
<br>
</div>
</blockquote>
<p><br>
</p>
<p>A render finding an unexpected value could simply handle it as
'shop=yes' and carry on.</p>
<p><br>
</p>
<p>If you want to flag these to mappers?Then contact the relevant
mapper then failing a contact add a fixme/note. ??? <br>
</p>
<p><br>
</p>
<p>shop=garage .. A shop that sells garages... <br>
</p>
<p><a class="moz-txt-link-freetext" href="https://www.totalspan.com.au/residential/garages/garages-with-workshops/">https://www.totalspan.com.au/residential/garages/garages-with-workshops/</a><br>
</p>
</body>
</html>