Chinese Postman Problem - Family of functions (Experimental) - pgRouting Manual (3.2)
Chinese Postman Problem - Family of functions (Experimental)
Warning
Possible server crash
-
These functions might create a server crash
Warning
Experimental functions
-
They are not officially of the current release.
-
They likely will not be officially be part of the next release:
-
The functions might not make use of ANY-INTEGER and ANY-NUMERICAL
-
Name might change.
-
Signature might change.
-
Functionality might change.
-
pgTap tests might be missing.
-
Might need c/c++ coding.
-
May lack documentation.
-
Documentation if any might need to be rewritten.
-
Documentation examples might need to be automatically generated.
-
Might need a lot of feedback from the comunity.
-
Might depend on a proposed function of pgRouting
-
Might depend on a deprecated function of pgRouting
-
Description
The main characteristics are:
-
Process is done only on edges with positive costs.
-
Running time: \(O(E * (E + V * logV))\)
-
Graph must be connected.
Parameters
Column |
Type |
Default |
Description |
---|---|---|---|
edges_sql |
|
The edges SQL query as described in Inner query . |
Inner query
An Edges SQL that represents a directed graph with the following columns
Column |
Type |
Default |
Description |
---|---|---|---|
id |
|
Identifier of the edge. |
|
source |
|
Identifier of the first end point vertex of the edge. |
|
target |
|
Identifier of the second end point vertex of the edge. |
|
cost |
|
Weight of the edge (source, target)
|
|
reverse_cost |
|
-1 |
Weight of the edge (target, source) ,
|
Where:
- ANY-INTEGER :
-
SMALLINT, INTEGER, BIGINT
- ANY-NUMERICAL :
-
SMALLINT, INTEGER, BIGINT, REAL, FLOAT
See Also
Indices and tables