TraceDownResult

URI

<fa3DNetworkDataName_uri>/tracedownresult[.<format>]

Supported methods

Parent resource

Introduction

TraceDownResult is the downstream tracking resource for 3D facility network analysis. It is to find the downstream of the specified arc or node, and return the arcs, nodes and total cost in the downstream.

Supported Methods:

GET: gets the arcs, nodes and total cost in the downstream.
HEAD: Checks whether traceDownResult resource exists, or whether it can be accessed.

Supported output formats:(rjson、json、html、xml、jsonp).

Resource hierarchy

HTTP request methods

Implement the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.

http://supermapiserver:8090/iserver/services/networkAnalyst3D-Pipe3D/rest/facilityanalyst3d/{networkDataName}/tracedownresult.rjson

GET request

GET: gets the arcs, nodes and total cost in the downstream.

Request parameter

Proper parameters need to be included in the URI when performing a GET request on the traceDownResult resource.

Name	Type	Description
edgeID	String	[Required parameter] Specified arc ID in the 3D facility network analysis, there will be only the edgeID or nodeID parameter in the request URL, and they cannot exist at the same time.
nodeID	String	[Required parameter] Specified node ID in the 3D facility network analysis, there will be only the edgeID or nodeID parameter in the request URL, and they cannot exist at the same time.
isUncertainDirectionValid	boolean	Whether to continue the searching when the flow is not determined. True means it will continue when it meets the undetermined flow; false means it will stop searching in this direction when it meets the undetermined flow. The field value 2 means undetermined flow.
weightName	String	[Required parameter] Specified weight field name

Response structure

The structure of the response resource representation after implementing the GET request on the traceDownResult resource will be as follows:

Field	Type	Description
cost	double	Cost in the result.
edges	int[]	Arc ID array in the result.
nodes	int[]	Node ID array in the result.

Response example

The returned rjson format resource representation after implementing the GET request on the traceDownResult resource http://localhost:8090/iserver/services/networkAnalyst3D-Pipe3D/rest/facilityanalyst3d/Network@Pipe3D/tracedownresult.rjson?edgeID=2&isUncertainDirectionValid=true&weightName=SMLENGTH is as follows:

{ "cost": 2921.1391792773893, "edges": [ 3, 4, 5, 166, 6, 7, 496, 8, 170, 171, 172, 173, 9, 10, 465, 11, 12, 13, 174, 175, 178, 176, 177, 187, 188, 189, 193, 190, 192, 200, 201, 202, 203, 191, 194, 204, 195, 196, 198, 220, 199, 250, 500, 501, 502, 503, 251, 252, 253, 254, 255, 256, 257, 258, 259, 221, 222, 223, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 235, 236, 237, 238, 239, 224, 197, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 14, 15, 149, 150, 151, 152, 153, 154, 155, 156, 157, 260, 158, 159, 160, 161, 162, 163, 164, 468, 165, 469, 261, 262, 263, 264, 265, 267, 266, 268, 16, 293, 17, 21, 18, 19, 87, 88, 90, 91, 93, 94, 97, 98, 99, 100, 95, 96, 101, 102, 103, 138, 104, 105, 106, 107, 108, 110, 111, 113, 114, 115, 116, 118, 457, 458, 459, 460, 461, 462, 463, 464, 117, 112, 109, 139, 140, 141, 143, 144, 146, 147, 148, 179, 180, 181, 182, 183, 184, 185, 186, 145, 142, 92, 89, 20, 22, 292, 23, 24, 26, 27, 28, 29, 31, 30, 33, 34, 35, 36, 38, 39, 40, 41, 44, 45, 47, 48, 50, 51, 49, 52, 269, 273, 281, 282, 470, 471, 472, 283, 284, 285, 286, 287, 288, 289, 290, 291, 274, 275, 489, 276, 277, 278, 279, 490, 491, 270, 280, 271, 272, 46, 42, 43, 53, 54, 56, 57, 58, 60, 59, 61, 62, 63, 65, 66, 68, 69, 70, 71, 72, 74, 75, 76, 84, 77, 82, 78, 79, 80, 81, 83, 85, 86, 73, 67, 64, 55, 37, 32, 119, 120, 121, 122, 123, 124, 125, 126, 127, 134, 135, 137, 136, 128, 129, 130, 131, 132, 486, 487, 488, 133, 25, 294, 295, 296, 297, 298, 299, 301, 302, 303, 304, 305, 306, 307, 314, 315, 316, 317, 318, 319, 422, 423, 425, 424, 426, 427, 428, 429, 430, 320, 308, 309, 310, 311, 313, 312, 300, 466, 467, 497, 498, 499, 167, 168, 169 ], "nodes": [ 71, 72, 73, 74, 69, 70, 102, 67, 44, 31, 30, 1, 68, 65, 100, 66, 63, 64, 128, 183, 129, 184, 230, 229, 231, 232, 268, 185, 233, 234, 235, 236, 237, 186, 333, 269, 411, 334, 412, 413, 414, 444, 415, 445, 465, 466, 456, 457, 458, 459, 460, 461, 462, 463, 464, 404, 405, 406, 431, 432, 433, 434, 435, 436, 437, 408, 409, 438, 410, 397, 398, 399, 400, 401, 402, 403, 363, 364, 439, 440, 441, 442, 443, 407, 343, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 305, 306, 307, 59, 60, 40, 41, 42, 43, 39, 28, 29, 27, 24, 25, 14, 15, 16, 17, 18, 19, 20, 22, 21, 23, 26, 4, 5, 6, 2, 7, 3, 8, 96, 61, 127, 97, 146, 147, 172, 173, 257, 258, 260, 261, 264, 265, 266, 159, 262, 263, 304, 331, 319, 332, 320, 321, 322, 323, 324, 389, 390, 392, 393, 478, 479, 503, 482, 483, 484, 485, 486, 477, 496, 497, 480, 391, 325, 339, 340, 341, 394, 395, 487, 488, 489, 498, 499, 490, 491, 492, 481, 493, 500, 396, 342, 259, 182, 148, 121, 98, 122, 123, 125, 126, 142, 143, 144, 158, 152, 153, 154, 155, 157, 163, 164, 165, 250, 251, 314, 315, 317, 318, 316, 377, 378, 382, 427, 428, 476, 494, 495, 423, 424, 425, 426, 450, 451, 452, 453, 454, 383, 384, 429, 385, 386, 387, 388, 430, 455, 379, 362, 380, 381, 252, 166, 167, 168, 169, 171, 177, 178, 180, 179, 221, 222, 223, 294, 295, 312, 313, 336, 360, 337, 361, 369, 370, 375, 371, 373, 372, 420, 421, 422, 374, 359, 376, 338, 296, 224, 170, 156, 145, 254, 267, 255, 297, 298, 299, 256, 253, 300, 226, 227, 181, 228, 301, 302, 303, 326, 327, 328, 329, 330, 225, 124, 62, 54, 93, 94, 55, 56, 58, 47, 48, 49, 50, 51, 92, 52, 53, 46, 87, 88, 89, 84, 85, 91, 86, 113, 114, 111, 115, 112, 90, 95, 117, 118, 119, 116, 120, 57, 99, 130, 103, 131, 149, 101, 104, 150 ] }

HEAD request

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.

HEAD request can judge whether traceDownResult resource exists or whether it can be accessed on the client. By implementing the HEAD request on the URI, with .<format> appended to the end, we can quickly get to know whether the traceDownResult resource supports the representation in <format> or not.