Latest Contributions by JoshuaBixby

If you are using ArcGIS Pro, which you should be by now, then 7.1.1. Formatted String Literals - Python 3.11.1 documentation are your friend.  Try: expression = f"reclass(!{widthField}!,!{lengthField}!,!{num}!)" ... View more

Not sure how it could get much simpler.  If the passing of field names is removed, the code boils down to: ', '.join([str(i) for i in [ ] if i]) That is pretty simple and compact.  The bulk of the line is in field names, and you can't remove them. ... View more

You are having a text encoding issue.  See geopandas.read_file -- GeoPandas 0.12.2 documentation: Notes The format drivers will attempt to detect the encoding of your data, but may fail. In this case, the proper encoding can be specified explicitly by using the encoding keyword parameter, e.g. encoding='utf-8'. ... View more

@RachelGomez , the original question had to do with ArcPy cursors and not computer mouse cursors, so checking hardware and mouse and trackpad settings would have no effect. ... View more

Esri has a bigger problem with that documentation you reference because ArcObjects has nothing to do with ArcGIS Pro.  According to ArcObjects Help for .NET developers (ArcObjects .NET 10.8 SDK), "ArcObjects is a library of Component Object Model (COM) components that make up the foundation of ArcGIS [Desktop/ArcMap]."  The ArcGIS Pro SDK for .NET is a completely different SDK than ArcObjects SDK, and there is a chance the code examples don't even transfer over.  It looks like Esri got sloppy and just fork-lifted the Desktop document over as Pro documentation. ... View more

Have you checked whether the issue is with selecting?  If something isn't working correctly with Select, it may be there isn't anything selected for Intersect to operate on. ... View more

@Bud wrote: What version of SQLite is the .geodatabase file? The question taken literally/explicitly doesn't have an answer, or at least a single answer.  SQLite as a file-based, serverless database has lots of different "versions."  Looking at Database File Format - SQLite Documentation, there are: File format write version File format read version Schema format number/version "user version" version-valid-for number SQLITE_VERSION_NUMBER One might assume your question is regarding the last version in the list above, but it is important to note that SQLITE_VERSION_NUMBER isn't the version of the SQLite client that created the database file, but the version of the SQLite client that "most recently modified the database file."  Upon first creating a SQLite database file those two are one of the same, but that isn't always the case. So is your question really "what version of SQLite is bundled with ArcGIS Pro 3.0.3?"  If so, just open up the ArcGIS Pro  Python Command Prompt: (arcgispro-py3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3> sqlite3 --version 3.38.2 2022-03-26 13:51:10 ...... The above is for Pro 3.0.2. ... View more

The SQL that is supported in ArcGIS applications has always depended on the back-end database/datastore.  The SQL reference for query expressions used in ArcGIS - ArcGIS Pro | Documentation clearly states: Review the following to help determine when ArcGIS SQL syntax is used or when the SQL syntax of the underlying RDBMS is used when creating an SQL expression. If the data within your SQL expression comes from a mixture of data source locations, the following will occur: Where the data sources come from both file-based and from an RDBMS, ArcGIS SQL syntax will be used. If all the data within your SQL expression comes from the same data source location, the following will occur: Where the data source is file based data, ArcGIS SQL syntax will be used. Where the data source is a database or enterprise geodatabase, ArcGIS will pass the SQL expression to the RDBMS for resolution and you will need to consult the documentation for your database management system for the specific expression syntax and data types supported. There is no minimum SQL standard at the geodatabase level.  If you are interested in SQL that is portable across multiple databases/datastores hosting geodatabases, then you need to look at the versions of those databases/datastores and determine what versions of SQL they support. Even viewing this as a database question and not a geodatabase question, the answer isn't straightforward because I don't think a single DBMS fully supports any specific version of the SQL standard.  Most database software companies like to use language similar to "provides full or partial conformance to SQL-XX," and one has to look deeper to see what exactly is supported. ... View more

I will be using the old UI for as long as you keep it around, so please keep the option around for a long time to switch back to old/classic UI. I find the new UI cumbersome, worse in several areas than the old UI.  I have also been running into lots of issues with filters not working correctly, so I just switch back to classic UI and get what I need in a few seconds. PLEASE (yes, all caps) bring back the Quick Search for Esri Support cases, defects, etc... ... View more

Regarding your question, yes, but the answer is slowly changing to, no.  Not all ArcGIS products  support mobile geodatabases and some only support a limited subset of functionality with mobile geodatabases.  ArcGIS Desktop/ArcMap is a good example with its very limited support for mobile geodatabases.  Over time older products like ArcGIS Desktop/ArcMap will be retired and most new ArcGIS products or versions are supporting more functionality with mobile geodatabases.  In the end, I suspect file geodatabases will always perform better than mobile geodatabases, but mobile geodatabases offer much better SQL support, so one will have to weigh the tradeoffs when deciding. ... View more

After years, more than a decade, of Esri not really responding to requests to improve SQL support and documentation of SQL support for file geodatabases, I would not be holding one's breath.  Now that mobile geodatabases are getting more support across ArcGIS product lines, I am using them more and more. ... View more

ArcPy AddMessage will display the expected result if you create the string yourself and then pass it to AddMessage.  For example, don't do arcpy.AddMessage(tuple), instead do arcpy.AddMessage(str(tuple)).  I would say this is another defect, but my overall suggestion is to always build the string you want and then call AddMessage because AddMessage is really about passing back informational messages, i.e., text. ... View more

Although a Query Layer and Database View could give the same result within a map, the implementation is different.  I think the difference is enough to warrant keeping this idea. ... View more

Instead of adding code as a comment, I suggest you update the original question with the added code.  Doing so would put all the relevant information in the same spot.  Also, don't use screenshots of code, but paste the code and use Posting code with Syntax Highlighting on GeoNet  ... View more