2009/6/4 WessexMario <[email protected]>: > 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-ambiguous. (what does '50' mean?) all can be fixed by supplying units "mph". > > - maxspeed keeps consistently metric units (kph) > > - exact - being in the local units, no rounding necessary (no decimal > places). you only need 5dp to get an exact mph->kph conversion anyway :-) > > - value will usually only be an integer in a multiple of 10 or 5. - easy > to validate. except in windsor great park where the speed limit is 38mph. People have a tendency to round anyway, so it probably doesn't tell you much. > > - both maxspeed and maxspeed_mph keys could be entered - no ambiguity again except if they happen to be different speeds maxspeed:mph=30 maxspeed=96... what do I do? > > - applications can easily convert between maxspeed and maxspeed_mph > where only one is entered as they can if there's a unit > > - in transition, having a separate key would make it simple for > validators (people and computers) or a batch process, to convert > existing maxspeed keys in the UK and USA from the various existing > maxspeed variations to the expected multiples of 10 in maxspeed_mph we've already got a fricking bot doing that and it's pissing people off. Dave _______________________________________________ Talk-GB mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-gb
