Latest Contributions by DrewFlater

‎03-27-2020

I would guess it is internet explorer that is out of date (yeah might be OS too). IE-based browser is embedded in several places in the app, including this initial sign in screen for your home use ArcGIS Online licensed account. The javascript errors Dan Patterson‌ mentions are old ArcMap errors that occurred when opening a geoprocessing tool, as in ArcMap days all tool dialogs were html forms.

‎03-25-2020

To me, this looks like you probably got an error the first time you started the app while it was creating the geoprocessing cache. The causes for this are often that the Python environment you are using needs to be recloned or just switch back to the default environment and restart the application. When the cache cannot be built, all of the tools that run in Desktop mode (on your local system) will not show up in the GP pane. Only the tools that run remotely in the cloud or in your connected portal will show up, evidenced by all those hammers with cloud icons in your search results.

‎03-25-2020

Peter MacKenzie‌ did you set the environment in the Python window via arcpy.env.maintainAttachments = False, and then run the tool through the Geoprocessing pane UI? Once the project environments are established, changing the arcpy.env does not impact the environment settings for your project or the tools run in the Geoprocessing pane UI. You can think about it as a one way street - the environments set in the project are automatically derived into arcpy.env, but changes in arcpy.env don't flow up to the project environments. This could be a reason why the tool is stuck at 100% for a long time - the maintain attachments setting never got disabled for tools run in the Geoprocessing pane UI. Transferring attachments is a post process of creating new relationship classes and transferring potentially large amounts of binary information in blob fields into a new table in the geodatabase. The progress bar accounts for the feature transfer, but not for the attachment transfer which is a much less deterministic process, as each attachment can be a different size and require more or less processing time. Dan Patterson‌ had a hunch about that output named g.gdb\_1 -- the geodatabase does allow this name, and I could successfully run CopyFeatures with an output named _1. Russell Brennan‌'s suggestion about Fiddler would help to debug if queries are still being made to the service or if things are stuck on the client side for a long period of time. Working with Esri Tech Support would help to do some of this troubleshooting for you.

‎03-25-2020

It likely depends on the processing that the tool is doing, your inputs and outputs, number of fields, if you've asked the tool to transfer domains and subtypes, if an expression is being applied, etc. (this tool can do a lot). I ran the most vanilla Table to Table I could find, moving 1million records from a feature class to a file gdb table, and the progress bar is quite smooth. Based on your images, the progress bar is definitely not ideal in your case, it would be great if you could work with Esri Tech Support for them to understand your case and get it to development for improvement.

‎03-25-2020

Specifically, I imagine, the Processing Extent (or potentially the raster analysis mask for raster tools)? I just tested Calculate Geometry, and it isn't impacted by the extent (and is documented as such), though many tools will be so your comment is definitely valid.

‎03-24-2020

And double check that your layer doesn't have a selection, definition query, etc that limits which records are processed by the geoprocessing tool. You can switch, instead of using the layer as input, browse and select the feature class on disk so you know you are working against the full dataset. Aside from this, I don't see any reason the tool shouldn't work to calculate the values. Dan's comment about tech support with your data is the best thing.

‎03-23-2020

Marjorie Jerez‌ This issue has been resolved in Alpha snapshots of ArcGIS Pro 2.6. The issue is due to loading new records into a shapefile and that shapefiles do not automatically recalculate a new spatial index/extent that includes those new features. As a temporary workaround you should be able to run the Add Spatial Index (Data Management) tool against the shapefile to get the shapefile to draw correctly.

‎03-18-2020

Dana Thompson‌ Ted Hallum‌ can you explain the versions you are using of ArcGIS Pro and ArcGIS Enterprise? The only case where I have seen this happens if if there is a tool inside of your script or model that has a fundamental change in Pro that isn't available in Enterprise. For example, say a new parameter was added to one of the tools in Pro 2.5, if you are publishing to an older version of Enterprise such as 10.7 it will have no knowledge of that new parameter and problems will ensue. Analyze does have checks for new tools and new parameters, but sometimes changes are more subtle and slip through the cracks. There are also some basic compatibility rules between versions of Pro and Enterprise when it comes to web tools: Web tool compatibility—ArcGIS Pro | Documentation . If either of you would be able to provide your model/script with a sample of the data you are using as input, we can try to debug the problem further. Email [email protected] , I can get you set up with a cloud share to upload data if it is too big to email.

‎03-18-2020

