Hi All – I’m struggling with a particular uturn and I think I must be doing something wrong, either on the configuration side or the request side. I’m making a request with the route API with the points:
# [lat, lon]
points = [[25.128716, 55.416487], [25.124923, 55.415341], [25.122013, 55.411738]]
This gives a route which includes a uturn:
I’d like to make it so that this request doesn’t result in a uturn but instead results in a route like this:
I’m on v10.2 and I’m using the following config
profiles:
- name: car
turn_costs:
u_turn_costs: 1200
sharp_left_turn_costs: 1200
sharp_right_turn_costs: 1200
vehicle_types: [motorcar, motor_vehicle]
custom_model_files: [car.json]
profiles_lm:
graph.encoded_values: car_access, car_average_speed, orientation
prepare.min_network_size: 200
prepare.subnetworks.threads: 1
routing.non_ch.max_waypoint_distance: 1000000
graph.dataaccess.default_type: RAM_STORE
When I make a request I’ve tried using various combinations of the following options (note here the points are listed in [lon, lat])
request_data = {
“points”: [[55.416487, 25.128716], [55.415341, 25.124923], [55.411738, 25.122013]],
“profile”: “car”,
“locale”: “en”,
“instructions”: True,
“calc_points”: calc_points,
“points_encoded”: points_encoded,
“pass_through”: [False, True, False],
“heading_penalty”: 10000,
“ch.disable”: True,
“debug”: True,
“heading”: [168, 276, 240],
}
However none seem to eliminate that uturn. If anyone knows how to fix this / what I’m doing incorrectly, I’d really appreciate the help.