I've been working with various clients to migrate from Map to Pro, and am trying to get an idea of the consensus in the GIS community regarding which one is used more often.
arcpro arcgispro arcgis arcmap arcmap
You should have an option or use both regularly. I use Pro now for any Feature Service, Web Map, etc. design. But if you want to do serious editing you may want to continue to use ArcMap
I'm just curious. Do you have an example of a specific editing workflow that you would prefer to use ArcMap for?
Scott Harris just a small fraction of editing workflows in Pro that are either slower, non-existent, or don't perform the task fully when compared to Arc Map:
Add Mirror Tool in Pro
Stop the ArcGIS Pro table view jumping around when I calculate attributes
See Fields while Scrolling Through Attribute Table in ArcPro
Stop having ArcGIS Pro automatically sort attribute domains when editing
Be able to see an entire cell in Pro attribute tables. Equivalent to ArcMap.
Cul-de-sac tool for ArcGIS Pro
Cut Polygon Tool for Pro. Equivalent to ArcMap.
In ArcGIS PRO allow formal edit sessions for unversioned data in an enterprise GDB
ArcGIS Pro - Add support for geometric overrides
ArcGIS Pro: Add Multi - field Batch Geoprocessing ability such as in ArcGIS Desktop
Create Steepest Path tool missing in ArcGIS Pro
Pro: Holes in Polygons (like Arc)
Thomas and all,
Thomas, great list that I'm going to keep in mind and checkout to familiarize myself with.
I'm a newbie to GIS but I'm already seeing the pros and cons of ArcMap and ArcPro. Is it my level of experience or is it much more difficult to add a field and do a simple calculation in ArcPro? I've found that in ArcMap it all happens within the attribute table while in ArcPro you have to use a separate tool and a couple of other menus.
Thanks for the list . I can speak to some of the Ideas related to editing features::
The others will need to be evaluated by their respective teams.
The split tool wipes all your attributes if you do not want to split policy. The cut tool does not. So I will have to disagree with the "has all the same functionality". I agree a new Cut tool is not necessary if a simple check box is created to allow edits to keep the attributes, as long as the option stays check throughout the current edit process.
Thanks for the feedback Matthew, and we will consider it.
This brings up a few hard questions: What if the GIS database administrator specifically set the data up with a split policy on their domain fields of Default instead of Duplicate? When split, domain fields with this policy will be assigned their default value - *which could be null. Shouldn't the software listen to policies the data admin set up?
*This is the scenario I think you are describing when you say wipes attributes, but please correct me if I'm wrong.
I would just add that although the same functionality *may* exist in Pro, the speed in which these tasks are executed (due to various ui update issues/sluggish behavior) is not the same as ArcMap.
This is an important distinction.
Totally agree, I used both in my day to day work. Sometimes, even if the tool exist in both, one of them wont respond adequately and you need to switch to the other. And it goes either way...
I use Pro for almost all of my day-to-day work - editing in particular is considerably quicker with Pro, plus Layouts in Pro are far superior to Map IMHO
My office is responsible for parcel maintenance for several counties, and we've been unable to fully replicate the parcel maintenance workflow in Pro - due mostly to issues with Attribute Rules in Pro detailed here (Attribute Rules in a versioned GDB with rec/post Python scripts? )
We haven't migrated to Pro as an organization yet but are planning to do so next year. However, we use Data Reviewer and batch jobs heavily which we'll need to continue to create and maintain in ArcMap as that functionality does not currently exist in Pro that I can see. Executing batch jobs in Pro is working fine though in my testing.
Hey there Jonathan Farmer! Looks like you've already found your way over to Having Data Reviewer Batch Job creation in ArcGIS Pro and Python Thank you for that!
Hey Kory, great to hear from you! Yep, already voted so hopefully that helps!
Majority of our organisation are still utilising ArcMap as the majority of our workflows are built with millions of lines of custom code.
As a developer I still use Arcmap/ArcCatalog to manage our in house services built on 10.5.1
All interactions to our Enterprise Portals built in AWS are via Pro as the functionality for this is not in ArcMap.
I am also using Pro for the majority of my development apart from a few things such as having to fix mosaic datasets which sometimes become unreadable by our 10.5 Servers when they have been processed by Pro.
Our legacy system was built with ArcMap, that is why we have to use ArcMap. I try to use ArcPro everyday for few things to train myself to the new soft. However, when we move to the cloud, I doubt that we will have ArcPro hosted because of the hardware requirement. And ArcPro does not keep the Python add-in as I have seen. I do not want to learn .Net or anything else just to migrate our ArcMap python addin to ArcPro.
One more thing, I'm trying to use OrthoMaker in ArcPro but the camera database does not support new drones such as Phantom 4 Pro V2 and Mavic 2 Pro. Sad
For better or worse, I've taken the cold plunge into Pro as it's the "future" of ESRI GIS.
Since moving more into a analysis role vs a feature editor role, I've preferred Pro in some ways for doing analysis. For editing features, 100% hands down, ArcMap. Pro has too many darn button clicks and I wish the Ribbon would stay static like ArcMap and not change when I click on different layers.
Really just give me ArcMap with the ArcPro functions.
As far as I have been able to find - there is no way to manage a SQL server express database in Pro? We have a Server for workgroups license and I think you can only connect to an existing database - but cannot manage it. This pretty much forces us to stick with ArcMap/Catalog
I use Pro for most of my work, and have for years, but Districting for ArcMap is not included in Pro and it REALLY needs to be. I hate using ArcMap and have to all the time for redistricting projects. The similar product, Redistricting for ArcGIS, also doesn't cut it because you can't use your own boundary data and it is subscription based. Please migrate Districting for ArcMap to ArcGIS Pro so I can get off of ArcMap for good!
Make Districting for ArcGIS available in Pro
Thanks...it was actually me who created that idea Please vote it up!
I've tried to move to Pro but it's just missing so much functionality. ArcMap was always 3 steps forward, 1 back but Pro is 4 steps forward, 2 back and 1 dead stop. I couldn't get it to do a simple join in Pro recently, it worked immediately in ArcMap.
We're stuck in a secure enterprise system on 32 bit ArcMap, I'd love to go to the fast graphics of Pro, but I'd never get any work done.
We're currently in a migration phase where several of our clients have cut over to Pro and we are encouraging others to do so as well as fast as we can move workflow customisations over. Of course this is where as Thomas said, there is a performance/feature reason to do so and only where feature equivalency is met.
To that end, I've unpinned ArcMap and pinned Pro to my task bar (I still have ArcCatalog if needed) and also pinned a catalog project in Pro. That way, if I need to do some GIS inspection, light geoprocessing or schema maintenance I'm very likely to just hit Pro, do what I need to do and move on.
The more you use it the more you use it, so to speak.
Given our enterprise hybrid deployment whwre we have Enterprise servers, with both internal and external Portals, standalone application servers and AGOL all integrated, we have to use both ArcMap/ArcCatalog mainly. We also have a number of 3rd Party systems that only integrate wtih ArcMap and the supliers are not likely to change to Pro until it matures a bit more (most are indicating the may look at it during 2021/22). We have started to roll out Pro 2.4 to small select group of users, but it is proving both interesting and frustrating at the same time, especially over performance of some simple tasks like extracting data to say .shp files. In the time that It took pro to think about doing the task, I opened ArcMap loaded the data layer and exported the data and it was only 4500 records. This was done on a laptop runing an i7 processor with 32Gb of memeory as well as a 4Gb graphics card, so not underpowered in anyway.
Performace is key or should be....
On a positive working with layouts and printing/quality of print is so much better than ArcMap
Hi Brian Bumpass
I'm sorry that you're experiencing a performance issue. From the information you provided, I tried to see if I could reproduce a performance problem when comparing ArcGIS Pro to ArcMap. The example you provided was working with 4,500 records, but I had a feature class handy with 63,095 records. It is a simple point feature class stored in a file geodatabase with 40 fields - a mix including mainly Text and Long fields, x and y as Doubles, etc. Here is a screenshot to give a sense of the data.
I exported this to a shapefile in a folder on the same computer's desktop at it took just under 11 seconds. (ArcGIS Pro 2.4.2)
I did the same from ArcMap 10.6 on the same machine, exporting from the same data source to the same directory on the desktop and it took just over 11 seconds. So, about the same.
To troubleshoot performance issues, it can be effective to work with Technical Support. You can contact them here: https://support.esri.com/en/contact-tech-support If you find that there is a reproducible case where performance in ArcGIS Pro is not keeping up when compared to ArcMap, Technical Support is also the most effective way to convey the information needed for development teams to act on the issue. It provides a trackable object (this may be a Case number and a bug number if applicable) that can be referenced in the future.
If you plan to go that route, things that can be helpful are:
Completes in 3 seconds.
Completes in 15 seconds.
In summary, if you are able to report a performance issue to Technical Support, have the following prepared:
If you made it this far, thanks for hanging in there
Hope this helps!
This is my favorite text on effective bug-reporting:
How to Report Bugs Effectively
From that text, this is the most common scenario I see with bugs in Pro being used in a way that the developers never thought of....
"Give the programmer some credit for basic intelligence: if the program really didn't work at all, they would probably have noticed. Since they haven't noticed, it must be working for them. Therefore, either you are doing something differently from them, or your environment is different from theirs. They need information; providing this information is the purpose of a bug report. More information is almost always better than less."
Also from the same text, thus making the entire thing worth the read:
"Users like this are like a mongoose backed into a corner: with its back to the wall and seeing certain death staring it in the face, it attacks frantically, because doing something has to be better than doing nothing. This is not well adapted to the type of problems computers produce. Instead of being a mongoose, be an antelope. When an antelope is confronted with something unexpected or frightening, it freezes. It stays absolutely still and tries not to attract any attention, while it stops and thinks and works out the best thing to do. (If antelopes had a technical support line, it would be telephoning it at this point.) Then, once it has decided what the safest thing to do is, it does it."
Really good stuff in there Thomas Colson! My favorites, in no particular order:
"I think the tachyon modulation must be wrongly polarised."
"Doctor, I need a prescription for Hydroyoyodyne."
Disclaimer: I've never actually seen a mongoose or an antelope. My zoology may be inaccurate.
Thanks for this, I may have not mentioned but this characteristic happens when interacting with enterprise databases such as MS SQL in our case.
I just tried exporting a feature class from a SQL Server geodatabase (~20,000+ features) to a shapefile.
ArcGIS Pro 2.5 (yes, this is a dev build but what I have access to at the moment) took about 30 seconds.
ArcMap 10.7.1 took about 30 seconds.
One thing that I did notice was the first feature class I tried from Pro exported in a bit over 1 minute. Then I went to ArcMap and everything was grayed out. Turned out that I had set up Attribute Rules on that feature class in Pro, thus making the schema unreadable in ArcMap - and of course attribute rules can't be carried into a shapefile, so that might also explain some of the additional "thinking" that the application has to do to translate into a shapefile (that's conjecture on my part...) Once I was working with a dataset usable by both ArcGIS Pro and ArcMap, my results were about the same.
I suppose this wouldn't be the situation you're running into if you're able to export a feature class from both Pro and ArcMap, but maybe there is something specific to the data you're working with. Are you able to share the feature class where you're seeing such a performance delay exporting in Pro? Is the delay reproducible (still occurring)?
I only use Pro. I can hardly remember where to find things/processes in ArcMap now
We have multiple editors. ArcGIS pro only allows one editor at time in the EDGB.
Can you explain this in more detail as I did not think that moving to Pro would not allow multiple editors in an enterprise SDE database?
Did you have a multi-editor enterprise SDE database setup to work with ArcMap in the past?
We have a county wide system and use domains and version editing. The data base is compressed to allow the incorporation of all the edits. This is managed in Oracle on EDBG server setup. We have the pleasure to adopt both Microsoft server, SQL and ArcGisPro for 64 bit during the same fiscal year, and this is a county wide effort. As you can imagine a lot of people are cuing up for single positions. Management is looking for help with this from ESRI.
For analysis ArcMap is more efficient right now, but for cartographic/map production work, Pro is my go-to. Although soon I expect that some of the common tasks in ArcMap will be just as quick in Pro.
For me, Pro is just not as responsive as ArcMap is for most things (Calculate Fields, editing attributes, selecting features, editing features, etc) - theres too much delayed response in Pro (ribbon/ui updates/spinning wheel every time you click something) and it reduces my ability to move as quickly through a set of tasks as I can in ArcMap.
I've been using Pro mostly to see if I can do everything that I need to compared to Desktop. There are some differences that cause me to do an extra step or use Desktop for something that I am unable to do in Pro.
I am pretty new to the world of spatial analysis. I am using R for most of my heavy lifting (computations and creation of interactive visualizations), however I also spend a good amount of time with esri products. I learned ArcMap over a year or two and am now migrating to Pro. If Pro is the new direction, I figure its better to hop on sooner than later. For my use case there is honestly little difference between the platforms.
It seems to me you'd get a more representative result if you made this question visible to other groups, not just the ArcGIS Pro group.
That is true. There are many other places where the poll would be relevant. Like Analysis Network Analyst ModelBuilder Spatial Statistics etc. Many users who participate in those parts of the GeoNet Community may use either ArcMap, or ArcGIS Pro, or both, and it would be insightful to hear about their experiences.
Kory Kramer Dan Gruber I would have loved to share this into multiple locations, but I wanted to keep it general and there are no ArcMap groups in GeoNet. I will definitely share it to those groups you mentioned, but it would have been great if we had a group dedicated to ArcMap as we do with Pro.
Fair enough - maybe we'll see a dedicated ArcMap space at some point in the future...
I've decided at this point to use ArcMap for editing and ArcGIS Pro for cartographic/map production. I attempted to do some editing in ArcGIS Pro and mistakenly deleted a column not a row and could not undo - then spent 5 days recreating the data for that column. So I went back to editing in ArcMap, which for me is much safer. Creating maps in ArcGIS Pro is much easier because of the multiple layouts in one project.
Sorry to hear about lost data. I'm curious - did you mistake the Delete button in the Field group as discussed here: In Arcgis Pro, add setting to hide 'Delete Field' button on attribute tables If so, that button has been removed in ArcGIS Pro 2.5.
I was trying to delete a row and it wasn’t deleting. I had clicked on an attribute within that row and hit delete and the column deleted not the row. Thankfully, it was a column that I could recreate. But had it been the date or one of the other columns I would not have been able to recreate the data. At this point, for me, editing in ArcMap is much easier.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
I've been using both ArcMap and Pro for three years now. While I adore Pro for making layouts, editing attributes is a pain in the neck. So, I still use ArcMap mostly for editing. For geoprocessing, I think both work fine.
Thank you for the feedback. Can you give us some specifics about the trouble Pro is giving you when you are editing attributes?
I only use ArcGIS Pro when I am desperate for something and away from the office. Nearly every time I crack it open I wind up hitting a wall trying to figure out simple things I'm used to doing in ArcMap or it crashes. I can't help but feel like the whole purpose of Pro was to sell more training courses, which upsets me because I already made a big investment in graduate school using ArcMap.
If I need something quick, then only ArcMap. Sometimes, if I need something at all, then ArcMap. Because it simply doesn't go like it should in ArcGIS Pro.
For example, couple days ago (true story, I swear, it is not a joke;)), I needed to copy feature class to feature class, from one database to another. Simple task, isn't it? Well, in ArcGIS Pro it is not so. I tried it, well, four or five times. First, you wait up to ten sec to just open that g...dd...mn geoprocessing window. Then set all things, parameters, from where to where and run. Not so fast. First, that g...dd...mn thing initializes... that takes time. A lot of time. And then, it was 4% on progress bar. And stopped, freezed. Not a thing more than that. Not really freezed, it scrambled something in the background, but no result. Than I shot the program, started again. Once I rebooted the whole machine, you never know... Four or five times played that game. And then, what I did and solved the problem? Of course, ran out my time and nerves and I switched to ArcMap. End of the story, in 30 sec I had everything under the hood. How about that?
And please, don't ask me anybody, what project, how many layers, what a network, OS, how many Volts has current from the wall in my country, if I had blue or black socks on and if I had breakfast or not that day... this is simply ridicilous. This should never ever happen, after all those years of development and being in the wild among consumers. I am not negative or positive, I just say facts.
Many times, I try to do something in ArcGIS Pro, I know, I have to learn it, that is our future (brrrrrr...). But that g...dd...mn waiting for every singl click, THAT makes me nuts, to say the least. And I don't even talk now about work in attribute table, my favorite issue;).
ArcMap is like a rocket, and ArcGIS Pro is a wounded snail.
I have been using ArcGIS Pro primarily for well over 2 years now and I find it extremely interesting the amount of people that refuse to make the switch. ArcGIS Pro definitely has its gripes (as I believe many software products do) but at this point it is far, far, superior to working in ArcMap. Choosing ArcMap over ArcGIS Pro at this point to me is like someone choosing to install Windows XP on a 2019 PC, unless you have proprietary add-ons, plugins or other that many you absolutely must use ArcMap, you are surely being adverse to change.
Retrieving data ...