Latest Contributions by DanPatterson

Notice how \n is inserted where appropriate and the indentation is maintained.  A 'print' statement will confirm everything codeblock13 = """def unassigned_fxn(inValue1, inValue2, inValue3, inValue4, inValue5, inValue6): result1 = inValue1 result2 = inValue2 result3 = inValue3 result4 = inValue4 result5 = inValue5 result6 = inValue6 if result1 == 0 and result2 == 0 and result3 == 0 and result4 == 0: return result5 * result6 else: return 0""" codeblock13 'def unassigned_fxn(inValue1, inValue2, inValue3, inValue4, inValue5, inValue6):\n result1 = inValue1\n result2 = inValue2\n result3 = inValue3\n result4 = inValue4\n result5 = inValue5\n result6 = inValue6\n if result1 == 0 and result2 == 0 and result3 == 0 and result4 == 0:\n return result5 * result6\n else:\n return 0' print(codeblock13) def unassigned_fxn(inValue1, inValue2, inValue3, inValue4, inValue5, inValue6): result1 = inValue1 result2 = inValue2 result3 = inValue3 result4 = inValue4 result5 = inValue5 result6 = inValue6 if result1 == 0 and result2 == 0 and result3 == 0 and result4 == 0: return result5 * result6 else: return 0‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

df is going to be a text reference not an object that you can slice on the second line. Throw a print statement in there and see what I mean ... View more

You might want to try a "repair" of the installation.   Go to windows Add/Remove Programs, select Remove, then you will be given the option to Repair the install Works sometimes. As for the 64 bit stuff, Pro is the way to go, but if you want, or are stuck with ArcMap.... Background Geoprocessing (64-bit)—ArcMap | Documentation  ... View more

As it says, contact Technical Support is your best option ... View more

no problem ... View more

It is a warning... one of your two fields has a null value in it, so when it tries to perform the numerator operation, it is either getting a number - None or None - a number So you will have to fix your data if you aren't expecting nulls in those fields, or you will have to fix the expression to deal with nulls. In any event, a warning probably didn't make all the calculations fail did it? ... View more

Are you using arcmap or pro?  your print statements aren't consistent with python 3. Justd as an FYI..., esri grids can't begin with a number  "51N_"+data so that would have been an issue without the *.tif file extension. ... View more

Glad it worked out ... View more

could you throw code formatting in /blogs/dan_patterson/2016/08/14/script-formatting  And I think you will need to put some print statements in since *.dbf files can only go into a folder and it isn't clear where you are trying to send it given your code above ... View more

"15" + !YourField![2:] or if you just mean the 2nd value, leaving the first along !YourField![:1] + "5" + !YourField![2:] ... View more

Maybe it wasn't reported as a bug, so nothing got addressed.  There is always next year ... View more

The documentation is current for ArcGIS Pro 2.6.  It rolled over to the new version yesterday. Perhaps you could share your expression. Also it is often useful to use the named parameters, rather than relying on parameter position ... View more

Release notes for ArcGIS Pro 2.6—ArcGIS Pro | Documentation  You will have to look through the release notes yourself ... View more