Latest Contributions by EricEagle

In ArcGIS Pro (2.9), I'm doing some processing work based on a mask I derive from the active map view. The processor expects UTM-projected data.  However, it might be that the user has not projected their map project to UTM, so I am trying to catch and handle that in the flow.  Right now my code looks like this: d = arcpy.Describe(raster_in) r_in_sr = d.spatialReference # Make sure data is not unprojected or in common GCS if r_in_sr.factoryCode in [4326, 3857, None]: raise ProjectionException("Input data not projected. Please ensure all inputs are projected and retry.") # Make sure the active map is set to same spatial reference as input layer p = arcpy.mp.ArcGISProject("CURRENT") m = p.activeMap m.spatialReference = r_in_sr # successfully switches active map coord system! # Now get the view extent view_extent = p.activeView.camera.getExtent() arcpy.AddMessage(view_extent) # Yields GCS Lat/Lons, not UTM! extent_poly = arcpy.Polygon( arcpy.Array( [ view_extent.lowerLeft, view_extent.lowerRight, view_extent.upperRight, view_extent.upperLeft, view_extent.lowerLeft ] ), spatial_reference=r_in_sr ).projectAs(r_in_sr) # neither of these sr's do anything, I still get GCS lat/lons mask = arcpy.CopyFeatures_management(extent_poly, os.path.join(scratch, "mask")) # scratch is arcpy.env.scratchGDB   The interesting thing here is that if I START the process with a UTM-projected active map, the whole thing works fine.  I get extent coordinates in UTM. If I start the process with a common GCS, the script does set the active map to a UTM coordinate system.  But nothing I do seems to coerce the Polygon object to UTM: it still reports GCS Lat/Lon coordinates.  Therefore when I call 'mask' on UTM-projected input layers, it throws an error and tells me the extent is wrong. The amusing thing is, that if I simply re-run it after that, the script starts out with the active map in the UTM projection set from the previous attempt, and runs fine. This feels like a bug, but I could definitely be doing something wrong, so I thought I'd check with the experts before I file it with our customer rep. ... View more

Hi, I need to create a memory featureclass from a JSON file (Esri). My code looks like this: json_out = f"C:/Temp/feats_{datetime.strftime(now, '%Y-%m-%dT%H%M%S')}.json" with open(json_out, 'w') as outfile: outfile.write(str(feature_set)) # feature_set is validated Esri JSON # The JSON file loads fine and the conversion works # without issue in the ArcGIS Pro GUI when writing to a file geodatabase. new_fc = arcpy.JSONToFeatures_conversion(json_out, r"memory\temp_fc") This yields arcgisscripting.ExecuteError: ERROR 000206: Cannot create FeatureClass 'memory\temp_fc'. I've tried giving it a geometry_type (unnecessary, it's EsriJSON) with no change. Ideas? ... View more

When I do this in python:     p = arcpy.mp.ArcGISProject("CURRENT") arcpy.env.workspace = p.defaultGeodatabase d = p.defaultGeodatabase arcpy.env.overwriteOutput = True # abbreviating here - "inlyr" is a layer that has been gotten in a GetParameter() call original_name = inlyr.name utm_out_name = (original_name + '_UTM').replace(".","_") utm_out = os.path.join(d, utm_out_name) out_layer = arcpy.management.Project(inlyr, utm_out, arcpy.SpatialReference(32638))     this gives me:     Traceback (most recent call last): File "M:\Temp\arcstuff\utm.py", line 246, in <module> out_layer = arcpy.management.Project(inlyr, out_layer, arcpy.SpatialReference(32638)) File "C:\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 13216, in Project raise e File "C:\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 13213, in Project retval = convertArcObjectToPythonObject(gp.Project_management(*gp_fixargs((in_dataset, out_dataset, out_coor_system, transform_method, in_coor_system, preserve_shape, max_deviation, vertical), True))) File "C:\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 512, in <lambda> return lambda *args: val(*gp_fixargs(args, True)) arcgisscripting.ExecuteError: ERROR 000210: Cannot create output M:\Temp\ArcGIS\Projects\MyProject\MyProject.gdb\osm_roads_UTM Failed to execute (Project).     When I run Project() on the data directly, using the same exact parameters (not scripted), it also fails! However, when I redirect the output to a shapefile in another directory (same NAS), it succeeds. Why is this?  How do I get more specific information to figure out why it is refusing to write to the default project geodatabase? I am able to create feature classes in the same .gdb (including via python) in the same session, so there is no permissions or lock issue that would seem to be at fault. Version: ArcGIS Pro 2.9 UPDATE: the input layer is from a GeoPackage.  Not sure why that should matter, as it's an open/broadly compatible format. ... View more