Latest Contributions by VinceE

I'd prefer ArcGIS Pro not decide what transformations are best to apply, and would like to receive the same warning that I did in ArcGIS Desktop when adding data of different coordinate reference systems. Is there a setting somewhere to turn off the automatic application of the first transformation from Esri's dropdown list. I'd prefer to force the user to manually go in and set one. It appears possible to toggle a warning message that a transformation has been automatically applied, but not prevent the transformation from being applied in the first place. This is particularly relevant when transforming between various realizations of NAD83 within a specific state, where the first choice is often a generalized transformation involving WGS84, versus a state-specific grid-method that is superior. ... View more

I'm having issues using arcpy and spatial analyst functions. The workspace environment seems to get selectively ignored. I am running this code directly in the Python window in ArcGIS Pro 2.5.1. The behavior appears the same in an existing project versus a brand new unsaved project. import arcpy as ap from arcpy import env from arcpy.sa import * testing = True env.workspace = r"C:\Users\Desktop\Prop\Prop_Slope.gdb" dem = r"F:\5_Tools\SlopeClass\AARM.gdb\DEM_AOI" demfs1 = FocalStatistics(dem, "Circle 5 CELL", "MEAN") demfs2 = FocalStatistics(demfs1, "Circle 5 CELL", "MEAN") demfs3 = FocalStatistics(demfs2, "Circle 5 CELL", "MEAN") #with arcpy.EnvManager(workspace = env.workspace): Contour(demfs3, "Contour", 10, 0, 1) remap = "0 19.999 1;20 49.999 2;50 10000 3" rclass = Reclassify(demfs3, "VALUE", remap, "NODATA") #with arcpy.EnvManager(workspace = env.workspace): ap.conversion.RasterToPolygon(rclass, "Reclass_Polygon", "SIMPLIFY", "VALUE", "SINGLE_OUTER_PART") if testing: demfs1.save("FS1") demfs2.save("FS2") demfs3.save("FS3") rclass.save("Reclassified") del demfs1, demfs2, demfs3, rclass‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ The code itself executes without a hitch, however the outputs get saved in different locations. Calling the .save() method on the returned raster objects will create permanent saves in the location specified in "env.workspace". However, both the outputs of "Contour" and "RasterToPolygon", get saved to the Default geodatabase for the project (either a named default, or just the "Default.gdb" in an unsaved project). Using the currently commented-out "EnvManager" and "with" blocks corrects this problem. Why does it appear necessary to explicitly define the workspace for these tools, when I have already done it globally at the top? What aspect of the workspace environment am I missing? Perhaps the use of spatial analyst tools here is coincidental, but it's when using these tools that I tend to experience strange behavior with the workspace environment. Any help would be greatly appreciated. ... View more

This is a similar issue another user posted (with nearly the same title), however this is occurring in Pro v2.5.1, and my experience with the "Save" button is slightly different. Original post about a similar issue: Unable to Save Contingent Values in ArcGIS Pro 2.3.0  To address some issues that came up in that thread: I have an Advanced License, there are no subtypes involved here (should there be?), and I am not currently editing anything (same experience in a fully loaded map vs. a new, unsaved project). My issue is that I am able to add new contingent value "pairs" using the drop downs in the Contingent Values window, and can then hit the save button, however upon "saving," they are just removed and I am left with a blank list again. I am not getting any error messages or warnings, and the colored indicator square in the table is green. The general setup: I have two fields in the field group (both TEXT type) from the same feature class. Each of the two fields has a unique domain, both of which use Coded Values. Both of the fields do not allow NULL values. While creating new features, I can successfully set the values for both fields, from their respective domains, and then proceed to create the feature. I have tried setting up the geodatabase, feature class, fields, domains, and the grouped fields for the contingent values using arcpy, and also doing the whole thing manually in the GUI, both to no avail. Everything else up to this step appears to work just fine. I have not tried adding the specific contingent value pairs using arcpy, but my feeling is that I'm doing something incorrectly before the adding values part, so I'd like to figure that out first. Not entirely sure I understand the setup for the CSVs to be used in the arcpy/geoprocessing tool either. As a side note, if anyone has a link to examples of what these look like, that would be helpful. I can't quite decipher how these are set up from the help docs. First image shows the CVs added, second image shows them disappear immediately after save. This is coming straight out of "Focus on Geodatabases in ArcGIS Pro" (2019) if the field group, fields, or individual CVs look familiar. Thanks in advance if anyone has ideas. UPDATE: Adding via arcpy does seem to work. Interestingly, once one has been added, doing it manually via the GUI seems to allow saving as well. This probably solves my issue, but I'd be curious if others have the same problem. ... View more