|
IDEA
|
@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)
... View more
02-28-2024
02:41 AM
|
0
|
0
|
2670
|
|
POST
|
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.
... View more
02-28-2024
02:22 AM
|
1
|
0
|
4109
|
|
POST
|
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.
... View more
02-27-2024
04:22 AM
|
0
|
1
|
1437
|
|
POST
|
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.
... View more
02-27-2024
04:09 AM
|
2
|
0
|
4143
|
|
POST
|
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.
... View more
02-15-2024
07:20 AM
|
1
|
3
|
1190
|
|
POST
|
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
... View more
02-06-2024
06:38 AM
|
0
|
1
|
1412
|
|
IDEA
|
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.
... View more
02-06-2024
06:28 AM
|
0
|
0
|
1356
|
|
POST
|
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!
... View more
01-18-2024
02:21 AM
|
1
|
0
|
1492
|
|
IDEA
|
When you use the Delete field tool on a featureclass in a geopackage it throws a 002557 error. My idea is simply to enable the delete field tool to interact with a geopackage table and allow you to delete the field. Improving ArcPro's ability to interact with such data formats will encourage the uptake and hopefully the replacement of a shapefile.
... View more
01-17-2024
10:16 AM
|
1
|
4
|
1371
|
|
POST
|
Without showing your workings, how you run the tool, what the parameter inputs were, it's not possible to answer this question. You need to edit your question and add much more detail. Currently your question is akin to saying my car won't start, and my first response is have you put the key in the ignition?
... View more
01-17-2024
08:40 AM
|
0
|
0
|
1919
|
|
POST
|
Having spaces and characters that are not letters or number is bad practise for folder names and invalid for geodatabase feature classes. You are digging yourself into a big hole, especially if you need to automate processing with model builder and or python. Don't do it!
... View more
01-17-2024
06:41 AM
|
1
|
1
|
2123
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | a week ago | |
| 1 | 12-03-2025 04:30 PM | |
| 1 | 12-03-2025 04:06 PM | |
| 1 | 12-03-2025 04:17 PM | |
| 1 | 12-02-2025 07:05 AM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|