Latest Contributions by ShaunWalbridge

The issue has been addressed, and will be fixed in the upcoming Pro release. ... View more

OK, yes the goal with arcpy-base is to strip out all non-critical packages, and move those which are normally included but not critical into arcpy. You can evaluate the versions we include by looking at the arcpy file information for the version you're installing, e.g. we ship scipy >=1.5.2 for Pro 3.1. I think including only the minimal set of things is the right way to break this up since different users will need different sets of things beyond the arcpy-base set, and if they need 1:1 mapping with Pro, they can use the full ArcPy package. ... View more

You'll need to first activate conda, either by using the Python Command Prompt session, or by changing directory to the <install>bin\Python\Scripts path. Cheers, Shaun ... View more

Because the arcpy package label already mapped to the full Python distribution we provide by default, we introduced the new arcpy-base package which includes only the minimal dependencies for Geoprocessing scripts. Separately, arcpy includes the full distribution (including the Python API), and pro_notebook_integration includes the specific packages needed for Notebooks inside of Pro. ... View more

Do notebooks work from outside the Pro application? There's a shortcut in the program group for Pro for  Jupyter Notebook that should allow you to start it outside of the application. That would help clarify if the issue is across all notebook environments, or specifically an issue with Pro. ... View more

The hotfix package isn't necessary at Pro 3.1, because the issue it would address is already installed into the software. Are you having issues loading notebooks in Pro 3.1? Do they work outside of the application? ... View more

@DuncanHornby The provided command was an example of how to create a new environment from scratch that included shapely version 2, but you can also use conda to install packages into existing environments (say that you created from the backstage). To do so, you could start a Python Command Prompt session, which by default will be initialized in the environment you use with Pro. If you need to work with a different environment (e.g. arcgispro-py3_Cloned in your example), you'd want to first run: activate arcgispro-py3_Cloned After the correct environment is set, you can run: conda install shapely=2 To install the latest 2.x version of shapely available. Of course, pip will also work, but conda is recommended because it manages the binary dependencies that overlap with Pro like GEOS in a direct way. Conda works via activation so that the environment has its paths set up correctly, and is not dependent on the current working directory. You can tell that your calls are correct by e.g. running where python or where pip to see that the execution would be happening against the versions in that environment, or by confirming the information you see from running conda info. ... View more

Any chance you're using the version of Summarize Within designed for online analysis? I would only expect that error when using the standard analysis version of the tool for working with online features. If it is happening with local data, please provide a more complete example of the inputs and error. Cheers, Shaun ... View more

@DuncanHornby This is a bug in the backstage logic for listing package versions that are installable. You can install it from the command line, e.g. running conda create -n pro-shapely-2 arcpy=3.1 shapely=2 will create a valid environment with both ArcPy and Shapely 2.0.1. Overall it is probably better to install it via conda so that the GEOS installation is managed, but if pip works and doesn't break anything on your end, go for it. I've logged the UI bug and we will look at it. ... View more

It may be that your coworkers are on different versions of the software, or there are specific circumstances where this bug is introduced that aren't universal, I haven't dug into it sufficiently to say. In terms of the path, could you try something like: dir_path = os.path.join(r'E:\ArcGISData', 'ForestEcosystemValuesData') If it persists as an issue despite 'hacks' like these, it may be worth seeing if using a different project location has any effect. ... View more

This sounds like a known logged bug, BUG-000147516, which unfortunately doesn't help you immediately. It may be easiest to fix the replaced strings on the server, or as a workaround, construct your path variables all as  os.path.join elements, and remove the one hiding inside of the comment. Best wishes, Shaun ... View more

Dan's suggestion is a good one. You could also log an idea for getting the display units from the map, which differ from the map units. ... View more