<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi.<br>
That's how it's documented and defined, but I fear, if you look
into maxspeed tags of countries not using the metric system on
signs, we probably have many "bugs" in values without units, if
you use that assumption.<br>
It's similar to everything else:<br>
If there's nothing declared, you don't know if it's wrong or
missing. If there's no maxspeed at all in the database, we don't
know if there's the national default or if nobody cared about
maxspeeds there, yet.<br>
<br>
That's why I want to ALLOW a unit information even where it's
metric.<br>
<br>
regards<br>
Peter<br>
<br>
Am 26.06.2012 17:03, schrieb Paul Johnson:<br>
</div>
<blockquote
cite="mid:CAMPM96rMekmD7TS7ruScQ084uULjjnL-RcfnG1tUVvFSo3S0-Q@mail.gmail.com"
type="cite">
<p><br>
On Jun 26, 2012 6:03 AM, "Peter Wendorff" <<a
moz-do-not-send="true" href="mailto:wendorff@uni-paderborn.de">wendorff@uni-paderborn.de</a>>
wrote:</p>
<p>> I would prefer to allow (not require) an additional unit
information (mph, km/h), simply to encourage data consumers to
deal with them as they are usually added by users.<br>
> On the other hand no data consumer can be sure about a
(global) default unit if there's no unit given.</p>
<p>I thought it was assumed to be metric unless specified
otherwise. </p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstreetmap.org/listinfo/tagging">http://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>