Skip to main content
Source

​
pub async fn match_graph( &self, graph_name: String, sample_points: Vec<String>, solve_method: String, solution_table: String, ) -> Result<MatchGraphResponse, KineticaError>

Match sample points to a graph.

Matches a directed route implied by a given set of latitude/longitude points to an existing underlying road network graph using a given solution type.

IMPORTANT: It’s highly recommended that you review the Graphs and Solvers concepts documentation, the Graph REST Tutorial, and/or some /match/graph examples before using this endpoint.

  • graph_name - Name of the underlying geospatial graph resource to match to using sample_points.
  • sample_points - Sample points used to match to an underlying geospatial graph. Sample points must be specified using identifiers; identifiers are grouped as combinations. Identifiers can be used with: existing column names, e.g., ‘table.column AS SAMPLE_X’; expressions, e.g., ‘ST_MAKEPOINT(table.x, table.y) AS SAMPLE_WKTPOINT’; or constant values, e.g., ‘1, 2, 10 AS SAMPLE_TRIPID’.
  • solve_method - The type of solver to use for graph matching.
  • solution_table - The name of the table used to store the results, in [schema_name.]table_name format, using standard name resolution rules and meeting table naming criteria. This table contains a track of geospatial points for the matched portion of the graph, a track ID, and a score value. Also outputs a details table containing a trip ID (that matches the track ID), the latitude/longitude pair, the timestamp the point was recorded at, and an edge ID corresponding to the matched road segment. Must not be an existing table of the same name.
Source

​
pub async fn match_graph_with_opts( &self, graph_name: String, sample_points: Vec<String>, solve_method: String, solution_table: String, options: MatchGraphRequestOptions, ) -> Result<MatchGraphResponse, KineticaError>

Match sample points to a graph.

Matches a directed route implied by a given set of latitude/longitude points to an existing underlying road network graph using a given solution type.

IMPORTANT: It’s highly recommended that you review the Graphs and Solvers concepts documentation, the Graph REST Tutorial, and/or some /match/graph examples before using this endpoint.

  • graph_name - Name of the underlying geospatial graph resource to match to using sample_points.
  • sample_points - Sample points used to match to an underlying geospatial graph. Sample points must be specified using identifiers; identifiers are grouped as combinations. Identifiers can be used with: existing column names, e.g., ‘table.column AS SAMPLE_X’; expressions, e.g., ‘ST_MAKEPOINT(table.x, table.y) AS SAMPLE_WKTPOINT’; or constant values, e.g., ‘1, 2, 10 AS SAMPLE_TRIPID’.
  • solve_method - The type of solver to use for graph matching.
  • solution_table - The name of the table used to store the results, in [schema_name.]table_name format, using standard name resolution rules and meeting table naming criteria. This table contains a track of geospatial points for the matched portion of the graph, a track ID, and a score value. Also outputs a details table containing a trip ID (that matches the track ID), the latitude/longitude pair, the timestamp the point was recorded at, and an edge ID corresponding to the matched road segment. Must not be an existing table of the same name.
  • options - The optional parameters; any left unset take the server’s defaults.

Sends a pre-built MatchGraphRequest to the /match/graph endpoint.

Sends a pre-built MatchGraphRequest to a specific worker URL, bypassing HA head-node selection. Used for multi-head access.