match_graph
- match_graph(
graph_name: string,
sample_points: string[],
solve_method?: string,
solution_table?: string,
options?: Record<string, string>,
callback?: GPUdbCallback,
): Promise<MatchGraphResponse>Parameters
- graph_name: string
Name of the underlying geospatial graph resource to match to using
sample_points. - sample_points: string[]
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’.
Optionalsolve_method: stringThe type of solver to use for graph matching.
Optionalsolution_table: stringThe 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.
Optionaloptions: Record<string, string>Additional parameters.
Optionalcallback: GPUdbCallbackOptional callback function
Returns Promise<MatchGraphResponse>
Promise<Types.MatchGraphResponse> - Promise resolving to the response
- Defined in src/GPUdb.ts:11981
- graph_name: string
match_graph_request
- match_graph_request(
request: MatchGraphRequest,
callback?: GPUdbCallback,
): Promise<MatchGraphResponse>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
- request: MatchGraphRequest
Request object containing the parameters for the operation
Optionalcallback: GPUdbCallbackOptional callback function
Returns Promise<MatchGraphResponse>
Promise<Types.MatchGraphResponse> - Promise resolving to the response
- Defined in src/GPUdb.ts:11941
- request: MatchGraphRequest
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.