On 10 Oct 2008, at 14:27, Chris Hill wrote:
Dermot McNally wrote:2008/10/10 Chris Hill <[EMAIL PROTECTED]>:Conversions to 0dp is inaccurate, accurate conversions are a mess,namespacing allows for conflicting values so only an optional suffix reallymakes sense, so this why I use.Well, maxspeed:mph would also work for your purposes. The only difference is that you have chosen to silently ignore the behaviour documented in Map Features. I'm not convinced by your point about conflicts - in a world where a single field can have, essentially, different data types in it, I think we've already sacrificed any pretence of orderliness. Dermotmaxspeed:mph only conforms to map features because Shaun amended it earlier today!!!!! [listens for the sound of the voting request email to arrive - hears nothing]
In my opinion the voting process is broken, as it can potentially vote in proposals that will break backwards compatibility and require extensively more complex processing of the data. Take for example:
http://wiki.openstreetmap.org/index.php/Proposed_features/Status(I'm wondering if there is a station out there that has all the railway=platforms mapped, rather than just placing a footpath to the railway=station node.)
Shaun
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
