A path is a map object that represents a sequence of connected, routable segments. It provides the informative functions of a junction box without the enhanced data collection and routing control functions. In simple terms, a path tells the routing server, “although this segment is not directly connected to this other segment, it should be treated as if it is when giving turn information to drivers.” It cannot tell the routing server, “Go this way”, but rather, “If you go this way, here’s how that should be presented to drivers.”
Paths and junction box connections are also known as far turns in parts of the WME interface; just as a normal turn crosses one node to another segment, a far turn crosses multiple nodes and intermediate segment(s) to another segment.
Paths are also known as far lanes phase 2 (FL2), because they were developed primarily to enable better lane guidance. They are not the same as far lanes; they merely enable far lanes to be added to turns outside of junction boxes. They are also useful for customized turn instructions.
Overview
Paths were derived from junction boxes, and it helps to be familiar with junction boxes when working with paths. Anyone who has worked with junction boxes may notice that a path looks exactly like a junction box connection, only without the box that it goes through. Like junction box connections, paths:
- Support custom far turn instructions and TTS.
- Support far turn voice prompts.
- Support far lane guidance.
- Are limited to 16 connections through a single node. (As of March 2023[update] WME says the limit is 32 connections, but it is still 16; this is a bug).
Unlike junction box connections, paths:
- Can be nested one inside another, with different entering segments, different exiting segments, or both.
- Do not prevent the cutting or merging of their entry or exit segments (As of March 2023[update] rank 4 and 5 editors encounter permission errors when doing this; staff have confirmed that this is a bug and that paths are designed to allow cutting and merging of any segment).
- Cannot affect routing.
- Cannot be restricted, NO RTC possible
- Cannot be marked as difficult turns.
- Do not collect speed data separate from the segments that comprise them.
- Need not fit within a 0.01° by 0.01° bounding box, the roughly 1 km size limit of junction boxes.
- Cannot start and end at the same segment.
- Have different route switching behavior (see Switch Route for further details).