Expand description
The messages and enums that are part of this client library.
Modules§
- async_
model_ metadata - Defines additional types related to AsyncModelMetadata.
- batch_
optimize_ tours_ request - Defines additional types related to BatchOptimizeToursRequest.
- break_
rule - Defines additional types related to BreakRule.
- injected_
solution_ constraint - Defines additional types related to InjectedSolutionConstraint.
- input_
config - Defines additional types related to InputConfig.
- optimize_
tours_ request - Defines additional types related to OptimizeToursRequest.
- optimize_
tours_ response - Defines additional types related to OptimizeToursResponse.
- optimize_
tours_ validation_ error - Defines additional types related to OptimizeToursValidationError.
- output_
config - Defines additional types related to OutputConfig.
- shipment
- Defines additional types related to Shipment.
- shipment_
model - Defines additional types related to ShipmentModel.
- shipment_
route - Defines additional types related to ShipmentRoute.
- shipment_
type_ incompatibility - Defines additional types related to ShipmentTypeIncompatibility.
- shipment_
type_ requirement - Defines additional types related to ShipmentTypeRequirement.
- skipped_
shipment - Defines additional types related to SkippedShipment.
- vehicle
- Defines additional types related to Vehicle.
- waypoint
- Defines additional types related to Waypoint.
Structs§
- Aggregated
Metrics - Aggregated metrics for ShipmentRoute (resp. for OptimizeToursResponse over all Transition and/or Visit (resp. over all ShipmentRoute) elements.
- Async
Model Metadata - The long running operation metadata for async model related methods.
- Batch
Optimize Tours Request - Request to batch optimize tours as an asynchronous operation.
Each input file should contain one
OptimizeToursRequest, and each output file will contain oneOptimizeToursResponse. The request contains information to read/write and parse the files. All the input and output files should be under the same project. - Batch
Optimize Tours Response - Response to a
BatchOptimizeToursRequest. This is returned in the LRO Operation after the operation is complete. - Break
Rule - Rules to generate time breaks for a vehicle (e.g. lunch breaks). A break is a contiguous period of time during which the vehicle remains idle at its current position and cannot perform any visit. A break may occur:
- Capacity
Quantity Deprecated - Deprecated: Use Vehicle.LoadLimit.Interval instead.
- Capacity
Quantity Interval Deprecated - Deprecated: Use Vehicle.LoadLimit.Interval instead.
- Distance
Limit - A limit defining a maximum distance which can be traveled. It can be either hard or soft.
- GcsDestination
- The Google Cloud Storage location where the output file will be written to.
- GcsSource
- The Google Cloud Storage location where the input file will be read from.
- Injected
Solution Constraint - Solution injected in the request including information about which visits must be constrained and how they must be constrained.
- Input
Config - The desired input location information.
- Location
- Encapsulates a location (a geographic point, and an optional heading).
- Optimize
Tours Request - Request to be given to a tour optimization solver which defines the shipment model to solve as well as optimization parameters.
- Optimize
Tours Response - Response after solving a tour optimization problem containing the routes followed by each vehicle, the shipments which have been skipped and the overall cost of the solution.
- Optimize
Tours Validation Error - Describes an error encountered when validating an
OptimizeToursRequest. - Output
Config - The desired output location.
- Route
Modifiers - Encapsulates a set of optional conditions to satisfy when calculating
vehicle routes. This is similar to
RouteModifiersin the Google Maps Platform API; see: https://developers.google.com/maps/documentation/routes/reference/rest/v2/RouteModifiers. - Shipment
- The shipment of a single item, from one of its pickups to one of its deliveries. For the shipment to be considered as performed, a unique vehicle must visit one of its pickup locations (and decrease its spare capacities accordingly), then visit one of its delivery locations later on (and therefore re-increase its spare capacities accordingly).
- Shipment
Model - A shipment model contains a set of shipments which must be performed by a set of vehicles, while minimizing the overall cost, which is the sum of:
- Shipment
Route - A vehicle’s route can be decomposed, along the time axis, like this (we assume there are n visits):
- Shipment
Type Incompatibility - Specifies incompatibilties between shipments depending on their shipment_type. The appearance of incompatible shipments on the same route is restricted based on the incompatibility mode.
- Shipment
Type Requirement - Specifies requirements between shipments based on their shipment_type. The specifics of the requirement are defined by the requirement mode.
- Skipped
Shipment - Specifies details of unperformed shipments in a solution. For trivial cases and/or if we are able to identify the cause for skipping, we report the reason here.
- Time
Window - Time windows constrain the time of an event, such as the arrival time at a visit, or the start and end time of a vehicle.
- Transition
Attributes - Specifies attributes of transitions between two consecutive visits on a
route. Several
TransitionAttributesmay apply to the same transition: in that case, all extra costs add up and the strictest constraint or limit applies (following natural “AND” semantics). - Vehicle
- Models a vehicle in a shipment problem. Solving a shipment problem will
build a route starting from
start_locationand ending atend_locationfor this vehicle. A route is a sequence of visits (seeShipmentRoute). - Waypoint
- Encapsulates a waypoint. Waypoints mark arrival and departure locations of VisitRequests, and start and end locations of Vehicles.
Enums§
- Data
Format - Data formats for input and output files.