Latest Contributions by curtvprice

This can't be done in ModelBuilder tools, but you can use the Calculate Value tool like this in ModelBuilder. Expression: proc(r"C:\users\me\my.gdb", r"C:\users\me\my.csv") Code Block: def get_gdb_feature_count(gdb_path): # set workspace to gdb prev_ws = arcpy.env.workspace arcpy.env.workspace = gdb_path # list all feature classes and tables in workspace fcs_and_tbls = arcpy.ListFeatureClasses() + arcpy.ListTables() # GetCount() on all of these counts = [int(arcpy.management.GetCount(ft)[0]) for ft in fcs_and_tbls] # revert workspace arcpy.env.workspace = prev_ws # return [ ["TableName", count] ] return zip(fcs_and_tbls, counts) def proc(gdb, csv_path): result = get_gdb_feature_count(gdb) with open(csv_path, "w") as f: f.write("Name,Count\n") for r in result: f.write(f"{r[0]},{r[1]}\n")   ... View more

Hi Dan.  Here's my fix Field Name: %Value%_Slope_Type  Expression: reclass(!%Value%_Slope!) (I am assuming this is a field name (of a numeric field in your table, since you are doing a numeric comparison in your code block) Code Block: (unlike label expressions you must use a local variable here. Make sure you handle the 0 or None [null]  case)   def reclass(vs): if vs < 0: return 1 elif vs > 0: return 2 else: return 0     The error message (ERROR 000013: N_Slope_Type already in N_Sample_Lines) may reflect that first time @KedaravindanBhaskar  ran the model the field N_Slope_Type didn't exist yet, so the field existed already from then on but ModelBuilder didn't know it so tried to add it hence the error.  The Calculate Field tool has the capability of creating a field as it runs, but because of ModelBuilder validation issues I do not use this feature as it may work the first time but not in future iterations because of validation confusion (the validation tells GP the field does not exist but in iteration two or another run, it exists!) (I think this was a bad design decision, but I'm sure they had their reasons.)  When I am creating a new field I run the Add Field tool first (in your case adding the field %Value%_Slope_Type) because if the field exists, Add Field just passes a warning and moves on. Hope this helps. ... View more

There is a windows mouse settings of number of lines to scroll, but it only turns down to 1 line. Tweaking it is worth a try. ... View more

The question was specifically for ModelBuilder so I think this is exactly the right place! You can use python modules in ModelBuilder using a python function inside the Calculate Value tool. So time.sleep() is probably your go-to here. Connect this Calculate Value output as a precondition to your tool call so it will have to run before your tool that gets the data runs. Expression:   wait(60)   Code block:   import time def wait(sec): time.sleep(sec) return 1         ... View more

I don't understand row[1] as you only have one field so row will only have one element row[0]. If you are trying to populate the 12 values on row at a time (assuming they come out in order, which isn't guaranteed, depending on data source) I think this is the pattern you want:     with arcpy.da.UpdateCursor(fc2, field2) as rows: k = 1 for row in rows: row[0] = LatY[k] rows.updateRow(row) k += 1     If order becomes a problem you can use the ID field:     with arcpy.da.UpdateCursor(fc2, ["ID", "Latitude"]) as rows: for row in rows: row[1] = LatY[row[0] - 1] # index 0 to 11 (IDs are 1 to 12) rows.updateRow(row)   One more issue, your latitude field must be FLOAT or DOUBLE not LONG (LONG will truncate all data to integer when you assign it to the field!) ... View more