Skip to main content
The following is a complete example, using the Python API, of solving a graph created with Seattle road network data for a backhaul routing problem via the /solve/graph endpoint. For more information on Graphs & Solvers, see Graphs & Solvers Concepts.

Prerequisites

The prerequisites for running the backhaul routing solve graph example are listed below:

Python API Installation

Depending on the target operating system, a Python virtual environment may need to be installed first: The native Kinetica Python API is accessible through the following means:

Python Virtual Environment

A Python virtual environment is necessary to install in an operating environment where Python is externally managed.
  1. Install a Python virtual environment:
  2. Activate the Python virtual environment:

PyPI

  1. Install the API:
  2. Test the installation:
    If Import Successful is displayed, the API has been installed as is ready for use.

Git

  1. In the desired directory, run the following, but be sure to replace <kinetica-version> with the name of the installed Kinetica version, e.g., v7.2:
  2. Change directory into the newly downloaded repository:
  3. In the root directory of the unzipped repository, install the Kinetica API:
  4. Test the installation (Python3 is necessary for running the API example):

Data File

The example script references the road_weights.csv data file, mentioned in the Prerequisites, in the current local directory, by default. This directory can specified as a parameter when running the example script.

Script Detail

This example is going to demonstrate solving for routing a given set of remote assets, e.g., stores, to a number of fixed assets, e.g, distribution centers, located in a Seattle road network.

Constants

  • SCHEMA — the name of the schema in which the tables supporting the graph creation and match operations will be created
    The schema is created during the table setup portion of the script because the schema must exist prior to creating the tables that will later support the graph creation and match operations.
  • TABLE_SRN — the name of the table into which the Seattle road network dataset is loaded
  • GRAPH_S — the Seattle road network graph
  • TABLE_GRAPH_S_BSOLVED — the solved Seattle road network graph using the BACKHAUL_ROUTING solver type
Constant Definitions

Graph Creation

One graph is used for the backhaul solve graph example utilized in the script: seattle_road_network_graph, a graph based on the road_weights dataset (the CSV file mentioned in Prerequisites). The seattle_road_network_graph graph is created with the following characteristics:
  • It is directed because the roads in the graph have directionality (one-way and two-way roads)
  • It has no explicitly defined nodes because the example relies on implicit nodes attached to the defined edges
  • The edges are identified by WKTLINE, using WKT LINESTRINGs from the WKTLINE column of the seattle_road_network table. The road segments’ directionality (DIRECTION) is derived from the TwoWay column of the seattle_road_network table.
  • The weights (VALUESPECIFIED) are represented using the time taken to travel the segment found in the time column of the seattle_road_network table. The weights are matched to the edges using the same WKTLINE column as edges (EDGE_WKTLINE) and the same TwoWay column as the edge direction (EDGE_DIRECTION).
  • It has no inherent restrictions for any of the nodes or edges in the graph
  • It will be replaced with this instance of the graph if a graph of the same name exists (recreate)
Create Seattle Road Network Graph

Backhaul Routing

First, the fixed assets and remote assets are set.
Define Fixed Asset Locations
Next, the graph is solved with the solve results being exported to the response. The fixed assets are provided for the source nodes and the remote assets are provided for the destination nodes. All assets are snapped to corresponding locations on the Seattle road network graph.
Solve Graph
The cost for each remote asset to travel to the nearest fixed asset is output:
Solve Graph Results
The solution output to WMS: seattle_bh_solved.png
To demonstrate how the remote assets are routed back to the fixed assets, the fixed assets can be plotted using a separate WMS call and mapped together with the solution. The picture below represents this; the fixed assets are * icons while remote assets can be found in lines leading away from the fixed assets.seattle_bh_solved_w_fixed.png

Download & Run

Included below is a complete example containing all the above requests, the data files, and output. To run the complete sample, ensure that:
  • the solve_graph_seattle_backhaul.py script is in the current directory
  • the road_weights.csv file is in the current directory or use the data_dir parameter to specify the local directory containing it
Then, run the following:
Run Example