Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
en:sidebar:remoteapi:apiref:order:optimize [07/05/2020 14:01]
shmi [Optimize order execution]
en:sidebar:remoteapi:apiref:order:optimize [07/05/2020 14:02]
shmi [Parameters]
Line 61: Line 61:
 | priority | order of orders: {unit index:​{order index:​expected index of order in a route}} (index equal to -1 will fix this order as last in a route)| | priority | order of orders: {unit index:​{order index:​expected index of order in a route}} (index equal to -1 will fix this order as last in a route)|
 | criterions | route completion criterions: \\ max_mileage - maximum mileage, m;\\ max_duration - maximum duration, sec;\\ max_order_count - maximum orders count;\\ max_idling - maximum idle time between orders, sec;\\ split_intervals - if 1, then split based on intervals \\ (if the execution time of the order with unloading and moving, misses the next order time interval) | | criterions | route completion criterions: \\ max_mileage - maximum mileage, m;\\ max_duration - maximum duration, sec;\\ max_order_count - maximum orders count;\\ max_idling - maximum idle time between orders, sec;\\ split_intervals - if 1, then split based on intervals \\ (if the execution time of the order with unloading and moving, misses the next order time interval) |
-| preference | order priority in route |+| preference | DEPRECATED: ​order priority in route |
 :!: JSON format is the same as in [[update]] request. :!: JSON format is the same as in [[update]] request.
  
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2024 Gurtam