tspPath



Description:
The tspPath resource. This page simulates how to perform traveling salesman analysis using REST interfaces.
Traveling salesmen problem analysis (TSP) is to find the path passing a series of specified nodes. The TSP is an unordered path analysis. The Traveling salesmen can determine the order of accessing the nodes for themselves, in order to get the traveling path with the minimum (or close to minimum) impedance.
If the end point has been specified, the end point must be the last one to be accessed by the traveling salesmen, and the order of accessing other points can be flexible.


nodes: * The array of nodes to be visited. It can be the array of ID, like [2,3], or node coordinates, like [{"x":32.754,"y":23.205} ,{"x":45.55,"y":87.66}]
endNodeAssigned: Whether to appoint the ending point. True means an ending point is specified, which must be visited last by the salesman.
weightFieldName The wight field name, which indicates the weight field used during network analysis. If not set, the first field in the environment setting will be used.
turnWeightField Turn weight field name
barrierEdgeIDs Barrier edge ID array.
barrierNodeIDs Barrier node ID array
returnEdgeIDs: true indicates the ID collection of the passed edges is included.
returnNodeIDs: true indicates the ID collection of the passed nodes is included.
returnPathGuides: true indicates the collection of path guides is included.
returnRoutes: true indicates the collection of route objects is included.
returnEdgeFeatures: true indicates the collection of the edge features is included.
returnEdgeGeometry: The default is false, indicating the edge feature collection returned doesn't include the geometry information.
returnNodeFeatures: true indicates the collection of the node features is included.
returnNodeGeometry: The default is false, indicating the node feature collection returned doesn't include the geometry information.
Output format
 
HTTP methods

Output formats