Latest Contributions by DanPatterson_Retired

hmmm except for the coordinate stuff z = np.zeros((10, 10), dtype = int) z[::2, 1::2] = 1 z[1::2, ::2] = 1 z array([[0, 1, 0, 1, 0, 1, 0, 1, 0, 1],        [1, 0, 1, 0, 1, 0, 1, 0, 1, 0],        [0, 1, 0, 1, 0, 1, 0, 1, 0, 1],        [1, 0, 1, 0, 1, 0, 1, 0, 1, 0],        [0, 1, 0, 1, 0, 1, 0, 1, 0, 1],        [1, 0, 1, 0, 1, 0, 1, 0, 1, 0],        [0, 1, 0, 1, 0, 1, 0, 1, 0, 1],        [1, 0, 1, 0, 1, 0, 1, 0, 1, 0],        [0, 1, 0, 1, 0, 1, 0, 1, 0, 1],        [1, 0, 1, 0, 1, 0, 1, 0, 1, 0]])‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Copy—Data Management toolbox | Documentation  does a lot more than Copy Features—Data Management toolbox | Documentation  I would start by comparing what you need to copy and whether your data has any of the conditions and properties that would require Copy to be used over Copy Features ... View more

where is this defined? OutPutLayer Also, code formatting will provide line numbers to your code /blogs/dan_patterson/2016/08/14/script-formatting  ... View more

Ahhh sorry ... don't do the 'consumed' side of things ... View more

I just tried both xlsx and xls for a table and both worked, finished and tables were intact. leaving the questions locally stored data and local destination folder? all tables or just this one? shutdown and restart Pro and do it again... same old? ... View more

I added to my post, YYYY-MM-DD is universal format great for sorting. If you need to parse by month, you can split on the string's - separator ... View more

s = "2020-01-15 23:15:30" # --- universal print(datetime.datetime(*time.strptime(s, "%Y-%m-%d %H:%M:%S")[:6])) 2020-01-15 23:15:30 t = "01-15-2020 23:15:30" # mon, day year print(datetime.datetime(*time.strptime(t, "%m-%d-%Y %H:%M:%S")[:6])) 2020-01-15 23:15:30‍‍‍‍‍‍‍‍‍‍ YYYY-MM-DD date format is it? ... View more

like 1/distance? Euclidean Distance—Help | Documentation  but it would have to be normalized to your cell size ... View more

Ahhh !  good one ... View more

here is a toolbox with an embedded script, give a look and see if it is secure enough for you ... View more

Additional security From  Comparing custom and Python toolboxes—Geoprocessing and Python | Documentation  it is pretty hard to pull out the code once it is embedded into a toolbox Custom toolboxes Python toolboxes Script tools in a custom toolbox can have their source code embedded into the toolbox and secured with a password. A Python toolbox .pyt file can be encrypted in place and secured with a password. ... View more

1e2 100.0 1e2.0 File "<ipython-input-2-3dea3e3816b2>", line 1 1e2.0 ^ SyntaxError: invalid syntax‍‍‍‍‍‍‍‍ spot the difference? ... View more

With a conventional toolbox (aka custom tool), all the parameter descriptions are stored within the *.tbx.  The xml portion doesn't contain the sometimes verbose parameter descriptions and help information ... View more

/blogs/dan_patterson/2016/08/14/script-formatting  your indentation was wrong and the code block (eg lines 3-6 or 17-20 ) need to be placed in the code section and the expression (line 10 or 24) in the expression line. Make the field (!some_field!) active, python parser, put in the code in the code block and the expression in its place and run. Also don't use == None, use ... is None ... you don't need your extra else since it will bypass to line 6 if value is not None # for string field def updateValue(value): if value is None: return 'no' return "yes" # calling expression updateValue(!some_field!) # ------------------------ # for numeric field def updateValue(value): if value is None: return -999 return value # calling expression updateValue(!some_field!)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more