Latest Contributions by ShaunWalbridge

@CordulaGöke Thanks for your report. We upgraded to a modern supported version of libxml2, and it looks like the builds of libspatialite on both defaults and conda-forge do not support such a new libxml2. If you're OK working in a standalone environment, you can create one with `conda create -n libspatialite libspatialite` and it should work, but would be decoupled from the rest of Pro. Hopefully the other channels catch up on dependencies soon and have a release compatible with Pro, we potentially could package it but it is non-trivial given libspatialite's large number of dependencies. ... View more

@Marco_Foi Thanks for your report, I can confirm the issue. For now, you can work around this limitation by using the `sqlite3.exe` included within Pro's Python environment, the command will work there and `PRAGMA compile_options` will correctly show the rtree extension as available (and it is present within the sqlite3.dll). If you needed this from Python, you should be able to do a subprocess call to sqlite3, though of course that is inelegant. For the Python build, it looks like the build environment is picking up a slightly different version of sqlite3 that does not include these extensions. I'll add an issue for us to look at and address in future builds of Python we redistribute. In a separate standalone environment, you could also get the Python client their working with `conda create -n sqlite -c defaults python=3.11` which will have rtree drivers loaded, but wouldn't recommend mixing that with ArcPy and our custom Python environment. ... View more

What does `arc.check_product()` report when it runs? Are you having crashes with any data source? Does this work? d <- arc.select(arc.open(system.file("extdata", "ca_ozone_pts.shp", package="arcgisbinding"))) Edit: I tried on 3.2 with R 4.4 and was able at times to get crashes, I will look. For now I would try an earlier R version like 4.2 or 4.3. ... View more

I haven't closely checked, but I think this is due to changes in the caching system of Python 2 vs 3. Deleting the .pyc was a handy trick, but perhaps not a directly supported "feature" from the Python developers perspective, sometimes cached module loading introduces other downstream issues, and typically Python executions expect to only import something once.  There are tools like IPython's auto reload module which allows hot reloading (https://ipython.readthedocs.io/en/stable/config/extensions/autoreload.html) but using importlib is the best general practice currently because it is explicit. We've discussed having some kind of 'debug' mode that would try to reimport modules, but nothing in the software today for that. Cheers, Shaun  ... View more

I would try creating the environment from your normal user account rather than doing it as an administrator, if you do that you should see the environment in %LOCALAPPDATA%\ESRI\conda\envs by default. One thing you can try is just running the Pro notebook before installing anything into the initial clone to verify it works before making changes. There was an issue with clones that was fixed in 2.9 and 3.0 (see the Notebook FAQ) but that shouldn't apply for 3.1. ... View more

As @DanPatterson mentions, currently upgrading Pro is the right path. Libraries which use the Python C API are versioned against the release, and aren't cross-compatible with other releases of Python. That said, Python 3.7 or 3.9 are the releases available in all supported versions of Pro, so you're probably due for an update in any case. Python 3.7 was still receiving security fixes until last year, but Python 3.6 has been unsupported for a couple years now. ... View more

You should be able to access the control point information with the ArcPy CIM access, see the symbols CIM definitions for the item types. There are a few different elements in the CIM to support this behavior, I'd recommend you try experimenting with some data, then extract the CIM from the .aprx you're using to examine its structure. The ArcPy class works well, but a working mental model of the CIM layout is important to make effective use of it. Cheers, Shaun ... View more

I just did some light testing with Pro 3.2, and can confirm that saving the project will save the notebook without needing to separately save the notebook from the Notebook ribbon. Could you search your machine for .ipynb files and see if anything else turns up? From your description of it being missing in the project, perhaps the file was renamed or otherwise changed in a way that Pro didn't track, and the updated file is present elsewhere. The other thing that comes to mind is if for some reason the file is stored in a read-only location, the save button won't do anything, but that case is usually pretty obvious in the UI which has this at the top: I'm hoping the notebook is in a different location and you haven't lost work. If there is a persistent issue with notebook saving, obviously that's a bug and we can look at it. Cheers, Shaun ... View more

Can you try to run the propy.bat included with the Server installation and see if the issue reproduces there? The documentation at https://enterprise.arcgis.com/en/server/latest/develop/windows/scripting-service-publishing-with-arcpy.htm provides some additional information. You can also try running the Python 3 Command Prompt from the start group shortcut and start your Python session from that to confirm it works when activated through conda. Cheers, Shaun ... View more

I understand your position. Generally, users providing enough context that we can reproduce the issue in house and logging issues allow all users to see when an issue is addressed makes the overall experience better, since there is a formal feedback loop. In some cases, bugs can only be addressed with the specific data provided by a user, and when choosing between issues, we will tend to choose ones that are reproducible and interpretable. In this case, we could address the issue in house without any further work and have fixed it for Pro 3.2. Cheers, Shaun ... View more

This issue is addressed for toolboxes in Pro 3.2, if you're on 3.2 and seeing this behavior, please provide details on it. ... View more

@FakeName I took a look at this, and I think I've identified what the issue is. If you have any existing resources open that reference the environment directory, it will currently cause a failure. So for example, if you have a command line prompt at the working directory of the environment, that will lock the location and Windows won't be able to delete the folder. There is a second bug which is that the restore doesn't happen in this case either. I have local fixes for these issues and will look to get them into software, for now, here's a workaround: 1. Your environment doesn't get deleted, it is archived first. If you navigate to %LOCALAPPDATA%\Esri\conda\envs, you should see a file called <env name>.tar.bz2. This is a conda-pack archive of your environment, you can extract it with current builds of Windows 11, 7-zip or by using conda pack to restore your old environment from Pro 3.1. 2. Once you have that in hand, from the Package Manager interface of Pro you can add the environment back to the environment list. If you do this, then ensure that no other resources are referencing that environment, the upgrade should work as expected. Sorry for the trouble and will look to fix this soon. Cheers, Shaun ... View more

Based on your description, you should be able to use Symmetrical Difference to remove the updated lines, then merge together this new feature class with the output from the unspilt operation. ... View more

Since this was logged a decade ago, significant work has gone into the help. For many tools, detailed examples are now available, and if you find the examples provided on a particular tool lacking, please provide feedback from within the help system by filling out this form: That feedback goes to the relevant authors and is regularly reviewed. In addition to the improvements in the help itself, since this issue was logged there have been a number of improvements to how code can be generated from tools. For example, if you run a tool and visit the history pane, you can now export the results to many places, including Copy Python Command which will generate a fully formatted snippet of code for that tool and its expanded parameters as they map from the UI into Python. You can also drag and drop those entries into the Python Window or Notebooks to further make moving between the UI experience and Python as simple as possible. If you have specific topics you'd like to see improved, please use the feedback system. If you still believe there are broader systematic issues, please log a new idea which refines this one to specifics we can assess. Thank you for your contribution to the ArcGIS Ideas site! Cheers, Shaun     ... View more