Latest Contributions by MattWilkie1

I ran into this too. GDB in SQL Server 2019 seem to be ok with indexing enabled, but regular db are invisible. In Sql Server 2016 and Oracle 19c both db and gdb are empty. Thank you Esri Canada's Sukhjit P. for putting me on the right track with this thread. Solving this was a multiday endeavour.

wonderful! thanks to all involved

‎02-22-2024

I've since located a UI path that's simpler than what I outlined above: there's a 'clear limits' button on the Feature Layer ribbon. This is good for my overall sanity, but still different from what this idea is about. The button is to clear limits on a single layer at a time, and the old values are lost. The idea is about simply toggling the limits on/off for all layers at once, though now that I think about it, it would be better as "all selected layers in ToC".

‎02-22-2024

I work a lot with layers that have Visibility Ranges set so they do or don't show in or out beyond certain zoom levels. This is a handy and needed feature. However I also very frequently, daily, need to remove the scale visibility for the duration of some task. It would be very useful to have a button, in the View ribbon perhaps, to toggle the Visibility Range settings on/off, so we don't have to "select layer >> properties >> General >> delete min >> delete max >> Ok" again and again. And then add them back again when finished the task.

‎02-15-2024

As often happens, the process of properly writing a question reveals a path to the answer. In this case: look a the metadata for the oracle spatial view and see of the Processing History has useful information. It does! Geoprocessing history Process Process name ...snip... Command issued: RegisterWithGeodatabase "Database Connections\..." which leads us to Register With Geodatabase: Registers feature classes, tables, views, and raster layers with the geodatabase. Registering is used for data created in the database with third-party tools using SQL or in ArcGIS Pro with tools that do not register with the geodatabase (Create Unregistered Feature Class, Create Unregistered Table, and Create Database View tools). Only limited functionality is available from ArcGIS clients and services for data is that is not registered. Registration stores information about the items—such as table and column names, spatial extent, and geometry type—in the geodatabase's system tables. This allows the registered items to participate in geodatabase functionality.

‎02-15-2024

What specfically is a "database feature class", as distinct from "feature class"? For example in Catalog here we see 3 layers in an enterprise sql server geodatabase. The bottom and top ones are regular polyon feature classes created the regular way. The middle one is also a polygon layer, but is created with the Create Database View geoprocessing tool. All 3 of them can be added to a Map in Pro and they behave identically in the map as far as we can tell for symbology, labelling, selection, etc. Why does Catalog not see the view as Polygon type? In another ent-gdb I have access that is oracle hosted instead of sql server there are spatial view layers, but they area seen the same as normal FC. I don't know how these oracle spatial views were created. How do we get our sql server database views to be recognised as layers with geometry types before adding them to a map?

‎02-08-2024

It's good to see this is now in the Product Plan, thanks @SusanTran . Please pass on: while they're working in this module, also increase detail in the warning and error messages that are produced. For instance what brought to me to revisit this idea today is that both Ribbon and GP packaging tools are are failing on sharing a particular project. The message simply says "Failed to consolidate project due to problem with Geoprocessing History item: Package Layer." There are many items in the history for "Package Layer". Which one is it? If the job number or date or something was included in the message I wouldn't have to go through the slow method of removing them one by one to identify the culprit.

‎12-28-2023

Hardlinking individual files between separate file geodatabases will definitely cause corruption of one or more of the geodatabases, it would be a matter of when and not if. Thank you for confirming. I thought this might be the case but wasn't sure. You're right that changing workflow is the <strike>better</strike> only real solution. I first started raising the alarm over "this is a workflow problem" 10 years ago when we were bumping against 2 TB. Twice since then the chosen mitigation has been "buy bigger servers" so now we're at 22 TB on a 24 TB volume, having the same conversation again. Whee.

‎12-28-2023

Thanks for that clarification Joshua, and drawing out that Randy and my scenarios are different. I was using the language of the reporting tool, Tree Size Pro, which uses 'deduplicating' when it's talking about hard linking (ref). So we are asking very different questions. Mine is: is hardlinking file-gdb files a la Tree Size Pro deduplication dangerous?

