I'm working my way through the Arc Hydro - Support for Hydrologic Modeling.pdf for the purposes of preparing a hydrologic model for input into HMS. For the Generate Node Link Schema script I get several warnings like what I have pasted below. I've ensured I have no unsaved edits in Pro. The Schema Nodes and Links get created but the HydroIDs, DownElemIDs, FromNodeIDs and ToNodeIDs attributes all populate as -2. Has anyone else experienced this and have a fix? I'm currently using ArcHydro Version 3.2.25 on ArcPro version 3.3. Thanks!
L142: ERROR 000496: table is being edited Failed to execute (Delete). ('line 135', 'c:\\program files\\arcgis\\pro\\Resources\\ArcToolbox\\Scripts\\ArcHydro\\apnextid.py', '')
L142: ERROR 000496: table is being edited Failed to execute (Delete). ('line 135', 'c:\\program files\\arcgis\\pro\\Resources\\ArcToolbox\\Scripts\\ArcHydro\\apnextid.py', '')
L142: ERROR 000496: table is being edited Failed to execute (Delete). ('line 135', 'c:\\program files\\arcgis\\pro\\Resources\\ArcToolbox\\Scripts\\ArcHydro\\apnextid.py', '')
Thanks for the response. I have tried closing and reopening the map and ensured there are no edits in need of saving. I've had this error across multiple projects and have had to find workarounds each time unfortunately.
Stefan,
i followed the Use Case 1 approach in the doc and was successful in running the Generate Node Link Schema tool without the errors you reported and all the fields correctly populated. had to do two (and possibly three) tweaks:
1. Create Hydro Network from Catchment generated a warning that "Topology was not enabled". i run "Enable Network Topology" from standard Pro Trace Network Tools toolbox.
2. When running "Drainage Area Centroid" i made sure that the resulting centroid FC was in the feature dataset where all other processed data are (typically Layers in the project gdb). Default output is not being placed there (we'll fix that).
3. Possibly third step is to close Pro and reopen it after running tool "Create Hydro Network from Catchment". Generating trace network sometimes leaves Pro in a "confused" state that closing/opening takes care of.
please try #1 and #2 first and see if that works for you (and then #3 if it does not). if that does not, i'll need a more detailed workflow (e.g. did you use Use Case #2) and possibly the data.
i've been working on the latest Pro 3.4 and AH build, but not sure that should make a difference - we have not tweaked those specific tools in a while. but might be good for you to upgrade your AH version to the latest one for Pro 3.2/3.3.
Dean