POST
|
I encountered an error running the ArcHydro for Pro Wetlands Identification Model - Train Random Trees tool. The error gave the following message: ('line 337', 'c:\\program files\\arcgis\\pro\\Resources\\ArcToolbox\\Scripts\\archydro\\trainrandomtrees.py', "AttributeError: 'NoneType' object has no attribute 'RasterXSize'") After surfing this forum for similar RasterXSize errors, I discovered that the issue is an incomplete path for the input predictor variable rasters in the ArcHydro Train Random Tree tool. Basically, if you accept the shortened "layer" path from the tool drop down (my inputs were in a group layer), the tool cannot find the input rasters. Instead, I navigated to the full network path for every input and the tool ran quickly and smoothly.
... View more
03-03-2021
09:25 AM
|
0
|
0
|
683
|
POST
|
I've also had this issue with ArcHydro 10.5.0.104 and ArcGIS 10.5.1. Everything ran fine but the adjoint output was empty. I took the above advice and gradually increased my stream threshold from a low of 500 pixels (at 9ft resolution) to 3000 pixels, or 0.022576 sq km, until my adjointment catchments finally got populated. This resulted in about 190,000 catchments and around 90,000 adjoint catchments in my area of interest. In any case, the batch delineation tool now works without any of the strange linear cutting off the output basin. I am disappointed that ArcHydro can't seem to tolerate more catchments than that, but since the delineation tool will cut out the downstream portions of my last catchment, this still gets me what I need in terms of basin delineation. Thanks for the advice!
... View more
04-26-2019
08:21 AM
|
0
|
0
|
2288
|
POST
|
In addition to moving my data to my C drive, I found that I also needed to move the Python script, through which I was running ArcHydro, to the folder where my data was stored on my C drive, to avoid the "hresult" error. Previously the script was on my organization's network and I would progressively lose ArcHydro tools to the "hresult" error. What is very strange is that everything worked on the network at the start of my project (including data storage), but as I did more runs and fleshed out my script, I began encountering the error in one ArcHydro tool after the next. After finding a work around for the tool I needed, the script would run ok for a while and then another tool would break. It was the same whether I was using the default ArcHydro toolbox or the Python toolbox. Finally I had to move everything to local storage and am now encountering no errors. I am running ArcGIS and ArcHydro 10.5 in IDLE. Thanks for the tips about local storage. Brenden
... View more
08-23-2018
09:15 AM
|
0
|
0
|
3680
|
Online Status |
Offline
|
Date Last Visited |
09-10-2021
09:18 AM
|