Difference between revisions of "Segment length"
(→Too long: copied from https://wiki.waze.com/wiki/index.php?title=User:Voludu2/Segment_length&oldid=143464 as per https://www.waze.com/forum/viewtopic.php?f=1464&t=188716&p=1429349#p1429349)
m (1 revision imported: Second import of transfer package)
Revision as of 21:37, 15 February 2017
When creating a segment, it is important to ensure that any individual segment is at least 5 m (16 feet). It is less important to keep segments under any particular length, but there are drawbacks to long segments discussed below.
When a segment is less than 5 m (16 feet) 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.
There may be times when driveways or other roads join a main road with close proximity to each other. This may cause small segments to be created between the two junctions along that main road. If the segment is shorter than 5 m (16 feet), it may be best to simply merge the two intersections into a single junction. It is OK if the joining roads in the map do not exactly align with the visual map in the Waze Map Editor.
See the Junction Style Guide section on offset roads for more details about this situation.
Segments longer than about 100km cannot be saved. In addition, there are several good reasons to keep segments shorter than 10km (though they should still not have unnecessary junctions):
- 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 screen.
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 meters. The length does not appear before it is saved.
Fixing 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 the minimum length and still meet the needs of the original purpose.