[OSM-talk] [tagging] Feature Proposal - RFC - waterways/ditch
osm.list at randomjunk.co.uk
Tue Sep 2 10:08:11 BST 2008
On Mon, Sep 1, 2008 at 10:46 PM, Andy Robinson (blackadder-lists)
<ajrlists at googlemail.com> wrote:
> spaetz wrote:
>>Sent: 01 September 2008 7:50 PM
>>To: talk at openstreetmap.org
>>Subject: Re: [OSM-talk] [tagging] Feature Proposal - RFC - waterways/ditch
>>On Mon, Sep 01, 2008 at 07:25:12PM +0100, Tristan Scott wrote:
>>> surely width=0.254 given width is defined as being in metres?
>>says who? I use meter as I live in continental Europe.
>>But if I lived in the UK I would surely tag speelimits as
>>maxspeed:mph=50 (or maxspeed=50mph) and not as some weird converted number.
>>Fun if your Garmin tells you: "the maximum speed here is
>>49.8789598 mph". If renderers couldn't cope (not that they care about
>>maxspeed) I would consider it a fault of the renderer or of the
>>preprocessor they are using to parse the planet file.
>>wasn't the motto, "tag the world as it is"? well if speedlimit is 50mph,
>>then it is 50 mph
I think we had this discussion before and came to the conclusion that:
- 50mph was essentially mapping a sign, because the speed limit is a
speed, not a unit, but it's quite understandable people doing it
because that's what they see
- that the tag without a unit should probably be assumed to be km/h.
Especially as that's what map features has said for ages. Obviously if
the tag has units you should use it or ignore the value if you don't
- that anything intelligent enough to know if it wants to represent
maxspeeds in mph/kph is intelligent enough to know it can safely round
to the nearest integer.
- and that it's possible to represent an exact mph in kph anyway if
you can really be bothered: 1mile == 1.609344km exactly
More information about the talk