Latest Contributions by DavidPike

The latitude 'distortions' are really just a product of overlaying a geographic coordinate system grid onto a projected coordinate system.  Any attempt to 'straighten out' the latitude bands will distort the data accordingly. I'd be tempted to educate the customer, and perhaps use an MGRS grid system instead. ... View more

omg I just need to reset the cursor at the end of the for loop within the cursor! and yes I wasn't using defaultdict.. You've added a lot to my knowledge here Joshua, much appreciated. ... View more

I was initially having the for loop within the cursor, but moved it out as it wasn't working as expected. Now you've explained why, this is very helpful and will save a lot of time on big processes. Big fan of that dictionary creation **steals code**.  Could you finally show how to reset the cursor if looping through a list like I was inefficiently doing? Big Thanks. edit - I've tried to replicate the dictionary += value, but it has a key error (ie if the key doesn't exist the value is not == '') ... View more

this will give a dictionary of your values import arcpy feature_class = r'filepath' fields =['Street Name', 'PageName'] #the gap in Street Name gives me anxiety street_name_list = [] with arcpy.da.SearchCursor(feature_class, fields) as cursor: for row in cursor: if row[0] not in street_name_list: street_name_list.append(row[0]) street_page_name_dict = {} for street_name in street_name_list: page_name_list = [] with arcpy.da.SearchCursor(feature_class, fields) as cursor: for row in cursor: if row[0] == street_name and row[1] not in page_name_list: page_name_list.append(row[1]) street_page_name_dict[street_name] = page_name_list print(street_page_name_dict) ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

I'm thinking you should have compressed the database before the upgrade, I'm guessing the delta tables are stored differently? Far from an expert answer. I would definitely seek Esri guidance. ... View more

I believe !Version! in field calculator would represent each entry, calculating the max of that would only return itself. by "that if the field is 0, it will find the max for the field and add 1 to it. " i'm assuming you mean: that if an entry in the field is 0, it will find the max for the field and add 1 to it. ? find the max for the field first then run the calculate field ... View more

Hi Benas, I've tried multiple syntax but no avail. I've been able to apply definition queries to feature classes using your code, but not a MD.  wrt the raster catalog footprints, it seems this is correct for a mosaic dataset (I think the MD is a repackaged raster catalog rolled in glitter) Look forward to someone solving this. ... View more

I'll try it on a dummy mosaic and get the syntax right for you. The data type on your screenshot is FGdb Raster Catalog not Mosaic Dataset? ... View more

field = "Date" values = "1950" query = '"' + field + " = " + values + '"'‍‍‍ Is it Sacle_1250 or Scale_1250 maybe? ... View more

As Steve says, Reclassify would be my go-to option. If you do need/want to cast it into memory: sloperasterpath = r"c:\myraster.tif" sloperasterobject = arcpy.Raster(rasterpath) then do a Con(….) using map algebra syntax. A useful part of the Reclassify tool is that if you change the symbology in the TOC to your desired classes, dragging that layer into the tool keeps those classified ranges. ... View more

The join remains static from the time the join was created. You would have to remove and add the join each time, or use a relate, which will be dynamic. ... View more

I've not studies the code thoroughly but i'm guessing it's updating the values as expected? I may be misinterpreting, but you're aware that the visible attribute table has nothing to do with the actual positions of the points? You would need to update the geometry object ("SHAPE@" token in a cursor) or use the update fields to create a new feature through a tool like add xy data. ... View more