Latest Contributions by Luke_Pinner

Yes. But you need to understand scope.  At it's simplest, functions (and variables) are objects and objects are only "visible" at (or below) the scope in which they are created. So by creating a function inside the local scope of a method (e.g. __init__ or execute), you can only use that function inside the method you defined it in. E.g. class Tool(object): def __init__(self): def func_in_init(): return "init" def execute(self): def func_in_exec(): return "exec" print(func_in_exec()) # this will work print(func_in_init()) # this will raise NameError If you want to use a function anywhere, define it globally, if you want to use it anywhere in your Tool class and not outside the class, make it a method.   ... View more

@JohnBranum wrote: In all my tests, what appears to happen is that the clipping process reevaluates the clipped raster, reassigning values from min to max, which will change those values if, for example, the removed portions were higher and/or lower values than what remains. I think what you are referring to there is what happens to the symbology which is just a visual representation. It doesn't change the underlying values though. ... View more

You can manually check by subtracting one from the other.  You'll get all zero values where they overlap. ... View more

Also, as your raster cells appear rotated in the screenshots, it looks like you are trying to run the clip in a different projection than the raster is in which is probably why it's taking so long.  Change your map /tool environments spatial reference system to match that of the original raster. ... View more

Can't reproduce. Extract by Mask maintains cell values, For example - using Identify to show cell values at the same point in both original large raster and the extracted raster: Luke_Pinner_1-1690344145279.png Of course your extent, n. rows/columns and min/max cell statistics will change, because you clipped/extracted out a smaller area.   But the actual cell values remain the same.  The rasters/cells may even look different in the map but the values themselves have not changed. This is simply because the symbology will have changed (as the statistics are different).  You can make them look the same by changing the symbology. Luke_Pinner_2-1690344389872.png   ... View more

You could create your own shortcut that calls C:\Program Files\ArcGIS\Pro\bin\Python\Scripts\proenv.bat and set the shortcut start in directory to whatever you want. ... View more

Or adding <install>bin\Python\Scripts (e.g. C:\Program Files\ArcGIS\Pro\bin\Python\Scripts) to the PATH user environment variable. using <install>bin\Python\Scripts\conda config --remove channels conda-forge ... View more

NVIDIA discrete graphics card?  Again not a proper solution, just a possible workaround  - try temporarily switching Pro (in Windows graphics settings) to use the integrated graphics (if you're using an Intel or AMD CPU with iGPU).   ... View more

Suggest you contact Esri Support (or your local distributor). https://www.esri.com/en-us/my-esri-login ... View more

It's probably related to the graphics driver. Very annoying and I don't have an answer, just a workaround - sharing the screen that Pro is on instead of the Pro window itself works for me in  Teams. ... View more

You could use PDAL. Installation instructions in the Quickstart pdal translate input.laz output.las   ... View more

That won't work.  Python Toolboxes aren't scripts. They are libraries and as such don't really get run, they get imported, the Tool class is instantiated and the tools execute method is called. You are missing all the required Tool methods (execute, getParameterInfo, isLicensed etc...) I think what you need is a simple script, either standalone or attached to a regular toolbox. ... View more