[OSM-dev] One value per key? Why not one pair per object?

Jochen Topf jochen at remote.org
Tue Feb 3 17:24:08 GMT 2009

On Mon, Feb 02, 2009 at 03:25:57AM +0100, Stefan de Konink wrote:
> What is the motivation to go to the one value per key thing again. 

Practically everything we have been doing with OSM tags until now has
assumed that keys are unique. Nearly all the software I have seen (like
editors, renderers, etc.) treat keys as if they are unique. Yes, some
things could maybe be cooler if we allow multiple keys, but the reality
is that basically every mapper out there and most of the software assumes
they are unique. By making them really unique we just enforce this now
and turn flaky software into solid software without much work. :-)

For years now we had the option of using multiple tags with the same
key, but didn't. From a practical standpoint I don't see how this would
change. Why would suddenly everybody change over the software to cope
with multiple tags with the same keys. So if thats not going to happen
anyway, why not acknowledge that by making keys actually unique?

Jochen Topf  jochen at remote.org  http://www.remote.org/jochen/  +49-721-388298

More information about the dev mailing list