Latest Contributions by JoshuaBixby

Are you trying to load spatial data or just a table?  Was the SQLite database created by ArcGIS Desktop or some other application?  If the latter, try making a SQLite database from ArcGIS Desktop and putting some data in it, and then see if ArcGIS Pro sees that database, especially if working with spatial data. ... View more

If communicating with Esri feels like screaming in the wind at times, dealing with Apple is like having that conversation in an asylum.  I gave up on them a long time ago, which is too bad because they do make some good products. ... View more

It is easier for fellow GeoNet community members to provide feedback if you post relevant, functional parts of your code. ... View more

I think Esri would agree, i.e., SQLite isn't currently fully supported in ArcGIS Pro. Although "seeing" SQLite databases isn't possible through the Project pane/window, you can load SQLite databases using the Make Feature Layer tool either through the GUI or ArcPy.  At least during beta testing, Spatialite-based spatial data wouldn't load because the correct DLLs weren't packaged with the installer, not sure if that changed.  I have successfully loading ST_Geometry and GeoPackage spatial data into ArcGIS Pro. ... View more

You can force indexes through Query Hints (Transact - SQL).  That said, forcing an index may not improve performance, sometimes it makes performance worse.  Since it seems you are in a development/testing phase and not writing production code yet, it might not hurt to experiment with forcing the different indexes to see what happens.  If forcing an index does help, especially dramatically, then the question becomes why isn't the query optimizer choosing to use either index.  By the way, I believe it is still true that SQL Server can only use one spatial index in a single query, but that may have changed. If you haven't already, you may want to review SQL Server 2012 - Spatial Indexes Overview.  The more you understand how MS has implemented spatial indexes, the less of a black box it will all seem, which makes for better SQL troubleshooting.  Also, there are some very specific syntax rules for maximizing a nearest neighbor type of query, which you are trying to do in some form. Beyond reading MS's overview, there are some good blogs and MSDN discussions on tuning SQL Server spatial indexes. Taking a quick glance at your specific code, you are missing some of the requirements for a spatial index to be used.  As the overview documentation I linked to above states: Geometry Methods Supported by Spatial Indexes Spatial indexes support the following set-oriented geometry methods under certain conditions: STContains(), STDistance(), STEquals(), STIntersects(), STOverlaps(), STTouches(), and STWithin(). To be supported by a spatial index, these methods must be used within the WHERE or JOIN ON clause of a query, and they must occur within a predicate of the following general form: .... ... View more

That error with findAndReplaceWorkspacePath is common when you are trying to not just replace the workspace path but also the workspace type.  Are you switching from a personal geodatabases to a file geodatabases?  If you are switching workspace types as well, then you need to use replaceDataSource as Xander Bakker‌ suggests. Also, if you are going to be coming across group layers or layers with lots of different data sources, it is good to use the layer.supports method to check the layer supports a data source property. ... View more

You mention "query table."  Are you using Make Query Table or Make Query Layer?  Make Query Table is powerful, but it is an older tool, and I am not sure if its outputs are editable. I just did a quick test using Make Query Table where I took a single feature class and used Make Query Table to create a layer, so this is a very simple case without multiple data sets or joins.  Although I could use an update cursor on the feature class directly, I could not use it on the layer created from Make Query Table. ... View more

Although using lists for field names is much more common, tuples are supported.  I am leaning more towards the query table. ... View more

Although I don't think this is related to the error, it looks like your indentation is off on lines 03 and 04.  Not sure if the code itself is that way or just a copy & paste problem into the text box. Can you post the specific error output, all of it?  Knowing the line of the error is helpful, but usually additional information is output that is also helpful. ... View more

I agree with Xander Bakker‌, i.e., you can't remove all of the data frames from an MXD.  Even through the GUI, you can remove data frames until you get down to the last one, at which point you are not allowed to remove it. If you want the border of the frame to not be visible, you can go in and change it, just not through ArcPy unfortunately. ... View more

Interesting, or oddly, IDLE on my 10.3 machine handles it fine. I am still convinced the extra error message is tied to the console where the original error message is trying to be printed.  That said, I can't imagine a bit change in IDLE or Python between 10.2.2 and 10.3. As you point out, you already know how to work around the issue, which is really the most important thing.  In terms of Unicode characters, it would be interesting to know why the ArcSDE errors are getting returned with a problematic character on the end. ... View more

The issue you are experiencing is likely due to your console the error messages are being printed to and not Python itself. If I run similar code in the interactive Python windows in ArcMap, it prints fine.  If I run the code in PyCharm, it prints fine.  If I run the code from a Windows command prompt, it generates a similar error you are seeing.  My guess is that the PyScripter console is not coping with the Unicode and hence the extra error is being generated. ... View more

Unlike the MXD version of findandreplace, which ends in paths, plural, the LYR version of findandreplace end in path, singular.  I am not sure whether the LYR version recursively searches or not, like the MXD version.  If not, you can add some code to loop through all the layers in a layer file: layer_paths = [list of layers with paths] for layer_path in layer_paths:     layer = arcpy.mapping.Layer(layer_path)     for lyr in arcpy.mapping.ListLayers(lyr):         lyr.findAndReplaceWorkspacePath(...)     layer.saveACopy(...) ... View more