Latest Contributions by DarrenWiens2

I think you're probably looking for Zonal Statistics as Table, using a new raster covering the whole area as a single zone. However, as Dan says, a single number might not describe your situation very well. For example, suppose you have a situation where you have a single dune covering the left 50% of your raster, and it moves to cover the right 50% of your raster. The left will all be -100% and the right will be all +100%, so the mean from Zonal Statistics as Table will be 0%, although there has been quite a bit of change. ... View more

My dreadfully boring two cents: if the data must be maintained by non-GIS people, leave it in a common format like your spreadsheet, CSV, or shapefile with instructions to update it with coordinates and attribute info, then give to GIS person to update the app. Points are easy enough to maintain in a list - if you were dealing with polygons or lines, that's a different story. Also, especially if the app is to persist more than a couple years, I'll suggest not relying on, dare I say, peripheral apps like Collector or Survey123, because who knows if they'll exist (gasp). ... View more

More info: Use the DataFrame Extent Polygon to Clip your feature class, inside the loop. ... View more

Without really paying attention to what your code is doing, just a couple thoughts: - Running any geoprocessing tool (e.g. spatial join) inside a cursor is a red flag. Tools are for datasets, not individual features, so there's probably a better way if you need to work with individual features. - Nesting any combination of search and update cursors is a red flag. Read the search cursor into a dictionary, like how you did with valueDict. - To address your main question, update (and search) cursors only operate on selected features if there is a selection, so just add a where clause to the update cursor to work on selected features meeting some criteria. ... View more

I can only suggest to take a close look at the raster properties to see what's different about those five, things like projection, pixel depth, number of bands, etc. ... View more

Did "Build Raster Attribute Table" run successfully, individually? ... View more

Your original question says you're trying to insert polyline geometries into a polygon feature class. Is that correct? ... View more

1.) Calculate total area of districts into a new field 2.) Intersect districts with mountain classes 3.) Dissolve intersected polygons by district ID, district area, and mountain class 4.) Calculate area for dissolved polygons. Now each polygon has its own area and the district area. 5.) Divide polygon area by district area to get proportions 6.) Dissolve again by district ID, mountain class, and proportion, also calculating MAX proportion 7.) Delete any features where proportion <> max proportion 8.) Join back to districts by district ID ... View more

for i in range(10):     print (i % 3) + 1 1 2 3 1 2 3 1 2 3 1‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Make sure you use "SHAPE@", a special token for the actual geometry. ... View more

Have you got a start on anything? ... View more

Ah, okay. Here are my thoughts on speed, but someone correct me if I'm wrong. You're in a situation that would naturally result in nested cursors (for each street, look through each address point). Nested cursors are bad due to the exponential operations, but I think they might actually be faster in some cases than selections because selections are just so dreadfully slow individually. Either way, check here for Richard Fairhurst's cursor/dictionary pattern to speed things up: /blogs/richard_fairhurst/2014/11/08/turbo-charging-data-manipulation-with-python-cursors-and-dictionaries So, I think you should load the points into a dictionary and read through streets with UpdateCursor. For each street, fetch the matching points and test whether they meet the street min/max criteria. If so, update the street row. Not sure if 400,000 records is reasonable for a dictionary, but I'd think so. ... View more

I just want to see if the where statement evaluates to 'true', and if so, update a field in the row of the cursor. Can't you just use an UpdateCursor, rather than SearchCursor? UpdateCursor—Help | ArcGIS for Desktop  ... View more