Latest Contributions by AZendel

If I'm interpreting these posts correctly, there is no way to specify that a particular/individual geoprocessing model should overwrite its outputs. The only option is to set this in the Pro options tab as shown in the first post. Is this still the case? I'm calling a lot of geoprocessing models from ArcPy and I want to allow some of the models to overwrite existing outputs. This setting in the Pro user interface is likely ignored when running a completely standalone ArcPy script.  Please confirm when you can. And ESRI, if you're reading this, please allow this option to be set within individual models.  ... View more

Is this still the case with ArcGIS Pro 3.0? I have a stand alone vb.net exe that executes geoprocessing models using libraries/assemblies from ArcMap 10.8.1. Windows Task Scheduler wakes it up every hour and it also performs a lot of SQL tasks via native SQL Server client libraries.  It also calls a geoprocessing model that geocode addresses and later calls another geoprocessing model that appends those features to a feature class. Since ArcMap will not exist in the future, I'm trying to migrate it to rely on libraries from Pro. Here's the VB.net / ArcObjects code: Dim parameters As ESRI.ArcGIS.esriSystem.IVariantArray = New ESRI.ArcGIS.esriSystem.VarArray Dim GP As esri.ArcGIS.Geoprocessing.IGeoProcessor2 = New esri.arcgis.Geoprocessing.Geoprocessor() 'Add the BestPath toolbox. GP.AddToolbox("C:\path\to\my\toolbox.tbx") parameters.Add(sGDBPath & "\databasename.DBO.myfeatureclass") 'Execute the model tool by name. GP.Execute("DeleteCountyStatusPermits", parameters, Nothing)   There's no way to do this on machines that have Pro and not ArcMap? It would be nice to not have to 'wrap' these models in python scripts - that adds too much complexity to maintaining my project.  Thanks for your time,   Alex ... View more

Thank you for the update, Jared. And thanks for listening, ESRI.  ... View more

It looks like the 64-bit compatible accdb MS Access format allows 'OLE Object' data types, which is the same field data type that the .mdb formatted Personal Geodatabases used to store the shape/geometry fields. So in theory, ESRI could have migrated the Personal Geodatabases to this new format. ESRI, if you're not keen on porting the PGDB to accdb, please start treating "Personal ArcSDE" geodatabases (based on SQL Express and one step down from the 'Workgroup Geodatabases') as first class citizens in Pro: 1) Allow the creation of these (and Workgroup GDBs) in Pro. We still have to do this in ArcMap or ArcCatalog 2) Make the user restrictions similar to the file geodatabase and personal geodatabase: a substantial number of read connections, only one editor. I myself hit the 5 read connection limit when I have a few geoprocessing models running while also reviewing the data in a maps. My coworker should also be able to read the data to help me QC output. You allow this in File Geodatabases and Personal Geodatabases, so why not in 'Personal ArcSDE' databases? This will still allow us to access our data via SQL tools: MS SQL Server Mgmt Studio, Azure Data Studio, ODBC links into numerous applications.  I was excited for the SQLite/Mobile geodatabases when they were announced, but as Steven noted above, they aren't very compatible with ODBC and third party tools: 1) you cannot do joins against text fields when connected via ODBC since the drivers consider all text fields to be 'memo' or long text fields. This is a problem in read-only (SELECT) queries and update queries.  2) you cannot update a non-spatial field in any type of feature class because the drivers don't have the libraries to maintain the spatial indexes. I believe that an update in SQLite is more akin to deleting the original record (feature) and then creating a new record (feature) -- this can't be done without the libraries needed to maintain the spatial index.  We need reliable SQL access to our data. If you won't give us ACCDB database, please loosen the reins the 'Personal ArcSDE' databases to allow more read connections. Please also allow the creation and management of these database types in Pro.  ... View more

Yes, please! This is so handy in other graphics programs. In addition to 0, 45, 90 degrees, it's be nice to have 30 and 60 degrees too.  ... View more

@KoryKramer , thanks for the reminder on the kudos. Done.  It'd be ideal to keep the PDF as a vector format (if the PDF contains vector layers). So ideally, it would be like a georeferenced PDF or a "GeoPDF" once you complete the georeferencing process.  ... View more

Yes, please! The majority of site plans and plats that we receive these days are PDF (and they should be since PDFs preserve vectors). I'd love to see native PDF georeferencing without having to convert it to a separate format.  ... View more

I agree. ESRI, please improve/fix this! ... View more

We often have databases with 200K, sometimes 1M+ records. Geoprocessing is way too slow when doing joins --> select by attribute --> calculate field, even with proper indexes. SQL can do it in a couple of seconds (literally) with UPDATE ... INNER JOIN....WHERE. There are many other areas where SQL is much more efficient than geoprocessing (and sometimes the opposite is true).  Beyond the need for Desktop Geodatabases, is ESRI going to continue to offer the Workgroup database? It seems like those can't be administered from Pro either.  ... View more

@George_Thompson , are there any updates to this? We rely on the 'Desktop Geodatabase' (formerly 'Personal ArcSDE' database) quite heavily. We are trying to ween our staff off of ArcMap since it won't be supported much longer.  ... View more

Yes, please! GPX files are likely to be a part of the industry for many years to come. I don't necessarily need 'drag and drop' functionality, but I'd like to add a GPX file to a map/scene in Pro via the 'add data' button or via the catalog pane without having to convert it to FGDB or shapefile first. ... View more

Thanks for your responses. I wonder if we are talking about 2 different issues. The 10 second wait that I'm talking about happens when you list the database contents by double clicking the database connection below ArcMap/ArcCatalog   ArcGIS Pro:   Our Oracle SDE database is otherwise very performant, even with large datasets that are versioned and/or have archiving enabled. The county's DBA regularly compresses the database to flush out the add and deletes tables when necessary. I imagine that he conducts other tuning and maintenance tasks to keep database operations in a healthy state. I only notice significant latency while waiting for Arc* desktop products to list the contents of the database. That's what makes me suspect that ESRI developers may want to investigate if they can improve the queries that this action kicks off.  Is anybody else experiencing this? ... View more

@ShanaBritt, thanks for clarifying! Our central GIS office manages our ArcGIS Server environment. A good number of people are on older versions of ArcMap, so I'm not sure if they can upgrade the locator yet. When that option is available, can you include the 'new' geocoding output fields (score, standardized address, etc.) and not have USER_ appended to the input fields? That would be the sweet spot for my needs.  ... View more

When using one of our inhouse locators (served via ArcGIS Server), I don't get the option mentioned in step 6D mentioned above. And I often want the geocoding result fields, such as match type, score, standardized address, etc. They help me hunt down poor matches. But what I do NOT want is the USER_ prefix on all of the input fields. ArcMap didn't do this. ESRI, please provide an option to exclude the USER_ prefix regardless of what geocoding service/locator that you're using! I think this idea should be reopened. ... View more