[Tagging] Feature Proposal - Voting - maxspeed:variable=*

Kieron Thwaites kieron.thwaites at gmail.com
Tue Aug 25 06:04:07 UTC 2015


A while ago, I came across the maxspeed:variable=* tag, to specify if
a highway's maximum speed could be further reduced using dynamic speed
indication.  This was proposed back in 2012 as an alternative to
maxspeed=signals; the main rationale being that maxspeed=signals does
not convey any information regarding the actual maximum speed, which
can affect routing decisions, speed warnings and the like.

The original proposal can be found at:

The proposal process was initiated on October 20th, 2012, and from the
talk page history (and the archives of this mailing list), many
suggestions and improvements were discussed and merged into the
proposal.  However, the original user behind the proposal (Eckhart
W├Ârner) appears to be no longer active, and the proposal has remained
dormant in the RFC stage.

However, it appears that this proposal has gained widespread usage and
acceptance.  Some examples that I've encountered:

- taginfo counts 7,748 objects tagged with maxspeed:variable=*,
compared with 5,444 objects tagged with maxspeed=signals.
- There is editor support: JOSM's "maxspeed" plugin displays a dashed
line on ways tagged with maxspeed:variable=* (though JOSM itself does
not have a preset for maxspeed:variable=*)
- The ITO "Speed limits fixup" map [http://www.itoworld.com/map/125]
recommends using maxspeed:variable=* over maxspeed=signals, despite
the former still lingering in the RFC stage.

Given the above, I would like to take the initiative and open the
voting process for this proposal.  Should voting fail, I am prepared
to manage a second round of RFC.


More information about the Tagging mailing list