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

Pull in fwa_upstreamtrace #77

Open
joethorley opened this issue May 26, 2023 · 1 comment
Open

Pull in fwa_upstreamtrace #77

joethorley opened this issue May 26, 2023 · 1 comment
Assignees

Comments

@joethorley
Copy link
Member

https://features.hillcrestgeo.ca/fwa/functions/postgisftw.fwa_upstreamtrace/items.html?start_blue_line_key=354153927&start_measure=10000

may just need wrapping in fwatlasbc

@joethorley
Copy link
Member Author

Seems fine so far but there may be edge cases that I haven't thought of - supply blue line key and measure and all stream upstream is returned, cutting the stream at the provided point. If the provided measure is within the tolerance to the endpoint, the source geom is returned (or nothing, if at the endpoint). (edited) 


Very cool - is it ready to pull into the R packages?


I think so. I haven't added it to the repo yet but it is live on the server and good to go.
There is no functionality to provide a watershed code like you were originally asking for in the GH issue, let me know if that is needed.


blk is better I think


there is just one nuance between the results and the source data in the streams table - any record with null local code will not be returned (because we can't tell where it is positioned)
this is a data error, apparently those are being cleaned up but it is very slow because there are so many
And of course unconnected segments won't come through either.

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

3 participants