CHANGELOG
Added
- Details of the territory optimization service.
- Introduced new constraints:
order_dependency
promptness
vehicle_attribute
vehicle_attribute_distribution
vehicle_attribute_duration_distribution
vehicle_balance
visit_range_across_shifts
- Documented "easter egg" parameters which output debugging information. These parameters can be searched for using the phrase "FOR DEBUGGING".
- Unlimited mixing of vehicle types is supported. For example, one vehicle object can have a
"type": "car"
and another vehicle object can be"type": "truck"
and so on. - Additional truck parameters:
num_trailers
weight_per_axle
.
- Where relevant, parameters now have
default
,minimum
, andmaximum
. - OpenAPI Specification validators now included in pre-publication to ensure standardization followed.
Added
- Documented the
shift_duration_sum
constraint - Documented the
visit_same_location
constraint - Documented the
max_flights
constraint - Added values for default constraint values when a request is sent without a
constraints
object
Changed
- Updated
max_distance
docs to indicate0
baseline is equivalent to minimizing distance travel - Corrected docs to indicate URLs expect one of
/sync
or/async
- Clarified
sources
anddestinations
usage in matrix documentation - Clarified
shifts
description in routing - Corrected
volume
andweight
descriptions initem
object to indicate arbitrary units - Updated description of
priority
andurgency
inorder
object - Updated
directions
description to reflect richness of response
Added
- Published a "coverage status" map per country based on random matrix and routing tests
- Added a strict, finite request/response data retention policy of maximum 90 days
Changed
- Improved driving directions for mainland China
- Fixed bug related to floating breaks some times not being honored
- Improved handling of
null
values in request and updated to a meaningful error message.
Added
- Routing optimization requests can now contain multiple vehicles of
type: "truck"
each with different parameters, e.g.,height
,weight
,volume_capacity
, etc. The routes for each truck are guaranteed to be compliant for that truck's parameters. - Standardized the expression of driving directions and polylines across all regions, including China and Japan.
- Verbose driving directions included for all
routing
responses.
Added
-
Addition of a
work_speed
parameter to theshift
object which controls the speed of work at an order. This parameter helps account for historical variations of technicians work speed versus the baseline duration one expects to complete an order.The default value is one (1). When set to a value other than 1, the
duration
at anyorder_id
serviced during theshift
is longer/shorter than the statedduration
of the order. For example,"work speed": 1.2
results in the order taking 20% longer to complete. -
Additional info incorporated into the response for problems involving drop-offs. Each stop in the
route
object'sstops
array now includes an array oforder_ids_dropped_off
. -
New constraints to handle appointments:
scheduled_appointment_shift
scheduled_appointment_vehicle
-
New constraints for problems involving drop-offs:
journey_time
additional_journey_time
dropoff_deadline
Changed
- Minor bugfixes in lesser used constraints involving journey time
- In
visit_gap
constraint, time intervals expressed via seconds as well as days by usingmin_seconds
andmax_seconds
to express desired visit spacing. Previously allowed onlymin_days
andmax_days
.
Added
- Documentation for existing constraints shown in examples but not explicitly noted in technical documentation.
Removed
- Removed
num_visits
constraint since it is redundant with thevisit_range
constraint.
Added
- New Max_Commute constraint added to handle first and last legs of routes
- Optional rounding_minutes added to the round start of service events to nearest k minutes
- For matrix calls with no path between source/end locations, added count and warning message to response
Changed
- Updated worldwide map with latest street network and traffic data
- A more cost-effective and efficient method of traffic window interpolation and storage
- Improved error checking for errors in input requests (e.g., empty orders, invalid parameters)
- Improved handling of complex pickup/delivery/-drop-off/replenishment problems
- Improved handling of truck routing with changes to underlying map service
- For cases of non-obvious input in routing JSON, changed HTTP return code from 409 to 422
- Bug fixed in output JSON for items_delivered and items_picked up in pickup/delivery problems
Changed
- Enforce the requirement that all vehicles with type truck have identical dimensions. Previously, the routing endpoint in the Optimization API accepted mixed dimension fleets; Now, the routing endpoint in the Optimization API responds with an error.
Added
- Enforce requirement that all vehicles in a problem be the same type vehicle, i.e., do not allow the mixed fleet problem.
- Submitting a request with an empty vehicle array now results in an error response.
Changed
- Updated the behavior of the Visit Sequence constraint.
- Solutions are now deterministic for repeatable behavior.
Added
- Forced route structures are now supported
Added
-
A constraint for limiting distance traveled from a home location.
-
A constraint for handling orders at the same physical location, e.g., apartment buildings.
-
Handling of hard, soft, and floating breaks.
-
A constraint for handling orders at the same physical location, e.g., apartment buildings.
-
Handling of hard, soft, and floating breaks.
Added
- Initial major release of all functionality.