What is the difference between Arc map calculating an area of acreage that take about 1 to 2 seconds compared to GIS PRO which takes nearly 30 to 50 seconds.
about 29 to 48 seconds.
can you provide any further details on how you're doing this process? i.e., possibly in a field calculator?
I bet your using SQLite/.geodatabase data? There is a performance bug that is likely avoided because of how ArcMap is constructed (Runs in an edit session, Runs on a single thread). We have a partial fix for it for 3.2 if this is the case (fingers crossed on getting to it).
Maybe this could simulate in Pro an ArcMap experience?
If you have any data (descriptions and datatypes are good too) or steps that you would like us to try please send so we can clarify this Idea a bit. (Probably a performance bug)
@PatrickAllen3 This is new to my knowledge.
+@KenGalliher1 @JasonCamerano
I've done a good bit of parcel work as well and used a similar process.
do you get a different result or just different length of time?
For Pro to do the calculation run time just to start the process and then run the acreage calculation takes much more time, same result.
Can you provide the following info:
1. The dbms or gdb type of both the ArcMap data and the Pro data. Is this an enterprise gdb, file gdb or mobile gdb?
2. Is the polygon feature class in a parcel fabric or a simple feature class?
3. How many polygons are being calculated?
Thanks @PatrickAllen3 Reached out, and will receive a .shp file to evaluate further for the performance bug.
- Other notes in our conversation are Some questions about using Locate that I will forward to the team for their evaluation (Forwarding to the team who understands this better).
- Other notes #2, maybe a productivity enhancement for Transect Lines, a clearer case will be sent for evaluation (Will reply back in email on that particular case).