Hey there,
Very new to ArcMap and am trying to use some HEC-geoHMS tools. I keep getting similar errors but can't decipher what is going wrong and don't know where to begin trying to troubleshoot. The only things I have tried is using different DEM versions for certain functions and trying to save outputs into different locations (folders/geodatabases). Can anyone tell me what these errors mean?
Thanks!
All of my knowledge and experience with ArcGIS started 3 months ago and is fairly superficial. Could you explain what a COM module is, where it is, what it does?
This part I don't know - I have not used HEC-GeoHMS myself.
My only guess would be that maybe HEC-GeoHMS is missing one of the COM modules? However, that is just a guess.
Chris Donohue, GISP
Just saw this answer to the question, I did end up figuring out is was from the spaces I had in my file paths. Would you mind checking out these other errors I'm now getting, I believe they have something to do with file paths/target locations but I'm not entirely sure. https://community.esri.com/thread/205228-problems-exporting-background-shape-file-and-basin-model-file-with-hec-geohms
Two immediate potential problems to resolve are the space in the path name at "ben poole", and the combined length of the grid filename and its path being potentially over 128 characters at any stage in the processing. Since the process is using an ESRI GRID, it has to meet very specific file and path-naming conventions, which are much more constrained than for other data types. I'd start by fixing these, as it often seems that these grid issues also spawn other unrelated errors.
The name of an Esri Grid format raster has more specific restrictions:
Output raster formats and names—ArcGIS Help | ArcGIS Desktop
Bear in mind that these constraints applies to the folder names also. Having just one space in a folder can cause things to go awry. Note that their is no specific error that will come up alerting the user that the issue is due to a space being present.
Also - not a hard and fast requirement, but can help - stay away from the /Users/username structure if possible. Try to use a very short, direct path to the data, like C:\Data\Model or such. In theory it should not matter, but in reality sometimes that can be the difference between an operating process and one that throws errors.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
