Latest Contributions by JCann

Running ArcGIS Pro 3.1.3 on a computer with an i7 hex core, Nvidia Quadro P2000, 32 GB of RAM, with all data stored in a mobile geodatabase on a Samsung 970 except for the World Imagery. The map has been clipped to a polygon to improve loading time. The network connection is 950 MBs. I am trying to build very simple 3 keyframe animation that zoom into a polygon, a.k.a a Google Earth-style animation that I had hoped would be reproducible for editing purposes. Length is flexible, I have tested 15-30 seconds. I had hoped to use the visibility settings to have the polygons appear at different levels of zoom as the animation zooms in, which does not appear to be possible. In the first screenshot, the highlighted polygon has the "Out Beyond" visibility set at 5.5 million feet, the animation was paused at 2, 582,910 ft, and the polygon is not visible. The only way to make it visible is to go to the "Out Beyond" box and re-enter the visibility setting. In this screenshot, it is the opposite issue of the first screenshot. The highlighted polygon is set to an "Out Beyond" visibility of 750, 000 ft but is showing up in the animation at over 1.5 million ft. This is also not a consistent issue, sometimes it works as expected with all visibility settings being honored. I have experienced this with multiple polygons, tested in three different projects, and made multiple local and global scenes. I am also seeing an issue where the visibility settings are honored in an export as a draft, but the visibility settings are non-existent in an export as 1080p, with all polygons being visible from the beginning to the end. Do I not understand how visibility settings interact with an animation? I have not found an in-depth discussion on how visibility interacts with an animation.  Is there a better way to do this or any way to do this in ArcGIS Pro?  I need to make multiple animations, one of which will be a fly along a project area with community points appearing as it moves along the area. ... View more

I have a Notebook that I have been working on for  more than 3 months. I have a persistent, intermittent issue affecting multiple variables in the notebook. It does not happen every time it is used, sometimes it goes weeks without issues, other times it will not run at all, throwing random errors constantly. The notebook uses multiple functions, two of which are below. The set_time( ) function runs without issues as does the get_hosted feature(gis) in other scripts and projects. Output from set_time( ). The issue that comes up is when "today" is called as a parameter a couple of cells down. It will randomly throw an error 'missing 1 required positional argument: today' despite the set_time ( ) cell having been run. It gets more perplexing because there are three cells that use 'today' as a parameter in a function and there are times when the first two cells run and the third does not, throwing the same error. This has also happens with the cal_ipmt_dc variable and a couple of other variables cause the the same intermittent, none of the cells, or some of the cells that use it throwing errors. The most recent test was to modify the functions that used 'today' and put just the code from set_time( ) in each of the functions that used 'today' and remove the parameter. The first two functions ran to completion, third function threw the error 'datetime does not exist', which obviously had to be imported, and was imported in the first cell, in order for two of the three functions to run. But two hours later, a restart of the computer, and of VS Studio Code, all three functions ran fine. This Notebook is being used by other people, hence using functions to create a cleaner Notebook. The other users do not want to mess with waiting, restarting everything multiple times, etc.  for the Notebook to randomly decided to start recognizing variables again. This is happening from both ArcGIS Pro 3.1.2 and VS Studio Code, across multiple computers, and multiple internet connections at differing speeds. Any thoughts or suggestions would be appreciated, I really do not want to have to strip out all variables to make this Notebook more reliable.     ... View more

Has anybody had the opportunity to run ArcGIS Pro 2.9.2 on a Dell 3570 laptop with a 12th gen, i7-1275U, 2 “big”, 8 “LITTLE” core CPU, 32 GB DDR5, and an Nvidia T550. I am coming from a Dell 7550 with an i9 8 core, 64 GB of ram, and an Nvidia T2000.  This is for work and and the 7550 was also a preselected work computer with same agency, so big change in specs that was suddenly announced.  I have no say in the process, but I am wanting to know how ArcGIS Pro runs on a system like this for all manner of task; from simple editing, raster work, processing point clouds, etc. Any insight would be welcome.  ... View more

