Latest Contributions by Bud

Idea - Add Join — Create independent definition query on join table (pre-filter)

I posted an idea: Move measure tool outside of map view

It looks like it's possible to move the measure tool within the map view. This idea is to move the measure tool outside of the map view so that it doesn't obscure the map. I'm aware that the tool can be collapsed. But I want the tool to still be expanded/useable, just moved away from the map. Move the Measure tool out of the way

I wonder if it would be worth submitting a case to Esri Support to see if it's a bug.

Somewhat related: ArcGIS Pro Question: Track Changes in Point Feature Class with Records

You could submit an Idea and see what Esri says. And you could look up Archiving. But I don't think many people use archiving; I suspect it has some pretty big tradeoffs and is buggy. Related: Edit Log to capture Insert, Update, and Deletes via ArcGIS Arcade attribute rule

I think it's good that you submitted an idea. But I wonder if it might help to get traction if you also submitted this as a case to support.

@SimiBasu, I hadn't gotten the error since your comment two weeks ago. But I got it just now:

Some relevant questions from Esri Case #03632162 - New workspace caching in Pro 3.3 — Improved GP performance in EGDBs?: Me: What triggers Pro to re-query the data (clear the cache)? For example, does it only re-query if the underlying data has been edited? How does Pro know when a table in an Oracle 18c 10.7.1 EGDB has been edited, especially if editor tracking isn’t enabled? It is my understanding that there isn’t a clean way to know when a row was last updated using OOTB Oracle database functionality. Reminder: Route event layers utilize both an M-enabled FC and a separate standalone table (linear referencing table). So I would think Workspace Caching would need to cache and re-query both of those FCs/tables, and have a way to know when they were last edited. Also, a schema change to a FC or table would also require a re-query to be triggered too.

ArcGIS Pro 3.3.1; Oracle 18c 10.7.1 EGDB; traditional versioning (moving edits to base) To improve performance, provide an optional setting that would cache the data of a given FC, table, route event layer (dynamic segmentation is notoriously slow), and other layers. The data would be cached when the layer is added to the map or when the project is opened. When the user refreshes the map (pan, open attribute table, hit refresh in the map or attribute table, etc.) then Pro would query the database to see if any edits have been made since the last cache. If yes, re-query, if no, use the existing cache. The check for edits would be done by getting the maximum edit date from editor tracking. select max(last_edited_date) from linear_referencing_standalone_tbl This idea is specifically for an editor-tracking-based cache mechanism. The thought is that querying the max LAST_EDITED_DATE would be faster than re-querying and redrawing the entire layer, especially if the LAST_EDITED_DATE field has a database index. I'm aware that there are existing caching mechanisms in Pro. But I've tested via the Diagnostic Monitor > Logs, and Pro doesn't appear to be caching the data using the technique I described. In fact, I couldn't see any evidence of data caching in the Diagnostic Monitor logs. Layer Caching — How does Pro know when data was last updated? Documentation about new workspace caching functionality in Pro 3.3.0 Notes: As mentioned, it might help performance to index the LAST_EDITED_DATE field using a database index. As far as I know, there isn't a clean OOTB Oracle mechanism to determine the latest edit date of the rows in an Oracle table. I'm not sure about other enterprise geodatabases. That's why I have suggested an editor-tracking-based approach.

Esri Case #03632162 - New workspace caching in Pro 3.3 — Improved GP performance in EGDBs? Please see the answer from the Product Engineers below. They are referring to the caching mentioned in the What's New article. “That caching optimizes turning a catalog path (eg: "c:\myproject\x.sde\myuser.mytable"), which is the way you enter a dataset in GP, into an ArcObjects (AO) table object. More specifically, we keep a list of catalog paths, and associated AO "NameObjects", these name objects are very light (keeps the workspace object & table name). Upon getting the same catalog path, we can quickly get the NameObject and from there create a fresh AO Table object. This "creation of an AO Table object" can happen multiple times within a single GP tool operation… and of course multiple times across a python/pro session (which could use the same dataset in multiple GP tool operations). Why it's particularly advantageous with egdb, is that creating the workspace (connection to the database) is a remote service call which can be comparatively slow. This cache shouldn't cause stale table schema or stale table records.”

Can you show us some data in a screenshot of the attribute table or in an Excel export of the attribute table? What kind of geodatabase? For example, Oracle 18c enterprise geodatabase. Are there multiple industry fields in the existing data: INDUSTRY_A, INDUSTRY_B, INDUSTRY_C? Do you want a dynamic solution (the data changes over time) or is populating a static MAX_INDUSTRY field via the Field Calculator acceptable? You could post an Idea for this, asking for dynamic, out of the box functionality (no code) in the symbology pane, to see what Esri says.

You could try submitting this as an Idea to see what Esri says: https://community.esri.com/t5/arcgis-pro-ideas/idb-p/arcgis-pro-ideas

Esri Case #03690461 - Symbology and labelling permanently stored in geodatabase FC metadata Hi Esri Support, ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB Background: There is a known issue in some versions of ArcGIS Pro where symbology and labelling are permanently stored in the GDB FC metadata – as a “layer file” within the metadata. The symbology and labelling is automatically applied to the layer when it’s added to the map. The issue is caused when geoprocessing tools, such as Add Relate, are used on a FC. If there was symbology and/or labelling applied to the FC prior to the geoprocessing tool being run, then the symbology and labelling will be permanently applied to the FC metadata in the GDB, which is not wanted. In our case, I believe the permanent symbology and labelling was applied (a few months ago) to some of our FCs when a user was using ArcGIS Pro 2.6.8. We no longer use ArcGIS Pro 2.6.8, we use 2.9.5. My organization is unable to upgrade to 3.x at this time. It seems like there are two components to this issue: Ability to apply new permanent symbology and labelling in FC metadata via GP tools. Pro honors permanent symbology and labelling when a FC is added to the map. #1 and #2 applied to 2.6.8. However, in 2.9.5, I am only able reproduce #2 at the moment. Question: An Esri staff member mentioned in the Esri Community that this issue was fixed at 2.8: FC has symbology and labelling permanently stored in GDB? However, as mentioned, we are still seeing this issue at 2.9.5. Can you please advise: What versions (2.9.6+beyond) have this issue, and at what version (2.9.6+beyond) was it fixed?

Related: Timeline for ArcGIS Pro 3.4 release

My Ideas

Latest Contributions by Bud

Re: Add Join — Indicate that a definition query on join table will effectively result in an inner join

Re: move the Measure tool out of the way

Move measure tool outside of map view

Re: Add a tool sidebar help image in ArcGIS Pro 3.1.4

Re: Edit Log to capture Insert, Update, and Deletes via ArcGIS Arcade attribute rule

Re: Track Changes in Point Feature Class with Records

Re: Have ArcGIS Pro's Transfer Attribute Tool Preserve True Curves

Re: Getting fewer notifications than usual

Re: Cache data and only re-query if subsequent edit found via editor tracking date field

Cache data and only re-query if subsequent edit found in editor tracking date field

Re: Documentation about new workspace caching functionality in Pro 3.3.0

Re: Symbolise by maximum value field's name

Re: Swapping Attributes between shapes

Re: FC has symbology and labelling permanently stored in GDB?

Re: Publish planned Pro release dates online

Case-sensitive one-to-first joins

Explore Tool — Automatically display feature attri...

Query Layers — Option to preserve all rows from un...

Move measure tool outside of map view

Catalog Pane — Scroll using mouse wheel when dragg...

Mapping and Charting Enterprise Databases

Roads and Highways User Group (RHUG)

GIS Jobs