(Created page with "{{TopLine}} <languages /><translate> ==Creating Routing to matching Alternative Street names== Incorrect routing to addresses matching Alternative Street and City names|Str...") |
Geen bewerkingssamenvatting |
||
| Regel 2: | Regel 2: | ||
<languages /><translate> | <languages /><translate> | ||
== | ==Routing to matching Alternative Street names== | ||
Incorrect 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 /> | ||
Example: Destination IJzerlaan 38, Antwerpen<br /> | Example: Destination IJzerlaan 38, Antwerpen<br /> | ||
Versie van 16 aug 2018 21:48
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”.