Latest Contributions by MarkBoucher

What Jacom Helfan said is a good approach. One issue is the different extents of each of the rasters. The suggestion of mine below might be the long way around, but should work. You should make all the rasters for each watershed with the same cell size and grid basis ( starting x, y). For each raster, run Con and IsNull to make all the Null cells 0. Create a polygon that encompasses all of the rasters. Create a raster from that one polygon based on the grid size and grid basis of the other rasters and making the value zero. Do raster math and add them all up with the new big raster with zero value as the starting point. This will make sure the extent is right. A key is getting any Null values to 0 because I think in raster math if one of the values is null, the answer will be null. If there is any overlap of the rasters you could get large numbers. There should be an option to use the value of the last raster as the final answer, but that might be mosic (and the problem you  are having. Again, I have not tested this and it is "the long way around" but it seems that it would work. HTH, Mark ... View more

Welcome to the forum. There are several reasons this error comes up. ESRI provides this page. http://resources.esri.com/help/9.3/arcgisengine/dotnet/a3bd05c8-64a6-4dd4-acb3-0d10b021f2f8.htm#ErrorCodes I wrote this about it in 2014. I assume it is still valid. https://community.esri.com/thread/114219 The same question is also posted here with some replies including my own. https://community.esri.com/message/804958-re-error-hresult-efail-has-been-returned-from-a-call-to-a-com-component?commentID=804958 Hope this helps, Mark ... View more

I have no code or book. You have to have the velocity in the river based on slope. Without a detail hydraulic model, you can only estimate. If you have varied "roughness" (smoother vs rougher), that can influence velocity. You should be able to Google "estimate river velocity" and find something. Length(ft) = Velocity (ft/sec) X Time (sec). If you have a dem you can created a slope raster. Somehow use that to come up with how far the flow would go in 24 hours. You must have a long river. ... View more

Please, someone correct me if I'm wrong ... ...  I believe  Batch Point delineation should work no matter what size the stream threshold is. I believe the more Adjoint Catchments you have, the faster the batch processing will go. This is because the batch delineation processes only have to delineate the areas upstream of the Batch Points to the upstream edge of the catchment polygon they are in. The the rest of the delineation happens very quickly by simply selecting the next upstream adjointcatchment. So Adjoint Catchment process is like prepossessing the delineation to make the batch processing faster. It is also used in other tools, so you need to do it for those.  So if you have a huge watershed and a large stream threshold (resulting in fewer adjointcatchment polygons), the batch delineation processes should take longer than if you have a smaller stream threshold ( resulting in more adjointcatchment polygons) . Until this issue gets addressed, increase your stream threshold (reduce the number of  adjointcatchment polygons)  until it eventually works. I recall a story that when this was first demonstrated live at a conference, many of the attendees thought it was a joke, a trick, or not real. They couldn't believe it. They were used to delineation taking forever. Using the network analysis capabilities (necessitating HydroID, UpstreamID, NextDownID, etc), Arc Hydro is able to do these tasks relatively quickly. Mark ... View more

The "usual suspects" are also discussed here: https://community.esri.com/message/45017#45017  ... View more

Clipped, linear borders can be a sign that the processing extent was constrained to some domain (sometimes that of the BatchPoints dataset).  Mark ... View more

Are you wanting to fill every sink in the watershed to whatever level it would fill, or to one large sink (reservoir/lake) at the low end of the watershed? If it is the former, I'd be curious with someones answer. If a minor sink fills, you'd have to determine where the overflow volume goes and how much it fills the next sink downstream and then the next, etc. If this is a dynamic model, where you aren't looking just at the total storm runoff, but how the sinks fill over time, you've go a pretty complex model going on. And I'm not sure you can to that using ArcMap. If it is the latter (one large sink), you would normally make a depth-volume curve for the sink/reservoir/lake that would allow you to determine the depth after determining the volume. Also, large sinks have an outlet. and you'd need to do reservoir routing to determine the maximum depth of fill for a storm. Again,  I'm not sure you can to that using ArcMap. Mark ... View more

Possibly convert the contours to a raster and then symbolize it. Use the elevation value for the raster value and you could do some interesting representation.  Just another idea. ... View more

Alex, Sorry to reply so late!  I routinely use the Extract by Mask tool to limit the area I'm analyzing. It really reduces the processing time. To keep things consistent throughout my county, I have a "master" agreestreams, innerwalls and outerwalls datasets in a geodatabase. This allows me to break up the watersheds as needed but keep the same features for modifying the DEM regardless of where I'm working. I don't use the "Adjust flow direction in lakes" function. What I do is put an agreestreams feature that goes through the lake an then to the outlet. I also put an innerwalls line across the dam. This allows me to put a batch point at the mouth of the lake or reservoir and perform watershed delineation, etc. at that point. Hope this helps, Mark ... View more