|
POST
|
Also regularly clear out any geoprocessing "History" in your project if you are an avid tool user. You can quickly collect a lot of junk there that will slow down opening your projects. See example image.
... View more
01-22-2020
10:50 AM
|
1
|
1
|
5345
|
|
POST
|
Related issue: https://community.esri.com/thread/199094-arcgis-pro-convert-labels-to-annotation-hanging
... View more
01-13-2020
01:54 PM
|
0
|
0
|
4629
|
|
POST
|
Well, as definitive proof of Pro's capability to use a lot of RAM, here is the result of some custom Python scripting in ArcPy that accesses a gigantic 172 M record database table and extracts data for each record. More than 80 GB work memory usage, 24 GB residing in actual physical RAM (laptop with 32 GB RAM).
... View more
12-23-2019
01:08 AM
|
4
|
0
|
13038
|
|
POST
|
Do you also say that knowing the result of those 500+ layers is this?... 😉
... View more
12-09-2019
08:32 AM
|
6
|
0
|
13038
|
|
POST
|
The biggest RAM usage I have personally seen for Pro, was just over 72 GB! That said, that is with a power users scenario of > 500 layers in the Pro TOC referencing a few dozen database tables, some with > 100M records.... However, please don't let Window's Task Manager fool you. Task Manager only displays a small part of the true memory usage by Pro. Open the Resource Monitor instead (Click on the second Performance TAB of the Task Manager, there should be a link to open it at the bottom of the display), it will show you the true memory usage of Pro, which can be vastly bigger than what the task manager displays.
... View more
12-08-2019
02:12 PM
|
3
|
3
|
13038
|
|
POST
|
I'm holding my breath. Me too, but looking at ESRI's history, they usually only get it right at the third major iteration of the software (ArcView 3.x, ArcGIS for Desktop 10, although some will probably say it never got better after 9.3.x...), so I think I will hold my breath for Pro 3.0 instead...
... View more
11-26-2019
09:55 AM
|
5
|
0
|
3478
|
|
POST
|
I had a user recently request a large, highly detailed wall-map of the city. The map has lots of street labeling. The Maplex labeling performance is much SLOWER in ArcGIS Pro. I wound up giving up on Pro for this project because I just didn't want to wait that long for every refresh while tuning the labeling. Measurements: ArcMap: 1 minute. ArcGIS Pro: 3 minutes. Just "three minutes"? You make me laugh... 😉 I have build a complex renderer for OpenStreetMap data that is completely dependent on Maplex as well for all labeling. For an A0 1:M scale Europe map, it probably took half a day for Maplex to figure out the label positions when set to "Best" quality and to output the final PDF (which used transparent hillshading as well, allthough not much visible in the images below, and also a performance killer on export). Granted, this is taking it to the extreme... ;-): Detail:
... View more
11-26-2019
09:10 AM
|
6
|
3
|
3478
|
|
POST
|
Ah, sorry, I am actually using a combination of the Terrain: Multi-Directional Hillshade Terrain: Elevation Tinted Hillshade layers stacked.
... View more
11-25-2019
01:50 PM
|
0
|
0
|
2825
|
|
POST
|
Rajinder Nagi, Although not exactly the same bug descriptions, but I got these two issues logged a while ago through the Dutch branch of ESRI: BUG-000122033 Intermittently, exporting a layout to a pdf if the map is using a coordinate system other than Web Mercator, the Terrain: Tinted Hillshade living atlas layer will export blocky and won't draw the entire layer if it is exported with "Best" image quality with a dpi greater than 96 and a page size greater than 64 x 33. BUG-000122689 Exporting layout to pdf that contain Terrain: Elevation Tinted Hillshade layer and high dpi will not draw the entire layer and some grid visible for all image quality. Since they may be related, could you potentially look up if any work has been done on these registered issues?
... View more
11-25-2019
01:39 PM
|
0
|
1
|
7211
|
|
POST
|
I am not entirely surprised. Your use of pyodbc and sending the SQL straight over to the database for evaluation, is bound to be the fastest option, as everything happens on the database server itself. Calling a geoprocessing tool inherently already has an overhead in terms of e.g. toolvalidation. In addition, but this is a bit of speculation from my side, it could well be that, in order to actually calculate the lat/long values, the da.UpdateCursor actually fetches the entire records and has them send over to your client PC. Combine that with a possible client side calculation of the actual lat/long values, and sending the result subsequently back to the database server in a row update statement, and there is both a lot more traffic and hoops to go through before you have your final result. Anyway, maybe you can get a better insight in what is happening with da.UpdateCursor if you watch the incoming SQL statements on the server through e.g. pgAdmin (if using PostgreSQL) or a similar tool for another RDBMS.
... View more
11-24-2019
01:27 PM
|
0
|
1
|
2090
|
|
POST
|
Hi Kory, Thanks, yes that helps. Yes, the text is subtle, and combined with my ignorance of how far reaching these new options are in terms of possible connections between attributes and symbology, I hadn't yet fathomed this, especially since I haven't yet tried out the options as described in the mini-tutorial included in the Help page. That ignorance was cleared up by your screenshot though...
... View more
11-11-2019
10:30 AM
|
1
|
0
|
8523
|
|
POST
|
Jamal, Your "on-chip" Intel Iris graphics, instead of a dedicated graphics card, is in your case very likely part of the problem. The 32GB is just shared RAM memory, not dedicated fast DDR5 graphics memory as on a separate graphics card. I see my laptop's NVidia graphics card with 4GB dedicated DDR5 video RAM continuously spinning up to max usage with Pro. Not having such a card, will surely limit Pro.
... View more
11-11-2019
06:39 AM
|
6
|
2
|
4274
|
|
POST
|
"Sometimes I feel as if I’m working with web App but not desktop!" I think this remark is not far off the mark... and at least part of the problem. ArcGIS Pro's UI is in fact build based on Microsoft's Windows Presentation Foundation (WPF: see: https://docs.microsoft.com/en-us/previous-versions/dotnet/articles/aa663364(v=msdn.10)?redirectedfrom=MSDN) which is according to that page: "They are: a unified platform for modern user interfaces, the ability for developers and designers to work together, and a common technology for Windows and Web browser user interfaces" As you can see, WPF is at least a shared technology with web browser UI's. I think Microsoft never envisioned or optimized WPF for applications as big and complex as ArcGIS Pro. Even the non-web version of Outlook can be really sluggish if it has to deal with hundreds or thousands of emails in an Inbox. It is probably only part of the issues, and ESRI definitely has made improvements in some areas in the last few releases (e.g.this partially implemented Idea from myself https://community.esri.com/ideas/15362-arcgis-pro-stop-queuing-senseless-ui-tasks-performance-issue), but I do think it may play a role here. That said, I don't think ESRI had any other logical choice for a pure Windows desktop application like Pro.
... View more
11-11-2019
06:27 AM
|
8
|
1
|
5003
|
|
POST
|
I have a point layer file that I imported from ArcMap into ArcGIS Pro. In ArcMap, the advanced symbol property of "Rotation" was set, and when I inspect the symbology properties in Pro, I see the rotation field properly set in the "Vary symbology by attribute" TAB of the Symbology pane. So far, so good, the layer displays the rotation properly as well, so no issue here. But at the bottom of the Symbology pane, when "Vary symbology by attribute" is the active pane, there is a checkbox "Allow symbol property connections". It is not clear to me, what this option does?? According to the Help page here: Attribute-driven symbology—ArcGIS Pro | Documentation "When you are in the Format Symbol mode of the Symbology pane, click the menu button to ensure that Allow symbol property connections is checked, indicating that the layer is enabled for attribute-driven symbology. If this option is checked and disabled, one or more properties are already connected for this layer." This text suggests that for some reason you are supposed to additionally activate the attribute driven symbology by checking this box on. In my case it isn't checked on, but still, the rotation is applied properly??? So what does this option do?
... View more
11-09-2019
10:28 AM
|
0
|
4
|
8866
|
|
POST
|
Hi Matt, This may be a far fetch, but I wonder if there is a relation with this issue as seen with PDFs exported from ArcGIS Pro that contain partially transparent ESRI basemaps?: Why does the World Hillshade show tiles when exported to PDF? ArcGIS Pro 2.4 The visual result / defect is remarkably similar..., see the attached image in the OP's post in that thread and that represents results I have seen as well when exporting PDFs from Pro.
... View more
11-08-2019
10:46 AM
|
0
|
1
|
1479
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 01-31-2026 04:45 AM | |
| 1 | 12-08-2025 09:12 AM | |
| 1 | 12-05-2025 12:38 PM | |
| 1 | 12-04-2025 10:08 PM | |
| 1 | 12-04-2025 10:11 AM |
| Online Status |
Offline
|
| Date Last Visited |
05-29-2026
03:22 AM
|