Page 1 of 1

UTURN MALUS / uTurnCost (for J.M.)

Posted: Wed Oct 31, 2018 11:25 am
by Bernd Welter
Hi there,

a colleague asked me for a sample dealing with the UTURN MALUS.

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<Profile>
	<Routing majorVersion="2" minorVersion="0">
		<Course>
			<Maneuver considerTurningBans="true" uTurnCost="0"/>
		</Course>
	</Routing>
</Profile>
The challenge is to find a valid input scenario for this. This example shows equal waypoints but different settings for the malus value.
Mercator<br />Start = 936611,95 // 6269768,08<br />Dest = 936620 // 6269686<br />Both waypoints linked via AUTO_LINKING<br />The left track performs a large detour just to avoid the UTURN manoeuvre.<br />In the right track the UTURN is possible (it's price was set to 0) and the overall distance is shorter
Mercator
Start = 936611,95 // 6269768,08
Dest = 936620 // 6269686
Both waypoints linked via AUTO_LINKING
The left track performs a large detour just to avoid the UTURN manoeuvre.
In the right track the UTURN is possible (it's price was set to 0) and the overall distance is shorter
Our parameter “uTurnCost” only applies on segments where the turn happens on the segment itself (single segment sided…).
Bigger (two segment sided) streets do not cause UTURN.

There’s a high probability for such a UTURN in the environment of turning restrictions.
The UTURN COST has been implemented to avoid such driving behaviours.
This manoeuvre is not seen as a UTURN because the street consists of two separate lanes.
This manoeuvre is not seen as a UTURN because the street consists of two separate lanes.
Best regards,
Bernd