ArcHydro Problem Solvers

73386
102
Jump to solution
01-19-2012 06:10 AM
Labels (1)
MarkBoucher
Occasional Contributor III
This is a collection of actions I've learned to take when I'm having problems with ArcHydro or HEC-GeoHMS. I'll add to the list when I find more.

  1. Make sure the Geoprocessing extents include the whole project: Go to the Geoprocessing menu>Environments...>Processing Extent. Under Processing Extent choose a layer that you know covers the full extent of the waters you are processing and click OK. This should ensure that the processing extent is large enough to do what you want.

  2. Delete everything you can in your temp folder: Mine is C:\Users\mboucher\AppData\Local\Temp. Get out of ArcMap first to clear temp files related to your project. You can do this without getting out of ArcMap through the ArcHydro Toolbar under ApUtilities>Additional Utilities>Clean User's Temp Folder.

  3. Make sure your Target Locations are correct: Under ApUtilities>Set Target Locations, make sure the HydroConfig and they GeoHMSConfig Targets make sense. The raster data should go to the project folder vector data to a geodatabase. The raster data will go to a folder in the project folder with the dataframe name and the vector data to a feature data set with the dataframe name. Through the ArcHydro Toolbar under there is a function to reset the target locations: ApUtilities>Additional Utilities>Reset Target Locations. I've not tested this to see if it corrects everything.

  4. When working on a complicated model, don't use the model mxd for your presentation map. It just adds baggage to an already "heavy" mxd.

If you have additional actions or clarifications on these, please chime in.
102 Replies
MarkBoucher
Occasional Contributor III

I've started a practice that seems to make many errors/crashes go away.

Layers/rasters needed for Arc Hydro are:

    • DEM PROCESSING:



      • rawdem (Extracted by mask from county-wide dem for each project. Set processing extents using this or mask ploly)

      • agreestream*

      • innerwalls*

      • outerwalls*


*I do work all over my County and so have county-wide "master" geodatabase for these that I use on all my Arc Hydro Projects.

    • WATERSHED DELINEATION:



      • BatchPoints


If I have these layers, I can recreate the hydrologically correct DEM (HC DEM) anytime I want and re-delineate the watersheds.

So my practice is this: As I'm developing my HC DEM, and have to modify the agreedem, innerwalls, outerwalls layers, I can save the BatchPoints to my project folder and then delete the geodatabase and folder with rasters in it (Target Locations). This starts everything fresh and new. Then I can use model builder to reprocess the watersheds. When I'm ready to re-delineate the watersheds, I copy the BatchPoints into the geodatabase and set the BatchDone value to "0".

I run the watershed delineation, etc. via the Arc Hydro menus though I could possibly do this via Model Builder also. Since I've started doing this (and following solutions in the postings above on this thread), my crashes and errors have all gone away! Here is the ModelBuilder model for my latest project. I don't use outerwalls on this project, but that could be added.


[ATTACH=CONFIG]18585[/ATTACH]

MarkBoucher
Occasional Contributor III
0 Kudos
YuryKorobochkin
New Contributor
Dear Mark,
my thanks for reply.
The matter is that befor I applyed the  Forum I have read information there and deleleted all files from directory by using "Clean Usre's Temp Folder". But these actions didn't help. I simply don't know what to do.
Now I again clean this folder , but have got the same negative result.
Please,  advise me what I have to do more.
Besty regards
Yury
0 Kudos
MarkBoucher
Occasional Contributor III
0 Kudos
MarkBoucher
Occasional Contributor III
Putting the data on your local drive instead of on the network will not only speed up the terrain processing, several functions that usually fail will magically work.
0 Kudos
MarkBoucher
Occasional Contributor III
0 Kudos
MarkBoucher
Occasional Contributor III
This is a very good overview of the Arc Hydro process though it is about the Spatial Analyst Hydrology toolset.
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Understanding_drainage_systems/009z000...

However, I have to disagree with the flow chart in this link (part of the same series). I would always perform a fill before running the flow direction. There is something wrong with the flow chart. It should show the process going from the dimensionless DEM box to a flow direction step then to the flow accumulation. Sorry, I'm being a little picky here, but someone new to this could get frustrated by the flowchart. The steps I use are posted and/or linked elsewhere in this thread (see post #2 in the post right before this one).
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Deriving_runoff_characteristics/009z00....

The third paragraph in this link (part of the same series) points out that most DEMs have sinks. Mine always do, hence, why I always would run a fill sink process before I run the flow direction.
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/How_Fill_works/009z00000061000000/
0 Kudos
JordanAdams2
New Contributor
Hi, I found this thread after finding a similar error here: http://forums.arcgis.com/threads/48081-ArcHydro-Error?highlight=flow+direction

I've been teaching myself Arc Hydro Tools using this walkthrough from Purdue University, using the data provided in the zip file: http://web.ics.purdue.edu/~vmerwade/education/terrain_processing.pdf

Even after making the adjustments recommended in this thread, I would say 50% of the time I get an error message similar to the one seen in the top link. The other half of the time, I get a Flow Direction raster that has no attributes. Any ideas what the heck is going on or how to rectify this situation?

Thanks!
0 Kudos
MarkBoucher
Occasional Contributor III
I've been meaning to make a list of things to do before starting an Arc Hydro project. JAdams15's question pushed me to do it. This is more to remind myself and staff here that might venture into watershed processing than anything else. I hate making the same mistakes twice. Many of these ideas you'll find earlier in this thread.

Getting a project started:

  1. For fastest processing, put the project directory on your local computer (C: drive). Processing over a network kills your speed.

  2. Keep the layer, file, and directory names short and with no spaces or non-alpha numeric characters. Use "_" if you must. I don't use "-". I suspect it causes problems.

  3. Make sure the HydroConfig Target Locations are correct. If you start the project and then move it to another folder, the Target Locations will not change on their own. The GeoHMSConfig Target Locations should be checked if using GeoHMS. Use the ApUtilities > Additional Utilities>Reset Target Locations menu command to reset them. I always check them under ApUtilities>Set Target Locations.

  4. Make sure the Spatial Analyst extension is selected under Customize>Extensions.

  5. Make sure your Geoprocessing Extents match the area you want to process. Use Geoprocessing>Environments>Processing Extent menu command. I make it match the DEM or the mask I used to extract the DEM for the project. In doing batch point delineation  I've had this change to the batch point extent and produce puzzling results.

  6. Disable Background Processing via Geoprocessing>Options menu.

  7. Set the "Max number of unique values to render" to a high number (I use 30,000,000: Don't ask me why.) Adjust this setting under Customize>ArcMap Options>Raster tab>Raster Dataset tab.

  8. Putting the agreestream, innerwall and outerwall layers in a geodatabase is a good idea.

After you've been working on the project a while:

  1. If you are starting over on the process after getting much of the way through it, close Arc Map and via Windows Explorer delete the folders (would have the same name as your data frame) and the geodatabase (would have the same name as your mxd). This makes sure there are not locks on layers/rasters and no denials for overwriting files. The only layer I copy out of this is the Batch Point layer. I make a copy in the main directory so I don't have to create them again.

  2. Clear out the temp file directory. Do this as often as you think of it. There's a tool under ApUtilities that does this nicely.

  3. At times, a reboot of the PC does wonders. I'm not sure why this helps other than it might eliminate software conflicts if you are using more than one program.

Please, please contribute if you see I'm missing something.

Word Version Attached:
0 Kudos
MarkBoucher
Occasional Contributor III
0 Kudos