Using ArcGIS Pro (2.2 in my case) how do you get statistics of a given field for just the selected records? I have 4400 of 11,500 polygons selected. I would like to see the mean of just one field: right clicking on the field name and selecting Statistics gives the statistics and distribution of ALL records....
Even summary statistics dosen't honor the selection; all I want to do is look at the mean value while making selections. Seems pretty simple; gotta be missing something silly...
Solved! Go to Solution.
The best explanation I've seen as to why they don't have it the way it was in ArcMap is because the emphasis on pro is repeatable workflows. I understand that, I personally love coding for that reason. However, from the forums I've crawled on the issue, it seems people really want the quick, ad-hoc stats tool. Those kinds of details may be small, but because it's used so often in our workflow, it's the type of thing that would stop another colleague from jumping from ArcMap to Pro.
I've read through your comments about comparing calculation speed for statistics on a selected set of records between ArcMap and ArcGIS Pro. I did a quick comparison using a dataset with 10 million features and see a dramatic difference if I only want to see the statistics for the selection. I've shared that with the development team and they have entered an issue in their repo to look into a way to solve the problem in Pro.
Here is my suggestion, though. I would highly encourage you to submit an idea on ArcGIS Ideas that describes what you're looking for and your use case. I think I understood enough from your comments on this thread, but specifics would be great. e.g. how many total records in your typical datasets?
And of those, how many are you selecting in order to view statistics on the selection? My assumption is that you're repeatedly selecting some features, looking at the sum, then selecting another set, looking at the sum, etc. Is that the workflow?
I know you mentioned Sum, but is that it? Are you ever looking for other quick stats on the selection for the work you're doing? e.g. Count, Mean,...
Detailing this in a new idea would give us a way to link the request to the development issue and allow the community to vote and provide more use cases.
Thank you so much!
After going through a few searches looking for the same thing I found this post.
@KoryKramer Can I raise the idea that ESRI first create parity with existing and efficient workflows and only then ask paying customers what other ideas they have?
I think it is a little bit preposterous to ask @MalleCarrasco-Harris1 to submit an idea to return a feature that was working fine and for some reason got dropped or relegated into inefficiency in Pro. Hiding the available and non-configurable statistics in the Chart Properties window a click deep is a really strange UX & UI design decision. I would love to hear how that came about or see the story boarding used to design the user flow.
A really good idea would be to mandate that the Pro developers take any equivalent feature they are working on and run a comparative real world task with it and within ArcMap. If it is faster in Pro to access (number of mouse clicks and distance of travel between clicks), configure (fill out required boxes) and run the process then keep it. If it is not better in all three aspects don't release it.
Regards from a very hot Australia.
Thank you for the feedback, Chris. The day that I wrote that comment, I had already communicated the problem with the appropriate development teams on our side. And an internal issue was created in the development system. Part of the motivation to have users submit either an idea or a bug/enhancement request is so that there is something to reference for communication. That object, whether it is a bug number or an idea url, makes it easier to communicate what work is being done through status updates.
I understand that this is one specific issue, and you're describing more generally that somebody shouldn't have to log anything at all in order to raise development teams' awareness of a deficiency or an opportunity for improvement in a software product. I'll share your feedback with ArcGIS Pro development teams and we'll continue to strive to do better.
Cheers from a very cold Southern California.
Just to be clear, I'm not proposing that users not log issues in order to raise developer "awareness of a deficiency or an opportunity for improvement in a software product". We need to do that for real problems, bugs, requirements.
My concern is with the like for like aspects between Map & Pro where it is Esri's responsibility to do their homework and not drop that burden on paying customers. As I have said, every feature in Pro that matches Map needs to have similar or better performance; measured using overall task execution duration, number of clicks, mouse distance travelled, geoprocessing time, etc. That is Esri's job - just own it already 🙂
I am more than happy to accept a discount on my annual Esri fees in return for my time to log every idea, opportunity for quality improvement, bug, etc. that I come across in Pro. I suspect though, the chances of that happening are quite low.
Do you realise that we are talking about Pro as if it is a new product? It has been around for almost 6 years and your users are still complaining about very basic things - finding tools, application performance (not data or task), etc.