Error K2 parameterize group watershed

16 views
Skip to first unread message

Davide Zoccatelli

unread,
Nov 20, 2017, 4:54:20 AM11/20/17
to AGWA Support
Hi,

I'm trying to run a group catchment analysis using KINEROS2. The catchment delination and discretization worked, but when I try to run the parameterization no errors are displayed in the parameterizer window, but the process does not work.
I've looked at the different steps, and I think that the problem is that AGWA creates a feature "elements" with string field "Group_ElementID" that combines the fields "WSgroup" and "ElementID".
The field Group_ElementID is later used for Zonal Statistics but, since the limit for Shapefile field names is 10 characters, the process fails giving a generic error.
Do you think that this could be the problem? If so, what can I do? I've looked around but I couldn't find a way to change ArcGIS settings to make this work.
Thank you,

Davide
Screenshot.png

Shea

unread,
Nov 27, 2017, 2:49:04 PM11/27/17
to AGWA Support
Hi Davide,
I just double-checked and was able to both crash the parameterization and then successfully complete it using a KINEROS2 group watershed. The field length limit for shapefiles is different than that for feature classes in File Geodatabases, which is what the input for the Zonal Statistics tool is, so the Group_ElementID field is not the culprit. 

Instead, I believe there must be a lock on the discretization feature class that is not being properly released when a the Group_ElementID field is added during the parameterization step. This field is added when the first parameterization is performed for a discretization; consequently, subsequent parameterizations on the same discretization will not need to have the Group_ElementID field added and the lock will exist, which allows the subsequent parameterizations to finish successfully. Try the parameterization again on the same discretization and see if it works this time, then report back the result.

Assuming this indeed is the problem, I will try to get this fixed for our for our next release.

Shea
Reply all
Reply to author
Forward
0 new messages