|
IDEA
|
Repairing broken sources is a very poorly thought out functionality in ArcGIS Pro, just like it was in ArcMap. Robust and automated repair of lost sources, which helps the user quickly solve such a tricky problem, is a much-missing functionality in ArcGIS Pro. Why not learn from those who can do it better? Adobe After Effects, for example, has an excellent and user-friendly solution for repairing lost sources.
... View more
04-20-2026
08:37 AM
|
0
|
0
|
191
|
|
IDEA
|
Provide the user with a general ability to edit/customize any context menu in ArcGIS Pro to allow to streamline the workflow (ArcMap has the ability to customize context menus).
... View more
04-20-2026
07:49 AM
|
0
|
0
|
143
|
|
IDEA
|
I have similar idea "Field groups for thematic division of large database" in relation to the attribution table. The principle is the same: being able to group fields for better overview and easier work.
... View more
04-16-2026
08:01 AM
|
0
|
0
|
434
|
|
IDEA
|
@AletaVienneau I understand that ArcGIS Pro brings new features, but this idea simply is not available in ArcGIS Pro. The main goal of this idea is to address only one aspect of ArcGIS Pro, namely to significantly expand the Catalog pane/view functionality, which was undervalued in ArcGIS Desktop and is undervalued also in ArcGIS Pro. I understand that there are other similar ideas, but they don't address the details and some of the proposed functionalities from my idea are not listed there. I would therefore like to ask whether you will take this closed idea into account when incorporating the aforementioned similar ideas. So that I don't have to write comments to these similar ideas or rewrite this idea "for ArcGIS Pro" again (after 15 years).
... View more
04-16-2026
03:59 AM
|
0
|
0
|
437
|
|
IDEA
|
@ValeriaChavez I understand that ArcGIS Pro brings new features, but most ideas I proposed simply are not available in ArcGIS Pro. I therefore think that closing this idea with 92 Kudos is not related to the transition to ArcGIS Pro, but rather means that ESRI does not want to deal with any of these ideas at all. I expected a more precise justification when closing the idea than this general statement. I would rather appreciate information on the individual ideas, whether you plan to deal with any of them in the future. So that I don't have to rewrite them separately and unnecessarily "for ArcGIS Pro" again (after 16 years).
... View more
04-16-2026
03:42 AM
|
0
|
0
|
580
|
|
IDEA
|
I would like to request additional functionality for the Contents pane so that it can visually distinguish a group from a regular layer (e.g. bold or italic text, different color, etc.). When working with complex, older, or unfamiliar projects, it takes an unnecessarily long time for the user to track and understand the layer structure and be able to work with the map. Currently, if all layers (including group layers), are collapsed, it is not at all obvious what type of layer it is. Visually distinguishing groups and regular layers will allow the user to immediately recognize the type of individual map elements and thus more quickly navigate the map structure. As an aside, different types of layers (e.g. raster, vector) could also be distinguished in the contents pane.
... View more
04-16-2026
02:19 AM
|
3
|
0
|
129
|
|
IDEA
|
Hi @ValeriaChavez, thank you for your interest in this idea. The difference between my idea and Measure Features tool is quite fundamental. These are the main differences: The first is the workflow. When I work with or evaluate features, the primary tool for me is Select tool - I select the features and then do some changes (change attributes, move, delete or whatever). And before doing these changes, there is always good to have some additional information (e. g. summary) to be in better control. But ArcGIS shows only how many features are selected. With suggested summary (area, length, volume), there would be instantly more information about selected features for decision-making. My suggestion is to make summary available naturally (displayed in the background) when selecting features (in Map for selected layer in Contents pane or in Attribute Table for opened layer) as additional information without having to launch a new tool. On the other hand, when I want to sum features with Measure Features tool, I can't use my selection (already done with Select tool) and I need to intentionally activate this other tool and do the same selection specifically for Measure Features tool once more (which is time consuming an far less practical). Measure Feature tool does not allow multiple elements to be selected at once. So if I wanted to know the sum of e. g. 500 features, I would have to select them them 500 times. On the other hand I can select features at once either with Select tool (lasso, line etc.) or Select By Attributes tool (from one layer) and with my idea the summary would be immediately shown. So this workflow would be quite quicker. Measure Feature tool summarizes any selected feature regardless of which layer it is from. On the other hand when I seek summarization of selected features, I mostly prefer to summarize features from the same layer. This idea could be also expanded to Selection tab in Contents pane, which shows only sum of features. This tab could be also enriched with additional summary of area/length/volume of selected features for each layer.
... View more
10-08-2025
07:03 AM
|
0
|
0
|
1278
|
|
IDEA
|
@AyanPalit My idea is to see summarizations of area and length immediately when features are selected without unnecessary mouse clicks. Data Engineering is a great tool, but not so interactive, as I proposed in this idea. It takes multiple mouse clicks to get the summary in Data Engineering and when the selection changes user needs to activate calculate again. Why not show these elementary values right in the status bar without any delay?
... View more
08-20-2025
06:45 AM
|
0
|
0
|
1743
|
|
IDEA
|
When selecting features (in Map or in Attribute Table) ArcGIS should automatically show the summary of area and length for selected linear or polygonal features. Area and length could be displayed by default with possibility to choose other numeric fields for summarization instead. The summary can be displayed in Attributes pane for each layer or in Attribute Table (like in Excel Status Bar). Summarized values should update immediately when selection is modified. Summarization may include sum, average, count, min, max or median. It would be a practical tool for interactively displaying summary from existing data that I often need to quickly obtain for better decision-making without having to run geoprocessing or open another application.
... View more
08-20-2025
06:05 AM
|
2
|
6
|
1768
|
|
IDEA
|
@KoryKramer I meant it at database level (when designing the database) and subsequently (as you write) the user can work with such groups in attribute table, fields view etc. But there could also be the possibility to modify or create user specified groups in individual project regardless of the database level for customization of the working process. I don't have any screenshot, I have only some excel designs (not in English). But for example, when I do urban structure analysis (in one feature class), the fields can be divided in these thematic groups: basic identification data administrative data historical development structural analysis and synthesis urban limits urban economy and demography urban design (proposal) infrastructure data data sources, etc. Each group contain for example about 15-30 fields. With so many fields the structure of the database becomes confusing and the work with each field individually is very tedious and time consuming.
... View more
08-23-2021
12:46 AM
|
0
|
0
|
1420
|
|
IDEA
|
Allow for the possibility to aggregate fields to thematic groups, which would help to increase efficiency when working with large database structures containing many fields (100+). In case of such large databases there are always more fields, which can be thematically grouped according to their contents, type etc. Such thematic groups of fields would significantly improve visual clarity and comprehensibility of database structure and speed when working with big tables throughout the entire working process (e. g. locating group of fields, hiding, moving or sorting group of fields etc.).
... View more
08-20-2021
06:41 AM
|
2
|
3
|
1470
|
|
IDEA
|
I remember times, when ArcMap's poor speed has been compared with quick old ArcView. So this idea and these complaints in comments about ArcGIS Pro poor speed are a kind of paradox, which means that something is historically rotten in ESRI's approach to desktop software development quality. There could be tons of ideas for improvement on this page, but to no avail because of this one crucial thing.
... View more
03-11-2021
07:42 AM
|
0
|
0
|
4850
|
|
IDEA
|
You are completely right. https://community.esri.com/ideas/8430
... View more
01-08-2019
11:22 PM
|
2
|
0
|
3488
|