8000 Error in width computation caused by "no data" pixels on the river · Issue #16 · CS-SI/BAS · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on May 6, 2025. It is now read-only.

Error in width computation caused by "no data" pixels on the river #16

Open
chadelmas opened this issue Mar 31, 2025 · 0 comments
Open

Error in width computation caused by "no data" pixels on the river #16

chadelmas opened this issue Mar 31, 2025 · 0 comments

Comments

@chadelmas
Copy link
chadelmas commented Mar 31, 2025 •
edited
Loading

Description
When "no data" pixels are present, covering some parts of the river, the widths are not accurate.

Reproduce the example

  • Area: tile T31TCK, around Cahors (France)
  • Surfwater optical mask: late v1.2 (1.3)
  • Datetime: 20190312T105841
  • BAS version: v1.0.3
  • Python version: 3.12

Output
Around Cahors, BAS gives a width value only for the node 23214200550031, which is 13,75m. In the image, blue pixels represent water, beige pixels represent land (non-water), and transparent pixels represent "no data" areas (Google Maps background)
Image

The width around this point should be approx. 100m
Image

Analysis
It seems that the algorithm already filters cases where the mask does not intersect the reaches line (SWORD v16). However, there may still be an issue when nodes intersect "no data" pixels. A possible solution could be to implement an additional filter to exclude cases where a node is located on a "no data" pixel ?
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chadelmas
0