Latest Contributions by AndrewVanWie

Upgrading to ArcGIS Desktop 10.7.1 somehow fixed the issue on the 2 workstations that were affected. I'm not sure what was going on with 10.6. ... View more

Pardon my newbie-ness with Python. Hope this makes sense. Not sure how to change my post from Discussion to Question. I have 8 workstations and users running ArcGIS 10.6. I get the error on only 2 workstations, it works well on the other 6, so that is my confusion. The workstations should be set up identically. After selecting a feature from the "blocks" layer in ArcMap, I run an executable script in the ArcMap Python window that requires parameters for "blockname" and "point density" to scatter random points in polygons at specified density:  import sys sys.argv = ["path_to_script.py", "NXXWXXX", "####"] execfile( "path_to_script.py" ) Then, in my main script "path_to_script.py" I set the layername with sys.argv[1] and sys.argv[2]. Processing is done from source data paths for imagery and features, running arcpy scripts. All layer processing is output to a temporary geodatabase workspace, which is removed at the end. I removed the remaining processing arcpy lines following arcpy.AddGeometryAttributes_management for sake of space since this is where it fails. Everything works right up to it. import arcpy import tempfile def main ( ):    blockname = sys.argv[1]    point_density = sys.argv[2]    arcpy.CreateFileGDB_management(tempfile.gettempdir(), blockname + "_" + point_density)    arcpy.CreateFeatureDataset_management(tempfile.gettempdir() + "/" + blockname + "_" + point_density + ".gdb", "dataset1", "WGS 1984 UTM Zone 17N.prj")    arcpy.env.workspace = tempfile.gettempdir() + "/" + blockname + "_" + point_density + ".gdb"    try:    arcpy.MakeFeatureLayer_management ("blocks", blockname + "_Layer")    arcpy.Clip_management(polygon_features_path, "#", blockname + "_clip", blockname + "_Layer", "#", "ClippingGeometry")    arcpy.Clip_analysis(feature_buffers_path, blockname + "_Layer", blockname + "_buffers")    arcpy.RasterToPolygon_conversion(blockname + "_clip", "dataset1/" + blockname + "_rast2poly", "NO_SIMPLIFY")    qry = '"gridcode" > 35'    flayer = arcpy.MakeFeatureLayer_management (blockname + "_rast2poly", blockname + "_rast2poly2_Layer")    arcpy.SelectLayerByAttribute_management (flayer, "NEW_SELECTION", qry)    arcpy.CopyFeatures_management (flayer, "dataset1/" + blockname + "_export")    arcpy.Dissolve_management (blockname + "_export", "dataset1/" + blockname + "_dissolve")    arcpy.AddGeometryAttributes_management(blockname + "_dissolve", "AREA", Area_Unit="SQUARE_KILOMETERS") ... ... ... if __name__ == '__main__':    main() ... View more

Here's a good one...  I've tried running this process on 6 different workstations now. I had 2 of our 3-year old hp z420's and 4 of our new hp z640's run the exact same process on the exact same dataset, copied locally to each. The process froze on all of the new z640's and the process ran perfectly on the older z420's. Is there an issue with hardware?  I've uninstalled and reinstalled on my z640 workstation. I don't get it. ... View more

I've tried that as well. I've disabled background processing. I've uninstalled 64-bit background processing. My Intel SSD is a secondary drive, so I've also tried running from my primary C drive, which is also an SSD PCIe NVMe drive. This is really driving me crazy!  Is there a processing log that I can access that will tell me where it is crashing? ... View more

Hi Arthur, thanks for the reply. Yes, I've been on your blog lately but have not run through your exact process, as I'm new to footprint extraction with ArcGIS. I'm on a new hp z640 workstation with 6 physical cores hyper-threaded to 12, 32 GB RAM with 1.2 TB Intel SSD 750 Series PCIe NVMe drive. Running ArcGIS Desktop 10.4. My initial dataset was just 4,700 buildings. It freezes at 2% complete. I broke it down to 102, and it freezes at 83% complete. I took that down even further to 2 datasets of 51 features each, and they ran through just fine without freezing. I've tried several more datasets and it seems to not process more than around 70 features without freezing. I've got a case # in with ESRI support and I've done a repair on ArcGIS Desktop. Didn't solve the problem. I sent them my data and they were able to get it to run just fine. I'm running completely local, no network processing. I've also tried running on another workstation and had the same problem. So, I'm wondering if there is some configuration that I'm missing? I've never had any problems with tools before. Andrew ... View more

Not likely. When I group the features into separate feature classes containing no more than 60-70 features, all run through the tool just fine. However, this is not ideal with thousands of features, it should run all through at once. ... View more

Thanks for the reply. Hardware is fairly new workstation Xeon quad core 3.6 GHz. Arc doesn't seem to take advantage of the multiple processors. ... View more

Thanks for the reply. Yes, I've tried that and also arcpy.FeatureClassToShapefile_conversion. They all take the same amount of time. The arcpy seems to take twice as much processing but same output time. With Export to Shapefile I can at least run several instances at the same time (4-5). The arcpy will only allow me 2 before pegging out my processors. ... View more