controlklion.blogg.se - Overpass bridge

The way in which individual spans are supported is often of mapping interest. The portion of a bridge between two of its supports is known as a span. An embankment should not have a layer tag in most cases. The bridge should either end before the junction (the normal situation) or in cases where the junction is actually 'in mid air' itself then the other ways joining the junction should also be made into bridges for the relevant sections.Ī ramp at an end of a bridge is not part of the bridge and can be tagged as embankment=*. It is good practice to not let a bridge terminate at a road junction or similar. Split the upper way at each end of the bridge (which is where it joins solid ground) and add bridge= yes to the central section.

2.1 Bridges with several roads/ways or additional features.

Notice that the outline can be also mapped but with a different main tag man_made= bridge and that, in this case, bridge=* can also be used as a secondary tag to give the type of the bridge. The functional description can be complete with additional tags such as bridge:movable=* and the physical aspects of the constrution with bridge:structure=* and bridge:support=*. But both options should not be used at the same time (a bridge tag for the upper way and a tunnel for the lower way for the same crossing). It is sometime, however, a matter of judgment as to whether to tag a particular situation using a bridge or a tunnel.

See the detail of the known types below.īridge or tunnel? Where the lower feature is surrounded by earth then the lower feature should probably be tagged using tunnel=* instead. The value of the key is used to indicate the type of the bridge. It can be combined with several types of ways such as roads, railways, path canals, pipelines or similar.

The key bridge=* is a property to describe that a way is on a bridge. Showing a bridge incorrectly meeting a non-bridge at a junction (left), and terminated early (right).