Latest Contributions by DarrenWiens2

I'd stick to editing Alex Tereshenko's code. The main thing to edit is the template line coordinates used for cutting the polygons: pnt_arr.add(arcpy.Point(x_min, y_max)) # top left pnt_arr.add(arcpy.Point(x_min, y_min)) # bottom left‍‍‍‍‍‍ Suppose you want a cut line 45 degrees from NW to SE. You'd change the coordinates to: x_diff = math.tan(math.radians(45)) * (y_max - y_min) pnt_arr.add(arcpy.Point(x_min - x_diff, y_max)) pnt_arr.add(arcpy.Point(x_min, y_min))‍‍‍‍‍‍‍‍‍ ... then keep trying cutting as you go right. Like picture below (maybe makes it more confusing...). Unfortunately, I don't believe there's any way to avoid coding on this one. You'd also have to do some extra coding to accommodate all possible line angles.  ... View more

Sure, there are lots of ways to do it. I was thinking just changing the output table name each time through, like below. Of course, you could substitute in your value for 'drainline' or whatever is most useful. Just so you realize the reason your table keeps getting overwritten is that if the name doesn't change, it overwrites the previous file. outStatsTable = "C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity" for i in range(10): # numbers 0-9     print outStatsTable + str(i) C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity0 C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity1 C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity2 C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity3 C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity4 C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity5 C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity6 C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity7 C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity8 C:/_LOCALdata/AB_ARCHYDRO/AB_ARCHYDRO_NOP.GDB/DrainageDensity9‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

You can either: a.) Calculate a unique ID to differentiate your lines in each feature class, Merge together, and calculate all the stats at once. b.) Change the output name of your stats table each time through the loop so it doesn't get overwritten, and Merge all those together afterwards. edit: I suppose you could also run Append each time through the loop to add to the stats table. General rule of thumb is to try not to run a tool each time through a loop, but it may be okay for just a few... ... View more

Thanks, Dan_Patterson‌. I was asking for a friend massaging data into a format suitable for their specific R package-dictated needs, which I gather relies on coordinates, not distances, from which it calculates distance via Pythagoras. In any case, they compared all the distances described above against geodesic, and both UTM and custom Polar azimuthal were extremely close to geodesic, so either of those seem adequate, as opposed to stock Polar, which seems to have more much more distortion near its edges than the distortion of almost completely crossing the next UTM zone. Thanks again. ... View more

my_string = '<img src="X:\UB_Routing\images\ServiceOrders\150 E MAIN ST.png"><br>150 E MAIN ST' print my_string.split('<br>')[1] 150 E MAIN ST ‍‍‍‍ ... View more

Have you considered using (or spatially enabling) your database do a point-in-polygon comparison, rather than pre-populating every possible point? Alternatively, calling a geometry service to do the comparison for you? for example: Geoprocessing - Point in polygon search | ArcGIS API for JavaScript 3.22  ... View more

You only get one Excel file with the results from the last iteration because the whole model runs on each iteration, overwriting the final Excel file each time. You could get multiple Excel files if you varied the file name like you did with the Spatial Join output. Or, you could get a single output in the end by using Collect Values and merging the results before exporting to Excel. It probably won't be the exact result you're looking for, but that's the trade-off using model builder rather than Python... ... View more

Totally appreciate you rolling your own here, but just to be annoying, I happened to be doing something like this, and came across generic filters in scipy you can use for focal stats. from scipy.ndimage.filters import generic_filter as gf kernel = np.ones((3,3)) my_min = gf(data, np.nanmin, footprint=kernel) my_max = gf(data, np.nanmax, footprint=kernel)‍‍‍‍‍‍‍‍‍‍‍‍ array([[1, 1, 0, 0, 0, 2, 1, 1, 0, 0],        [1, 1, 0, 0, 0, 2, 1, 1, 0, 0],        [2, 2, 2, 0, 0, 0, 1, 0, 0, 0],        [2, 2, 2, 0, 0, 0, 1, 0, 0, 0],        [3, 3, 4, 0, 0, 0, 1, 0, 0, 0],        [0, 0, 0, 0, 0, 1, 1, 2, 0, 0],        [0, 0, 0, 0, 0, 1, 1, 2, 0, 0],        [0, 0, 0, 0, 0, 3, 2, 2, 0, 0],        [2, 2, 2, 3, 3, 3, 2, 2, 0, 0],        [2, 2, 2, 3, 3, 3, 2, 2, 0, 0]]) array([[5, 9, 9, 9, 9, 9, 9, 7, 3, 3],        [7, 9, 9, 9, 9, 9, 9, 7, 7, 7],        [9, 9, 9, 9, 9, 9, 9, 8, 7, 7],        [9, 9, 9, 8, 9, 9, 9, 9, 9, 7],        [9, 9, 9, 9, 9, 9, 9, 9, 9, 7],        [9, 9, 9, 9, 9, 9, 9, 9, 9, 9],        [9, 9, 9, 9, 9, 9, 9, 9, 9, 9],        [5, 5, 5, 9, 9, 9, 9, 9, 9, 9],        [6, 6, 9, 9, 9, 8, 8, 8, 8, 7],        [6, 6, 9, 9, 9, 8, 8, 8, 7, 7]])‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

How to create a script tool: Create a script tool—ArcGIS Pro | ArcGIS Desktop  Couldn't find the ArcGIS Pro help page for this, but I assume it's the same in Pro: Integrating scripts within a model—Help | ArcGIS for Desktop  ... View more

Can you just replace the word "Highway " (include space) with nothing (i.e. "")? See the examples here for replace syntax: Specify text for labels—ArcGIS Pro | ArcGIS Desktop  ... View more

First change your data frame to WGS84, then: Calculating area, length, and other geometric properties—Help | ArcGIS Desktop  ... View more

Working backwards, you need to use SQL in your where clause, something like: StreetName not in ('BLVD', 'AVE', 'CIR')‍ So, you need to somehow format your dictionary keys into a list of quoted strings, like in the final line below: typeDict = {"AVE":1,"BLVD":2,"CIR":3} print typeDict print typeDict.keys() print ','.join(typeDict.keys()) print ','.join("'{}'".format(w) for w in typeDict.keys()) ... {'BLVD': 2, 'AVE': 1, 'CIR': 3} ['BLVD', 'AVE', 'CIR'] BLVD,AVE,CIR 'BLVD','AVE','CIR'‍‍‍‍‍‍‍‍‍‍‍ ... View more

Include the full error message. There shouldn't be a problem trying to cast an existing string to a string (e.g. str("my_string")). ... View more