Latest Contributions by DavidSolari

Is this different from what Jackson did in their listing? ... View more

I tried your code with a cut down expression in 3.4 and it worked on my test data. Try a simpler expression and then slowly build it up until you find the subexpression that breaks it. ... View more

Have you tried building a Field Map link? ... View more

I think your listing missed the line where you grab the child's parent, but either way: that error is a sign that you have a parent to child update going on — either from an attribute rule on the parent or a composite relationship class — that retriggers the child, which retriggers the parent, and so on. Check what you have going on in the parent and look for potential loops. In some cases you can fix this by comparing fields in the $feature with matching fields in the $originalfeature and returning early if there were no changes. ... View more

The GlobalID column technically sorts correctly, the issue is the byte ordering of the raw GUID data vs. the standard presentation. If I use data stored in a SQL Server EGDB it's sorted per the SQL Server uniqueidentifier type as described in this blog post, which is why it doesn't appear sorted. I couldn't tell you if every EGDB host has their own behavior or if ArcGIS in forcing everything to sort like uniqueidentifier but there is a method to the madness. ... View more

Ah sorry, I reread your question and the issue is with the labelled points themselves. The solution to this question has a clunky workaround where you buffer the points and then label the polygons instead, but below that there's a bunch of things you can try that are done at render time, maybe one of those work. ... View more

In Pro 3.4 I was able to build a callout label with a point symbol as shown in the image below. Adjusting the "Gap" put some distance between the image marker point symbol and the leader line. "Leader tolerance" is used to remove the leader lines unless the distance between the feature's label centroid and the label symbol exceeds the tolerance.   ... View more

If you want a full rebuild: Delete Features followed by Append. If you want a less violent update you can either do some Pro upgrades and check out the new "Matching Fields for Update" parameter, or dive into arcpy to write your own update tool. ... View more

The only geoprocessing tool that's ever given me trouble with the memory workspace was Project and that might've been fixed over the years. In general, if the tool doesn't operate on a whole workspace, a feature dataset, or anything that has to reside in a feature dataset then it'll work with the memory workspace. Don't use "in_memory" unless you still need ArcMap compatibility. ... View more

Unfortunately I didn't run any bulk edit, in the process of cutting and pasting different chunks around I must have slowly erased all the bad line endings. I use Notepad++ for general text editing and you can use Edit → EOL Conversion to bulk convert a file. If you need to fix a mixed-ending file something like this should work: import re bad_file = r"C:\path\to\file" good_file = r"C:\path\to\output" with open(bad_file , "r") as f1, open(good_file, "w", newline="\r\n") as f2: f2.write(re.sub(r"\r\n?|\n", "\n", f1.read())) ... View more

This would be a fantastic addition, but it's unlikely a non-critical update will make it into a previous Enterprise release. As a stopgap, you can use tools that directly manipulate Web Map definitions (such as the AGOL Assistant or the Python API) to change the filter using hand-written SQL. Something like: date_resolved >= CURRENT_DATE   ... View more

This is a fantastic idea unless you read the entire first sentence in the OP, then it's useless for this case. ... View more

If you can't filter up front, filter out back. Here's a sample that will remove all non-PDF/JPEG attachments from the folder you downloaded them to: import os out_dir = r"C:\path\to\folder\with\attachments" extensions = [".pdf", ".jpeg", ".jpg"] for root, _, files in os.walk(out_dir): for f in files: if not any(f.lower().endswith(e) for e in extensions): os.remove(os.path.join(root, f)) Feel free to tweak that third line to match your desired results. ... View more

A Feature Class can only take feature classes via a path, but gives you guaranteed access to the data definition (fields, indices, attribute rules etc.). A Feature Layer can take a feature class by path or a layer from the current map. You can't always edit the structure of your data but you can edit its features, and the user can pass in a subset of the full data. A Feature Set can take all of the above plus arbitrary feature data from any source. But it's even less likely that you can modify the data's structure. In short: as you go from FC to FL to FS it becomes harder for the user to specify what exact data is edited but the script has an easier time modifying the data. I usually go with Feature Layers if I don't have a specific use case but it's up to you. (Note that Table, Table View and Record Set are the non-spatial types of their respective parameters. This doesn't stop you from passing in spatial data but you lose the guarantee that you can work with the data's coordinate system, geometry data etc.). ... View more

You can try checking if the original value is different from the current value first: if ($originalfeature.pole_depth == $feature.pole_depth) { return $feature.pole_height * 0.1 + 3 } If you edited the field directly then the original value will be different from the current value and you don't return a new value, if you edited another field then the value should stay the same and then you can recalculate it. That said, adjusting the height will probably re-run the rule again. Other solutions include running the rule on insert only, or adding a "is_calculated" field that is set when the rule is run, then checked to ensure it isn't run again. ... View more