> From: Peter Miller
> Incidentally, I was speaking to a senior professional person from the
> South West a few days ago who was aware that OSM had just mapped MK
> and was wishing that something similar could happen where he was. I
> suggested that all he had to do was ask, be nice and of
On 4 Jun 2009, at 17:11, WessexMario wrote:
> Robert Naylor wrote:
On Thu, 04 Jun 2009 11:13:28 +0100, David Earl
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
>>
Peter Miller writes:
> 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).
> 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
I
Robert Naylor wrote:
>>> On Thu, 04 Jun 2009 11:13:28 +0100, David Earl
>>> 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, on
> 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
Talk-G
On 4 Jun 2009, at 15:01, Andy Allan wrote:
> Out of interest, how much would one of these tenders go for i.e. how
> much do people pay in the "real world" for this kind of thing? Are we
> talking £500, £50,000, £250,000?
>
No idea, but the tender process must have significant costs associated
It appears to be a suburb of Hastings - I couldn't find separate
population data for it just now. Wikipedia thinks the full name is correct.
David
On 04/06/2009 14:56, Shaun McDonald wrote:
> It took me a while to find, as I was searching for:
> St Leonards-on-Sea
> However (assuming I've found
Out of interest, how much would one of these tenders go for i.e. how
much do people pay in the "real world" for this kind of thing? Are we
talking £500, £50,000, £250,000?
Cheers,
Andy
On Thu, Jun 4, 2009 at 2:15 PM, Peter Miller wrote:
>
> The DfT have just published a contract out for the coll
It took me a while to find, as I was searching for:
St Leonards-on-Sea
However (assuming I've found the right place) it appears to be in the
data under just:
St Leonards
http://www.openstreetmap.org/browse/node/356906703
So, which is correct?
Map location:
http://www.openstreetmap.org/?lat=50
>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 its
The DfT have just published a contract out for the collection and
management of cycle data for St Leonards on Sea
"Lot 1. Cycle data collection. Undertaking cycle surveys to extend the
Ordnance Survey Integrated Transport Network to include information
about existing cycling infrastructure
2009/6/4 WessexMario :
>
>> 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. 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 s
On Thu, Jun 4, 2009 at 11:13 AM, David Earl 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 PITA, and we need to
make
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 kilom
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 specif
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 hour value! "
which is specified below to 5dp.
On Thu, 04 Jun 2009 11:55:06 +0100, Tom Hughes wrote:
> Robert Naylor wrote:
>> On Thu, 04 Jun 2009 11:13:28 +0100, David Earl
>> 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
>>> necess
2009/6/4 WessexMario
> 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, when it should be maxspeed
2009/6/4 WessexMario
>
> > 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 ;)
__
> 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
> 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
On 04/06/2009 11:55, Tom Hughes wrote:
> Robert Naylor wrote:
>> On Thu, 04 Jun 2009 11:13:28 +0100, David Earl
>> 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 defau
Robert Naylor wrote:
> On Thu, 04 Jun 2009 11:13:28 +0100, David Earl
> 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 there is an exception
2009/6/4 WessexMario :
> 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 speeds.
>
> - un-ambiguou
On Thu, 04 Jun 2009 11:13:28 +0100, David Earl
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 there is an exception to the
> general rule
If the
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 - b
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.
Ri
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
2009/6/4 Peter Miller :
>
> 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
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.
Richar
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
Hi
I think the principle of keeping it easy for the mapper should apply. In
the UK, speeds are signed in mph, and most mappers will think in mph, so
let's record speeds in mph. Anything else leads to confusion, conversions,
varying degrees of accuracy. But to my mind, the worst result is the
in
I think we should tag what's on the signs ie. mph, as a conversion to kmh is
error prone even without the rounding issues. I've tagged my local roads as
maxspeed=20mph|30mph|etc
Any application parsing maxspeed values needs to validate the data anyway
because like all our data the field could
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
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 17,000
37 matches
Mail list logo