<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 31/07/19 20:28, Paul Allen wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPy1dO+-oLVZ3Siv8g3=cni9ROdPr0RU7--ejN2dLvtAhCyWQw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">
<div dir="ltr">On Wed, 31 Jul 2019 at 08:35, Warin <<a
href="mailto:61sundowner@gmail.com" moz-do-not-send="true">61sundowner@gmail.com</a>>
wrote:<br>
</div>
<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"><br>
Err the wiki could state the default is kW.<br>
There is no present default unit for power - see <a
href="https://wiki.openstreetmap.org/wiki/Map_Features/Units#Default_units"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Map_Features/Units#Default_units</a><br>
Adding a default would be good, and kW is probably the most
universal in this case, but for power generation MW is more
universal.<br>
</blockquote>
<div><br>
</div>
<div>There have been sporadic discussions here about mapping
the availability of USB charger</div>
<div>outlets. A default of kW doesn't suit everything. </div>
</div>
</div>
</blockquote>
<br>
USB outlets are typically specified by the current capability. So I
would not tag power on them but current. <br>
Say, current=0.5 A or current=2.1 A .. where A stands for Ampere. <br>
<br>
<blockquote type="cite"
cite="mid:CAPy1dO+-oLVZ3Siv8g3=cni9ROdPr0RU7--ejN2dLvtAhCyWQw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>But, assuming we agree that SI multipliers</div>
<div>can be used, then sure, kW is a reasonable default. I
would also propose that any value</div>
<div>that defaults to any SI unit should allow SI multipliers.<br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
And the wiki could also state that a space is required
between the numeric values and the units, if any.<br>
This is the case for all other units so the convention
should be held.<br>
</blockquote>
<div><br>
</div>
<div>It is certainly desirable that a space be there (in
non-monospaced fonts, a good typographer</div>
<div>would insert a thin space rather than a full space, this
does conform to SI requirements for</div>
<div>spacing). However, people are fallible and may omit the
space for many reasons (didn't</div>
<div>read the documentation, typo, etc.). It would be nice if
editors (at a minimum, it could be</div>
<div> applied to other steps in the chain too) applied
Postel's robustness principle: "Be conservative</div>
<div> in what you send, be liberal in what you accept." I.e.,
an editor would allow a user to enter</div>
<div> "7kW" but would upload it as "7 kW." Some editors
already strip superfluous spaces from</div>
<div>values (of any kind) so this would not be a drastic break
from what they currently do.</div>
</div>
</div>
</blockquote>
+1<br>
<br>
<p><br>
</p>
</body>
</html>