Entry point logic

Entry point logica

Routing without an entry point: The default logic

The Waze routing server follows a complex, multi-step filtering process for destinations without a defined entry point. This means the server doesn’t route directly to segments like ramps or tunnels. Instead, it routes drivers to a nearby standard road. This was designed primarily to prevent drivers being routed to potentially hazardous or inaccessible locations.

Here’s how the routing server works when a venue has no defined entry point:

Identify segments: The server looks for all road segments within a certain radius of the venue’s coordinates
Sort segments: It then sorts these segments by distance
Apply filters: The server then applies a series of filters to this list:

• Filter out undesirable road types, like freeways and ramps
• Filter out segments with undesirable road attributes, like tunnels
• Filter out segments separated from the venue by geographical barriers, like rivers

Choose destination:

• If the filtered list is not empty, the system chooses the closest segment as the destination for the final route
• If the filtered list is empty, the system ignores all filters and routes to the single closest drivable segment, regardless of its type.

While this approach is well-intentioned, it can sometimes lead to situations where drivers miss legitimate stops (such as a bus station located on a ramp) and are occasionally directed to a less optimal or incorrect location.

Routing with an entry point: The entry point logic

This logic gives you, as editors, more control by introducing the concept of a “high-confidence indication.” If a venue has a defined entry point, it provides a signal to the routing server to bypass the default filtering process. This means that Waze will now route directly to destinations on segments like ramps, tunnels, and other previously less preferred types when an entry point is set there. For example, if a bus station is located on a ramp, adding an entry point will ensure Waze routes a driver directly to that spot instead of the nearby road.

As a result, we can now reflect real-world mapping more precisely and help drivers reach their exact destinations. This change empowers you to use your judgment when setting a correct and safe entry point.

What if there’s no entry point?

If a venue has no defined entry point, the logic remains the same as before: Waze will revert to its previous filtering process to find the closest drivable segment.

Routing guidelines

Here’s a breakdown of the recommended action for each segment type.

Segment type / attribute	Should I add an Entry point
Freeway	yes
Ramp	yes
Tunnel	yes
Parking Lot Road	yes
Private road	yes
Narrow street	yes
Street through a Major Highway	yes
Unpaved road	yes
Off-road	no
Pedestrian Boardwalk	no
Stairway	no
Railroad	no
Walking trail	Depends
Ferry	Depends

Key exceptions

To help you avoid common mistakes, here are some exceptions to keep in mind.

The “Ferry” exception

Waze handles ferries differently depending on the region:

Ferries aren’t a preferred route, but are considered a valid destination. If a venue is located on a ferry, editors in regions where they’re considered valid destinations can use an entry point to route to them. We recommend using good judgment when deciding whether to route to ferries.

Walking trails (Routable pedestrian paths)

The routing logic for walking trails depends on whether an entry point is added:

• Without an entry point: If there’s a drivable segment within 20 meters, Waze will route to that drivable segment
• With an entry point: Waze will route to the nearest node instead of the same drivable segment, even if that node is farther away
  

Due to this unique behavior, we recommend using caution when deciding whether to set entry points on walking trail segments.

Segments to avoid

The segments below are not meant for driving, so it’s highly recommended that you never set an entry point on them:

• Off-road / Not maintained
• Pedestrian boardwalk
• Stairway
• Railroad

Why avoid these segments?

Setting an entry point on a non-drivable segment creates unnecessary, incorrect data on the map. Even though the system protects the user from a routing error, adding an entry point to these segments provides no routing value.

What happens if an entry point is accidentally set on these segments?

If an entry point is placed on a non-drivable segment, the routing system will ignore the entry point entirely. The logic reverts to the default behavior: Waze will route the user to the closest point on the nearest drivable segment, as if the entry point didn’t exist.

Ongoing work

This routing enhancement has been recently deployed to production across all environments. We’re happy to share that the primary use cases have been successfully tested and verified.

While we’ve confirmed this new logic works for the most common scenarios, we’re still testing the behavior of complex cases. We’ll provide an update when more information is available.

Your continued efforts in mapping and providing feedback are what make these improvements possible, and we’re excited for the positive impact this change will have on the Waze driving experience.

This text is based on Discuss on Entry-point-logic.

Hoofdpagina | Index