There are multiple things going on here. Natalie Robbins‌ correctly identified she had a custom Python toolbox in the system toolbox directory, and that ENVI toolbox likely didn't have the correct libraries to work with the updated ArcGIS Pro 2.5 Python environment. Installing 3rd party toolboxes into your system toolbox directory can have these negative effects when moving between Pro versions. William Mayr‌ had you previously cloned and made a custom Python environment? Environments need to be repaired or re-cloned when updating versions of ArcGIS Pro. The Intelligence Tools PYT toolbox is not the problem, that just happens to be the first Python functionality that the application is trying to load, as the system loads all the system toolboxes alphabetically (that is alphabetically the first toolbox in the system toolbox directory built with Python). Removing that PYT will just make the next one in the system toolbox directory fail. You have an underlying Python environment problem that must be remedied to proceed. You may want to contact tech support if none of this Python environment stuff that I mentioned applies to you

‎03-18-2020

Hi Rickey Fite‌, The mean is an area-weighted mean of those four buildings. The building that has the most overlap will contribute more towards the mean. Based on your pictured values and the output mean value it is very hard to tell if the value is correct, there just isnt enough information. We need to know the area of overlap between the highlighted circle and each building that intersects it, then we weight those buildings values by how much of the total overlap they contribute. If you want me to double check the match and send you the results, send a sample dataset to [email protected]. The mean WILL NOT be the average of (35.33333+46.5+44.83333+38.66667)/4. Doing an average like this throws away the spatial component of the analysis, since each of those buildings spatially overlaps the highlighted circle different. If you want a simplified result that does the basic average I just described, Spatial Join can accomplish it using a MEAN Merge Rule. Spatial Join—Help | Documentation

‎03-18-2020

Dan Patterson‌ I just reviewed that tech support bug and the case logged is non repro in current Pro versions. The weighted mean computation appears correct. Here is the math I used for the black border polygon summarizing the two colored polygons inside it. The mean Score calculated for the output is based on the ratio of overlap between the two summary features. The yellow feature accounts for 95% of the total overlap, so the weighted score will be much closer to that value. The orange polygon has a higher value, but only accounts for ~5% of the overlap, so it just nudges the mean value up a little.

‎03-18-2020

Multiple field names can be given in a Python list: ["FIeldA", "FieldB", "FieldC"]

‎03-10-2020

Thanks for your feedback. We avoid the kind of popups you described in ArcGIS Pro. But I agree it could be more clear that the tool will modify the input dataset, and you may wish to have a visual reminder to enable undo if that is important for you. It will likely be designed as a banner at the top of the tool that can be dismissed at any time, and links to the documentation about tools that modify the input dataset, and strategies for avoiding unintended data modification.

‎03-10-2020

Briana Mercuri‌ there isn't a way to restore one attribute that the geotagged photos to points tool produces. Since you've made changes to the points layer that you want to keep, an acceptable workaround that comes to mine is: 1. rerun the geotagged photos to points tool, which will generate the output including the direction field 2. run Join Field to move the DIrection field from the new output back to your original output point layer, based on the common "Name" or "Path" attribute in the geotagged output feature class. I hope the workaround might work for you! Good luck

‎03-10-2020

David Wheelock‌ you are correct. In Pro 2.5 you need to run your model inside ModelBuilder to see all the verbose messages. We consider the messages from the tools inside the model to be debugging messages. Those standard processing and command line messages do not bubble up when running the model as a dedicated geoprocessing tool. We received feedback that large models delivered too much content with verbose messages due to every tool returning its command line execution syntax plus messages about when each tool started and completed, when the user was really only interested to see that the entire model tool completed, or warnings and errors. Those detailed verbose messages are important for some situations like debugging the model or profiling the performance, in which case you can run inside the model debugging environment - ModelBuilder - to see those messages.

Online Status	Offline
Date Last Visited	‎05-20-2026 01:10 PM

My Ideas

Latest Contributions by DrewFlater

Re: Script Error ArcPro

Re: Not Finding Geoprocessing tools in ArcGIS pro

Re: arcgis pro geoprocessing tool stuck at 100%

Re: Running a tool in ArcGIS Pro 2.5

Re: ArcGIS Pro - Calculate Geometry just does nothing, but says there is no error.

Re: ArcGIS Pro - Calculate Geometry just does nothing, but says there is no error.

Re: XY Table to Point output shapefile features not showing past a certain zoom in Pro 2.5

Re: Geoprocessing Tool Publishes with no Task

Re: Failed to Load System Tools ArcGIS Pro 2.5

Re: Arcgis Pro - Summarize Within

Re: Arcgis Pro - Summarize Within

Re: ArcGIS Pro Python

Re: How do you force a warning before a field calc outside of an edit session?

Re: Geotagged Photo Direction Field

Re: ArcGIS Pro 2.5: What happened to the "detailed" geoprocessing details?

Re: Can't Sort Table on "Date_Only" Field Type?

Re: View FC geoprocessing history in Pro UI?

Re: FC has symbology and labelling permanently sto...

Re: Why is ArcGIS Pro's Multicore Support Still So...

Re: Pro not exporting all fields of hosted feature...

Wildfire Response GIS