Closed joewheaton closed 6 years ago
Glad to hear you're having a play with VBET down under. @jtgilbert and @wally-mac or @bangen may have better or further ideas then below.
By far, the longest geoprocessing operation in VBET is the drainage area calculation. 2-3 hours for a large area is totally plausible. From what you described, it sounds to me like its actually doing the drainage area calculation fine (for 2-3 hours of chugging away) and then it crashes when writing that to disc? However, here's what comes to mind from what you've provided as possibilities:
"G:\WNRMShared\G4 Corporate Governance\GO4063_NRM Strategy and Dashboard\TPC\Sedimentation\Riparian Zone\VBET_0.2.1\VBET_0.2.1\VBET.py"
is causing the write to disc operation to crash. I would try running the tool not from that horrible burried path on a network drive, but from a local drive (e.g. c:\VBET\MyProject
) and see if it works. If it does you can always move it over to that network path.Let us know if it works.
Never heard back from user...
A User submitted this inquiry:
I am trying to use the VBET tool (using ArcMap 10.6) to derive a riparian zone for the Avon River Basin in Western Australia. I have a 10m DEM and hydrographic stream network but have been unable to get the tool to run. It stalls about 2-3 hours in to the analysis while “Calculating Drainage Area”; the error I get is variations on the one below:
Can you provide any assistance? I have Googled the stuffing out of it and have come to the conclusion that something in the script doesn’t agree with the fields in my stream network. So I tried to run the NHD Network Builder but that didn’t run successfully either. I am very excited by this tool and would love to get it to run.
Regards,