‎12-28-2023

How did this work out Randy? Our file reporting tool is finding terabytes of duplicate files within file-gdb directories but I'm not sure I believe it. Or better said as: I trust that the contents of these reported dupes are currently identical, but I'm concerned that replacing the duplicates with hardlinks to a single source will mean that when ArcGIS changes one of them, that will cascade through all the others, and that would almost certainly be wrong.

‎12-19-2023

Yes please! This topic is worth exploring. I'm also interested in whether this spatial queries have the same performance profile, in general, across DB vendor types. For example are PostGIS and SQL Spatial using their native spatial types equally slower than in-client location queries? Assuming they are similar, what exactly is happening to slow things down?

‎11-16-2023

that link is " Sorry, the page you are trying to access has either been archived or you are unable to access with the account you are logged in with."

‎10-18-2023

Hello world, Anyone know of software that's capable of digitizing hand written field forms with results that are worth using? Field observation form with table of handwritten data and coordinates in degrees, minutes seconds. MS Office "copy text from picture" fails miserably. I've tried a couple of online services that allow demos without going through a tedious sign up process but they were only marginally better. Many numbers were recognized, but without the table structure so it comes out a jumbled mess. Recommendations?

‎10-16-2023

I haven't fully ingested your setup, that will take more attention time than I have at the moment as I try to solve my own challenge du jour, but one thing that comes to mind is perhaps `proswap.bat`? (found by way of https://samgeo.gishub.org/examples/arcgis/)

‎10-12-2023

Where do you save python scripts and modules for re-using across multiple projects? That you yourself work on? That you share with colleagues? I'm not asking about how to share python modules or modify PYTHONPATH and so on. I'm interested in what conventions have you settled on as practical for your general operations in ArcGIS Pro. For example, I save my batch and powershell scripts that are used for general system maintenance in C:\bin. The corollory for tools that I and co-workers share is Z:\Tools\bin. Both of these are in PATH. Having settled on a location, how do you make them available across projects? To yourself? to co-workers? As above, my question isn't about the technical how to package scripts but the practical day to day use of them. ArcGIS Pro defaults to extracting under "C:\Users\USERNAME\Office365_Onedrive_ORG_NAME\Documents\ArcGIS\Packages" which is a horrible path to refer to repeatedly. What's your alternative? High value scripts can be added to a project toolbox and then "Add to New Projects" and be always at finger tips. What about things that are less polished? Something that does useful work but the doesn't warrant the overhead of adding parameters and tool validation etc. to make it a 'tool'. Lastly, how do you work with other python projects that are not ArcGIS? Do you resign yourself to using Pro's built in Package Manager and cloning? Or just stay inside what's given and not reach for new cool things in python 3.11 and 3.12? I've tried installing Anaconda/Miniconda alongside Pro (the built in one is dreadfully slow). I made a mess of things that wasn't straightened out completely until I got a new machine. Maybe an isolated experience though, there is a way to dance together cleanly, and I just fumbled. Thanks in advance for your thoughts and experience.

Online Status	Online
Date Last Visited	7 hours ago

My Ideas

Latest Contributions by MattWilkie1

Re: ArcGIS Pro 3.2 database connections to SQL Server 2019 not showing contents, no error

Re: Optionally package history including errors

Re: Toggle Visibility Range for all layers

Toggle Visibility Range for all layers

Re: What is a Database Feature Class?

What is a Database Feature Class?

Re: Optionally package history including errors

Re: Data Deduplication on the File System

Re: Data Deduplication on the File System

Re: Data Deduplication on the File System

Re: Why are spatial SQL queries so much slower than Select By Location?

Re: Overwrite Web Map from Pro

OCR of hand written coordinates in field forms?

Re: Conda activate scripts are not executed within ArcGIS

Reusing python scripts and modules across projects

Re: What is a Database Feature Class?

Re: Why are spatial SQL queries so much slower tha...

Re: Overwrite Web Map from Pro

Re: Offline S123 map example

Optionally package history including errors