The other day, I decided to start a list on the whiteboard at work of what ArcGIS Pro would need to have before we would be able to consider adoption of ArcGIS Pro in our current environment.
So here are some disclaimers about our environment. We are currently running with 2 - ArcGIS 10.2.2 Server Enterprise Standard (1 for GIS and 1 for Spillman) and we are currently running 10.3 ArcGIS Desktop. We have not deployed Portal and we are only using ArcGIS Online for our Public Mapping applications that are being fed from Map Services hosted on our ArcGIS Server.
So here is our list of items that we would need in order to adopt ArcGIS Pro
This is just my first pass after about 2.5 weeks of testing our ArcMap workflows against ArcGIS Pro. I am sure that as I play with it more, I will find more things that I miss from ArcMap. But overall, I see ArcGIS Pro as a huge step forward in the walk with Desktop GIS software.
Since I don't want this to only be a rant about what I don't like. Here is a list of features that I love in ArcGIS Pro.
I've started a running list of things Pro can't do that Arcmap can. Among the features that didn't migrate from Arcmap to Pro that I use:
Until then, hard pass.
Steve
Hi Steve,
You bring up some good ones. I doubt however that ArcGIS Pro will ever support personal geodatabases because that was a Microsoft Access database saved as a .mdb. When Microsoft switched their file format from .mdb to .accdb (Access 2007), to my knowledge, they stopped allowing new versions of Access to create .mdb files.
For the export to Illustrator, have you taken a look at ArcGIS Maps for Adobe Creative Cloud? I haven't used it but I know the premise behind it is being able to bring maps into Illustrator.
Data Interoperability extension for Pro can read and write mdb/accdb tables, you'll need the 64bit redistributable here and if Office is on your machine it will need to be the 64bit edition.
Yeah, personal GeoDBs aren't a BIG deal to me since they can be converted to File GeoDBs. Still, I may have a couple floating around that I haven't converted. Anyways, several of the others I listed are larger deal killers. As for the Creative Cloud alternative, I think there's already some sort of limitation with that option (doesn't work with local layers? or something like that).
I'm frankly tired of ESRI's continual pattern of suggesting fundamental workflow changes because they can't be bothered with keeping existing functionality (CTRL-V, Calculate Geometry, etc).
"As for the Creative Cloud alternative, I think there's already some sort of limitation with that option (doesn't work with local layers? or something like that)."
You are correct, the "Creative Cloud" tool only allows you to consume content that is online, not "Local Layers". You can no longer create custom queries of the same local layer for different rendering effects in AI, unless you first take significant time out of your workflow to publish them online.
Ditto, the list is becoming endless... As is my workload from wasting time trialing the app...again. Strike 2
Steve,
This is a nice list. I find myself struggling with many of these same things. The vertices thing drive me nuts, haha!
I was really not liking the copy/paste omission, but somehow I found it. I am not sure if it was added 'recently' or not but it's there. Here is an article on it:
Copy and paste using the clipboard—ArcGIS Pro | ArcGIS Desktop
It's in the Map ribbon toolbar thing at the top:
These suggestions are great and need to be included in the next update of Arc Pro!