Latest Contributions by JohannesLindner

With Arcade: Create a new integer field Calculate the field, change language to Arcade, use the script below The rows you want have IntegerField = 1. You can use that to eg Select Layer By Attribute Query definition Delete all other rows var fid = $feature.In_FID var min_days = Min(Filter($featureset, "In_FID = @fid"), "Days") return IIF($feature.Days == min_days, 1, 0) ... View more

It's line 15 of my code. It found at least 1 domain, but one of the domains' codedValue attribute is null. This might be a ranged domain. You could try replacing line 15 with this: domain_values = dict() for d in domains: try: domain_values[d.name] = list(d.codedValues.keys()) except AttributeError: print(f"{d.name} is not a coded value domain.")   ... View more

Have you tried using the qualified sequence name? NextSequenceValue("SCAOPFOwnerTest.ParcelNumberAssignmentSequence") creating the sequence with the ArcGIS tool (Create Database Sequence (Data Management)—ArcGIS Pro | Documentation)? ... View more

this will raise exceptions in at least these scenarios: you input a shapefile you input a flag_field that is not Integer probably when you have range domains in your database ... View more

Huh, I would have guessed that it's easier in Python than in Arcade, but it certainly took longer to write...   Same setup as in your Arcade question (Flag row if any field has invalid domain values - Esri Community).     import pathlib def check_domain_values(in_features, flag_field, database=None): """sets the flag field to 0 if at least 1 field value is not in the field's domain, else 1 in_features: str, path to the feature class or table flag_field: str, name of the field that has the flag database: str, path to the database. defaults to the parent directory of the feature class, should be set when the fc is in a feature dataset. """ if database is None: database = pathlib.Path(in_features).parent domains = arcpy.da.ListDomains(database) domain_values = {d.name: list(d.codedValues.keys()) for d in domains} print(f"domain_values: {domain_values}\n") fields = arcpy.ListFields(in_features) allowed_values = {f.name: domain_values[f.domain] for f in fields if f.domain not in ["", None]} fields_with_domains = list(allowed_values.keys()) print(f"allowed values: {allowed_values}\n") print(f"domain fields: {fields_with_domains}\n") fields = fields_with_domains + [flag_field] with arcpy.da.UpdateCursor(in_features, fields) as cursor: for row in cursor: ok = True for i, value in enumerate(row): try: field = fields[i] if value not in allowed_values[field]: ok = False break except KeyError: # flag_field is not in the dictionary pass new_row = list(row) new_row[-1] = ok cursor.updateRow(new_row)           fc = arcpy.Describe("TestPoints").catalogPath check_domain_values(fc, "IntegerField")       domain_values: {'MyDomain': ['Value 1', 'Value 2', 'Value 3']} allowed values: {'TextField': ['Value 1', 'Value 2', 'Value 3']} domain fields: ['TextField']     ... View more

You can set a fixed scale for map frames in layouts: Map frame constraints—ArcGIS Pro | Documentation   For working in the actual map, you can utilize a custom scale:   ´Then you can pan (and zoom)  to a differnet part of your map and select your scale from the scale list:   If you only want to see your custom scale, you can delete all other scales from the list...   ... View more

Very basic: If you don't have one already, create a feature class for the trees (probably points) with a text field. When you planned the tree, fill out the text field with the current date (you could also use a date field, but working with date fields becomes tiresome later on [time zones, different sql formattings etc.]). Symbolize the trees by unique values:   Kinda basic: Use Summarize Attributes to create a table containing the dates and a tree count for each date:     In your layout, insert a table frame, point it to the summary table, show the date and count fields:   Advanced: Automate the process with Attribute Rules. Create a table with a text field and an integer field (this will mimic the summary table). Create a Calculation Attribute Rule on your tree fc (add GlobalIDs first): // Calculation Attribute rule on tree fc // field: empty // triggers: update (I'm assuming you don't insert or delete tree features) // Exclude from application evaluation: checked // determine if the planning date changed // it changed if it was previously empty or if we previously edited the tree on another day var current_date = Text(Today(), "Y-MM-DD") var original_date = $originalfeature.TextField var date_changed = (original_date == null) || (original_date != current_date) // if the date didn't change, we don't need to do anything. if(!date_changed) { return } // load the summary table var summary_table = FeatureSetByName($datastore, "TestTable") // create empty arrays that will hold edits to be made to the summary table var adds = [] var updates = [] // if the date changed, we have to increase the cuurent date's count in the summary table. // if the current date isn't there yet, we have to create it var sql = "TextField = @current_date" var summary_current_date = First(Filter(summary_table, sql)) if(summary_current_date == null) { // nothing found -> insert row var new_row = {"attributes": {"TextField": current_date, "IntegerField": 1}} Push(adds, new_row) } else { // row found, increase count var updated_row = {"objectID": summary_current_date.OBJECTID, "attributes": {"IntegerField": summary_current_date.IntegerField + 1}} Push(updates, updated_row) } // return current_date to the tree feature's date field and tell ArcGIS to update the summary table return { "result": {"attributes": {"TextField": current_date}}, "edit": [{ "className": "TestTable", "adds": adds, "updates": updates }] } Now, when you update a tree feature, the entry in the summary table with today's date will be inserted or its count increased. If you point your table frame to the new summary table, the changes will be reflected there: You will probably still have to refresh the symbology after each day...   Also, charts!:     ... View more