POST
|
I have a feature service set up that includes several relationship classes between feature classes. When I select features by attributes in the origin layer, I then click 'select related records' for the desired layer. The attribute table of the desired table opens, but no records are selected. When I manually select records, the selections seem to work better. There are 1,785 records selected in the origin table when I run the selection query. Are there any kind of limits or stipulations when using relationship classes with feature services? Any ideas about what I can do to fix this? This is happening in both ArcGIS Pro and ArcMap 10.7.
... View more
10-16-2020
08:25 AM
|
0
|
0
|
34
|
POST
|
I've been generally frustrated with Pro's lack of ability to complete simple tasks without being so slow that it is unusable. Most frustrating right now, is the speed that it takes for Pro to update after setting a definition query on a layer. Is there some reason why this is so slow or something I can do to make it faster? Currently, if I set a definition query, it will take around 30 seconds to a couple minutes for the window to become active again.
... View more
07-17-2020
09:18 AM
|
0
|
0
|
61
|
POST
|
Ahhh, I'm connecting to Access 32 bit. This is probably the issue, right? Is there a workaround for this at all other than the 64 bit install of Access?
... View more
05-08-2020
12:11 PM
|
0
|
1
|
454
|
POST
|
I have a Python script that connects to an Access database, brings in some data, and then appends to a feature layer in ArcGIS. This script runs okay as a stand-alone script, but I am having issues creating the connection to the Access DB from within ArcGIS Pro. I installed the PYODBC module in the Python manager. Then, when I try to make a connection to the Access DB with the same code that works in the stand-alone script, I get this error message: pyodbc . InterfaceError : ( 'IM002' , '[IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified (0) (SQLDriverConnect)' ) This happens whether being run in a tool or whether the following code snippet is run from within the Python window in Pro: conn = pyodbc . connect ( 'Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=P:\\Conservation Programs\\Natural Heritage Program\\Data Management\\ACCESS databases\\POND_entry\\POND_be.accdb;' ) Any insight would be much appreciated.
... View more
05-08-2020
09:07 AM
|
0
|
3
|
822
|
IDEA
|
I am also running into major speed issues in ArcGIS Pro 2.5 when trying to accomplish very simple tasks that makes Pro practically unusable for my workflows. Right now, my biggest issue has been with definition queries. When I set a definition query on a feature service layer with around ~11,000 features, it takes anywhere from 3-8 minutes for the Pro project to become responsive again. When I set a definition query on the same dataset with the same computer and connections, it updates instantaneously.
... View more
04-13-2020
11:00 AM
|
5
|
0
|
1163
|
POST
|
Anyone else notice that ArcGIS Pro is super slow to update after establishing a definition query on a feature service layer? I will list a new definition query on a layer with ~11,000 records and press okay and then it will take about 5 minutes before I am able to open attribute tables or do anything in Pro. In ArcMap, it is almost instantaneous with the same feature service layer.
... View more
04-10-2020
02:50 PM
|
0
|
0
|
167
|
POST
|
I'm continuing to have issues with previous functionality not working after the update to Pro 2.5. I'm trying to use arcpy.da.InsertCursor() to insert features into a feature service feature layer. This is something that I did fairly frequently without problems prior to the update. After the update to Pro 2.5, I am getting the following error: RuntimeError: ERROR: code:500, Unable to complete operation., Unable to perform applyEdits operation., An error occurred., Internal server error. I am attempting to insert into a feature service layer that is in a project in ArcGIS Pro. I'm able to edit, create, delete fine in the feature service manually. An example of the code I'm trying to run is below: values = [ refcode , geom ] fields = [ "refcode" , "SHAPE@" ] with arcpy . da . InsertCursor ( elem_poly , fields ) as cursor : cursor . insertRow ( values ) Any ideas about what I should be doing differently?
... View more
02-18-2020
12:08 PM
|
0
|
1
|
113
|
POST
|
Okay, after much trial and error, it seems that a period was the culprit. A period used to designate version number of the tool in the alias and label were breaking the tool after the update to Pro 2.5.
... View more
02-17-2020
01:14 PM
|
1
|
1
|
56
|
POST
|
I'm trying to run the custom python toolbox from within Pro. I'm struggling to understand why I need to import the toolbox into the toolbox itself - and thus struggling with how I should try to write this in within the script. I did create a new toolbox in Pro and copy and pasted my custom toolbox into it and that worked. However, I'd like for the tool to be able to run from a static file location without having to copy/paste into a new toolbox because others will be using it within our organization and it's easier to push out edits like this.
... View more
02-17-2020
11:06 AM
|
0
|
3
|
56
|
POST
|
I have a custom Python Toolbox that has been running fine. Since the update to Pro, when I run the script, the program immediately crashes and if I can open the dialog box in time, it contains the following error: Error 000819: The tool is not available or is unassigned All of my third party packages are in the python environment that is active in Pro and I have background processing turned off int he script. I'm not sure what else to try. What would have changed in the update to make this suddenly start to happen?
... View more
02-17-2020
07:15 AM
|
0
|
5
|
256
|
Online Status |
Offline
|
Date Last Visited |
3 weeks ago
|