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.
98% of my work is easier, faster, and looks better in Pro. The only real exception I can think of is if I'm doing some cumbersome wading around in attribute tables; in this case, as of the last time I tried, ArcMap's tables are still more user-friendly (related to #2 and #3 on Thomas Colson's list).
I'm actually surprised to see so many people in this thread who still prefer ArcMap for speed, ease of use, etc. Having grown more comfortable and accustomed to Pro, I see virtually none of these issues (although of course results will vary with different workflows/tasks). I just wonder how much of the ongoing frustration with Pro has to do with the fact that, for many, ArcMap is all muscle memory and Pro is not yet.
It's less about muscle-memory and more about memory. In my experience pro is way faster with cpu related processes but when it comes to ram, desktop is more efficient.
Scott Harris, not to mention the fact that there's no way to back out edits for non-versioned data in Pro. This is a fundamental issue and a real show-stopper for many.
Just read the commentaries in the idea and question below:
"Automatically save edits" is disabled, but so are the 'Save' and 'Discard' button. And my edits are being saved
Hi David, I'm not sure what your issue is with editing in Pro. If I accidentally make the wrong edit in Pro, I simply discard those edits and fix the issue. It certainly doesn't save all edits unless you click save.
If users are having edits saved automatically, they should reach out to Esri support to troubleshoot that issue, as it isn't a default function in Pro.
This applies to non-versioned SDE data. It does not apply to shapefiles and file-geodatabases which allow you to cancel edits. Sorry, I was not specific there.
But the problem remains, edits to non-versioned SDE data are saved immediately without asking the user to confirm the save and gives no way to cancel the edit session. It ignores the setting in Options to "Show dialog to confirm save edits". I'm under the understanding that a fix from ESRI is on the way.
Thanks for the feedback. That idea is on our radar.
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? )
I like to edit in Pro, but if you edit a dataset with +30.000 features Pro is gettig extremley sluddish. Not like ArcMap.
I totally agree with Robert. Arc Pro is still in an incipient form and is not ready for "hard-working". It will crash almost all the time and all the stuff Robert had mentioned above. Regarding the number of users that use ArcPro well is big enough since in most of the countries, they now offer support and training exclusively for it and not anymore for desktop.
It is obvious the direction of Esri, but they should consider that the pro version could be used as a unique software only when it will get to maturity (which is not now). Maybe this current is to, fast improve the pro version, but is really frustrating since not everybody is willing to be a "beta" tester and while you want your job gets easy, you have to work harder...
As a user since ArcView 3.2, I can say that I am not really happy with the end-user interface changes that had been implemented in the pro version from nowadays but we will see what's next.
Anyway, keep mapping and happy holidays, folks!
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.
Check out this blog and download about how to leverage the quick access toolbar to have a toolbar similar to ArcMap's standard toolbars within Pro:
ArcGIS Pro: Ribbons, Toolbars, and UI Hacks
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’ve seen the same hesitation to adopt Pro – usually among users who have spent years developing workflows and Toolboxes specific to their needs and tastes. With software that’s as configurable (not to say customizable) as Esri’s products are, it’s not surprising that users develop a sort of proprietary devotion to a set of tools that are in many cases absolutely critical to their job functions.
Your point about Windows XP is well taken, but I don’t think it really fits the current situation with ArcMap vs ArcGIS Pro – there are fundamental differences in performance and functionality between the two platforms that will continue to prevent many GIS shops from adopting Pro – not necessarily out of preference, but out of necessity – until the gaps in functionality are filled.
I like the speed of Pro when using cloud based layers, orthos, basemaps, etc. Map production and design is better in some ways, but massively frustrating in others and that is keeping us from migrating fully. Legends in particular are a huge headache: ArcGIS Pro Legend Options
I've been trying, but I just can't get behind Pro. Doing simple tasks that take seconds in ArcMap require multiple, sluggish steps in Pro, if it even works at all. Editing is much more difficult in Pro and don't get me even started on Legends in Pro... ArcMap is just much quicker and intuitive to use. I also hate the whole Projects deal with Pro... sometimes I just want to open a blank map, add a layer, and perform a quick analysis. But nothing is simple in Pro.
Thank you for the feedback. Can you give us some specifics about the trouble Pro is giving you when you are editing?
One of the more frustrating things I've experienced with Pro and ESRI staff reaching out to the community is when they ask about "the specific issues [we're] having in Pro". Why take a great product and then replace it with something that is only half-baked and then rely on user feedback to make it fully functional?
ArcGIS Pro is a new way of doing analysis. Yes it will have most of the features of Map but it is essentially a new way of thinking. Those new to geospatial science may find a different way of looking at data creation. Then it may not be just about the pretty pictures (maps), but intelligence across the web. ESRI is responsive to its users and may find they have new different ways to use their products. ArcMap is the great platform of the past.
Well david martin, I wouldn't say Jeanette Bachand questions "new way of doing analysis", "intelligence across the web", future and the past of cosmos, I think nobody does it. In case of interest please read her post again. Doing that, pay more attention to the text in quotation marks.
"Half-baked" product has nothing to do with new technology. It is just not so well thought and half way executed. Good direction, but still long way ahead. In my opinion, frustrating for end user is, that this result of now five years of cooking at seemingly relaxed pace (look at how long it takes to get through their funny voting games) meets not expectations a seasoned user of ArcMap has got about every day work on ESRI platform.
The Process is change and requires many iterations of improvements and updates. It has been the same for Windows10. There are many different methods for working towards cloud based solutions and the internet. This includes software security and server based services that have to be allowed for. Performance improvement occurs in time. I just want to imply the benefits. The process is customer based and will always seem half baked.
Change does require iterations and will never be perfect, I agree. You're absolutely right. But releasing a product that is not fully functional is another thing. Also, pushing a product that contains bugs such as deletion of data in a row if it is edited or running a tool and it resulting in a linear network being unregistered is a major problem. Someone else mentioned using Pro is like taking some steps forward but more steps back and that's absolutely true when every release has a bug major enough to force the user to revert to the previous version. There's too much lacking and too many big bugs for me to have trust.
What about those of us who are not going to be using or needing the cloud? The data my department collects is confidential, and we store it on our servers. We will not allow another agency or corporation to store our data.
If I need to produce a project quickly, I use ArcMap. If I have time and no rush deadline, then I use ArcPro. I still need lots of time to figure out where functions and tools are located in ArcPro. The best part of ArcPro is the flexibility to manipulate symbology and text. I can do a whole lot more creative styles in ArcPro than ArcMap.
As a GIS developer I love ArcGIS Pro. But the users in my organization insist on using ArcMap. It may have to do with performance issues.
This is probably the biggest hurdle to getting switched. It is encouraging to see half the votes are Pro, I don't think you would have seen that a year and a half ago!
Perhaps this poll title should be amended to include "...at version 2.4.2", since that's the current version of Pro. It will be useful to redo this poll for future versions, so that we can see how the migration is going.
Also, I agree that there should be a third option for "about the same".
My own usage is that I try to be a good sport and start off with Pro, to see if I can do the job with that. Then, if I can't, I revert to ArcMap and do it there. I recently reverted to ArcMap to do some ticklish editing on non-versioned data because Pro doesn't give you the option to back out your edits if you make a mistake. (For more details, see my comment above in this thread.)
Setting the poll to a specific version would not be particularly useful to me, as many users may still be on versions 2.0 - 2.3, and I'm after general opinions across the entire range of versions for both Map and Pro.
And I didn't put an option for "about the same" because that wasn't my goal for information gathering. Everyone has a preference, and that's what I'm trying to see.
I have replied to your comment about editing in Pro, as I have always been able to back out of edits from Pro by discarding. As I said in that reply, if your edits are being saved automatically, that is not a default feature of Pro (as you seem to think) and you should reach out to Esri support to resolve this issue.
What I find most interesting about this poll, is the number of folks adopting the "replacement" 5 years (almost) after it's release, and the number of people still using the "original". If you had asked how many people were still using Betamax 5 years after VHS, or how many people where still buying cassettes 5 years after CD's. I bet I get flamed by all of you still watching Betamax and rewinding your Doobie Brothers tapes with a pencil eraser...
I still buy cassettes to this day... and the difference is that they were never redesigned 3+ times every year after its release.
My boss often wants me to work on Pro, but to be honest, Map is what I'm used. Map is still more reliable and Pro lacks some basic features like changing the default font for attribute table. I like to have a monospace font for attribute table, so I can spot typos more easily; yet I'm stuck with Arial or whatever in Pro.
I love using Pro. Yes, of course it may take a bit of time to get used to it and change your habits, but once you have tested how easy and quick some of the editing actions are in Pro and how interactive this software is, and then going back to ArcMap makes you feel dreary. Simple operations can now be done very quickly and effectively. As I am a user of both CAD and GIS I am fascinated with editing experience in Pro as it is quite alike now. What I also found out is that with every update in Pro you get better performance. There were quite a lot of issues when I started working in Pro, but recently I can think of hardly any that I had a problem with. Thank you for inventing Pro, I love it
Pro for cartography and maps, ArcMap for everything else. I treat Pro like a photoshop application. After I've done edits and maintenance in Map I spruce it up in Pro. The UI performance is just too slow in Pro right now.
ArcMAP displays labels and data faster
easier to configure hyperlinks
better system for map geek
raster data takes a long time to load
limited to 1 layout view
ArcPRO Incredibly fast display of raster data
multiple layout frames in one map
Better system for computer geek
more complicated process to configure hyperlinks
Labels take forever to load and display
Currently we have a foot in both, with the intention to move along to ArcGIS Pro once our GIS professionals are comfortable with its functionality. Personally, I've been able to migrate many of my arcpy geoprocessing scripts to ArcPro easily, and find working in python 3 both easier and simplier to manage using conda than ArcMap's python integration.
We remain in ArcMap due to some continued missing functionality, in particular around a number of mapping scripts that leverage mxds as templates. Below are a handful of issues in ArcGIS Pro 2.4 that we're still waiting to be solved before we can continue migration:
- Stretch symbology legends do not render correctly (see my post on this here). This is the biggest issue as we do primarily raster mapping and cannot change over until this is fixed.
- The "inspect" tool has reduced functionality compared to ArcMap. Where in ArcMap you could return the pixel values by clicking for all layers, or all visible layers, only the top-most layer value is returned when inspecting in ArcGIS Pro.
- As mentioned above, I can get some strange errors when attempting attribute table manipulation, in particular using calculate fields.
However I try to use ArcGIS Pro for data inspection and other minor tasks, in order to get better acquainted with the layout etc. Our GIS Team enrolled in an online ArcGIS Pro course which has been useful in identifying the similarities and differences between the platforms.
Editing for sure is much easier in ArcMap. Splitting lines for example takes fraction of a second compared to a long time in Pro. Drawing is about the same, but so many little editing tools just seem to have such a lag time associated with them that it's painful and often you have to re-do them several times before they actually work if you are a fast worker like me.
Editing the Attribute Table is also easier in ArcMap as Pro doesn't seem to often let you select and accept domain names all the time.
Pro has locked tool bars that you can only place on the side, top or bottom which is also a pain when you don't want them visible there (guess that's the thing without having the toolbars anymore, but still annoying).
If use Pro as much as possible to get more and more familiar with it, but had to resort back today to use ArcMap after a few months as there's no LRS creation support implemented for actually creating new and editing and changing LRS which I do from time to time. Doing that just today made me realize how much faster editing is in ArcMap compared to Pro.
I'm not knocking all of Pro at all, and somethings are fine, but it seems there's too much fancy things little things that might be slowing down some of the functionality...
I also forgot as I just recalled today is that I forgot Arc Pro can't access and work with Access databases at all, which is a big problem for a certain number of projects that we have that use Access for the front user end form capabilities...
Pete, the ability for ArcGIS Pro to read ESRI Personal Geodatabases is one of the most requested ideas on the ArcGIS Ideas site that has not yet been implemented.
If you haven't already, please go here and up-vote this idea:
Enable ArcGIS Pro to access ESRI Personal Geodatabases
Yeah I've already done that already...
The main reason for me not switching full time is it currently takes roughly 2-3 minutes to copy a polyline feature class (1 record) in ArcGIS Pro. It also takes about the same time to re-name it. In desktop, this process will take roughly 3-10 seconds.
How are you copying? Are you copying one new feature into another using the editing template? Copying a feature class to a new one in a GDB? If so, what sort of GDB, version, storage type? Is the source FC versioned or archived?
Process - Right-click 'Copy' -> 'Paste' (entire Feature Class in Catalog)
Storage - File Geodatabase (Feature Dataset) on Network Attached Storage
Versioned - No
Archived - No
Can you make a copy of the file geodatabase onto a local drive such as C-drive and try performing the same operation in Pro?
I am stuck with ArcMap for now (although learning Pro).
No mention of Geometric networks yet?
The transition to Pro is intrinsically coupled to the transition to Utility Network.
- Pro will not edit a Geometric Network.
- ArcMap will not edit a Utility Network
I can see how moving to Pro is going to cause problems for my group. For the most part they do cartography for reports, and changes to something as different as Pro is going to slow down our workflow. Most of the people in my group are not highly trained in GIS, they've taken an introductory class and I've done the rest of the training. For myself, I find Pro so different, and I honestly do not have the time during the work day to figure it out.
If you haven't taken a look at the quick-start tutorials yet, they're a really good place to start. Each one includes a video that is only a few minutes (or less) so just taking a couple of minutes here and there to watch those might help get familiarized with Pro. Another tip that somebody shared with me is that it's still helpful to just read through those tutorials, even if you don't actually do the exercises. That can take the time needed down to just 5 minutes. Anyway, I've heard positive feedback from ArcMap users who have tried that approach.
Otherwise, there are many other resources out there - ArcGIS Pro Learning Resources - but I understand that it can be challenging to fit more in to a work day.
Thank you, that is good information to know. If the quick start tutorials are in fact just a few minutes here and there, they will be easier to fit in as my workload allows.
I use both depending on what I need to do.
ArcMap:- Data editing- Layout (since all our templates are in ArcMap - there are elements that do not get imported over to Pro so we'll need to fix / redesign our layouts in Pro first)
ArcGIS Pro:- Publishing or editing AGOL layers- working with web map, feature service layers from others- large Image / raster files - load faster than in ArcMap
Both:- Geoprocessing / Analysis - both ArcMap and Pro works fine for what I need to do. Just wondering if the underlying algorithms are the same for both (e.g. Spatial Analyst and 3D Analyst tools). If not, I might have to stick to ArcMap for projects with a long history.
Due to the nature of my job and workload, I have to learn Pro on my own outside of work hours for the most part. This doesn't leave me with a lot of time so I won't be migrating fully anytime soon. However, I think ArcMap and Pro complements each other. I know Pro is the future but I hope ESRI keeps supporting ArcMap in the foreseeable future because it is still a fine software for a lot of its customers (perhaps even the more appropriate solution for some).
Retrieving data ...