Road Aspects/en

Segment Properties

Properties relevant for most Road typesː

Address

See the page on Street and City names.

Road type

See the page on Road types.

Road details

Unpaved road
Check the Unpaved road attribute for every road that is drivable by a normal car and that is not paved.
The app has a setting for whether or not to use Unpaved roads. By default, this is set to "Don't allow." Other possible values ​​are "Allow" and "Avoid long stretches (> +/- 400m)." For the penalty, see the Routing page.
Only in the exceptional case that an unpaved road is only drivable by a 4x4 and really should be on the map, choose the Off-road road type.

Adjacent to HOV/bus lane
Select this attribute for a segment if it is directly adjacent to a carpool or bus lane. Do not use this attribute on the carpool or bus lane segments themselves.

Checking this feature will take GPS deviations into account when calculating the arrival time. GPS deviation can cause speed information to be assigned to the wrong (adjacent) segment.

"Headlights required"
In the Waze app, the "headlights warning" is displayed every time a route starts that passes a segment with "Low headlights required" checked. This warning is only useful in the few countries for which it was developed. It is best to leave this feature unchecked.

Routing

With this road segment attribute, you can increase (preferred) or decrease (unfavored) the importance of a road type in the routing. Neutral is the standard setting. For example: a positive mH behaves like a MH and a negative mH behaves like a PS. The effective locking changes accordingly. Do not use without consulting a CM.

Restrictions

See the page on Restrictions.

Direction

The ends of a segment are indicated by an A and B node. Choose two way, A -> B or B -> A.

Speed limit

See the page on Speed limit.

Average Speed Cameras

Check on all road segments where average speed cameras are operational the Average Speed Camera check boxes. If a ASC zone starts or ends in the middle of an existing (longer) segment, you may have to add a new node (by splitting the segment), to get the ASC notifications to start / end at the correct locations. If the start/end is approximately 20m from an existing node, this is not necessary.

If the cameras are already placed but not yet operational use dummy camera's.

Currently , due to a bug, a Average speed control should always start at the A point of a segment. In case of a two way average speed control it may be necessary to split a segment in two parts, change the A and B points of the newly created segment with as result that from both ways the average speed control can be defined on a segment starting with an A point. The A-point triggers the warning message.

Lock

See the page on Locks.

Elevation

See the page on Elevation.

Add house numbers

See the page on House numbers.

Aspects

• Page on Road shield.
• Page on Tunnel.
• Page on Lane Guidance.
• Page on New Housing Development.
• Page on Nodes, segment nodes.
• Page on Segments.
• Page on Junction Arrows
• Page on Junction Box

Keep It Simple/Stupid (KISS)

"As simple as possible, as complex as necessary"

KISS means keeping the road geometry as simple as possible without losing the essential information needed for navigation instructions. For more information, see the page about KISS.

Filter lanes

Filter lanes are not mapped as separate segments but can be configured as Lane Guidance.

Filter lanes, as separate segments, don't fit the KISS principle because they are the cause of very complex situations that are hard to manage, while they don't add a lot of value in most routing instructions. Short segments and extra splits can have a negative influence on routing (extra penalty, incorrect average speeds, ...).

Of course, there is always an exception. If the choice of a filter lane must be made more than 50 meter before coming to the crossing AND the main road and filter lane are divided by obstacles (concrete blocks, ...), it should be mapped.

Splitting roads

The standard representation for any roadway is a single 2-way segment, even if the physical roadway is divided.

A road may be divided when the GPS tracks show two clearly definable flows at the 100m 500ft zoom level.

There are a few extra considerations when the road has possible destinations / addresses.

A street with physical separated lanes with addresses/destinations - fi. with parking in between, separated by a ditch, strips of grass or bushes or an other obstacle - can be drawn in different ways. Most important consideration when choosing: the best navigation to, if possible, the front door of your destination.

Two possibilities:

• Separate 1-way traffic segments with connecting roads in between.
• 2-way traffic segments with U-turn arrows on green at the connecting roads. (The KISS variant)

Considerations to consider when choosing between both variants:

