Latest Contributions by DarrenWiens2

Blake T, sorry to harp on this, but I'm not seeing the reference to the update cursor returning rows as a tuple. There are a few places that may take a tuple as input (e.g. fields), and outputs some properties as tuples (e.g. SHAPE@XY), but not rows. Perhaps you're thinking of the tuple row returned by next(), but this is hardly ever used anymore. ... View more

Just a small note that update cursors return rows in a list not tuple  (search cursors return rows in a tuple), so you can skip that step. ... View more

Please post the error. ... View more

Agreed, mostly. What's this about spaces? AFAIK, they are irrelevant. ... View more

There are lots of arcpy examples using Con here​ - scroll to the bottom. ... View more

Is your colleague editing in a data frame with a different coordinate system than the data? See here for how this can cause alignment issues. ... View more

What exactly are you trying to achieve? Eliminate the overlaps? ... View more

This discussion is so unnecessarily long. Hardcoded values are directly written in the code, rather than obtained from user input or existing data. ... View more

Or (lazy answer), replace the value to 91 - then you're guaranteed to include the maximum value of 90 degrees regardless of the actual maximum data value. ... View more

You could ​use the Con tool (see this page for relevant examples): Con(("rclslope">=45)&("rclmosaic">=2000)&("rclfocal">15),1) This returns a raster with pixel value = 1 which meets the criteria. If you're looking for a way to spatially query pixel values in ArcGIS, that doesn't exist to my knowledge. ... View more

In your first script, the line should be: if field.name == 'total_length' and field.type == 'String': There are other logic issues in the first script, too. For example, it is only looking for one field, but does the operation once per field per row. ... View more

This is great, and potentially has uses outside city planning (wildlife habitat suitability comes to mind, although you'd rarely have enough detections to make it work). The only thing throwing me off is the use of the term "suitability" for the input, when for me the output is "suitability". The input is more like "known occurrences" or similar. Of course, I may be interpreting this backwards. Thanks for sharing. ... View more

I won't pretend to understand the inner workings of it (I usually use 'SHAPE@', as a convenient but wasteful practice), but I think that because cursor.updateRow updates the table value rather than changing the tuple itself, it works, like below. >>> with arcpy.da.UpdateCursor("fc",'SHAPE@XY') as cursor: ...    for row in cursor: ...        cursor.updateRow([[row[0][0]+100, row[0][1]+1000]]) The value of row never changes within the loop. Conversely, the following does not work, for the reason you've identified: >>> with arcpy.da.UpdateCursor("fc",'SHAPE@XY') as cursor: ...     for row in cursor: ...         row[0][0] += 100 ...         row[0][1] += 1000 ...         cursor.updateRow([[row]]) ...         Runtime error Traceback (most recent call last):   File "<string>", line 3, in <module> TypeError: 'tuple' object does not support item assignment ... View more

Thanks. I could work out the simpler geometries, just curious if there was some magical algorithm for figuring out more complicated shapes. ... View more