(Redirected from Minimum segment length)
When creating a segment, it is important to ensure that any individual segment is at least 19.69 ft (6 m). It is less important to keep segments under any particular length, but there are drawbacks to long segments discussed below.
Determine the length
The length of a segment can be determined after it is created and saved by selecting it and looking at the general tab with the segment selected. The length will be displayed toward the bottom of the tab in feet or miles (using the imperial unit setting in WME) or meters or kilometers (using the metric unit setting in WME). The length does not appear before it is saved.
|The displayed length for both imperial and metric settings is based on a rounded metric number and does not reflect the actual segment length. However, a developer in the Waze editing community has developed a script called WME True Segment Length. This script will display the true length of the segment in both metric and imperial units with two decimal places of accuracy. Unfortunately, that display is not really important since the server only considers the rounded metric values.|
When a segment is less than 19.69 ft (6 m) it becomes difficult for the navigation engine to determine traffic speed through that segment. That will in turn negatively affect drive time estimations and best routing.
See the Junction Style Guide section on offset roads for more details about this situation.
Necessary short segments
There are a few instances where a single short segment may be present between two other segments with no other segments at those junctions. Sometimes these junctions are necessary and should not be removed. These include:
- Loop roads. A single segment cannot loop back upon itself, so a junction is required to create two separate segments. It does not matter where the junction is located, so long as each segment meets the minimum segment length. Some roads have two separate segments that share the same start and end junctions creating two alternate paths between them. These configurations cause routing problems and require one of the two segments to have a 2-segment junction. More details are covered in Junction Style Guide on Loops.
- Ramp or freeway splits. There are cases where a freeway may split into two separate freeways. In order to provide navigation to drivers, it may be necessary to create short segments on the freeway to show the two different road names at the split. Under certain situations it may be best to make the segments as short as possible, so long as each segment meets the minimum segment length. This is covered in detail in the Junction Style Guide.
- Long segments. Segments are best kept under a certain distance.
- Segment Property Change. When a segment property changes between intersections, a two-segment junction may be required:
- Road, city, or state name change. When the road, city, or state name changes between intersections, add a junction so the segments on either side may have a different name.
- Elevation Change. When elevation changes at complex interchanges, a junction can be added to introduce an elevation change.
- Speed Limit Change. When the speed limit changes between intersections, add a junction so the segments on either side may have a different speed limit.
In the above cases, the segment is necessary so it cannot be deleted, but it can be made at least the minimum length and still meet the needs of the original purpose.
Segments longer than about 62 miles (100 km) cannot be saved. In addition, there are several good reasons to keep segments shorter than 6.2 miles (10 km):
- Long roadways or railroads with the city name present will cause a smudged city issue on the city layer.
- Long segments require more resources in the client and WME to render on the screen.