[OSM-talk] Map Features, maxspeed and maplint

[Mark Williams]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dermot McNally wrote:
> 2008/10/5 Ed Loach <ed at loach.me.uk>:
> 
>> 30mph. If we had stayed with assumed country-specific units then the tagging
>> would have been more consistent, easier for the user to tag, and not require
>> a conversion to a random number of decimal places.
> 
> I'm not a fan of the options that include suffixes or other tricks to
> imply units. That said, even that approach is better than using
> country-specific units, because it's a huge burden on applications to
> work out what country a restriction falls within (twofold, since the
> border data is often imprecise too). Consider the Irish border, which
> is also an imperial/metric border. Yuck!
> 
> A further drawback with the approach is the assumption that units stay
> uniform within a particular country. But in the UK, it's getting
> common for height restrictions to be stated in dual units. So for
> transitional cases like that, the country-specific model breaks down.
> 
> I'm with Shaun on the namespacing thing. Allowing fields like maxspeed
> to contain normalised, pure numeric data is beneficial for fast data
> extraction, and the namespaced approach allows for automatic updating
> of the "real|" numeric field.
> 
> Dermot

Maybe <grin> this is calling out for a 'bot approach, to take
maxspeed:mph & add a numeric maxspeed, to check out maxspeed=30's & mark
them in some way (restricted to UK, obviously), and to check for entries
of both=30 & fix them?

Note: I haven't said "I'll do it" because I know I'd be shot...

I think a lot of people have refrained from using these tags where the
speed limit is what you'd expect, so residential defaults to 30mph,
trunk to 70, etc & tagging it is not required - so any bot approach
should respect that.

+1 on the namespace; I'm not generally keen on it, but here it makes
sense. Either the way mentioned, or maxspeed:en as per name:en for
consistency?

Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI6/LZJfMmcSPNh94RAijGAJ9M/dxPTjuPkCsUNgkbMhs9sFLupwCePQsZ
oQltkcfxNEHS9tLSEfMxtfI=
=JYyp
-----END PGP SIGNATURE-----