ArcGIS Desktop does not need to be written in 64bit for you to take advantage of a 64bit OS and x64 architecture. The 64bit OS allows you to run 32bit apps within a shell called the WOW64 subsystem. 32bit apps may not be able to address more than 32bits of data but the x64 architecture means that more processes and users can share the increased RAM and virtual memory. We run terminal servers with ArcGIS Desktop installed on x64 machines with Windows Server 2003 R2 x64 edition and the 16 GB of RAM means that we can support many more users and simultaneous processes than we could on our x86 machines with 4 GB of RAM.
What David Wheelock said is what I have been told by Esri. Like it or not, ArcGIS Pro is where Esri is headed. I have already been moving some of my regular workflows to Pro (if supported currently) and found that in many ways, Pro is much easier to navigate and get things done. It just takes time to learn a new interface.
imho this is true. While you're waiting for Pro to mature and get all the functionality Desktop offers, you might want to look at the 64-bit background geoprocessing extension for Desktop.
It's a bit clunky and annoying to set up, at least in an Oracle environment where you will require both 32- and 64-bit clients setup and configured. In our testing it offers a 5-10% performance improvement on geoprocessing of substantial datasets.
Agree with last poster. How has this been implemented? Pro...is not desktop. It has no features, functionality, or utility.
Could not agree more - we have built all or workflows and database structure around Desktop and I find Pro cumbersome and slow Please ESRI a 64 bit version of ArcMap!
As far as I know there is not going to be a 64 bits version of ArcMap, however ArcMap will be around for many years more.
If ArcGIS Pro is slow please have a look at this blog to investigate what might be the problem: Troubleshooting Performance Issues in ArcGIS Pro | ArcGIS Blog
I think many people are confused about 64 bit applications. I am under the impression that many people think 64 bit applications are faster than 32 bit. They are not. 64 bit applications only mean that programs can access more than 4GB of memory. Lets face it, most ArcGIS users will never need that much memory. Although developing applications for 64 bit is not a bad idea that alone will not make ArcGIS any faster.
I think it would be better if ArcGIS made or continued to make ArcGIS faster by
the product exists- it is called ArcGISPRO
Pro is cumbersome, hard to use, there are too many differences in workflows from Desktop, and despite what others have said, it runs much slower than Desktop.
we are going to have to learn pro
i heard yesterday that desktop will not be receiving any new or updated functionality.
think the fate of arcview 3.x.
example- vector tiles will not be visible or usable in arcmap only in pro.
Despite your experience, Pro has been consistently faster than Desktop for me in a number of different tasks.
Most workflows have been sped up by the layout of Pro…
Did you have the same problems when converting from Arcview 3.x to Desktop?
Change can suck. It can also help make progress. Take small bites and make sure that you go through the training!
Thinking of the plethora of tools that are built on the desktop platform (e.g. X-tools, Arc Hydro, HEC-GeoHMS, GME) that...to my knowledge...there are no plans to port these to Pro....I'm failing to grasp how Pro should be a direction that I should take my shop? Yes, change can suck, especially when we have no choice but to use whatever product Esri makes us use. Kinda reminds me of the good ole' Bell Telephone days, when you had no choice but to pay their long distance rates. Call them to complain "Well, you can always choose another provider (snicker)." Not a big fan of the hardware requirements, either, to get reasonable performance out of Pro. Maybe the folks in Esri testing lab have a nice computer replacement budget, but that is definitely not the case in many organizations that require you to get 5-7 years out of a desktop, which was purchased with bare minimum to start with (I can read my email just fine I don't know what you GIS people are complaining about....).
Looks like X-tools pro is already ported to ArcGIS pro:
XTools AGP Features | XTools
At the 2016 User Conference, it was very clear regarding Esri's path. I attended the Intro to ArcGIS Pro Technical Workshop, and the presenter explained that they sat down to brainstorm what it would take to make ArcGIS Desktop a 64 bit application. They realized very quickly that it would entail a ground-up rewrite of the application if they were going to do it right. (And let's face it, if they didn't do it right they would never hear the end of it from most of the commenters on this idea). So, faced with a complete rewrite they decided to also look at all of the other things that they, or users, didn't like with ArcGIS Desktop and address those issues as well.
ArcGIS Pro is the result. Like it or not. In that session and elsewhere during the UC, I heard that ArcGIS Desktop would be around for quite a while but that it would not be getting any further enhancements except for major bug/security fixes and whatever might be necessary for it to continue to work with supported file formats (i.e. if they enhance the geodatabase in some way, they would create a patch/fix for Desktop to understand how to work with those enhancements). The recommendation was that we should all begin to use ArcGIS Pro in our daily work where we can, even though not all of the features from Desktop are yet present.
I, too, have been resistant in moving to ArcGIS Pro. But I've started to explore it a bit more because I know that AGP is the future and I don't want to be totally left behind. Complain or lament all you want about Desktop not becoming 64 bit, but it isn't going to happen. AGP is different, no question about that. But for all of you 'long-timers' in the crowd--How long did it take you to get accustomed to ArcGIS Desktop from command line ArcInfo? It will take longer than a day or two to become comfortable using AGP, but even the limited amount of time I have now spent using it, I can already see some benefits--and for the record I am currently running on an older laptop that is severely limited, resource-wise (even for 32 bit Desktop). Ultimately, such a change is necessary and inevitable given that we work in a technology-driven field.
My feelings exactly.
A year or two ago I complained to ESRI that some vital functionality (that we all take for granted in Desktop) was missing from Pro. I understand, OK, it's a new program, lacks some features, so we can wait a little until they will be added, presuming that their precedence will be set on high, before other fancy features. All this assuming that ESRI wants us to use the new program for our daily production, for enthusiastic adoption, not for struggle and frustration. But what was offensive in their response - their entire attitude: why do you need it at all, they asked. It was a basic feature, which I used to use daily and couldn't imagine my workflow without it. I responded with a polite but angry letter. They called me back, with some customer ombudsman too. We had a lengthy discussion over the phone. But the feature is still unavailable! Every time I have to force myself to take another stab at the program. Nothing like the joyous experience when I switched from AV 3.2 fifteen years ago . Or am I just too old for the changes? I don't think so
My feelings exactly.....
I share your feelings, too, Alex. Which is why I'm still not using Pro. Too much stuff still missing. And no support for personal geodatabases, at all.
Fair call on functionality, but it is improving, if not as fast as some would like. As for PGDBs, along with VBA and VB6 Esri considers these dead technology and is actively getting rid of them. Is there a reason you can't upgrade to FGDBs? Code to access these should be able to be container-neutral.
I still use access a lot.
It would be great if someone could build a access style "query builder" for fgdb.
Good question Andrew.
A File GDB is a silo and cuts the data off from most other programs. It isolates the data and can only be accessed from ESRI programs or GIS programs that can access it and cannot be read at all by Office productivity software or any other database software. It's not useful to me.
Ah, thanks David. I don't do anything with Office (enterprise GDB work mostly) but I'm surprised to hear that the API doesn't allow for Office customisations/applications to access FGDBs; that specifically says you can manage data in a FGDB outside ArcObjects. I was also pretty sure that any ArcObjects code targeting esriLocalDatabaseWorkspace would work. You could even still use VBA, depending on your version.
That said, I appreciate that working with Access makes more sense for you as it's all native tools.
While we reminisce, I had Avenue code. The switch wasn't joyous for all of us.
We (Stanford Geospatial Center) are considering the eventual forced migration from Desktop to Pro (which will mean a rewrite of all our training and support materials) as a fantastic opportunity to move to a more Open Source based (or at least mixed) model. We've already begun recreating our Introductory materials for QGIS, and we've found it to be a mature desktop GIS capable of much of the functionality our researchers are interested in, while also freeing us from issues of licensing, use restrictions, OS dependance, etc...
Also, QGIS is available as a 64-bit application.
That said, we will continue to license, provide access to and support Esri products, they will simply become a less overwhelming component of our offerings.
Sounds like smart way to go.
With the end of Desktop in sight, we're undertaking a similar evaluation - to assess whether continued investment in Esri (transitioning to Pro) is the best/most cost efficient path, or whether a OS mix (QGIS, PostgreSQL, etc) might be better. This is probably not the right forum to discuss it but I think that'd be a great topic for a community or blog post.
Where have you seen that they were planning to discontinue Desktop?
There's a number of threads on Geonet where posters, coming back from the UC, have stated that "Esri said..." that the desktop is going away and Pro is the future. Could that just be "word on the street" or true...I have no idea...
Considering that half of the "solutions" in the help for Desktop issues instruct you to use Pro I would say the writing is on the wall.....
i llstened to esri technical staff say that desktop would remain around for a few years but that no new functions would be added. they use vector basemaps (which are really cool) as an example. you will not be able to view them in arcmap.
in pro you can actually edit the xml file and change the styling. i must say i was impressed.
The fact we are still talking about a 64 bit program as an idea some years after it materialized is significant in itself. It does unfortunately suggest that the Pro product does not meet users expectations.
Having been a user since beta 2, I still use it rarely as I find it an incredible waste of time. ESRI has really dropped the ball with an "all new" approach, by not implementing some of the core aspects of Desktop, they have created a terrible waste of time and ridiculous frustration.
Here is a few of my "favorite" problems with Pro:
The claim 64 bit runs faster. Somewhere in the marketing this is indeed a claim. Clearly ESRI employees have never used it. It is slow. Really slow to do just about anything.
Dropping the universal access to Folders and Database connections. My first reaction to using Pro was "Where's my data?". I still have the same question three years later. The idea that you have to recreate connections to your data for every project is just plain dumb and stupid when they had such a great solution for the last decade. Whoever made this decision needs to be shown the door. Yes you can create a project template and save connections in it, and no ESRI, this does not fix the problem. Editing a project template is a pain and difficult. In fact try searching for 'editing project template' and see what you get. Nothing. Yes it is possible, but difficult.
Having to create a new project EVERY time you start Arc Pro. Again clearly no one at ESRI uses this program otherwise you'd know how impractical it is. If someone wants to just open a copy of arc to see some data, sorry son, you're out of luck, create yet another My Project #. While you wait for the project to be created, after you waited for the program to actually start, which is itself quite a while, you've probably got enough time to write a letter to ESRI complaining how much time it takes to do anything with this program.
3D. Yes it can do 3D simultaneously with 2D maps. Very clever, pity they are so hard to use. First problem is that big picture of the world as a background image. I am kind of curious as to who, as professional GIS users would use such a useless image as the background map to 3D data. Not only is the background map pretty useless, but then you have the background DTM lurking there. Now put some data over it is and see if you can find it. Most of my data is not visible because the default background world DTM data is not terribly accurate. Surely YOUR data would be the prefect base height for YOUR 3D data. Now put a TIN on it. A TIN in Pro defaults to being a 2D dataset. This is despite the fact that ESRI itself clearly describes a TIN as a 3D dataset. Now try and visualise it with the same colour scheme you'd use in ArcScene. It is drab, the vibrancy of the ArcScene colours are completely lost, the effect is a flat image on the screen.
Arc Pro 3D Visualisation with unknown drawing artifacts leftover after lifting the image by 10 metres to actually see the data above the background DTM
Arc Scene Visualisation, which do you think provides the better information?
So after three years, it is safe to say that I am not a fan of Pro. Most of the problem I have noted are about getting started with data in Pro. In terms of using Pro to manipulate data, via Editing or through toolbox, using the ribbons etc, I have found the new system pretty easy to get used to. Once you get started.
But getting it going is a time consuming and frustrating experience all mainly due to ESRI dropping so many features that have made Desktop so succesfull for more than a decade. Pro, is not, in my opinion, an anywhere near ready substitute for Desktop. Yesterday I was trying to use the Modify Feature Tab, the problem was it literally kept disappearing on the screen, you could run the mouse over it and some of the items would appear, but in the end, after some hours of yet further time wasting annoyance, the task was solved quickly in ArcMap Desktop.
I certainly do not feel we have not achieved a usable 64 bit ArcGIS application.
Unfortunately, ESRI is not going to see any of these comments, as they consider this "implemented" and "the product is meeting everyone's needs".
i am teaching right now with both Qgis and Arcgis desktop.
the reaction from the students is that Qgis is complex and not intuitive compared to Desktop.
i agree. i am not sure the future is in teaching with Qgis or desktop or pro.
i plan on staying with desktop for another couple of year.
Qgis, even with it being free, is just not integrated enough.
the goal with teaching is to get the concepts and problem solving process locked in.
with Q there are so many steps to do anything and each plugin is different.
i am not sure what the future holds but i don't think Q is the answer.
All good comments, David. The comment from Thomas, above, is also true that ESRI may not be monitoring this thread, now.
To achieve change, we need to create and promote specific suggestions on the ArcGIS Ideas website. Please do that with YOUR ideas. Then post the links to those suggestions back here so that we can all give it an UP vote.
I did that here with this idea:
Enable use of ArcGIS Pro without creating a project folder
It's worth noting that ESRI will change course and modify software/geodatabase performance in a major way in response to user pressure. For example, about 15 years ago, there was an episode where ESRI modified the geodatabase to store coordinate values in integers rather than in decimal. This resulted all of the coordinates being shifted when various processes were performed. The result was that adjacent polygons with coincident points no long lined up and were no long coincident. MAJOR mistake. It took a year or two, but user pressure finally forced ESRI to backtrack and go back to a decimal storage system.
Good idea(s) BUT....I have a fundamental problem with having to take time out of my work schedule to compel and cajole a software vendor to provide me with a product with features that I need to do my job, which already work in a product I use, but I'm told that product is going away...and I need to create an "idea", get thousands of people to "vote" on it, so Esri will consider it an "enhancement" in the "new" product. At some point, someone in Esri sat down and did some sort of user/business requirement exercise, and the result is...all of the tools/features/functionality in current desktop product. Does that person still work there? Have there been "focus" sessions where GUI engineers visit sites and observe workflows? Arc Catalog and folder connections to drive roots exists for a reason...because users wanted and needed it. Calling those things "enhancements that we MIGHT consider after the "idea" gets 1000 votes" is kind of frustrating from an end user point of view.
Here's my suggestion to have give users more opportunity for input on new features. Please give it an UP vote.
David, I like your idea of a test/feedback site. In fact, I just upvoted it. But I'll play devil's advocate a bit with the following comment...
One thing I love about GIS and being a part of this profession is the fact that GIS can be used for ANYTHING spatial. That ranges from the traditional and typical "features on the Earth" to where cans of soup are in a grocery store, anomalies on the retina of your eye, and mapping other planets (and an infinite list of others). The sheer breadth of possible uses means that everyone--beyond the basics--has different needs, even when it comes to how a particular feature should operate. The top 3 "must have or my work life will end" items are likely "meh, whatever" items to any number of others. I don't envy Esri at all when they must look at all of our submitted ideas and evaluate how best to implement (if they are able to at all) them.
What I most want to see from Esri is a roadmap of planned features that are/will be implemented with Pro. Then we can see what is coming and [generally] when. Maybe the grand plan is that everything in Desktop will eventually be in Pro, but I haven't heard anyone at Esri actually utter those words. A roadmap might at least allow me to plan when I could effectively transition, and submit specific ideas for things that I don't see on the roadmap. I'd also like to understand Esri's thought process behind the Pro "workflow" they have forced upon us. I, too, dislike the whole "create a project first" philosophy.
I remember using command-line ArcInfo long after Desktop arrived to do parcel entry because the COGO tools weren't available or implemented very well/completely. I expect my transition will be measured in years rather than months yet again.
That's a GREAT idea Brian. Please make your "roadmap" suggestion, here in Ideas, as well.
Done. Please upvote the idea here:
Create an ArcGIS Pro feature "road map"
Did it. Look at all the UP votes, already.
But someone already gave it a DOWN vote. I wonder if that was an accident? I once accidentally down-voted my own suggestion when I wanted to look at who had voted it down. The buttons are close together. I fixed it but it made me wonder how many DOWN votes are accidental.
I'm not sure why downvote is even an option. It seems really counterproductive.
I tend to agree with you. It may be that people who don't understand the issue would give it a down out of ignorance and penalize an otherwise good idea.
Here's a comment from ESRI staff with information on the future of ArcMap/ArcCatalog and ArcGIS Pro.
Here's another important suggestion. Please follow the link and give it an UP-vote.
Add Stand Alone Data Catalog Like ArcCatalog to ArcGIS Pro
It comes from sites like Reddit, where you can exercise your opinion in either a positive and negative way. What you think is essential to your work processes I may find irrelevant to mine. What I think is a deal-breaking issue may not affect you at all (example, see PGDB vs FGDB discussion above). Because resources for adding new features to ArcGIS are limited, this gives Esri a tool to gauge not only the community's preferences, but how widely supported those are. A contentious idea means that Esri needs to look at it more closely, not simply look at total votes for something.
True, but for the specialized functionality we can use the third-party plug-in modules (XTools, EnviroInsite, etc. come to mind), when ESRI is too busy to build it on their own. But we should be able to expect a rich, well developed framework from ESRI if they want to minimize their users' frustration. But now it seems that their attention is not focused enough on the main product, but instead dispersed on "ANYTHING spatial." And this is how many mighty have fallen...
Alex, I cannot disagree with your sentiments.
I used to post my suggestions on the old Ideas site quite often (40+). Some were, in my view, worthy of serious consideration and not difficult to implement. Only a couple were implemented, coincidentally. And those were, even in my own opinion, the second tier, less important. So I'm skeptical...
Yes, Alex, the old Ideas site seemed like it didn't get a lot of traffic. I'm getting a different impression of the new Ideas site. Give it a chance to make a difference.
Sorry to necro, but I just dealt with the "where is my data?" question.
I'm not sure when it was implemented but Pro now has Project Favourites, which is kind of like a subset of ArcCatalog. If you use the same sources all the time, you can also check "Add a favorite item to all new projects" so they will appear in every project without you having to snipe hunt them. This replicates pretty well the way the ArcCatalog pane works in ArcMap.
If your catalog looks anything like mine, this is actually a welcome simplification. This are (just some of, not all) the DB and server connections for our enterprise.
By comparison here are the project favourites for a recent Pro project:
They don't just "appear" in your project, the sde connection file is copied to your project directory. For example, if you work on 10 new projects per week, and use 10 SDE's, on average, for all of your projects, you now have 100 SDE connection files being generated per week. Project templates and favorites are a big improvement over the early days of Pro, but the firehosing of SDE and GIS server connection files all over the shared drives needs a lot of work. With Arc, the same SDE connection files lived in a single location on your hard drive, and could be referenced regardless of what project you're working on, or where it was saved.
ESRI accounted for this partially under Options | General
David Wheelock that is sort of true, but there is a file gdb api that can let you interact with the data. For instance, OGR2OGR can extract all of the data from a file gdb fairly quickly and move it into a sql database or any other format that OGR supports. Perhaps another good suggestion for esri would be to expand on this api to allow office programs to access fgdb data sources.
Adoption rates for the File Geodatabase API have been pretty low, at least from any perspective I look at it. Esri would likely get higher adoption of the file geodatabase if they opened up the specification instead of just releasing an API, but I don't see Esri releasing the specification because it would show a fairly weak file system-based database model.
The creation of the file geodatabase over a decade ago was necessary do deal with several functional and performance issues with the personal geodatabase. Although the file geodatabase was a step forward in many important areas, it was a step backwards in a couple areas. Instead of trying to improve the file geodatabase and release an open specification, I think the time has come for Esri to build the next-generation file system-based geodatabase storage format for ArcGIS. A lot has changed in the past 10 years, and there have been huge steps in the open data arena. I would like to see Esri implement their geodatabase model within GeoPackages. That way, we would get the functionality we need for working with ArcGIS but also get a much richer, complete, and open storage format that other programs can work with as well.
ESRI just needs to get ArcGIS Pro up to the same caliber as ArcGIS Desktop ASAP if they are indeed planning to phase out ArcGIS Desktop.
Here's another critical weakness of ArcGIS Pro. You can't run more than one Pro on your PC at a time. I often have multiple ArcMap windows open simultaneously.
Below is a suggestion to remedy that. Please follow the link and give it an UP-vote.
Run more then one instance of ArcGIS Pro
This. David makes a very good point - while the single entry, queued processing model sounds good on paper, it's a killer for productivity. A standard way to multitask for many of us is to have multiple MXDs open, switching from one to another while waiting for geoprocessing to finish.
With 64-bit Arcpy since 10.2.1 (IIRC) I have been leaning heavily on python command line when using ESRI products for geoprocessing. While such a workaround will still be available, in my experience Pro is not nimble enough to pull off what I assume are the design goals. While the rendering engine is very nice to look at, I do remain to see how they will support data management and data development roles. Or rather, anything other than cartography.
I completely agree, it's nonsense not having a 64bit product. Maybe they want more people going into AGOL
Here's another important Idea, folks. Please, UP-vote it.
Drag & Drop Data into ArcGIS Pro
Currently, you cannot drag-and-drop data from Windows Explorer into ArcGIS Pro the way you can with ArcMap/ArcCatalog. Great feature!
Alright... ...this has become well past the ridiculous stage on sooo many levels.
1) My email has been getting blown up with these latest comments and for someone to say that "...ESRI has considered this implemented and is no longer monitoring/listening to this thread/idea..." makes me mad. Then why I AM GETTING ALL THESE EMAILS!!! And if I'm getting all these email notifications then there better be someone at ESRI, with some pull, getting blasted with these too. I'm not saying that I do not want the emails to stop because I like to know that I'm not alone and what others are doing. Misery loves company, right.
2) As much as I appreciate those like David Wheelock submitting and finding all of these additional "ideas" to be voted up, I feel like this SHOULD BE unnecessary. As this idea says a 64 bit version ArcGIS Desktop. This was suggested (an "Idea") prior to ArcGIS Pro being released. ArcGIS Pro is not ArcGIS Desktop that we know and have come to love with all that functionality. This functionality is nonexistent in ArcGIS Pro, therefore, this idea has not been "implemented" as ESRI has stated above. If it was, then why is there SO MUCH chatter 6 1/2 years latter; and why do we have to create additional "ideas"? ...because these Ideas are for a new product that lack the functionality of ArcGIS desktop and, therefore, not ArcGIS Desktop that we as customers have come to love.
3) I was once told that if someone says something enough times, over and over again, it becomes true. Keep in mind that this quote was in a business setting. I do not care how many times someone tries to say that ArcGIS Pro is 64bit ArcGIS Desktop; it will never be that to me unless the functionality becomes mirrored in ArcGIS Pro. And now there are new functionality only available in ArcGIS Pro. I understand new technological advances will not be available in ArcGIS Desktop but ArcGIS Desktop, once again as we the customers have come to know, is still in 32 bit. PLEASE CHANGE THE "Implemented" status to something other than this because, to your customers, this is a FALSE statement. ...unless there is a 64bit ArcGIS Desktop product out there other than ArcGIS Pro that I'm unaware of.
Folks so bent out of shape over calling it implemented would do well to remember to that at the time of the original Idea -- the 64-bit Python geoprocessing module had not been implemented. That has been available for some time and in fact makes ArcGIS for Desktop 64-bit where it matters. I've no objections to calling it implemented in the sense that nothing further will be done with the 32-bit ArcGIS for Desktop code base.
Not that it couldn't be, just that there is not a lot of incentive for Esri to do so.
Everything else posted to this Idea has just been complaining about how Esri is moving forward with their development of native 64-bit tools, aka ArcGIS Pro--"supplemental" to ArcGIS for Desktop.
The noise level has gone up because someone at Esri thought it would be a good idea to link the Ideas content into Geonet--and then have it spit out incessant emails for issues on which we've cast votes--and that is annoying.
Timothy Hales -- can we have some way to "unfollow" ArcGIS Ideas we've cast votes on? Individually or globally...
I think these are the options you can use to unfollow this idea individually. I wonder if there is a global option so you don't have to do this for every single idea you vote on. Kinda silly if there isn't.
Thanks for the tip Ryan. Yes, if you do not want your email inbox blown up by a popular topic, turn off 'Inbox Following'.
(I think you can set it to just Following if you want less spam?)
If you want even less hassles, you can have your geonet inbox update mailed to you periodically as a digest, or turn it off altogether here. This option is a whole of site configuration, and would be a sledgehammer solution for Adam Cottrell et al.
I created a subfolder in my Inbox called GeoNet and then created a rule to move all incoming mail from GeoNet to that subfolder. It's a great way to track what's going on while automatically keeping your inbox clear at the same time.
Not any that I am aware of. I am going to take another look at it this
morning. I still think it needs a super simple table that is a quick
reference. Like last 5 years summed together by vessel id and rookery and
percent by of those vessels. I like your tables already but they take a
while to parse with your brain.
Disregard. Wrong email.
On Fri, Oct 7, 2016 at 10:19 AM, Steve Lewis - NOAA Federal <
Didn't think to check, but you're right. Thanks!
Seems questionable to have done the migration from the Salesforce hosted Ideas portal and set Follow -> Inbox by default on each migrated idea for each user who voted.
Hi All. Thank you for your continued feedback. While there are no plans to create a 64bit version of ArcMap, we will continue to focus on ArcMap quality, maintenance, and the addition of targeted functionality through new geoprocessing tools.
ArcGIS Pro was developed to answer the request for a 64-bit desktop application and will continue to be our focus for new development efforts as we see it as the future of the ArcGIS Desktop product.
Customer feedback continues to be a key driver of ArcGIS Pro software development. Therefore, we encourage you to continue commenting and posting your ideas as this helps us to build ArcGIS Pro to your needs and requirements.
The answer to "request for a 64-bit desktop application" is fine, as long as we have the adequate tools to do our daily jobs without struggle or, at least, not worse than before. Thank you.
Hi Alex Zhuk, I hope you're doing well. I believe we discussed your product feedback regarding ArcGIS Pro early last year. I'd be happy to schedule another call with you to understand which tools and workflows you're looking for in Pro now and where you feel there is opportunity to improve, if you're interested? Thanks!
Yes, I remember our discussion. In fact, I recently told about it on this forum (page 4). Please rest assured, there is nothing personal, it is just a vendor-customer thing.
You see, I’ve always been an early adopter of the ESRI (and other software makers’) products. I usually install a new version of ArcGIS for my group within a week of its official release, not waiting, as some other users do, for six or more months. But it’s not the case with AG Pro. After several unsatisfying experiences it’s hard for me to spend more of my (valuable) time on playing with the program (even as I again have the latest version installed). I still do try it occasionally, but nowhere near the point of production.
As far as the “wish list “ goes, I bet, out of more than 17,000 user comments ESRI should be able to pick a few ideas to begin with.
pretty sure this is not implemented... only 64bit geoprocessing was. not the same as the actual desktop software being 32bit.
This is exactly what ArcGIS Pro is, a desktop 64bit software.
But all of the critical functionality of ArcMap or ArcCatalog is not present in Pro; And ESRI is not prioritizing bringing them to parity before expanding.
Depends on what you call critical functionality and they are quite articulate in responding to what is desired by users and what is practical to implement at various time frames in their road map
If you have something not covered in the ArcGIS Ideas they certainly want to hear from people.
For me, I waited for 8 long years to be able to program within an Arc* product natively using python 3.x, NumPy Scipy etc. They did it with PRO
There are more than a few people both here and @ UC that have said replacing/migrating the ability to administer Server is a critical item.
David Wright speaking of "Critical Functionality" don't forgot to add your use case and vote to ArcGIS Pro Publish Services To ArcGIS Server
Already voted that one up; and now adding additional thoughts. Going to also forward to my State's GIS Steering group to get their support.
For me critical functionality is Editing Dimensions. I have 10,000+ parcels that each have lot size dimensions and easement dimensions. ESRI needs to make ArcPro have all of the functionality that ArcMap has/had before I can make the jump to Pro.
I voted up ArcGIS Pro Publish Services To ArcGIS Server.
Retrieving data ...