Select to view content in your preferred language

RegularizeBuildingFootprint fails in arcpy

122
1
02-27-2026 05:07 AM
zminko
by
New Contributor

6 months ago I made a script I ran from VS Code in arcgispro-py3 env. Now all of a sudden the script started printing this error:
Traceback (most recent call last):
File "c:\Users\processdz\python_envs\env_test.py", line 2, in <module>
arcpy.ddd.RegularizeBuildingFootprint(
File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\ddd.py", line 1180, in RegularizeBuildingFootprint
raise e
File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\ddd.py", line 1177, in RegularizeBuildingFootprint
retval = convertArcObjectToPythonObject(gp.RegularizeBuildingFootprint_3d(*gp_fixargs((in_features, out_feature_class, method, tolerance, densification, precision, diagonal_penalty, min_radius, max_radius, alignment_feature, alignment_tolerance, tolerance_type), True)))
File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 512, in <lambda>
return lambda *args: val(*gp_fixargs(args, True))
arcgisscripting.ExecuteError: Failed to execute. Parameters are not valid.
ERROR 000854: The value is out of the range from 0,05 to 0,25.
ERROR 000892: The numeric value is outside of the valid range.
Failed to execute (RegularizeBuildingFootprint).


I can confirm the values itself are correct despite the error code, because the script still works on other computers. Also when I try to run a basic arcpy.ddd.RegularizeBuildingFootprint tool on the non functioning computer through python inside ArcGIS Pro GUI it works perfectly but when I switch to VS Code it fails. Note that multiple people use this computer so something  may have changed in the entire ecosystem that makes the tool fail. I have already tried to clone the base arcpy enviornment and even resintalling ArcGIS Pro but the issue persists. Any ideas on what could be the problem are appreciated.

Kind regards

JB

0 Kudos
1 Reply
RichardDaniels
MVP Regular Contributor
You should check the version of ArcGIS Pro version (to include Service Pack) and Visual Studio Code you have installed on each machine. For VS Code also check and the available resources -look at the version numbers. Most likely a resource is unavailable or needs to be updated on the machine with the problem.
0 Kudos