Comments (6)
I am not sure what I am looking at in the picture, and need a bit more information to help. The program is supposed to label each grid cell in the outputs with the identifier (from column id) of the gage to which it drains directly without passing through any other gages. If there are areas that do not drain to any gage they would appear as gaps. To figure out what is going on it would be helpful to know more about the inputs and what is being shown. A type mismatch on the column ID that ends up writing no data to the output comes to mind as a possibility. Improper flow directions - perhaps related to unfilled pits are also an option, though you said the D8 results were continuous.
from taudem.
Thank you very much for the fast reply.
I should've been a bit clearer. The colored points are points representing the stream network extracted at 30m resolution. Each color represents an unique ID. I passing these points as input to gagewatershed
command line interface with the -o
flag.
The colored raster is the result from gagewatershed
. Because of the number of unique "catchments" (not sure if that's the correct term here) it is a bit hard to apply a nice colormap to the raster.
As I mentioned, the D8 results look correct and so do the slope results.
I am wondering if the point data I am passing to gagewatershed
are not really what I should be using.
Thanks again for your help, it's much appreciated
from taudem.
I have two theories. The first is that the unique identifiers for certain points are overflowing the integer variable into which they are written and then leave no data in the result. This could be related to type mismatch. But I do not have much confidence in this because each gage watershed should be attached to a gage and the no data streaks do not always connect to a point. However there may be a loss of resolution in the image and a much closer look may show a but more.
The other theory is that there is numerical rounding in the positioning of the gages that somehow leaves out certain grid cells. I am also not very confident in this.
If you zoom in very close around where these no data areas seem to be starting (their downstream ends as the algorithm propagates upslope) you may learn something. Alternatively, if you want to send me a small art of the data, I could investigate a bit myself.
from taudem.
I spent the day looking at the it and could not figure anything out. I put the data here: https://drive.google.com/file/d/1fexJwE5flGWLwQdLIKbweimFps22q9bI/view?usp=sharing
Files are:
stream_points.shp
: input for the-o
flagD8_Tau.tif
: flow directions for the-p
flagstream_px_ws.tif
: current resultselev_res_flat.tif
: pit-filled and flat resolved DEM (for reference)
Thank you very much for your help!
from taudem.
I checked the data you sent and found that this is due to real pits, and hence internal drainage in the DEM. See https://drive.google.com/drive/folders/1dT-TSdrKU4sYNgcieglqSUO7lwsTQNYW?usp=sharing
from taudem.
Thank you so very much for all this insight, it is much appreciated!
I will close the issue now as this is not a TauDEM issue.
Just for a bit extra context, I was following the workflow from here: https://code.usgs.gov/gft/python-gis-flood-tool. I may open a issue there with the information that their workflow may not be fully compatible with TauDEM.
from taudem.
Related Issues (20)
- InunMap executable not created during compile HOT 3
- Process refusing to die? HOT 1
- Burned flow direction HOT 4
- updateParameters Execution Error HOT 4
- Parameters Execution Error: Runtime error Traceback HOT 3
- job abortion when run aread8 HOT 2
- Stream Reach and Watershed HOT 1
- Error in GNU/Linux Ubuntu 22.04 HOT 2
- Pit Remove failed HOT 1
- ERROR TauDEM 000732 HOT 3
- ERROR 000732: Input Raster Dataset #19 HOT 1
- D-infinite Transport limited accumulation returns no value on some cells HOT 5
- aread8 difference in GDAL versions > 3.4.3 HOT 1
- Pit removel does not work with -depmask HOT 4
- PitRemoven.cpp not buiding
- DropAnalysis HOT 3
- I have encountered a problem and I need urgent assistance. Thank you very much for your help. HOT 2
- Compilation errors HOT 6
- Error 127 when installing on a remote server
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from taudem.