Match Graph - Markov Chain (Seattle)

The following is a complete example, using the Python API, of matching GPS sample data to road network data via the /match/graph endpoint. For more information on Network Graphs & Solvers, see Network Graphs & Solvers Concepts.


The prerequisites for running the match graph example are listed below:

Python API Installation

The native Kinetica Python API is accessible through the following means:

  • For development on the Kinetica server:
  • For development not on the Kinetica server:

Kinetica RPM

In default Kinetica installations, the native Python API is located in the /opt/gpudb/api/python directory. The /opt/gpudb/bin/gpudb_python wrapper script is provided, which sets the execution environment appropriately.

Test the installation:

/opt/gpudb/bin/gpudb_python /opt/gpudb/api/python/examples/


When developing on the Kinetica server, use /opt/gpudb/bin/gpudb_python to run Python programs and /opt/gpudb/bin/gpudb_pip to install dependent libraries.


  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.0:

    git clone -b release/<kinetica-version> --single-branch
  2. Change directory into the newly downloaded repository:

    cd kinetica-api-python
  3. In the root directory of the unzipped repository, install the Kinetica API:

    sudo python install
  4. Test the installation (Python 2.7 (or greater) is necessary for running the API example):

    python examples/


The Python package manager, pip, is required to install the API from PyPI.

  1. Install the API:

    pip install gpudb --upgrade
  2. Test the installation:

    python -c "import gpudb;print('Import Successful')"

    If Import Successful is displayed, the API has been installed as is ready for use.

Data Files

The example script makes reference to two data files in the current directory: the Seattle road network CSV file and the raw GPS samples CSV file. These paths can be updated to point to a valid path on the host where the files will be located, or the script can be run with the data files in the current directory.

CSV1 = "road_weights.csv"
CSV2 = "mm_raw_gps.csv"

Script Detail

This example is going to demonstrate matching raw GPS points to a Seattle road network, relying on timestamps to determine the start and end point of the GPS signal.


Several constants are defined at the beginning of the script:

  • HOST / PORT -- host and port values for the database
  • OPTION_NO_ERROR -- reference to a /clear/table option for ease of use and repeatability
  • TABLE_SRN -- the name of the table into which the Seattle road network dataset is loaded
  • TABLE_GPS -- the name of the table into which the raw GPS samples dataset is loaded
  • TABLE_SOLUTION -- the name of the table into which the solution is output
  • GRAPH_S -- the Seattle road network graph
HOST = ""
PORT = "9191"

OPTION_NO_ERROR = {"no_error_if_not_exists": "true"}

TABLE_SRN = "seattle_road_network"
TABLE_GPS = "raw_gps_samples"
TABLE_SOLUTION = TABLE_SRN + "_match_solved"

GRAPH_S = TABLE_SRN + "_graph"

Graph Creation

One graph is used for the match graph example utilized in the script: seattle_road_network_graph, a graph based on the road_weights dataset (one of the CSV files 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 represented using WKT LINESTRINGs in the WKTLINE column of the seattle_road_network table (EDGE_WKTLINE). The road segments' directionality is derived from the TwoWay column of the seattle_road_network table (EDGE_DIRECTION).
  • The weights are represented using the time taken to travel the segment found in the time column of the seattle_road_network table (WEIGHTS_VALUESPECIFIED). The weights are matched to the edges using the same WKTLINE column as edges (WEIGHTS_EDGE_WKTLINE) and the same TwoWay column as the edge direction (WEIGHTS_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)
print("Creating {}".format(GRAPH_S))
create_s_graph_response = kinetica.create_graph(
        "recreate": "true"

The graph output to WMS:


Matching the Graph

Matching to a graph typically requires another table's worth of data. In this case, the data that will be matched to the graph will come from the mm_raw_gps dataset (the other CSV file mentioned in Prerequisites). The sample points are defined using the lon and lat columns as the X and Y coordinates for each sample point; the datetime column is used for each sample point's timestamp. The time component is required for determining the start and end points of the samples.

match_s_graph_response = kinetica.match_graph(
    TABLE_GPS + ".lon AS SAMPLE_X",
    TABLE_GPS + ".lat AS SAMPLE_Y",
    TABLE_GPS + ".datetime AS SAMPLE_TIME"

The mean square error score is returned:

Score for how well the samples matched to the graph (closer to 0 is better): 0.000037037552829

The solution output to WMS:



To demonstrate how successful the map matching solution was, the raw GPS samples can be overlaid on top of the solution using WMS. Below is a sample of the total solution.


Download & Run

Included below is a complete example containing all the above requests, the data files, and output.

To run the complete sample, ensure the, road_weights.csv, and mm_raw_gps.csv files are in the same directory (assuming the locations were not changed in the script); then switch to that directory and do the following:

  • If on the Kinetica host:

  • If running after using PyPI or GitHub to install the Python API: