Do you have any fields that do not overlap with the DEM at all? The script is failing when attempting to determine the approximate # of 1-meter contours that can exist in each field. It does this by finding the total elevation range in each field, then dividing this by 1 meter (then rounding up or down to the closest whole #). Instead of returning a value, a “None” value is being returned (basically NODATA). This may happen if a field has no elevation values to go by (i.e. it lies entirely beyond the DEM). Moving forward, I can try to account for this in the script. We recommend clipping your DEM to the extent of the buffered watershed boundary, and I have not seen this problem as of yet.
- Response: Turns out, there were field boundaries that were outside of the buffered (DEM) area. Once the field boundary feature class was updated to only those that intersect the DEM and the tool worked properly.