Separated 1-way traffic segments
Advantage: map image in the app corresponds to reality.
Disadvantage: crowded map image in app and WME, (too) little space for the connecting roads due to the minimum segment length of 6 meters, U- turn prevention can occur with higher road types.

KISS variant
Advantage: clear, uncluttered map image in the app and WME, no problems with U-turn prevention.
Disadvantage: map image deviates from the street image, editing is more difficult, green U-turn arrows can mislead editors. Navigation to destination without taking into account any difficulties in reaching the front door of your destination due to a blocking lane divider.

Also important when choosing an option is:

• does it matter which side to come from?
• can I still get to my destination from the side where I arrive? Or do I first have to cross fences / roadsides / ditches?

If so, split away. If not, then do not split. Because why be sent all the way around the block while you can just drive straight there.

How to divide

• Note how the 2-way segment currently is connected to the connecting segments. Which incoming/outgoing traffic movements are possible.
• Cut the 2-way segment into two parts and separate them.
• Make both segments 1-way traffic.
• Extend both segments so that they are parallel to each other.
• Connect both segments to the surrounding segments, as noted in the first step.

See also this video How to divide a two-way- road.

Merge two 1-way traffic segments

Merging two 1-way traffic segments into one 2-way traffic segment is only possible if both segments have the same name, type, maximum speed and locking level.

Merging a road split in two 1-way traffic to one 2-way traffic segment is best done like this:

• Select both 1-way traffic segments to merge.
• Change the selected segments to 2-way traffic.
• Detach both selected segments on one side. One segment on one side, the other on the other.
• Bring the loose ends of both segments together and connect them.
• Delete the now created connection node.
• Move the new 2-way traffic segment in the middle of the road.
• Check the arrows of all incoming and outgoing directions
• Now set the stop point / segment marker of any house numbers correctly.

Roundabouts

If you want to add a Roundabout, you firstly draw the roads as a normal crossroad, but don't connect the roads/segments. Secondly you draw the Roundabout and WME will connect the crossing roads automatically.

A Roundabout must always get a city name but never a streetname. The reason for this has to do with the navigation instructions and road announcements. A Roundabout always gets categorized as the type of the highest connected road.

See the Roundabout page.

Secundaire wegen

Een weg direct naast een doorgaande weg, bedoeld voor plaatselijk verkeer tekenen we alleen in wanneer deze weg meer verkeer kent dan af en toe een tractor. Check de GPS-sporen. Teken alleen de doorgangen tussen de secundaire weg en de doorgaande weg in op plaatsen waar er een mogelijke bestemming aan de secundaire weg ligt.

• Voorkom zo nodig U-bocht preventie via a mDL

Shopping streets

Shopping streets only allowed for pedestrians (and cyclists) with the exception of certain hours loading/unloading, are defined as Private Roads.

Two left turns or two right turns (Median U-turn penalty)

The Waze routing algorithm prevents routes with two consecutive left or right turns (U-turns) by applying a high median U-turn penalty.
This penalty is applied directionally and only applies in the direction of travel A → B → C when all of the following conditions are met:
1. Three segments
The U-turn consists of a reversal of direction via three segments: the inbound segment (A), a connecting segment (B), and the outbound segment (C).
2. Short connecting segment
The connecting segment (B) is 15 meters or shorter.
3. In/Out Parallelism
The incoming and outgoing segments (A and C) are parallel to each other within an angle of ±5°. If the connecting segment is not straight, the angle is determined as if A and C were connected by an imaginary straight segment.
4. Road Type Condition (Directional)
The incoming segment (A) is not one of the following road types: Street (ST), Parking Lot Road (PLR), Private road (PR), Narrow Street (NS), or 4x4. If segment A does have one of the above road types, the median U-turn penalty will not be applied, even if all other conditions are met.

Example / see picture: Driving from left to right on the top street (A) with destination towards the west requires a reversal of driving direction. When the median segment B (red arrow) is 15 meters or less the app will navigate over the lower street towards the west. Only if this median segment is 16 meters or more the app will navigate over the bigger road in the middle (C).

Hoofdpagina | Index