Routing to matching Alternative Street names: verschil tussen versies Geschiedenis weergeven

Geen bewerkingssamenvatting
(Marked this version for translation)
Regel 2: Regel 2:
<languages /><translate>
<languages /><translate>


==Routing to matching Alternative Street names==
==Routing to matching Alternative Street names== <!--T:1-->
Incorrect [[Routing|routing]] to addresses matching Alternative [[Street and City names|Street names]]. This issue occurs when closeby another street exists with as alternative name the same name.<br />
Incorrect [[Routing|routing]] to addresses matching Alternative [[Street and City names|Street names]]. This issue occurs when closeby another street exists with as alternative name the same name.<br />
<br />
<br />

Versie van 16 aug 2018 22:46

Andere talen:

Routing to matching Alternative Street names

Incorrect routing to addresses matching Alternative Street names. This issue occurs when closeby another street exists with as alternative name the same name.

Example

Destination IJzerlaan 38, Antwerpen

The main road is N1-IJzerlaan, alternative name IJzerlaan.
North of the canal lies a street with the name IJzerlaan.

If the entered destination of a house number or Residential Place lies on the main road, the app will indicate the endpoint in a correctly but the routing leads to the road named IJzerlaan, north of the canal.

Solution

This issue can be prevented by adding a RPP with a “Entry-/exit- point”.


Without the Entry/exit point the routing passes the destination, while with the Entry/exit point the routing delivers the Waze at the correct location.

Without Entry/exit point With Entry/exit point
Without Entry/exit point With Entry/exit point

Main Page | Index