If segment properties match as described above, a small black bridge icon will appear above where the two segments meet, as shown below.Ĭlick the bridge icon and three things happen: The first step is to select two adjacent segments of what is to become the bridge or overpass. Road type, directionality, locked and separating line settings do not matter. The attributes which need to match are country, state (applicable countries only), city, and street name. Before you will be allowed to bridge, several properties of the segments to be bridged must be identical. This same is true of both sides of this interstate.īridging works on only two segments at a time. This ensures that the Waze problem detection system doesn't flag the spot where two segments overlap as a location where a junction might be needed.įirst, in this view, you can see that there is a junction between the interstate freeway and an overpass. When two segments overlap, the value of Elevation for each segment must be different. By default, the Elevation of a segment is "Ground" (equivalent to zero). Waze has a value called Elevation which is assigned to every segment. How overlapping roads are defined in Waze This is where the Elevation value assigned to a segment and the Bridge function comes to the rescue. So that the Waze routing servers understand the reality that an overpass doesn't intersect with the freeway, or an urban bridge doesn't intersect the streets of a neighborhood below, a map editor needs to be able to separate the roadways in an efficient manner.
Overpass bridge driver#
In these situations, it has happened that Waze would request that a driver turn while on a bridge to get to the interstate freeway below. This can lead to incorrect and even dangerous navigation instructions. In unedited areas where the map is pretty raw from its import from public sources, all roads tend to be set to the same height with junctions between roads at different levels, such as overpasses and the freeways which pass under them.
0 kommentar(er)
