Latest Contributions by RichardFairhurst

Using a Parcel centroid to determine the largest area is unreliable.  For example, in a Parcel that had Zoning in shapes that resembled an Archery Target of concentric rings, the zone with the largest area is not in the bulls eye in the center, but in the outer most ring. I normally do this by using the Summary Statistics tool in the Analysis Tools->Statistics toolset. 1. I would use the Summary Statistics tool to Sum the Area field in the Statistics Fields section and add both the Parcel and Zoning fields in the Case Fields section.  This gives you the true amount of total area for each zone when the same zone occurs on separate portions of the same parcel. 2.  Then I run the Summary Statistics tool again on the output of the previous summary, and this time I get the MAX of the SUM_Shape_Area field in the Statistics Fields section and only add the Parcel field to the Case Fields section. 3.  Then you can do a join of the first summary table as the target and the second summary table as the join table on the PARCEL field.  In Model Builder you would first have to use the Make Table View tool in the Data Management Tools->Layers and Table Views toolset on the first summary table, then use the Add Join tool in the Data Management Tools->Joins toolset. 4.  Select the records where the SUM_Shape_Area field is equal to or greater than the MAX_SUM_Shape_Area field using the Select Layer By Attribute tool in the Data Management Tools->Layers and Table Views toolset. 5. Use the Remove Join tool Data Management Tools->Joins toolset to break the Join you created in step 3. 6. Export those records to a new table so it only contains the one record with Zoning that had the greatest area for each Parcel.  You could use the Copy Rows tool in the Data Management Tools->Tables toolset. 7.  Join the original parcel and zoning layer (or just your parcel layer if it had a Zoning field you could calculate) as the target and the exported table as the join table on the Parcel field.  In Model Builder you would first have to use the Make Feature Layer tool in the Data Management Tools->Layers and Table Views toolset on the feature class with the intersected parcels and zoning and then use the Add Join tool in the Data Management Tools->Joins toolset. 8.  Use the Calculate Field tool in the Data Management Tools->Fields toolset to calculate the Zoning in your layer from the exported table. 9.  Use the Remove Join tool Data Management Tools->Joins toolset to break the Join you created in step 7. 10.  If you used the layer with parcels and zoning intersected as the target in step 7, you should use the Dissolve tool in the Data Management Tools->Generalization toolset on that layer with the Parcel and Zoning fields checked in the Dissolve Fields section to create a single shape for each Parcel that will have the Zoning that covered the largest area in that parcel. ... View more

You have to customize the label expression of the label class in the Recreation Site Points layer.  If the layer only generates one label you could hard-code the text as "DEER CREEK CAMPGROUND".  If you want the expression to replace "CG CAMPGROUND" with "CAMPGROUND" for many different campgrounds and your field name was NAME, in VB you could make the expression: REPLACE([NAME], "CG CAMPGROUND", "CAMPGROUND") ... View more

Your loops are backwards.  The SearchCursor is always on the outer loop and you must do all lookups only on the dictionary in the inner loop.  This way you just go through the searchcursor rows once and don't get killed instatiating a new cursor for every value in your dictionary.  Also dictionaries are specifically designed to optimize the performance of lookup operations.  You should also apply a query to the SearchCursor to limit it to just records where the D_DATE > tMinus92.  The D_DATE field should be an indexed field to improve the performance of creating a SearchCursor that applies a query on that field.  I am not bothering to time one value, since now the entire table will be completed in seconds or minutes, depending on the size of the table. table = acDaily # This is a SQL Server database table of daily water volumes. There are ~1300 wells represented in the table, each with daily records covering several years. fields = ['PROPNUM','D_DATE','WATER'] # PROPNUM is the unique identifier for each well in acDaily, D_DATE is the date of the daily volume, and WATER is the volume of produced water. print strftime("%Y-%m-%d %H:%M:%S") # This is used to time the duration of the loop portion of the script. #Build an SQL expression to limit D_DATE to within the past 92 days SQL = "D_DATE > '{}'".format(tMinus92.strftime('%Y-%m-%d %H:%M:%S')) # Use a search cursor to go through the records that are from the past 92 days in acDaily and if the PROPNUM matches the key in propNumDict, add the water volume value to the dictionary. with arcpy.da.SearchCursor(table, fields, SQL) as cursor: for row in cursor: keyValue = row[0] if keyValue in propNumDict: # propNumDict was generated previously and start as an empty list prior to running the SearchCursor propNumDict[keyValue].append(row[2]) print propNumDict print strftime("%Y-%m-%d %H:%M:%S")‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more