only numeric values are allowed for maxspeed. So I removed
some maxspeed=no at the A555 near Colonge.
The effect of the tag was the motorway disappearing from
the AllInOne Garmin map......
Comment from TomH on 28 May 2009 at 21:46
I think you'll find there's no such thing as an "allowed" or "not allowed" value for a tag - we're not proscriptive about such things.
Comment from Tordanik on 28 May 2009 at 23:11
How about fixing the bug in that Garmin map conversion instead? There is no such thing as "allowed" tags in OSM, so applications have to be able to deal with unknown tags.
Comment from Richard on 29 May 2009 at 06:48
Alphanumeric tags are very common in maxspeed, anyhow. It's the convention in the UK to tag as (say) maxspeed=30mph.
Comment from grenzdebil_bonn on 30 May 2009 at 12:05
Hi! Please revert this edit! maxspeed=no(ne) is absolutely common and there is a difference between this and a road without a maxspeed tag.
Comment from chris66 on 31 May 2009 at 15:01
The voting for maxspeed=no/none was REJECTED :
@grenzdebil: with the same argument I could map not existing highways
with highway=no. Doesn't make too much sense.
Comment from grenzdebil_bonn on 1 June 2009 at 19:54
@Chris66: no. maxspeed=* refers to the maxspeed rule applying to some section of a road - and this is exactly what was tagged here in the first place. If you don't like it, please come up with some other way of tagging "no speed limit applying here" before deleting other people's work.
The new Version of the Garmin map in question works with maxspeed=no, by the way.
Comment from grenzdebil_bonn on 1 June 2009 at 19:55