Latest Contributions by ShaunWalbridge

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

Did you have a chance to log this? We can make sure it gets looked at once it is. Thanks! Shaun ... View more

Right, unfortunately that script still imports ArcPy, so it doesn't help determine whether the problem affects all Python code or is specifically within ArcPy. Can you see if this script runs successfully?   try: unicode except: print("In Python 3, all strings are unicode")     If that also fails, it lets us know that the issue is affecting all Python code. If it prints the output, then its something in the relationship with ArcPy specifically. Cheers, Shaun ... View more

Got it. Pro ships with a very rudimentary IDE called IDLE, but for most users they'll want something more sophisticated.  If you have choices, I would recommend looking at Visual Studio Code, you shouldn't need to do any work with custom environments to get it to work, you can point it at the Python environment that ships with Pro (arcgispro-py3). Spyder is a somewhat complicated case, because it also has all its dependencies managed through conda, but it can work. I would start by creating a cloned environment following these instructions: https://pro.arcgis.com/en/pro-app/latest/arcpy/get-started/clone-an-environment.htm Once you've created that custom environment, it should be possible to install spyder, but it isn't an entirely simple process. Some have had success adding it through pip, I would look at threads like this one for further feedback if Spyder is important to your workflow.   ... View more

Right, the function returns a Raster object because you passed in a raster in the previous step. In your original example of  hillshade = arcpy.sa.Hillshade(input_dem) the type of input_dem isn't explicit If you pass in a string or layer name, then hillshade will be a Result object, but if you are passing in a Raster object, you'll get a Raster result (this is how I'd recommend working with rasters from ArcPy). The scratch workspace can be different things, it isn't guaranteed to be a temporary location but is configuration dependent. You could set it to a temporary location yourself, you can also use the ARCTMPDIR environment variable to affect this behavior. If the location is e.g. a temporary folder inside of TEMP, it still won't be removed automatically, but would be cleaned up by some Windows processes or tools. ... View more

Probably for most cases where you want to work with more Python rasters, you'll want to start with arcpy.Raster, I think its documentation covers the general problem and some of your questions well, and while Zandbergen's book is solid, the documentation is generally authoritative. In the example you provided, the result will be an arcpy.Result object, but if you unwrap this with hs_raster = hillshade.getOutput(0), you'll get the resulting raster path. The location will be specified by the value of arcpy.env.scratchWorkspace. Using the raster class instead gives you a little more insight into the rasters and will let you work with them in a nicer way. ... View more

Where will you be using the layer? If you're working with the JavaScript API, you should be able to add it directly with https://developers.arcgis.com/javascript/latest/sample-code/layers-geojson/. If you'd like to use it more generally across products (e.g. add it to Pro), you might be better served by getting a free account from https://developers.arcgis.com/ and adding it as a normal feature service. You could do this with e.g. the Python API, and then you can just plug into the other systems which well understand feature services.  ... View more

Did you do any specific configuration to add more verbose warnings or other configuration changes? I believe that VSCode + ArcPy is a common combination in use, and the `unicode` call, while failing, is expected to because it is wrapped in a try/except block which will raise on Python 3. These should ultimately be removed from the ArcPy code in the future, but I wouldn't expect a Python import to fail on them. You could check if only your code is set to debug, but also try making a dummy script with the same try / except lines as you're seeing raise, and see if that also fails. Cheers, Shaun ... View more

Can you describe what you're trying to accomplish? Pro ships with the Python API already, so unless you have reasons to need the very latest builds, you can use it from the default environment that ships with Pro. If you do need an even newer version, you can get it but don't think that post well covers the problem. By default, each release of Pro supports a specific major.minor version of the Python API, as parts of the Python distribution itself depend on the Python API and are tested at that major.minor release. ... View more

Got it. That would be great, once we have a clear set of interactions causing this we can get a reproducible case together and start debugging it. I don't think we have had anything like this happen before and wouldn't normally expect any interaction between the two "worlds" of .NET and Python. ... View more

Does your Python script work from the command line without the Pro SDK installed? It'd be good to see if this only happens specifically in an interaction with that component or is more broadly occurring. Thanks! ... View more