drop rendering of bridge/tunnel/oneway = true/1

[Klumbumbus]

Currently elemstyles.mapcss is often written like way[bridge?]{} So it also renders for bridge=true and bridge=1. I think this is bad tagging because only "yes" should be used. Same for tunnel, oneway, noexit, motorroad, area, ford,... I would change this to way[bridge=yes]{}. Same for the other keys. I would create the diff file, if it gets accepted. I just want to ask before I do the work.

[Don-vip]

I agree this is bad tagging but I don't think this is worth the trouble.

[naoliv]

It should not be dropped at the rendering, but fixed in the data itself.
Or, if you like, have another validator rule for these values (which could also include a fix for true|1 → yes)

[Don-vip]

There is no added value in changing the rendering, let's keep it as it is.
I checked the numbers of *=true, this tag is already very uncommon, and does not need a specific test neither.

[Klumbumbus]

In 8137/josm:

fix #10346 - drop rendering of bridge/tunnel/noexit/motorroad = true/1, add validator warning for oneway=1

[Klumbumbus]

Only some minor changes.

[stoecker]

Replying to Don-vip:

I checked the numbers of *=true, this tag is already very uncommon, and does not need a specific test neither.

I'm happy that I succeeded here. It was my decision that I don't like multiple boolean values and JOSM should only produce yes and no whenever possible. :-) JOSM has influence!

[aceman]

Replying to Klumbumbus:

Currently elemstyles.mapcss is often written like way[bridge?]{} So it also renders for bridge=true and bridge=1. I think this is bad tagging because only "yes" should be used.

You mean bridge=yes and bridge=<some of the different types of bridge> is to be supported.

[Klumbumbus]

Replying to aceman:

You mean bridge=yes and bridge=<some of the different types of bridge> is to be supported.

Yes, see ​http://josm.openstreetmap.de/browser/josm/trunk/styles/standard/elemstyles.mapcss#L111 for supportet values.