Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trace comparison to Regionalization Extents #4

Open
gassc opened this issue Nov 21, 2017 · 0 comments
Open

Trace comparison to Regionalization Extents #4

gassc opened this issue Nov 21, 2017 · 0 comments
Assignees

Comments

@gassc
Copy link
Member

gassc commented Nov 21, 2017

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.

@gassc gassc self-assigned this Nov 21, 2017
@gassc gassc mentioned this issue Nov 21, 2017
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant