Latest Contributions by MarkBoucher

You may be aware that ESRI is moving GeoNet to a new platform. To preserve this thread I've exported it to a Word Document. The option to export to a pdf wasn't working and it looks like some paragraph numbering was lost in the simple copy/paste to Word. Once the new GeoNet is up and running, and if we last this thread, I will post the document somewhere I think it is searchable. Best, Mark - Original Arc Hydro Problem Solvers poster. ... View more

Annina, I don't recall seeing that recently. First: I assume you have filled the sinks under the DEM Manipulation tools.. If not, make sure you do that. Second: The black lines ( DrainageLines) appear to cross each other. Some look like they follow flow paths defined by the DEM (irregular in alignments), others look long and sweeping and like they wouldn't follow a path defined by the DEM. These appear to have have more generalized alignments. Make sure your agreestream layer is correct. I try to limit the agreestream polylines in natural area and only put them in where the DEM misses where water flows under roads or bridges. In developed areas, I put in agreestream polylines where there are pipes. Third: Make sure you are setting the datasets correctly in the Terrain Processing>Data Management Terrain Processing menu. Hope this helps. Mark ... View more

Darin, My initial thought is to suggest you check and ensure that the geoprocessing extents includes the extent of your data. In older versions the processing extents would change during a prior process and not change back if one of the prior  processes didn't execute successfully. In my case the geoprocessing extents would match the patch points extents and cut off watersheds to the extent limits of the batch points. A remedy was to reset the geoprocessing extents. I have not used the "append coastal catchments" tool. Could be an error in that process that I've not encountered. If you find the processing extents is the issue, you may want to check the processing extents before and after you run append coastal catchments.  I have run into a similar situation as you and gotten watersheds delineated round a small area instead of what I expected. In those cases the point I clicked was not right on the str grid and I'd get a very small watershed delineated as a result. I then would use the flow trace tool and click on the fdr cells all round the point of interested until I was certain I was on a cell that would work. A bit tedious, but it was a work around. Hope something here helps, Mark ... View more

Annina, I can't tell from those error messages what might be going on. The " error message" I'm thinking of is the one that appears while processing. An example is that provided in the image by  Anne-Marie Dubois in her post on Aug 8, 2019 7:22 AM. If you can screen shot the run time error messages it might reveal something. I did a Google search on "arcpy memory error" a few of the results could help your Python programmer. (I suspect done this type of search already): A result in GeoNet: memory error with python  A result in ERSI support: Error: ERROR 000426: Out Of Memory  A result in stackexchange: arcpy - Python MemoryError when running ArcGIS Python Toolbox tool - Geographic Information Systems Stack Exchange  Hope this helps. I look forward to seeing the solution. I want to get my Python black belt doing Arc Hydro for me soon so your experience will be goo to follow. Best, Mark ... View more

Annina, Thanks for the ego boost. I am experienced through the "beating the head against the wall" ArcHydro methods gauntlet, so I guess that makes me an "expert".  I am not a Python pro at all. I have gotten accustom to deciphering the ESRI error messages. If you can send the text or a screen shot of the error message, I'll see if that can point to a potential problem.   Are you processing the project on your local machine or over a network? That can make a difference, in my experience. Best,   Mark ... View more