|man_made = bridge|
|The outline of a bridge, grouping together all features for that bridge.|
|Used on these elements|
|Tools for this tag|
The tag man_made=bridge is used to tag a bridge defined by the outline of the bridge. It is suitable to group together all ways running over that bridge and for holding descriptive tags for that bridge.
Draw the outline of the bridge as area and apply man_made=bridge and layer=* to it. The outline should encompass the continous structure of the bridge. Cables and pylons beside the bridge are tagged with bridge:support=*.
Attributes of the bridge itself should be added to the outline. The key bridge=* can be used to indicate the type of the bridge. Add the name of the bridge to the outline and the name of the roads to the ways running over the bridge.
Ways across the bridge should be tagged with the same values of layer=* and bridge=* as the outline. Where the ways cross the outline they should be connected to it with a shared node. Do not connect the ways running under the bridge to the outline.
Proposed: The load-bearing architecture of individual bridge spans can be tagged with bridge:support=*. For a bridge with more than one type of span in its length, the outline can be split at the support where the type of span changes and each piece tagged with a different value.
Bridges with more than one level
The same as before but the key layer=* should now contain the lowest number of all the features on the bridge. To group together all features of the bridge the proposed relation bridge is now used and the outline tagged with man_made=bridge is added as outline-member to that Relation of the bridge itself should be added to the relation.
A new (alternative) proposal to map multi-level bridges using level=* and location=bridge is described in Proposed features/Simplify man made=bridge mapping#Multi-level bridges
Objects and features on bridges
See proposal objects on bridges.
One way, one level
It is possible but usually not necessary to specify the outline in this case. One possible reason would be the ability to specify the name of the bridge and of the road separately.
Two ways, one level
A bridge represented by two OSM ways, both of them at the same level. The ways are tagged with bridge=yes and layer=1. The outline is drawn and tagged with man_made=bridge and layer=1. The OSM ways are connected to the outline.
If the bridge has a specific name it would be added to the outline.
Multiple ways, two levels
A large bridge with two carriage ways and a cycleway running below those. For better visibility only a part of the bridge is shown and the outline is displayed as a red-dashed line.
The OSM ways of the roads are tagged with bridge=yes and layer=2. The cycleway is tagged with bridge=yes and layer=1. The outline is drawn and tagged with man_made=bridge and layer=1. The proposed relation bridge is used to combine all features together and the OSM way of the outline is added as the outline-member to the relation.
The name of the bridge would be added to the relation.
- Approved proposal
- Proposed relation for bridges and tunnels
- New proposal to refine some aspects of man_made=bridge
- Discussion on the tagging mailing list: Part 1 and part 2