Talk:Tag:man made=bridge

From OpenStreetMap Wiki
Jump to: navigation, search

New proposal for multi-level bridges and objects on bridges

I think this can be done much easier, without the relation and quite robust: Proposed features/Simplify man made=bridge mapping RicoZ (talk) 14:56, 20 June 2015 (UTC)

Covered=* under man_made bridge?

Discussion over at Talk:Key:covered#What_to_do_with_building.3Droof.3F.--Jojo4u (talk) 14:28, 4 October 2015 (UTC)

"Outline"=supported structure

In Stuttgart there is a unusual foot/bicycle bridge with a wide steel net supporting the path. The type is called "Seilnetzbrücke" by Structurae with only 3 worldwide and no one of the same design (OSM, Structurae). The steel net is very wide and should not be tagged man_made=bridge in my opinion. man_made=bridge should outline the the supported structure of the bridge.

Example: The Millennium Bridge in London does not include the supporting structure (OSM, Wikipedia).--Jojo4u (talk) 11:37, 25 October 2015 (UTC)

Would man_made=canopy be a good fit for this ? Somewhat described here building=roof. RicoZ (talk) 09:36, 9 June 2016 (UTC)

Ways below bridges as tunnels

Should ways that run below a man_made=bridge area be applied the tunnel=yes key? --Absay (talk) 06:19, 25 February 2017 (UTC)

No, use either tunnel or bridge. --geozeisig (talk) 06:34, 25 February 2017 (UTC)

Why not, when layer is correctly tagged

Many people like to use tunnel and bridge together or asked for covered. Why? They want the carto give transparant and dashed lines under the man_made=bridge to the way.
I read: Do not connect the ways running under the bridge to the outline. ([[1]])

The solution could be, to do so.
When man-made=bridge is tagged correctly, layer=1 and the underneath way is attached to the man_made=bridge, outline, this way does not have a layer, the render could calculate the length from the connecting points and make the underneath way dashed and transparent. I see this as a solution for a problem, that keeps coming up every time again.
There is a relation between the underneath way and the bridge.

Routing: with a connecting point to the outline, the underneath way, could give a hint like 500 meter go under the bridge.
Maxheight: could be set to the correct point. On node not a layer tag or lower then the bridge layer tag.

When I think about it this is also for the waterway line possible.
What are the disadvantage for connecting?

For me, this visualisation problem must be solved, but how? Can we do it this way?--AllroadsNL (talk) 07:54, 10 October 2018 (UTC)

You could indeed use "covered" for the way bellow a bridge. However, the rendering problem you mention is just a rendering problem and a renderer can fix it without changing the way it is mapped, in fact I suspect some renderers and other tools might break if we change it that way. As man_made=bridge is a bit new it may take renderers some time to figure out the optimal rendering, did you look at the bug trackers of the various renderers?
The answer to the philosophical question - why the ways are not connected in OSM - is because OSM considers bridges and the objects bellow them completely independent and the connection would break that assumption. This is often not a good model of reality but mostly works. RicoZ (talk) 21:33, 18 October 2018 (UTC)

man_made=bridge on small bridges

man_made=bridge is also useful with small bridges!
It give visual, the width of the bridge.
You could even calculate the width of the bridge.
A advise not to do so, is not correct!
People should decide by themselves, what they tag.
In the Netherlands we could import all the bridges from Government Data.
This gives a better topographic effect, then the route line sideline, it depends where you use it for.
--AllroadsNL (talk) 18:35, 30 November 2018 (UTC)

I suggest using the Key:width tag and a renderer which will render the bridge and adjoining roads/paths according to the given value instead. --Hjart (talk) 19:09, 30 November 2018 (UTC)
"Please note that this construction for simple bridges (mapped by a single way only) in most cases is overkill." This advice is wrong, it not a overkill. I would suggest delete it. People should make their own decision to do so. If people do not want it, do not render it.--AllroadsNL (talk) 19:31, 30 November 2018 (UTC)
The Key:bridge tag with most simple bridges & most renderers gives all the visuals you really need. I just think some mappers are really taking the man_made=bridge construction way too far. I think it should be either one or the other. --Hjart (talk) 20:06, 30 November 2018 (UTC)
"it should be either one or the other" why? Mateusz Konieczny (talk) 20:43, 30 November 2018 (UTC)
"The intended use of this tag is with complex bridges" was claimed in one of edit description. I want to say that restricting it to solely large bridges was not my intention (I initiated voting for proposal for this feature and was first to add rendering of this feature to a popular map style). If you are aware of consensus that really small bridges must not be tagged this way please link me to a discussion on this Wiki or to tagging mailing list Mateusz Konieczny (talk) 20:48, 30 November 2018 (UTC)
See https://wiki.openstreetmap.org/wiki/Proposed_features/man_made%3Dbridge#One_way.2C_one_level - proposal explicitly described this case. Marking area of smaller bridges is described as "It is possible but usually not necessary to specify the outline in this case.". And if anything changed then it went toward mapping also smaller and smaller bridges with man_made=bridge , not forbidding it Mateusz Konieczny (talk) 20:52, 30 November 2018 (UTC)
Please note that my sentence does not explicitly forbid anything, but merely notices that it (in maybe somewhat stronger language) is not necessary. I have until quite recently not seen it used with smaller bridges in the areas I watch (Denmark) and so far I'm definitely not a fan of it being used everywhere. --Hjart (talk) 21:19, 30 November 2018 (UTC)