On Thu, Jun 04, 2009 at 08:45:20AM +0100, Peter Miller wrote:
I have been looking at the coverage of maxspeed limit data for highways
in the UK and we seem to have a right mix of styles.
Here is the data for bug chunk of England while avoiding including
anything from France or Ireland
Peter Miller wrote:
Any suggestion on what we should recommend for the UK? I guess the USA
should also be party to this discussion but they have far less
population of the maxspeed field (only 70 uses in the Bay area) so
possibly we should come to a view first. Our options seem to be:-
I have been looking at the coverage of maxspeed limit data for
highways in the UK and we seem to have a right mix of styles.
Here is the data for bug chunk of England while avoiding including
anything from France or Ireland (which would include km/hour figure).
We current have over
Peter wrote:
Any suggestion on what we should recommend for the UK?
Either of:
maxspeed=30mph (the user should strip a trailing mph to find the
value)
maxspeed=30 mph (the user should strip the last word if it is mph
including the space)
The maplint validation uses a regular expression which
, 4 Jun 2009 08:45:20 +0100
From: Peter Miller peter.mil...@itoworld.com
Subject: [Talk-GB] maxspeed field - what units should we use. etc
I have been looking at the coverage of maxspeed limit data for
highways in the UK and we seem to have a right mix of styles.
Here is the data for bug chunk
I tag what I see. I see 30
which implies 30mph, so I tag 30mph. The units differentiate it from
km/h. Another mapper in this area (East Yorkshire) has tagged
some in km/h with 2dp. Ulf then went over all of these and stripped
the decimals off. As I encounter them I change them to imperial
I'd vote for 30mph (no space), and locally (Oxford) we'll hopefully have
cause to be using maxspeed=20mph for quite a lot of residentials, quite
soon...
It should be the digits on the sign. There might be a case for a different
tag (maxspeedmph=30, say), but maxspeed=30mph is just as good.
2009/6/4 Peter Miller peter.mil...@itoworld.com:
I have been looking at the coverage of maxspeed limit data for highways in
the UK and we seem to have a right mix of styles.
Here is the data for bug chunk of England while avoiding including anything
from France or Ireland (which would include
There is no right answer. If you tag things 40mph (which is what I do,
like most of the other people who've replied) then you may well find
that someone else goes round systematically changing them to km/h and
puts in maxspeed:mph - that's what's happened to most of the ones I've
done. I think
I think a rude email to the talk list describing the bot and asking for
someone to fess up to it would be appropriate.
If someone is correctly tagging as per the wiki, why does anyone think a bot
is tolerable? This is exactly the sort of thing that puts people off
participating in the project.
I propose that we adopt a new key: maxspeed_mph
It would be
- simpler for UK, USA and other imperial countries to enter the speed.
- less prone to error - users may not be used to kph speeds.
- un-ambiguous. (what does '50' mean?)
- maxspeed keeps consistently metric units (kph)
- exact -
2009/6/4 WessexMario wessexmario-...@yahoo.co.uk:
I propose that we adopt a new key: maxspeed_mph
It exists: maxspeed:mph
Problems I'll do inline:
It would be
- simpler for UK, USA and other imperial countries to enter the speed.
- less prone to error - users may not be used to kph
Robert Naylor wrote:
On Thu, 04 Jun 2009 11:13:28 +0100, David Earl
da...@frankieandshadow.com wrote:
I also came across someone tagging maxpeed=NSL yesterday. If it gives
someone happiness, fine, but I don't really think it should be necessary
to tag the default situation, only when
FWIW highway code conversions are:
20mph = 32
30mph = 48
40mph = 64
50mph = 80
60mph = 96
70mph = 112
Ah - which differs from what is posted on roads out of ports:
http://wiki.openstreetmap.org/wiki/Image:MaxSpeedConversionHarwich.jpg
(60mph = 95km/h, 70mph=110km/h, and it looks like I
you only need 5dp to get an exact mph-kph conversion anyway :-)
I think that's the big issue.
People won't be able to agree on whether we should enter 0, 2,3 or 5 decimal
places, if anyone can remember or look them up correctly. And it's completely
unintuitive thinking of speed limits with
2009/6/4 WessexMario wessexmario-...@yahoo.co.uk
you only need 5dp to get an exact mph-kph conversion anyway :-)
I think that's the big issue.
People won't be able to agree on whether we should enter 0, 2,3 or 5
decimal
places,
Personally I think it should be to 1 decimal place ;)
2009/6/4 WessexMario wessexmario-...@yahoo.co.uk
I propose that we adopt a new key: maxspeed_mph
If we have maxspeed_mph, I would be far happier seeing.
maxspeed:mph
maxspeed:km/h
I don't like the idea of maxspeed and maxspeed_mph, we'll almost certainly
find things defaulting to maxspeed,
On 04/06/2009 12:48, WessexMario wrote:
Isn't all this already specified?
The trouble is tag specifications count for very little in OSM, as
people ignore them because they think they have a better way of doing
it, or when they make a mistake, or just on a whim. They're conventions
not
On 4 Jun 2009, at 12:48, WessexMario wrote:
Isn't all this already specified?
http://wiki.openstreetmap.org/wiki/Key:maxspeed
If your country uses kilometers tag the value without unit!
If your country still uses miles tag the value and append mph OR
convert to the EXACT kilometers per
On Thu, Jun 4, 2009 at 11:13 AM, David Earl da...@frankieandshadow.com wrote:
you may well find
that someone else goes round systematically changing them to km/h and
puts in maxspeed:mph - that's what's happened to most of the ones I've
done.
Call them out publicly. This kind of thing is a
Very helpful. And to be clear is says their should be a space between
the number and the unit, ie '50 mph' not '50mph'.
I wouldn't get too concerned about the space, computers can handle that well,
so
an optional whitespace should be allowable.
So. are we reaching a point where we
2009/6/4 WessexMario wessexmario-...@yahoo.co.uk:
Very helpful. And to be clear is says their should be a space between
the number and the unit, ie '50 mph' not '50mph'.
I wouldn't get too concerned about the space, computers can handle that well,
so
an optional whitespace should be
if a bot can do it then there's no reason the data consumers can't do
it too without the bot.
If you don't have a good reason to change something just leave it be.
Or alternatively, why not just run the bot on the copy of the data at the input
to the renderer*, rather than on the database
Adding another log to the fire...
Is there a case for specifying knots in the same way as mph for
waterway
tags?
Maplint validation already allows this (maxspeed=10knots for
example, with or without a space)
Ed
___
Talk-GB mailing list
Robert Naylor wrote:
On Thu, 04 Jun 2009 11:13:28 +0100, David Earl
da...@frankieandshadow.com wrote:
I also came across someone tagging maxpeed=NSL yesterday. If it gives
someone happiness, fine, but I don't really think it should be
necessary
to tag the default situation,
There is a major problem with using maxspeed=NSL.
Dual Carriageways.
How will the applications know that a way is part of a dual
carriageway
or is just one oneway way that happens to be near another
oneway way?
http://wiki.openstreetmap.org/wiki/Relations/Proposed/Dual_carriagew
ays
If
On 4 Jun 2009, at 17:11, WessexMario wrote:
Robert Naylor wrote:
On Thu, 04 Jun 2009 11:13:28 +0100, David Earl
da...@frankieandshadow.com wrote:
I also came across someone tagging maxpeed=NSL yesterday. If it
gives
someone happiness, fine, but I don't really think it should be
27 matches
Mail list logo
