Latest Contributions by VinceE

Experienced this in ArcGIS Pro 3.0.2. Couldn't replicate in 2.9. I was recently setting some values to NULL using Field Calculator. Expression type is Python 3, value I am inputting is None. To be clear, I'm typing in None without quotes or anything extra. Just the Python data type None. This used to set all values in the field to Esri's NULL, represented as <Null>. Standard stuff. However now this operation yields the following: [WARNING 003571: Certain rows set to NULL due to error while evaluating python expression: Cannot be evaluated to value.] To be clear, the operation still works--highlighted rows in the specified field (tested with SHORT and TEXT fields) still evaluate to NULL. I'm just curious what the function of this warning is. Is there now a preferred way of setting values to NULL? If this Python expression results in an evaluation "error," as stated in the warning  message, why does it still work? Is there something that has changed here that I should be aware of? Am I missing something? Thanks in advance if anyone has any insight into this bizarre change. ... View more

I am attempting to use Python's .sort() with a lambda function to spatially sort an existing list of Polygon objects, to then write to a feature class with an InsertCursor. Sorting will be based on user-supplied specifications (north to south first, followed by east to west as a secondary sort, for example). This snippet is part of a larger script that has been pared down so it's easier to look at (the list of polygons and the output feature class are created at an earlier stage, not shown here).   # User supplied sort priorities. sort_1 = 'EW' sort_2 = 'SN' # Example: for N to S sorting, sort polygon using centroid.Y attribute, descending. sort_dict = {"NS": (-1, 'Y'), "SN": ( 1, 'Y'), "WE": ( 1, 'X'), "EW": (-1, 'X'),} # Getting the direction and axes (primary and secondary) to sort by. dir1, axis1 = sort_dict[sort_1] dir2, axis2 = sort_dict[sort_2] # An existing list of polygon objects, sorted using specifications above. # "dir" handles ASC/DSC, getattr() gets the appropriate x or y value from the # centroid. all_sheet_polys.sort(key=lambda poly: (dir1 * getattr(poly.centroid, axis1), dir2 * getattr(poly.centroid, axis2))) # Write sorted polygons to an existing blank feature class. with ap.da.InsertCursor(out_fc, ['SHAPE@', 'PageNumber']) as icurs: sheet_count = 1 for sheet in all_sheet_polys: icurs.insertRow([sheet, sheet_count]) sheet_count += 1    The problem is that the two-part lambda sort does not always work. If the FIRST sorting is along the x-axis (EW/WE), it will. The first image is east to west, then south to north. The second is west to east, then north to south. Both are created as expected. East to West, then South to North. West to East, then North to South. The problem occurs when x-axis sorting is done as a SECONDARY priority. Here is an example using inputs "SN" and "WE" as inputs, for south to north followed by west to east. The primary sort, south to north, works fine. However, the west to east does not, and the ordering appears arbitrary. South to North, failed sorting West to East.  Any ideas would be appreciated. Seems like something silly I am overlooking, but it has got me stumped. ... View more