Download the PHP package detrack/elasticroute without Composer

ElasticRoute for PHP

With effect from 02 January 2021, we will deprecate support for this client library and there will be no future updates. If you are currently using the client library, the integrations done based on it should still be able to work. Moving forward, we recommend the use of our API documentation (Dashboard and Routing Engine) to build your integration.

API for solving large scale travelling salesman/fleet routing problems

You have a fleet of just 10 vehicles to serve 500 spots in the city. Some vehicles are only available in the day. Some stops can only be served at night. How would you solve this problem?

You don't need to. Just throw us an array of stops, vehicles and depots and we will do the heavy lifting for you. Routing as a Service!

BETA RELASE: ElasticRoute is completely free-to-use until 30th April 2021!

Preface

ElasticRoute offers two APIs depending on your needs, and different sections of this documentation are relevant to you depending on which API you wish to interact with:

• Routing Engine API – if you already have your own fleet management system and you only wish to use ElasticRoute to solve the routing problem and inspect the solution. This is effectively using ElasticRoute in a headless environment, a.k.a. "routing as a service".
• Dashboard API – if your team uses the ElasticRoute web application to review stops and vehicles on a map, and you wish to push data from your existing applications to the ElasticRoute dashboard.

Regardless of how you use ElasticRoute, this client library is capable of interacting with both services.

Quick Start Guide (Routing Engine API)

Refer to this section if you have a separate application to display the results on a map, table or whichever method you prefer, as long as you are not using the ElasticRoute dashboard as-is.

Install with composer:

composer require detrack/elasticroute

In your code, set your default API Key (this can be retrieved from the dashboard of the web application):

Create a new Plan object and give it a name/id:

Give us an array of stops:

Give us an array of your available vehicles:

Give us an array of depots (warehouses):

Set your country and timezone (for accurate geocoding):

Call solve() and save the result to a variable:

Inspect the solution!

Quick notes:

• The individual stops, vehicles and depots can be passed into the Plan as either associative arrays or instances of Detrack\ElasticRoute\Stop, Detrack\ElasticRoute\Vehicle and Detrack\ElasticRoute\Depot respectively. Respective properties are the same as the associative array keys.
• Solving a plan returns you an instance of Detrack\ElasticRoute\Solution, that has mostly the same properties as Detrack\ElasticRoute\Plan but not the same functions (see advanced usage)
• Unlike when creating Plan's, Solution->stops|vehicles|depots returns you instances of Stop, Vehicle and Depot accordingly instead of associative arrays.
• The Stops created by this method (attached to a Detrack\ElasticRoute\Plan object) cannot be seen in the dashboard of the ElasticRoute web application. Please refer to the Dashboard API.

Advanced Usage

Setting time constraints

Time constraints for Stops and Vehicles can be set with the from and till keys/properties:

Dropping from and till keys from either class would result to it being defaulted to avail_from and avail_to keys in the Plan->generalSettings associative array, which in turn defaults to 500 and 1700.

Setting home depots

A "home depot" can be set for both Stops and Vehicles. A depot for stops indicate where a vehicle must pick up a stop's goods before arriving, and a depot for vehicles indicate the start and end point of a Vehicle's journey (this implicitly assigns the possible jobs a Vehicle can take). By default, for every stop and vehicle, if the depot field is not specified we will assume it to be the first depot.

IMPORTANT: The value of the depot fields MUST correspond to a matching Depot in the same plan with the same name!

Setting load constraints

Each vehicle can be set to have a cumulative maximum weight, volume and (non-cumulative) seating capacity which can be used to determine how many stops it can serve before it has to return to the depot. Conversely, each stop can also be assigned weight, volume and seating loads. The fields are weight_load, volume_load, seating_load for Stops and weight_capacity, volume_capacity and seating_capacity for Vehicles.

Alternative connection types (for large datasets)

By default, all requests are made in a synchronous manner. Most small to medium-sized datasets can be solved in less than 10 seconds, but for production uses you probably may one to close the HTTP connection first and poll for updates in the following manner:

Setting the connectionType to "poll" will cause the server to return you a response immediately after parsing the request data. You can monitor the status with the status and progress properties while fetching updates with the refresh() method.

In addition, setting the connectionType to "webhook" will also cause the server to post a copy of the response to your said webhook. The exact location of the webhook can be specified with the webhook property of Plan objects.

Quick Start Guide (Dashboard API)

Refer to this section if you wish to push data to the Dashboard API that other users in your organisation can review.

If you haven't already, install the library:

composer require detrack/elasticroute

The service revolves around the Detrack\ElasticRoute\DashboardClient object. It is responsible for pushing your Detrack\ElasticRoute\Stop and Detrack\ElasticRoute\Vehicle to the ElasticRoute Dashboard where your team can review and edit.

Set the default API Key (retrieved from the Dashboard, the same key can be used for both the Routing Engine API and the Dashboard API):

Next, you can create a list of stops, either as associative arrays or instances of the Detrack\ElasticRoute\Stop object:

Push them to the dashboard using the uploadStopsOnDate method:

This would set today's dashboard to show these stops. Use the second argument to pass a string under the YYYY-MM-DD format to change the date you want to upload these stops under.

To retrieve existing stops on the dashboard, use the listAllStopsOnDate method:

By default, this would list 100 stops on that date. Pass a second parameter to denote how many you wish to retrieve:

And a third parameter for pagination:

To delete all stops on a date, use the deleteAllStopsOnDate method:

The Stop object also has methods to do CRUD operations on individual stops:

Vehicles

Vehicles can also be pushed to the Dashboard (found under settings in the Dashboard) using the uploadVehicles method:

The Vehicle object also has methods to do CRUD operations on individual stops:

Planning

The planning process for a given day/date can be started with the startPlanningOnDate method:

This would automatically start the planning process on the Dashboard. Note that unlike the Routing Engine API, you cannot inspect the results of the route plan through the Dashboard API, you or your team must use the ElasticRoute web application to open the Dashboard to inspect the solution.