Latest Contributions by DanPatterson_Retired

go old school... nothing like a spreadsheet. there are tons of examples on the web,  Nearest-Neighbor Analysis Lab: CSULB Geography  a little python ? https://machinelearningmastery.com/tutorial-to-implement-k-nearest-neighbors-in-python-from-scratch/  numpy, scipy, scikit learn? 1.6. Nearest Neighbors — scikit-learn 0.22.2 documentation  python - Find nearest neighbors of a numpy array in list of numpy arrays using euclidian distance - Stack Overflow  ... View more

errors would help ... View more

Jeff Legato‌can you mark the thread answered so it will bubble up to the top next time someone searches for this. ... View more

sadly, intermittent probably means not reproducible ... if you can do so, then it might be an issue for Tech Support ... View more

pretty sketchy examples for calculate field in modelbuilder Examples of using ModelBuilder utilities—Tools | Documentation  If using pro, there is the warning about significant changes to it ModelBuilder: migration to ArcGIS Pro—ArcGIS Pro | Documentation  I dont use modelbuilder... maybe Curtis Price‌ will be of some help ... View more

do you remember moving the mouse or clicking in the cell twice?  I saw it once entering text and I had done the first ... View more

apparently he didn't try... I highlighted those in my previous post ... View more

Then add these lines to your script and devolve the project path relative to the running script in the toolbox. import sys script = sys.argv[0] Then you can find the location of the script and if your project is located 'relative' to it, you should be able to construct the project name and location. script 'C:\\Git_Dan\\npgeom\\_load_sample_.py'‍‍‍ ... View more

ArcGIS Pro has it... you can even open a Jupyter Notebook in your project for quick testing and 'dir' away on objects to find out what they have. Pro has some nifty features... don't know if they are available in arcmap ... View more

issue_code = os.path.basename(mxdInicio) Did you try to print  issue_code?  If it doesn't print anything, it can't be sliced on the next line since it has no length and you can only slice things that have a __len__ property ... View more

I suspect garbage collection by either python or arc*, who knows for sure... sometimes adding a time.sleep solves a problem, sometimes not. I only get worried if I can't delete something after the script has finished by 'conventional' means, that is through python, Pro tools or the operating system. So check first, then delete if you have a repetitive workflow makes me worry less but does leave a bit of junk lying around.  Just add a secondary standalone 'delete' process to your toolbox (assuming you are creating them) for preparing for an analysis, or to clean up after. Apparently, gil, threading and python versions cover some of these issues, but I find it just makes my head hurt sometimes  PEP 0 -- Index of Python Enhancement Proposals (PEPs) | Python.org  ... View more

Just an general FYI for people reading this looking for solutions Delete—Data Management toolbox | Documentation  Feature classes and tables participating in a network analysis dataset or a topology cannot be deleted. Considerations when using the in_memory workspace—Appendices | Documentation  The in_memory workspace does not support geodatabase elements such as subtypes, domains, representations, topologies, geometric networks, network datasets, or feature datasets. Which now raises the question, can the gdb be deleted by conventional means after the script is complete? If so, one thing to consider in your workflow is to check for the existence of your temporary gdb at the beginning of a script and if it exists, try the delete there. ... View more