|
POST
|
Unfortunately, ArcGIS pro doesn't currently provide support for cloud storage services like OneDrive, and this may be related to your error. Can you create a new Geodatabase which resides locally without cloud syncing, e.g. C:\workspace, and have both your input and output reside in that location? If you get the same error then it wasn't the cause, but would be helpful on eliminating one potential class of issues.
... View more
04-04-2023
08:06 AM
|
1
|
0
|
1836
|
|
POST
|
Have you tried removing the plugins as Wolf described? Based on our internal testing, this is the cause of the issue, we are working toward a solution but don't have something available in software yet.
... View more
04-03-2023
02:30 PM
|
0
|
7
|
2446
|
|
POST
|
In a more complex case where this is only happening in an environment like Citrix, it makes sense to try and work through this with support. I'm not aware of any reproducible cases we have when the machine is typically configured and the installation is fully clean other than the configuration being manually changed like Hannes mentioned. Cheers, Shaun
... View more
04-03-2023
02:26 PM
|
0
|
0
|
8841
|
|
POST
|
What kind of layer are you working with? I would expect to have it accessible via the CIM, does https://github.com/Esri/cim-spec/blob/1429b1bbba551c1614989a5e50552521d780bcd6/docs/v3/CIMVectorLayers.md#cimfeaturelayerdefinition look like the kind of layer you have?
... View more
03-30-2023
08:44 PM
|
1
|
0
|
996
|
|
POST
|
I'm not sure it will address the issue, but have you installed the TLS 1.2 patch for the affected machine? https://support.esri.com/en-us/knowledge-base/how-to-install-the-tls-1-2-patch-on-arcgis-desktop-000019327 That article specifies that 10.4 is the earliest release that can be supported, there are additional details in this SSL/TLS platform briefing.
... View more
03-30-2023
08:39 PM
|
1
|
1
|
3585
|
|
POST
|
We can reproduce this issue, and have logged an issue to address it in the next release.
... View more
03-30-2023
10:47 AM
|
0
|
1
|
855
|
|
POST
|
You'll want to use the arcgis-server-py3 package as mentioned in the documentation. For Linux, this package contains special components to talk between the native Linux environment and the rest of the ArcGIS Server installation, and is the only one of these components which is built as a Linux package. The other packages can be installed and used in custom environment that exist on the Wine side of the house, but typically you'd want to set up the native Linux environment as you like it, unless you're working in custom packages within an ArcPy workflow where you need the tools to share the same memory space as the Server.
... View more
03-28-2023
07:23 PM
|
0
|
0
|
916
|
|
POST
|
Can you show the earlier part of your code where you access the input feature class? Are you able to view the metadata successfully from within Pro? As a cross-check, you could export the metadata to another format and confirm the contents are present in that XML. It should be possible to use arcpy.metadata, but failing that the lxml package can be used to extract information from any XML file.
... View more
03-28-2023
07:13 PM
|
0
|
0
|
793
|
|
IDEA
|
03-28-2023
12:33 PM
|
0
|
0
|
1104
|
|
POST
|
OK, is there any chance that you have the deep learning installer laid down for Pro 3.0 still? If you follow the instructions under the "Upgrading from a Previous Version" section of https://github.com/Esri/deep-learning-frameworks/#installation you should be able to get a clean arcgispro-py3 to start with. Once you've confirmed that Pro 3.1 works without the deep learning installer, I would then try to add the 3.1 installer afterward. Unfortunately, this is a gap in our upgrade story as installing the deep learning packages doesn't force an uninstallation of the earlier deep learning packages. If you've already done this, I would uninstall both Pro and DL, then remove anything remaining as in step 3 of those instructions, and then add Pro 3.1 back. Sorry for the hassle!
... View more
03-28-2023
12:21 PM
|
0
|
0
|
1629
|
|
POST
|
I tried both in Pro and from standalone notebooks and it looked like it worked OK on my end: If you're trying this from Pro, could you see if it works from standalone notebooks? Could you also try using the default arcgispro-py3 environment to isolate if it is environment specific? Thanks! Shaun
... View more
03-27-2023
01:27 PM
|
0
|
0
|
1653
|
|
POST
|
Yes, in the automation case you'll want to work with arcpy.mp to determine what layers you're using and passing to the downstream functions. Here's an example which shows some basic information about scene layers in the project: project = arcpy.mp.ArcGISProject("CURRENT")
for project_map in project.listMaps():
map_type = project_map.mapType
print(f"Found {project_map.name} of type {map_type}")
if map_type == 'SCENE':
scene = project_map
print(f"Working with scene {scene.name}")
for layer in scene.listLayers():
fl_str = 'is' if layer.isFeatureLayer else 'is not'
print(f" found {layer.name}, {fl_str} a feature layer") Once you've used code like that to identify the layers you'd like to work with, you can then feed them into the GP tools you'd like to call. Cheers, Shaun
... View more
03-27-2023
10:00 AM
|
1
|
0
|
1691
|
|
POST
|
OK, if that script doesn't print In Python 3, all strings are unicode then it indicates there is some broader issue with the debugging configuration of VSCode. I would double check the Python interpreter configuration, and perhaps try creating a separate clean profile to see if you can reproduce the error there as well and isolate any possible configuration changes. Unfortunately, if the basic Python configuration doesn't respect the normal exceptions model, there's not much we can do on the ArcPy tier to handle the problem. Cheers, Shaun
... View more
03-27-2023
09:08 AM
|
0
|
0
|
4000
|
|
POST
|
If you've already run the package tool once, you can visit the history pane of the application, and select "Copy Python command" as described in the Geoprocessing history documentation. That will give you a code snippet that you should be able to paste into your existing Notebook. If you're using Pro 3.1, you can also open your notebook directly in Pro, and drag and drop the layer names into cells, and that will similarly work against the active map. If you need to work with the scenes from a standalone Notebook or in a context where Pro isn't directly involved, you'd want to start with arcpy.mp to first load the project, find your local scene, then work against the layers present in that scene, once you have the layer paths, you can use them as geoprocessing inputs as normal. Cheers, Shaun
... View more
03-27-2023
08:58 AM
|
1
|
1
|
1698
|
|
POST
|
Did you have a chance to log this? We can make sure it gets looked at once it is. Thanks! Shaun
... View more
03-27-2023
08:45 AM
|
0
|
2
|
2149
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 11-24-2025 09:10 PM | |
| 1 | 08-12-2022 10:14 PM | |
| 1 | 05-05-2025 10:56 AM | |
| 1 | 04-04-2025 09:03 PM | |
| 1 | 02-09-2023 10:10 PM |
| Online Status |
Offline
|
| Date Last Visited |
a month ago
|