POST
|
After upgrading to ArcGIS Desktop 10.8, I initially got the 'unable to run' error message and found and installed the patch. After installing the patch, the application now simply does not run. Event Viewer shows an error with an exception code of 0xe0434352. Anyone else having this issue post-patch?
... View more
05-18-2020
11:32 AM
|
0
|
0
|
293
|
IDEA
|
This really seems to be the sticking point that ESRI is not taking into account: that there are workflows, there are business needs, that require working on spatial data in non-spatial contexts, and PGDBs are a standard, efficient way of managing and transferring that data.
... View more
04-19-2019
08:12 AM
|
0
|
0
|
953
|
POST
|
Not a question, per se, because I've solved it, but since it's impossible to report a bug to ESRI, I wanted to make sure the fix was available somewhere. In PyCharm and other IDEs, an attempt to import `arcpy` throws one of the two following errors: error: [Errno 10054] An existing connection was forcibly closed by the remote host or error: [Errno 10053] An established connection was aborted by the software in your host machine In the `interop.py` module, the docstrings for QuickImport and QuickExport contain URLs that do not have slashes properly escaped. Because the docstring isn't a raw string, the slashes are thus considered to start escape characters, as typical for Python string parsing. (\a seems to be the culprit in this case.) This causes an error on import in some IDEs. The fix is simple: escape out all slashes in URLs contained in the docstrings. Thus, instead of this: * The ** characters match any subdirectories, recursively. For instance, c:\data\**\*.mif will match c:\data\roads.mif, c:\data\canada\rivers.mif, and c:\data\canada\alberta\edmonton.mif. the docstring should include this: * The ** characters match any subdirectories, recursively. For instance, c:\\data\\**\\*.mif will match c:\\data\\roads.mif, c:\\data\\canada\\rivers.mif, and c:\\data\\canada\\alberta\\edmonton.mif. I manually edited `interop.py` to resolve the issue, but I was hoping to notify ESRI so that they could fix the issue on their end.
... View more
10-25-2017
12:08 PM
|
0
|
0
|
334
|
IDEA
|
Further, FGDBs only support a restricted subset of the SQL language, and some parts of the subset are only accessible through ArcObjects (using their PostFixClause attribute). You can't, for example, use ORDER BY or DISTINCT to select by attribute with an FGDB, but you can with a PGDB. PGDBs aren't perfect, but they do have their uses.
... View more
06-16-2017
08:33 AM
|
5
|
1
|
7016
|
Title | Kudos | Posted |
---|---|---|
5 | 06-16-2017 08:33 AM |
Online Status |
Offline
|
Date Last Visited |
03-09-2023
08:21 PM
|