Latest Contributions by Bud

‎05-12-2024

@DrewFlater The docs say: Update item properties in metadata - Geoprocessing history and metadata You can optionally log geoprocessing operations in the item's metadata. When this option is enabled, each time you run a tool that modifies the item, an entry is added to the item's metadata. Are the docs misleading? The Add Relate tool doesn't modify the item, but Add Related is tracked in the item metadata.

‎05-12-2024

As @BarryNorthey mentioned, it sounds like the "How was the FC created?" info is available in the FC metadata: Metadata will be created for the feature class by the process, and it will be updated to include the first entry in the geoprocessing history to indicate how the item was created. So I guess that just leaves the "How was the geodatabase created?" question. @DrewFlater might find this interesting.

‎05-11-2024

I don't see how a request for additional documentation would be "too complex" and an "unimplementable feature". If Esri's testing/benchmarking hardware changes over the years, then that could be noted in the documentation to provide context. It's when a tool is orders of magnitude slower that we want to watch out for. It's difficult to find a version of Pro that doesn't have show-stopper bugs. Each organization has its own specific must-haves. Documentation like this would help us find a version of Pro that will work for us.

‎05-11-2024

@RTPL_AU We are not discussing performance issues but Esri being more transparent about 'things' they introduce that will impact paying customers' productivity. The core of the idea is the implementation of functionality, either in ArcGIS Pro, or in related documentation, that exposes more information about new versions and potential benefits/regressions. Related post from @JoshuaBixby here: New Geodatabase Features Add Functionality But Complicate Compatibility and Interoperability

‎05-10-2024

ArcGIS Pro 3.3.0; Oracle 18c Database: I want to use a FC as the Target Feature Class in the Make Aggregation Query Layer tool. The FC has a text field that is a unique identifier. The tool is giving me an error: Error 000358 No fields can be mapped to unique identifier. Bud_3-1715409261801.png Bud_2-1715408655311.png If I add a Long Integer field to the FC, then that field can be used as the unique ID. I wouldn't get the error. But that's not how my data is structured. My ID field is text, not integers. Could the tool be enhanced so that a text field can be used as the unique ID?

‎05-10-2024

ArcGIS Pro 3.3.0; Oracle 18c database: It looks like the Make Aggregation Query Layer only supports "feature classes or spatial tables" in the Target Feature Class parameter. Bud_0-1715406648103.png Error 000368 Invalid input data. Could that tool be enhanced so that it allows non-spatial tables as the target? Or is there a reason why that wouldn't work?

‎05-10-2024

One-to-first joins are case-insensitive. That's inconsistent with one-to-many joins which are case-sensitive. ArcGIS Pro 3.3 — Add Join (Data Management) Optionally, set the Join Operation parameter to Join one to first to prevent duplicate object IDs. The Join Operation parameter has three states to adjust the cardinality. The default is blank and will allow the data source to attempt a one-to-many join. The Join one to many option will work only on specific data sources that have an Object ID field. The Join one to first option will use the first match in the table, which may result in different outputs if the Object ID field is changed or the workspace the table is copied to changes. One-to-first joins are not case sensitive; one-to-many joins are case sensitive. To make joins more intuitive, make them all case-sensitive. Why aren't one-to-first joins case-sensitive?

‎05-10-2024

[removed]

‎05-10-2024

Possibly relevant: What's new in ArcGIS Pro 3.3 - Enterprise geodatabases and databases If your enterprise geodatabase contains branch versioned data, it is strongly recommended that you upgrade the geodatabase at ArcGIS Pro 3.3. See How Upgrade Geodatabase works for more information.

‎05-10-2024

Notes: A user other than me could have edited the data since the last cache. Editor tracking is enabled for both the FC and the table. Does Pro compare the max editor tracking date/time against the last cache date? As far as I know, there isn't an OOTB Oracle mechanism to determine the last DML time of a table. It doesn't seem like much caching is being done in Pro with the Route Event Layer. 10 seconds is a long time to wait for a layer to load. The Diagnostic Monitor logs suggest nothing is being cached. Bud_0-1715391265193.png Is there anything I can do to make it cache better to improve performance?

‎05-10-2024

ArcGIS Pro 2.9.5; Oracle 18c 10.7.1. EGDB: In the Catalog data source properties of an FC, there are index names displayed in the Indexes tab. Bud_0-1715382998864.png When doing database admin and documentation work, it would help if we could right-click a given index name and copy it to the clipboard.

‎05-10-2024

@SSWoodward Yes. I edited the idea.

‎05-10-2024

Also, why does searching for query layer extents produce more results than extents? If anything, I'd think query layer extents would further refine the query (fewer results) since it is more specific, compared to extents.

‎05-10-2024

Create a fake view via a SQL client (outside of Pro) that uses the same name as the broken Catalog view: create or replace view roll_up_vw as select 1 as objectid from dual Then, delete the view via Catalog. The view will disappear from Catalog.

‎05-10-2024

ArcGIS Pro 3.3.0; Oracle 18c database (non-GDB) Sometimes database views get broken in ArcGIS Pro. I try to delete the view using Catalog, but I get various errors. Often, the cause is the view has been deleted from the database. The view was never registered with the geodatabase (in this particular case, the Oracle database is not an enterprise geodatabase, proving that the view isn't registered). So it's unclear why the view persists in Catalog since the view wouldn't be listed in any geodatabase system tables (since the geodatabase system tables don't exist). How can I delete the broken database view from Catalog?

My Ideas

Latest Contributions by Bud

Re: Don't track GP tools like Add Relate in item metadata

Re: Automatically log information in GDBs about how the GDB or item was created

Re: Benchmark GP tool execution times against previous versions

Re: Benchmark GP tool execution times against previous versions

Make Aggregation Query Layer — Use text column as unique ID

Use standalone table as target in Make Aggregation Query Layer

Case-sensitive one-to-first joins

Re: Are UTM coordinates at bottom of map view independent from UTM projection in Project's Map/FC?

Re: New Geodatabase Features Add Functionality But Complicate Compatibility and Interoperability

Re: Layer Caching — How does Pro know when data was last updated? (LRS)

Copy database index name from Catalog properties

Re: Catalog Copy/Paste — Don't bring over "main." alias prefix from mGDB table to fGDB table

Re: Why does searching for singular word "extent" return fewer results than plural "extents"?

Re: How to delete a nonexistent, broken database view from Catalog

Delete a nonexistent, broken database view from Catalog

Integrate ArcGIS Data Pipelines in ArcGIS Enterpri...

Send configurable email notifications from ArcGIS ...

Re: How reliable are ArcGIS Online webhooks?

How reliable are ArcGIS Online webhooks?

Sharepoint List Connector

GIS Jobs

Roads and Highways User Group (RHUG)

Local Government Solutions Users

Mapping and Charting Enterprise Databases

ArcGIS Arcade