I would like to move to Pro and have tried to on and off for several years now,
but each time I do I run into too many obstacles. I thought at first it was just the learning curve and I could push through it, but there is a speed issue. (Without going into specs let me say that my computer is relatively new and with plenty of RAM, video processing and processor speed.) I just did a quick test between ArcPro and Desktop (10.6):
- How long to load an SDE feature class of address point data for the county?
- 20 seconds for the data to load in Pro
6 seconds for Desktop.
- Then how long to apply a definition query to just my jurisdiction?
I could not run the second test in Pro because the Query builder would not seem to take a wildcard statement like:
Jurisdiction Contains the Text '%My Jurisdiction%'.
This is a definition query I use all the time on my data. I have a lot of feature classes that are county wide, but I only want the data for my city. We have a number of parcels with split jurisdiction of 'My City, Other City' or sometimes 'Other City, My City'. So a SQL query of
Jurisdiction LIKE '%My City%'
is what I need. I tried a lot of variations in the query builder in Pro, but none of them worked. I could use
Jurisdiction Contains the Text 'My City'
but that did not give me the split jurisdictions. It looks like it should work, but when I looked through the attribute table none of the split jurisdictions made it through the query. This certainly seems like a learning curve issue except I cannot find an answer online. I know things change, but this should not be that hard.
I have also noticed some of the drawing and geoprocessing issues that Mark Jackson mentioned above. Not as many or as often, because I end up giving up and going back to desktop to get my work done.
I like a lot of the features I have heard about and some that I have tried in Pro. I like having multiple layouts in one project; that is something very useful to me. I often need to make a map in 11"x17" and then a large poster size version as well. Or several pages with the same base area of interest, but with different variations of related data on top.
I was also very intrigued by the ability to create a task work flow in a map document that could be used to guide other staff through a process.
However, on a day to day basis, even allowing for a learning curve, ArcPro ends up frustrating me far more than helping me at this point.
I will keep checking back and hoping for improvements in ArcPro, but for now I am sticking with Desktop.