<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 12/04/2011 09:38, Peter Miller wrote:
<blockquote
cite="mid:BANLkTimNF5iDutY5jGdKcbpnOQqxKu7Wog@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On 11 April 2011 23:39, SomeoneElse <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:lists@mail.atownsend.org.uk">lists@mail.atownsend.org.uk</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"> <br>
We've lost the information that the sign is actually NOT a
60 mph sign. Something like method 2 above would have
avoided losing information (although "GB:rural" is
meaningless; if pushed, "GB:national" or some variant would
be better).<br>
</div>
</blockquote>
<div><br>
The general conclusion of the discussion above was that where
maxspeed=60mph is applied to a single carriageway road there
is also a default 'maxspeed:type=GB:unrestricted' (or whatever
value is decided on). </div>
</div>
</blockquote>
<br>
Really? Perhaps we were reading different discussions, but what I
saw were:<br>
<br>
o People saying "national != 60 mph"<br>
<br>
o People saying "don't make it harder for the mapper"<br>
<br>
I'm guessing that you prefer a single numeric speed limit because it
makes things easier to parse by e.g. the ITO World maxspeed layer,
but surely changing the data to match the application is the wrong
way around?<br>
<br>
I don't mind you always ensuring that maxspeed is numeric, provided
that information isn't lost in the process - so if you complete your
edits to indicate that, despite what the maxspeed tag is set to, the
speed limit sign actually says "national", I wouldn't object.<br>
<br>
<blockquote
cite="mid:BANLkTimNF5iDutY5jGdKcbpnOQqxKu7Wog@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div>This default (and the one for 70mph for motorways and
dual-carriageways) was including to avoid burdening the mapper
with another tag to add in most situations. The only 60 mph
signs that need another tag are those rare cases where a
single carriageway road does have a numeric speed limit.<br>
</div>
</div>
</blockquote>
<br>
If you choose to change where I've mapped to "maxspeed=national" to
"maxspeed=60 mph; and some other tags to indicate that it is
actually national" that's not a burden to me in the slightest! I
can still map "maxspeed=what_the_sign_says" as I have been doing.<br>
<br>
Cheers,<br>
Andy<br>
<br>
</body>
</html>