Skip to main content

◆ matchGraph() [1/4]

MatchGraphResponse gpudb::GPUdb::matchGraph (const MatchGraphRequest &request_) const

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.

Parameters
[in]request_Request object containing the parameters for the operation.
Returns
Response object containing the result of the operation.

◆ matchGraph() [2/4]

MatchGraphResponse & gpudb::GPUdb::matchGraph (const MatchGraphRequest &request_,
MatchGraphResponse &response_ ) const

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.

Parameters
[in]request_Request object containing the parameters for the operation.
[out]response_Response object containing the results of the operation.
Returns
Response object containing the result of the operation (initially passed in by reference).

◆ matchGraph() [3/4]

MatchGraphResponse gpudb::GPUdb::matchGraph (const std::string &graphName,
const std::vector< std::string > &samplePoints,
const std::string &solveMethod,
const std::string &solutionTable,
const std::map< std::string, std::string > &options ) const

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.

Parameters
[in]graphNameName of the underlying geospatial graph resource to match to using samplePoints.
[in]samplePointsSample 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’.
[in]solveMethodThe type of solver to use for graph matching. Supported values:The default value is match_graph_markov_chain.
[in]solutionTableThe 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. The default value is ”.
[in]optionsAdditional parameters.The default value is an empty map.
Returns
Response object containing the result of the operation.

◆ matchGraph() [4/4]

MatchGraphResponse & gpudb::GPUdb::matchGraph (const std::string &graphName,
const std::vector< std::string > &samplePoints,
const std::string &solveMethod,
const std::string &solutionTable,
const std::map< std::string, std::string > &options,
MatchGraphResponse &response_ ) const

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.

Parameters
[in]graphNameName of the underlying geospatial graph resource to match to using samplePoints.
[in]samplePointsSample 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’.
[in]solveMethodThe type of solver to use for graph matching. Supported values:The default value is match_graph_markov_chain.
[in]solutionTableThe 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. The default value is ”.
[in]optionsAdditional parameters.The default value is an empty map.
[out]response_Response object containing the results of the operation.
Returns
Response object containing the result of the operation (initially passed in by reference).