Latest Contributions by DuncanHornby

‎03-13-2024

Seems alright to me. Remember a multi-value comes back as semi-colon separated, so first thing I tend to do split it into a list. You can add the following line to your execute function to get an idea of what is returned. arcpy.AddMessage(account_numbers.split(";"))

‎03-13-2024

Your idea is unlikely to get traction. A float raster is typically some sort of surface where every pixel has a different value. Yes you might get areas where there are clusters of pixels with the same value but I would imagine that is an exception rather than a rule. So taking an elevation raster I have at hand it has 6558 cols by 12150 rows. That could very easily end up outputting a polygon dataset with 79,679,700 polygons! Start messing around with lidar derived data and you could end up with billions of polygons.

‎03-13-2024

When you select a feature layer in the Contents pane the Ribbon shows a Data tab for which you can access a variety of tools, a button I use almost hourly is the Attribute Table button that simply opens the attribute table. Yes I know I could have done CRTL+T or right clicked on the layer but the ribbon is what I tend to use. Now an Integer raster typically has an attribute table which I will want to view and interact with it. For example select a row and that selection feeds into the zonal stats tool. The ArcPro user experience is not the same when you access a raster layer, there is no button to open the attribute table associated with the raster. I would like to see an open attribute table button in the ribbon. Happy for it to be greyed out when raster is a float, that makes sense. Now I know I can customise the ribbon and add such a button but for the sake of having a consistent user experience such a button should be part of the default interface, no one should need to be messing around with creating custom groups for a button that gets used by everyone every day!

‎03-13-2024

That is indeed good news..

‎02-28-2024

@ReidHarwood11397 The Export Table tool has had its fields mapping interface much improved with ArcPro 3.2. They have removed the annoying feature of it forcing you to have an OID_ field in your csv file. They have given you much more control over what the field output is and in what order. In the example below I have included back the objectid field to show that you can indeed "put it back" as well as moving it to another position. Or in my user case get rid of it completely. Nice! There is a really good blog you should read - ArcGIS Pro 3.2 Field map enhancements and design updates (esri.com)

‎02-28-2024

I'm surprised you did not observe a reduction in processing time by moving the data into a file geodatabase. May be the shapefiles had a spatial index already built? You can tell this by simply opening up it's attribute table and if you can see a * next to the shape field header then you have a spatial index. Having seen your screenshot and knowing you are talking about millions of polygons which would suggest your dataset is covering a nation, another thing that can cripple performance is having large MULTIPART features that cover the majority of the extent of your data. If that is something you have in your data then another simple performance boosting thing you can do is to convert the data into SINGLEPART. You run your selection tool on those datasets. Just an idea, won't make your PC use all its cores but makes the query significantly more efficient.

‎02-27-2024

You can use this tool to extract the dangling node and then use that as the selecting layer in the select layer by location tool.

‎02-27-2024

Can you explain your data a little more? You seem to be saying that both your farm land and steep terrain polygons are "100m mesh polygons"? What do you mean by that, a picture would be helpful. You also say your data is stored as shapefiles, these are an old format and spatial indexing is something you need to add to the data. But as you are talking in the millions of polygons I would move the data into a file geodatabase, you will get an instant boost in performance. Your PC hardware is pretty high spec so I don't think you can improve upon that.

‎02-16-2024

Your advice is very much appreciated!

‎02-15-2024

I have a general question about best practise with file geodatabases. I'm currently building a file geodatabase which will contain approximately 2,500 feature classes where each feature class will contain 1 million rows (cells from a vector grid created by the fishnet tool). I have subsequently run compact tool on file geodatabase which reduced the database down by approximately 50GB then I ran the compress tool to further reduce data volume. I'm current copying into this database about 400 compressed feature class. This is chuggin' away and taking forever. So my question to the user community is there a sensible number of feature classes one should have in a file geodatabase, after which performance degrades? Are people thinking 2,500 featureclasses in a single file geodatabase, that's a crazy number and not surprised copying into it is taking for ever. Has anyone got any experiences to tell and how they resolved it? An obvious solution is to split out the featureclasses into a set of geodatabases.

‎02-06-2024

David, This is a really interesting answer, a property of parameters I was unaware of. I'm developing a toolbox (the python code is embedding in the atbx) and was wondering if what you suggest can work for a specific scenario. ESRI have have introduced that switch under parameters that take layers\tables with a selection. If the layer has a selection then the switch appears in an on state. Can your technique you show above be used to hide the switch? It causes conflicts with the design of my tools and the code to fail if a user chooses to switch it off. Duncan

‎02-06-2024

I would imagine if ESRI implements this then it would be an option you tick on/off in the options dialog, much like being able to turn off the annoying group outputs.

‎02-06-2024

I too have suggested a similar improvement.

‎02-06-2024

I posted this idea that compliments this idea.

‎01-18-2024

I had considered that approach too as it works just as well, the only "issue" would be that sort creates an output table and the user would need to deal with that (i.e. keep it or delete it). If I had taken this route I would probably have written it to an in-memory workspace. Anyway nice to have shown two solutions for the question!

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by DuncanHornby

Re: How to Handle MultiValue Parameters in Python Toolbox Tool

Re: Raster to Polygon, enable none Integer transfers

Add an open attribute table button to ribbon for rasters layers

Re: Add Pause Drawing function to arcpy

Re: Export Table tool should not create OID_ field when exporting to CSV format

Re: Optimizing the performance of processing task with heavy load overlay analysis

Re: dead end roads, or lines in my network that only intersect once

Re: Optimizing the performance of processing task with heavy load overlay analysis

Re: Any advice/experience with large number of Feature Classes in a File GeoDatabase?

Any advice/experience with large number of Feature Classes in a File GeoDatabase?

Re: Disable "add another" in Python Toolbox

Re: Running ModelBuilder tool in ArcGIS Pro Geoprocessing pane should display detailed logs of each step

Re: Ability to change the color of connector lines in Model Builder

Re: Customize model builder display

Re: ArcGIS 3.0.2: What tool can select the records with the highest values in a particular field?

Re: Wayback imagery and wayback metadata do not ta...

Re: Wayback imagery and wayback metadata do not ta...

Wayback imagery and wayback metadata do not tally,...

Add the ability to clear all selections on all map...

Add start and end symbology to vertices and nodes ...

ArcGIS Arcade

Coordinate Reference Systems