Latest Contributions by DavidSolari

Ah, much better! I haven't looked too closely at the exact logic of the script, but there's a couple of big issues: You're attempting to "eval" a SQL expression on line 24, which is generating invalid Python. If you want to apply a filter to a cursor, you should create the SQL string and then pass it in as the third parameter to the cursor constructor. This'll let you use SQL syntax features and it filters the data in the database which saves you some needless Python work. Alternatively you can rewrite the conditional expression to use Python syntax, something like:   [row for row in cursor if row[0] >= search_range[0] and row[0] <= search_range[1]]​   That list comprehension on line 24 is burning through the entire cursor object so it won't update the correct row. Overall I think your best bet is to take a step back and rearrange the order you're running your statements in. One trick that might apply here is to use a dictionary comprehension to quickly turn a dataset into a lookup table. Something like:   lookup = {x[0]: x[1] for x in arcpy.da.SearchCursor(lookup_table, (lookup_key_field, value_field))} with arcpy.da.UpdateCursor(update_table, (update_key_field, data_field)) as cursor: for key, current_value in cursor: new_value = lookup.get(key, current_value) if new_value != current_value: # Avoid needless updates, saves costly db hits cursor.updateRow((key, new_value)) That way you do one pass through the lookup table and make matches in memory, saving a ton of database activity. Good luck!   ... View more

Does this work?  regex(., '^\d+(?:\.\d)?$) ... View more

Please post your code with the code sample formatting and proper indentation so we can see how things should work on our end, thanks!   ... View more

The Field Calculator also loads datetime fields in as native datetime objects so it'll work there as well. If they need the year as a string in a different format then the strftime method and the format code of their choice should do what they need. ... View more

As ESRI product, using malformed JSON? Say it ain't so! Anyways, I did some digging and the demjson package comes up a bunch, I'd say that's your best bet short of building your own parser library. ... View more

I'd expand this to make multi-choice options a full domain type, that way other parts of the platform can edit multiple choice questions. Bonus points if the choices are stored as bit flags if the backing field is an integer, the Survey123 method of concatenating every choice in the backing field seems wasteful when you can shove 16 choices in a short field. ... View more

The table structure for Branch Versioned data is much simpler than Traditional Versioning, it's basically a tweaked version of the format used by Archive-only tables. If you want to make direct edits via SQL, start by reconciling/posting/deleting all your child versions as appropriate, then add records in accordance with how ArcGIS clients do. Off the top of my head for SQL Server EGDBs: Inserts add a new record with a new GDB_ARCHIVE_OID, OBJECTID and GlobalID. The GDB_FROM_DATE is the UTC date of the transaction (this is different IIRC from classic archive tables, which use the local time). Updates add a new record with the same OID and GID but a new GDB_ARCHIVE_OID. Same rules for GDB_FROM_DATE. Deletes are the tricky one. In my initial testing it looked like you just grab the most recent record, set the delete flag and fill out the appropriate delete fields. In a later testing session it looked like deletes added a whole new record that's just a copy of the final record, but with the delete info set and the GDB_FROM_DATE set to the delete time. Make sure you test thoroughly. Almost goes without saying, but the state you set should always be 0. If you want to make edits against a specific version then good luck. Basically just observe how all your clients adjust the table under a variety of circumstances and then mimic that in SQL. I understand why nobody from ESRI will confirm how the operations work from the DB side but that would be a good resource, pretty please? ... View more

Great! I got this straight from the official docs, I recommend you keep them on hand until you've fully tested your deployment just in case you run into any other issues. ... View more

Did you forget the format call on the SQL string in line 7 in the script? If that's just a copy/paste typo, try wrapping the Counties polygons and each Well FC in an arcpy.management.MakeFeatureLayer call and work with the output layer, there's a good chance your selection is silently failing on a non-layer input. Another method is to merge all your wells into one big FC, spatially join it to the Counties, then select every record where the county name doesn't match the original FC name (the "add_source" parameter on the Merge tool makes this easy if your version of Pro supports it). This avoids fiddling with dynamic selections and should run much faster due to batching all the geometry calculations. ... View more

If multiple apps pull from the same web map, any changes to that map will propagate to all apps. You may have to open the app and tweak anything that doesn't automatically carry over, which items require manual updates depends on the app platform and the specific components of each app, best to keep write down what does and doesn't update. ... View more

Those default Shape fields are calculated automatically by the database backing the data using the spatial reference of the feature class. In most cases they're completely useless and should be ignored. There's a few ways to get the proper area for a feature: Good ol' Calculate Geometry Attributes. This gives you the most flexibility in how you do the math and the output units, but you'll have to run the tool every time a feature updates which won't work for every workflow. Use the Area or AreaGeodetic Arcade functions in a popup or attribute rule. The former does the calculation every time a user picks a feature in a web map in the popup only, the latter does the calculation on every insert/update and stores the result in a field. This gives you real-time updates on the Area, the catch is "Area" doesn't let you specify the spatial reference so you'll have to test what reference it uses for the calculations. If that isn't good enough then you'll have to use AreaGeodetic, which is fine for most purposes but you may be required to calculate geometry in a specific SR which means you'll have to fall back to option 1. Give these options a try, you should find something that suits your workflow and requirements. ... View more