-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong Delineate Flow Oath #27
Comments
What ArcGIS Pro version are you using? Newer version of ArcGIS Pro might cause issues due to API changes. |
I am experiencing a similar issue with Delineate Flowpath, though instead the error was an ExecuteError: Error00059. See below image. I'm running ArcPro 2.9.3. I'm not sure what other information you need from me? Thanks for all your hard work! |
It seems the recent updates of ArcPy cause the issues. I will look into that next week when I have time. You can try out the toolbox ArcMap version for now. |
Hi, first of all, thank you so much for this great tool for hydrological analysis! Like the others above, I've also encountered the same error - 000539. Furthermore, the subsequent steps don't seem to work either. My version of ArcGIS Pro is 3.1.3. Have you managed to resolve this issue by any chance? |
I've jumped around from Arc 3.2.3 to 3.1.0 and now to 2.9.0 and I still am having issues with this step in the process getting the same error message as @FernandaDavi, @Dorka44 and @wobrotson. My traceback was exactly the same as @wobrotson. I was successful once with 3.1.0 but I can't process steps after #5. Has anyone had any success with this step since they've posted their issues? If so, what was your work-around? Unfortunately you can no longer download ArcMap and I regrettably have uninstalled that from my computer... |
I figured out the issue! If your DEM has a LZ77 compression type or potentially anything other than an LZW, you will run into issues with this step of the analysis. This is true for multiple versions of Pro and the packages used. To change this you must do so in a .gdb. I am still unable to complete step 6 & 7, but I'm thinking the solution may be one similar to this as the traceback has a similar structure/pattern. |
Description
I am running the example you provide in the Lidar folder.
When I run script 3 I get the following error:
Traceback (most recent call last):
File "C:\lidar\lidar\toolbox\scripts\3_Flow_Path.py", line 425, in
FlowPath(in_dem, in_sink, rain_intensity, out_flowpath)
File "C:\lidar\lidar\toolbox\scripts\3_Flow_Path.py", line 303, in FlowPath
code_block="",
File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\management.py", line 4530, in CalculateField
raise e
File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\management.py", line 4527, in CalculateField
retval = convertArcObjectToPythonObject(gp.CalculateField_management(*gp_fixargs((in_table, field, expression, expression_type, code_block, field_type), True)))
File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\geoprocessing_base.py", line 511, in
return lambda *args: val(*gp_fixargs(args, True))
arcgisscripting.ExecuteError: ERROR 000539: File "", line 1
0,05
^
SyntaxError: invalid token
Failed to execute (CalculateField).
Failed to execute (DelineateFlowPath).
What I Did
The text was updated successfully, but these errors were encountered: