Goal: Display the calculated length of regionalized pipe in the trace. In most cases it would be 0; however, it would entice a user to question what it means.
This requires modification of 3RWW's network trace service, so that, in addition to the trace result geometry, it returns a summary of pipes within the trace that are also potentially going to be regionalized. Since the regionalization data changes frequently and is being managed in a separate database, the most straightforward way to identify this will be to implement some spatial intersects on the trace results with available regionalization data.
Since that kind of analysis will require more processing time, we'll turn that functionality in the trace service off by default (we don't need that for other applications that utilize the Sewer Atlas trace service), but call it for this app.
Goal: Display the calculated length of regionalized pipe in the trace. In most cases it would be 0; however, it would entice a user to question what it means.
This requires modification of 3RWW's network trace service, so that, in addition to the trace result geometry, it returns a summary of pipes within the trace that are also potentially going to be regionalized. Since the regionalization data changes frequently and is being managed in a separate database, the most straightforward way to identify this will be to implement some spatial intersects on the trace results with available regionalization data.
Since that kind of analysis will require more processing time, we'll turn that functionality in the trace service off by default (we don't need that for other applications that utilize the Sewer Atlas trace service), but call it for this app.