-
Notifications
You must be signed in to change notification settings - Fork 2
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
Potential Path Issues #25
Comments
I think a similar thing is happening here, in Norway, involving a large inland lake, but could be wrong: path |
I think I see a similar issue here in the Netherlands (which is, admittedly, designed to foil tools like this). The Amstel river might as well not exist, a “droplet placement” on the river itself will jump elsewhere. |
There is also an overall issue that the application currently uses a bounding box search around a point click and choosing an arbitrary flow path within to start from. A future version of this will be more rigorous and be based on actual catchments
…Sent from my phone
Kyle Onda
Data Architect
Internet of Water
Nicholas Institute for Environmental Policy Solutions
Duke University
Box 90355
Durham, NC 27708
(919) 613-8747
***@***.***
________________________________
From: Hans Gerwitz ***@***.***>
Sent: Wednesday, January 5, 2022 4:56:17 AM
To: ksonda/global-river-runner ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [ksonda/global-river-runner] Potential Path Issues (Issue #25)
I think I see a similar issue here in the Netherlands (which is, admittedly, designed to foil tools like this). The Amstel river might as well not exist, a “droplet placement” on the river itself will jump elsewhere.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/ksonda/global-river-runner/issues/25*issuecomment-1005538241__;Iw!!OToaGQ!_a8q__kzgNvSOlWoKN2BPJLz7-SHXLZcCUyL1xpBxEL2XBt3m-22GtaE0cpjT6F1wg$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AKQHTNUK3XLRE4AYUS4ZXCTUUQIUDANCNFSM5LAXB4FQ__;!!OToaGQ!_a8q__kzgNvSOlWoKN2BPJLz7-SHXLZcCUyL1xpBxEL2XBt3m-22GtaE0cq84Mek0A$>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've noticed a couple of naming issues where features are over-grouped or over-extended at the end of paths, potentially related to these paths running through numerous large inland features? Not sure if the terminal flag/stream level properties might be impacted by the path running through something like the Great Lakes?
The River Runner tool now overrides names on flowlines inside of inland features, so it might be a little easier to see with on the IoW plots:
The text was updated successfully, but these errors were encountered: