You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 5, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: docs/source/tour_planning.rst
-116Lines changed: 0 additions & 116 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,119 +12,3 @@ The HERE Tour Planning API supports the following use cases:
12
12
- Heterogeneous or mixed fleet VRP: Tour Planning API supports routing multiple types of vehicles with different gas mileage, cost of driving, capacity, and more. For example, your fleet can include passenger vehicles and even specialized trucks with fridges in one route.
13
13
- Pick up and delivery vehicle routing problem: With Tour Planning API, you can schedule a vehicle to pick up and deliver an item in one route.
14
14
- Vehicle routing problem with priorities: Do you have jobs that must be served, such as today, and others that could also be delayed until, such as until tomorrow, and ideally you would like to prevent those priority jobs from being skipped in cases where fleet capacity or shift durations do not allow to serve all jobs, but at the same time you would like to serve as many non-priority jobs as possible? With Tour Planning API, you can define jobs to be with high priority internally the algorithms will try to avoid skipping those high priority jobs and will skip low priority jobs first in scenarios where it is impossible to serve all jobs due to constraints. The priority of a job does not imply its order in the route, as in the position of a high priority job might be anywhere in the route and not necessarily before lower priority jobs.
15
-
16
-
17
-
Example
18
-
-------
19
-
20
-
.. jupyter-execute::
21
-
22
-
import os
23
-
24
-
from here_location_services import LS
25
-
from here_location_services.config.tour_planning_config import (
26
-
VEHICLE_MODE,
27
-
Fleet,
28
-
Job,
29
-
JobPlaces,
30
-
Plan,
31
-
Relation,
32
-
VehicleProfile,
33
-
VehicleType,
34
-
)
35
-
LS_API_KEY = os.environ.get("LS_API_KEY") # Get API KEY from environment.
fleet :class:`Fleet <here_location_services.config.tour_planning_config.Fleet>` A fleet represented by various vehicle types for serving jobs.
125
-
plan :class:`Plan <here_location_services.config.tour_planning_config.Plan>` Represents the list of jobs to be served.
126
-
id string optional A unique identifier of an entity. Avoid referencing any confidential or personal information as part of the Id.
127
-
optimization_traffic string optional "liveOrHistorical" "historicalOnly" "automatic" Specifies what kind of traffic information should be considered for routing
128
-
optimization_waiting_time Dict optional Configures departure time optimization which tries to adapt the starting time of the tour in order to reduce waiting time as a consequence of a vehicle arriving at a stop before the starting time of the time window defined for serving the job.
129
-
is_async bool optional Solves the problem Asynchronously
0 commit comments