Module: Google::Cloud::Optimization::V1::SkippedShipment::Reason::Code

Defined in:
proto_docs/google/cloud/optimization/v1/fleet_routing.rb

Overview

Code identifying the reason type. The order here is meaningless. In particular, it gives no indication of whether a given reason will appear before another in the solution, if both apply.

Constant Summary collapse

CODE_UNSPECIFIED =

This should never be used. If we are unable to understand why a shipment was skipped, we simply return an empty set of reasons.

0
NO_VEHICLE =

There is no vehicle in the model making all shipments infeasible.

1
DEMAND_EXCEEDS_VEHICLE_CAPACITY =

The demand of the shipment exceeds a vehicle's capacity for some capacity types, one of which is example_exceeded_capacity_type.

2
CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DISTANCE_LIMIT =

The minimum distance necessary to perform this shipment, i.e. from the vehicle's start_location to the shipment's pickup and/or delivery locations and to the vehicle's end location exceeds the vehicle's route_distance_limit.

Note that for this computation we use the geodesic distances.

3
CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DURATION_LIMIT =

The minimum time necessary to perform this shipment, including travel time, wait time and service time exceeds the vehicle's route_duration_limit.

Note: travel time is computed in the best-case scenario, namely as geodesic distance x 36 m/s (roughly 130 km/hour).

4
CANNOT_BE_PERFORMED_WITHIN_VEHICLE_TRAVEL_DURATION_LIMIT =

Same as above but we only compare minimum travel time and the vehicle's travel_duration_limit.

5
CANNOT_BE_PERFORMED_WITHIN_VEHICLE_TIME_WINDOWS =

The vehicle cannot perform this shipment in the best-case scenario (see CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DURATION_LIMIT for time computation) if it starts at its earliest start time: the total time would make the vehicle end after its latest end time.

6
VEHICLE_NOT_ALLOWED =

The allowed_vehicle_indices field of the shipment is not empty and this vehicle does not belong to it.

7