Are you a datauser Paul Allen? Because I hate doing replacements, they ugly and they are work I hate. Replacements make Queries more ugly and longer.<br>Replacements also make the database less reliable, that's literally the opposite of what OSM mappers actually want.<br><br>AND<br><br>EXAMPLE SCENARIO: I look for a way to list all pois with phones. I find the wikipage for the `contact:phone` key. I start to use it in my query. I do not get all data and I think OSM has not good coverage for phone numbers as I thought. In this situation OSM is less reliable to me.<br><br>My example scenario shows a datauser (in this example myself) who missed out the wikipage "phone" and just took the first one "contact:phone". That means some data is hidden from me. And datausers don't have the idea to search for a second wikipage which describes another way of tagging phone numbers because it's logial to have one aggreement on storing data and not one. Two or more ways of storing literally the same thing is what I call inconsistent and bad for database usage.<br><br>~ Sören Reinecke alias Valor Naram<div class="quote" style="line-height: 1.5"><br><br>-------- Original Message --------<br>Subject: Re: [Tagging] Feature Proposal - RFC - (Phone)<br>From: Paul Allen <pla16021@gmail.com><br>To: "Tag discussion, strategy and related tools" <tagging@openstreetmap.org><br>CC: <br><br><br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 6 Oct 2019 at 20:35, Sven Geggus <<a href="mailto:lists@fuchsschwanzdomain.de">lists@fuchsschwanzdomain.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
I fully agree with this. In opencampingmap POI database I currently do a<br>
replacement of the following tags during database import:<br>
<br>
booking -> reservation<br>
contact:phone -> phone<br>
contact:fax -> fax<br>
contact:website -> website<br>
contact:email -> email<br>
<br>
Would be nice to get rid of stuff like this.<br></blockquote><div><br></div><div>Maybe, maybe not (I'm on the fence). I doubt you'll manage to. There are too many</div><div>on both sides who insist that their way is the one true way. It's possible that your</div><div>kluge is actually the best way of handling things like this. Data consumers can translate<br></div><div>contact:phone to phone or phone to contact:phone or leave both untouched as they</div><div>choose. One problem with enforcing a single tag by mappers or preprocessing</div><div>data before putting it in the database is that if there are subtle distinctions they are</div><div>forever lost. You can always scramble an egg but you can't unscramble one.<br></div></div><div class="gmail_quote"><br></div><div class="gmail_quote">-- <br></div><div class="gmail_quote">Paul</div><div class="gmail_quote"><br></div></div>
</blockquote></div>