A bridge place is used to represent a named bridge with local or navigational significance. With more than 600,000 bridges in the US, these guidelines are in place to prevent app clutter from polygons, labels, and search results of bridges with little to no significance for navigation.
Bridge places serve as a routing destination and/or a landmark in the app. As a destination, these place allows users to navigate to a bridge for purposes such as visiting a pedestrian accessible bridge, driving to the designated viewing area of a non-accessible bridge, or adding the bridge as a stop during navigation to get a preferred route. As a landmark, a bridge place is represented by a label and polygon on the map to help users orient themselves.
Bridges should be added as area places. The geometry of the polygon should be limited to the area of the bridge span(s) and, for multi-span bridges, care should be taken not to cover any significant open area between spans. This prevents the area place layer from covering portions of other map layers between the spans in the app.
Given their height above ground level, bridges are subject to parallax on aerial imagery. This may cause the bridge to appear shifted, curved, and/or wavy in WME imagery compared to its actual position. To resolve this issue, a bridge place should be drawn offset from its position on the imagery to match the segments that cross the bridge when available (see more about segments below).
If the bridge is an active road bridge, use the street name and city of the segments crossing the bridge with no HN. If the segments on the bridge are divided and labelled for each direction, the street name should not include the ordinal direction.
Non-road bridges that are destinations should have their address set to their main entry point. If a non-road bridge is added purely as a landmark and/or would not be navigated to (e.g., active railroad bridge with no designated viewing area), do not add a street or HN in the address category.
When a bridge crosses two or more city names within a state:
- If the segments share a common street (primary or alternate), select that street name and check the none box for city
- If the segments do not share a common street (primary or alternate), check the none box for street and city
If a bridges crosses state or country borders, select the state that encompasses a majority of the bridge or consider mapping two area places in their respective state and/or country.
This should be an official or locally-used name, preferably signed at each approach. Do not map unnamed bridges signed only for the feature they cross or the name of the road that crosses the bridge, unless this is an official name of the bridge. Bridge areas may also be used to add a signed or known commemorative name that is different than a bridge name which is used in the street name.
In addition to bridge, add any categories relevant to the bridge as a destination. These may include categories such as Tourist Attraction/Historic Site, Scenic Lookout/Viewpoint, Park, etc. Do not add additional categories to bridges that serve only as a landmark.
|As of April 2021, Multiple Entry Points (MEPs) are only used in the iOS (Apple) version of the Waze app, and not used by the Android app. When adding entry points, keep in mind that production Android users are routed only to the originally created entry point.|
Entry points should be added according to the navigation needs of the bridge place:
- As a destination
- If a bridge has (a) parking area(s) for pedestrian access near the approach for the bridge and on the same road, they should be set as an entry points and named accordingly.
- If a bridge does not have pedestrian access but has a nearby lot designated for viewing, the entry point should be set to that lot
- If a bridge is added purely as a landmark, do not add an entry point unless it is necessary to prevent undesirable routing (e.g., routing to a nearby private driveway).
- As a routing aid
- For single span with an undivded road, add a single entry point that allows a route to come from either direction. If the bridge already has a destination entry point near the approach to one or both sides of the bridge, this point does not need to be added.
- For a single span with divided roads or multi-span bridges, an entry point should be added at the entrance of the bridge from each direction to allow routing from the selected direction.
Completed bridge places should be locked to at least 2, though regional guidance may suggest a higher level based on road type, landmark importance, etc.
Segments Crossing Bridges
The addition of/edits to a bridge place may also require edits to the segments utilizing the bridge, given the association of their geometry, names, and navigation purposes.
Like the geometry of the bridge place, bridge segments are subject to parallax and the resulting offset can be significant enough to disrupt the app's snapping algorithms. Segments should be adjusted to compensate for this shift by using the GPS points layer or allowed GIS sources to align the segment to its real-world position.
*Currently under construction
Names of non-drivable segments that cross a bridge should follow their standard naming conventions, including no name if applicable.
Segment elevation should be set to regional elevation guidance.
Examples (screenshots and explanations later)
- Bridge place versus no bridge place
- Meridian Bridge - Old bridge (bridge place) next to modern, unnamed US-81 bridge (no bridge place)
- Bridge with destination entry point(s)