<div dir="ltr">On Fri, Jul 27, 2018 at 6:48 PM, Kevin Kenny <span dir="ltr"><<a href="mailto:kevin.b.kenny+osm@gmail.com" target="_blank">kevin.b.kenny+osm@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I'm all for SI units for things like voltages and elevations. I'm<br>
perfectly fine with tagging the elevation of Slide Mountain as 1274<br>
metres and letting a US data consumer convert that to 4180 feet.<br></blockquote><div><br></div><div>I respectfully disagree. One reason is of rounding errors in conversions, as somebody said<br></div><div>earlier in the thread. The other reason is one you imply below.<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>
Regulatory things like maxspeed=* should have the unit in the tag, and<br>
they should be in the same units that the signs are in. A sign reading<br>
'Speed limit 25 mph' means 25 mph, and entering 40.2336 km/h loses the<br>
information that the regulatory signs are in US customary units.<br></blockquote><div><br>+0.5<br><br></div><div>Not +1 because this reasoning applies to *everything.*<br><br></div><div>If you're navigating somewhere unfamiliar to you and GPS isn't giving you an<br></div><div>accurate signal, what you're interested in is what signs actually *say.* Because<br></div><div>when you're in confusing territory a speed sign, or a bridge clearance, or whatever<br></div><div>may be a significant clue. Knowing that the speed limit is 40.2336 km/h doesn't tell<br></div><div>you to look for a sign saying 25 mph. You need both (so you don't break the speed<br>limit), and I hope advances in rendering will eventually allow both (see Wikimedia project<br>to provide multilingual mapping) to be displayable.<br><br>Actually, you only need both if you take your own car to a different country, so your car<br></div><div>speedo is marked in km/h and the signs are mph. Because if you rent a car you're<br></div><div>almost certain to get one where the speedo is marked in the appropriate unit. Actually,<br></div><div>it's been many decades since I've seen speedos that were not marked in both mph<br></div><div>and km/h, but it may be different in other countries.<br><br>That just leaves bridge clearances which will cause problems. But even people<br></div><div>driving in unfamiliar parts of their own country can get that wrong. See this youtube<br></div><div>channel for amusing videos about a bridge with 11' 8" clearance and people who<br>don't understand their vehicle needs more clearance than that:<br><a href="https://www.youtube.com/channel/UCXX0RWOIBjt4o3ziHu-6a5A">https://www.youtube.com/channel/UCXX0RWOIBjt4o3ziHu-6a5A</a><br></div><div><br></div><div>The alternative is to tag in SI units, accept rounding errors in some countries, and<br></div><div>then tag US (and other country) speed limits with something like customary_unit=mph.<br></div><div>Much cleaner to tag in whatever units are actually used and do conversions on the<br></div><div>display side rather than the data entry side.<br></div><div><br>-- <br></div><div>Paul<br><br></div></div></div></div>