I am currently running ArcGIS Pro 2.9.1 on my personal computer and ArcGIS Pro 2.9.1.179945 on my work computer. The geoprocessing Flow Accumulation tool is producing a very different output from the Arcpy based tool (and from the Flow Accumulation output that was generated for the project in 2.8.X, the project has spanned 2.8.X to 2.9.X). This is occurring on both computers, which have entirely separate installations of ArcGIS Pro and have had the DEMs downloaded to each, not transferred between the two. The first screenshot is the output from the Arcpy based tool, (purple lines). This output matches the previous output generated in 2.8.X. The filled DEM, flow direction, and flow accumulation in the first screenshot were generated using Arcpy The second screenshot is from the Flow Accumulation geoprocessing tool(red lines). The "missing" lines are not isolated to one section, the gaps occur across two mosaiced DEMs downloaded from USGS 3DEP (converted from .tif to geodatabase raster and projected to NAD 1983 2011 UTM Zone 10 N). The Flow Accumulation in the second screenshot used a Flow Direction Raster generated in the Geoprocessing toolbox from the same filled DEM that was used in the first screenshot and the same threshold (3000). I have also replicated this with a clip of the mosaic, on both individual DEMs before mosaicing, and on a Topo To Raster generated from a single DEM (I have also re-downloaded the DEM's re-ran just to be sure). I also tested the Watershed Tools in Raster Functions and was able to get a "correct" output, but after I ran those tools, Pro crashed and is failing to initialize (work computer, whole other issue) Has anyone else run across this recently? Is this an issue with the geoprocessing tool, or am I just missing something? Output from Arcpy   Output from Geoprocessing Toolbox   ... View more

I have not found anything on this issue, and it is not easy to search for. I have a Python Toolbox that has multiple, user-selected feature class inputs with each feature class input having 3 or 6 dropdowns for values. The tool is set up so the feature class inputs are optional and each value input is optional, basically, the user can choose to include a feature class and include 1 to 6 values from that feature class. This setup was as per the requester, so I am trying to maintain it as close as possible.  As the title says, I am having values "disappear" after selecting the value; I click on the value, it shows in the box, and then resets to zero or none, depending on the box. This is behavior is occurring on features with 6 values; with values 1 and 2 working properly and 3-6 showing then disappearing after selection. I am not seeing this behavior on 3 value features, all three dropdowns work as expected. I have the dropdown values hardcoded in the toolbox and have copied a portion of the script into a new toolbox and tested auto-populating dropdown values from within def updateParameters(self, parameters). Dropdowns populate correctly but exhibit the same behavior as the hardcoded ones. I have attached two short screen captures. Geocapture is from the complete toolbox showing a three value feature with no issues, and a 6 value feature with "disappearing" selections. Geocapture2 is from the test-toolbox and auto-populates the values based on the feature and exhibits the same behavior. Please note, the screen capture videos did not capture the dropdown boxes popping up. The block of code starting with "params13" is from the complete toolbox. I did not post the entire script as it is around a thousand lines long. The second block of code is from the test-toolbox using auto-populate. I think this is a recent occurrence, possibly after 2.6 came, out because this was written and tested back in May and June and was working and has cropped up in the final testing and editing. Any ideas on where to go from here or possible fixes would be most appreciated. I am guessing it is something simple and I am just missing it. params13 = arcpy.Parameter( displayName="Vegetation Feature Class", name="inVegfeature", datatype="DEFeatureClass", parameterType="Optional", direction="Input",) params13.value = None # First Input params14 = arcpy.Parameter( displayName="First Vegeation Class", name="veg1", datatype="GPDouble", parameterType="Optional", direction="Input") params14.value = 0 params14.filter.list = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76] # Second Input params15 = arcpy.Parameter( displayName="Second Vegetation Class", name="veg2", datatype="GPDouble", parameterType="Optional", direction="Input",) params15.value = 0 params15.filter.list = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76] # Third Input params16 = arcpy.Parameter( displayName="Third Vegeation Class", name="veg3", datatype="GPDouble", parameterType="Optional", direction="Input",) params16.value = 0 params16.filter.list = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76] # Fourth Input params17 = arcpy.Parameter( displayName="Fourth Vegeation Class", name="veg3", datatype="GPDouble", parameterType="Optional", direction="Input",) params17.value = 0 params17.filter.list = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76] # Fifth Input params18 = arcpy.Parameter( displayName="Fifth Vegeation Class", name="veg3", datatype="GPDouble", parameterType="Optional", direction="Input",) params18.value = 0 params18.filter.list = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76] # Sixth Input params19 = arcpy.Parameter( displayName="Sixth Vegeation Class", name="veg3", datatype="GPDouble", parameterType="Optional", direction="Input",) params19.value = 0 params19.filter.list = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76] ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ # -*- coding: utf-8 -*- import arcpy class Toolbox(object): def __init__(self): """Define the toolbox (the name of the toolbox is the name of the .pyt file).""" self.label = "Toolbox" self.alias = "" # List of tool classes associated with this toolbox self.tools = [Tool] class Tool(object): def __init__(self): """Define the tool (tool name is the name of the class).""" self.label = "Tool" self.description = "" self.canRunInBackground = False def getParameterInfo(self): """Define parameter definitions""" # Geology Class Feature Class Parameters params0 = arcpy.Parameter( displayName="Geology Feature Class", name="inGeofeature", datatype="DEFeatureClass", parameterType="Optional", direction="Input",) params0.value = None # First Input params1 = arcpy.Parameter( displayName="First Geology Class", name="geo1", datatype="GPString", parameterType="Optional", direction="Input") params1.value = None # Second Input params2 = arcpy.Parameter( displayName="Second Geology Class", name="geo2", datatype="GPString", parameterType="Optional", direction="Input",) params2.value = None # Third Input params3 = arcpy.Parameter( displayName="Third Geology Class", name="geo3", datatype="GPString", parameterType="Optional", direction="Input",) params3.value = None # Fourth Input params4 = arcpy.Parameter( displayName="Fourth Geology Class", name="geo3", datatype="GPString", parameterType="Optional", direction="Input",) params4.value = None # Fifth Input params5 = arcpy.Parameter( displayName="Fifth Geology Class", name="geo3", datatype="GPString", parameterType="Optional", direction="Input",) params5.value = None # Sixth Input params6 = arcpy.Parameter( displayName="Sixth Geology Class", name="geo3", datatype="GPString", parameterType="Optional", direction="Input",) params6.value = None params = [params0, params1, params2, params3, params4, params5, params6] return params def isLicensed(self): """Set whether tool is licensed to execute.""" return True def updateParameters(self, parameters): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parameter has been changed.""" if parameters[0].value: with arcpy.da.SearchCursor(parameters[0].valueAsText, "GLG_SYM") as rows: parameters[1].filter.list = sorted(list(set([row[0] for row in rows]))) if parameters[0].value: with arcpy.da.SearchCursor(parameters[0].valueAsText, "GLG_SYM") as rows: parameters[2].filter.list = sorted(list(set([row[0] for row in rows]))) if parameters[0].value: with arcpy.da.SearchCursor(parameters[0].valueAsText, "GLG_SYM") as rows: parameters[3].filter.list = sorted(list(set([row[0] for row in rows]))) if parameters[0].value: with arcpy.da.SearchCursor(parameters[0].valueAsText, "GLG_SYM") as rows: parameters[4].filter.list = sorted(list(set([row[0] for row in rows]))) if parameters[0].value: with arcpy.da.SearchCursor(parameters[0].valueAsText, "GLG_SYM") as rows: parameters[5].filter.list = sorted(list(set([row[0] for row in rows]))) if parameters[0].value: with arcpy.da.SearchCursor(parameters[0].valueAsText, "GLG_SYM") as rows: parameters[6].filter.list = sorted(list(set([row[0] for row in rows]))) return def updateMessages(self, parameters): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return def execute(self, parameters, messages): """The source code of the tool.""" return‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

I have not encountered this issue before, and after a month, I do not have a solution. This a snippet of a larger, predictive model. This is one, of two feature classes (there will probably be more added), each has a small python script to eventually allow for a drop-down list when used as a tool. There are also three raster layers (so far), with two variables each, that use scripts and do not have this issue. When I go to  Properties, Tool Properties: Model, "Parameters" is underlined in red, the numbers have been replaced by asterisks, and "Ok" is greyed out. When hovering over an asterisk I get "Parameter Name and DataType are required". This leaves me with a model that I cannot make changes to, including creating the drop-down list that I need to create. I have tried setting Data Type as feature class and feature layer, I have tried setting Type to Optional and Required, I have tried saving to memory\ (the preferred option) and to the gdb, and I know that it validates, runs, and adds to the map. I have tried searching for this, but have not found anything that specifically addresses this issue. Also, the final tool must consist of fill in the blank or drop-down list with no build an SQL query in the tool interface. ... View more

I have been trying to write a simple script to append features (currently using ArcMap 10.6) that were created in a "working" file gdb to a "master" file gdb. The feature classes have the same fields and are both in feature data-sets. The "master" generally resides on an office wide server while "working" is local. Where it goes wrong is the stand alone script copies all features in the feature class, not just the selected features. Append honors selected features when run from python in ArcMap and from the GUI tool. Also experiencing the same issue if I create an append model.  What I have tried: "NO_TEST" and "TEST", setting the "working" gdb as the work-space, placing the file pathways directly into Append_management, placing a copy of the "master" onto my computer. I have even tried creating temp gdbs, one with the "working" feature class and one with the "master" with no change.  Going to test this on a different computer that has ArcMap 10.7 and in ArcGIS Pro 2.3 (can't use this computer at work though) and see if I can replicate it. import arcpy in_feature = r"C:\\\\Working_GDBs\Central.gdb\Lands\Disposals" out_feature = r"C:\\\\Master_GDBs\Central.gdb\Lands_Master\Lands_Disposals" schema = "TEST" arcpy.Append_management(in_feature, out_feature, schema, " ", " ") print("Append Completed")‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more