Latest Contributions by JohannesLindner

That would be helpful. Also, do the same for $datastore and for the labeling profile. Though my guess is that evaluating this expression for each feature shown in the map each time the map is updated is going to be very slow. But for small datasets this would be great.   In the meantime, you can add a field to your FC and calculate it with your expression. This works for more or less static data, but is too much of a hassle for regularily updated datasets.   ... View more

It is possible. But you dont define the rule on the feature class, you do it on the work history table. // Attribute Rule on the work history table // Triggers: Update // Field: empty // do nothing if meter id did not change (so you don't send senseless update requests) if($originalfeature.MeterID == $feature.MeterID) { return null } // get the water meter var water_meter = First(FeatureSetByRelationshipName($feature, "RelationshipName")) if(water_meter == null) { return null } // Send a request to update the MeterID in the parent FC return { "edit": [ { "className": "WaterMeterFC", "updates": [ {"globalID": water_meter.GlobalID, "attributes": {"MeterID": $feature.MeterID}} ] } ] }   ... View more

These are the properties of the layer, not of the shapefile. A layer's properties are only stored in the map project or in a layer file. Nothing gets written to the underlying data. If you want to edit the shapefile's metadata, try using ArcCatalog: https://desktop.arcgis.com/en/arcmap/10.3/manage-data/metadata/viewing-metadata-from-arccatalog.htm  ... View more

I don't know Geopandas, but if you have access to arcpy, you can do it like this: grid = "path:/to/grid.shp" pipes = "path:/to/pipes.shp" grid_id_field = "GridID" # unique identifier of your grid features pipe_length_field = "PipeLength" # name of the new field # intersect grid and pipes intersection = arcpy.analysis.Intersect([grid, pipes], "memory/intersection") # read intersection into a list # [ (GridID, PipeShape) ] intersection_list = [row for row in arcpy.da.SearchCursor(intersection, [grid_id_field, "SHAPE@"])] # add the new field to the grid arcpy.management.AddField(grid, pipe_length_field, "DOUBLE") # loop through the grid and fill the new field with arcpy.da.UpdateCursor(grid, [grid_id_field, pipe_length_field]) as cursor: for grid_id, pipe_length in cursor: # get all pipe shapes in this grid cell pipe_shapes = [d[1] for d in intersection_list if d[0] == grid_id] # get total length of those shapes pipe_length = sum([s.length for s in pipe_shapes]) # update field values cursor.updateRow([grid_id, pipe_length])   ... View more

What format do the photos in the attachment table need to be? The field mapping only recognizes BLOB (Binary Large OBject, so byte data) fields. If you have an ArcGIS Attachment table, there should be a BLOB field in there. If not, you can also create a BLOB field in your feature class and store the images there.   And do you think there would be a way to dynamically offset all the labels so that the points don't get obscured (maybe in Python)? Dynamically? Probably not, for that you need to work with labels, not symbology. Maaaaaybe with Point Clustering in 2.9, but it doesn't seem likely. With Python? You could map X and Y offset to fields in your feature class. You could then calculate these fields with Python, using the distance to nearby points as input. This could work for a fixed map scale and picture marker size. But as soon as you zoom out, the images will overlap each other again. A simple approach to that with Arcade: // calculate field OffsetX // load other features var gid = $feature.GlobalID var fs = Filter(FeatureSetByName($datastore, "FeatureClass"), "GlobalID <> @gid") // get nearby features var nearby_features = Intersects(fs, Buffer($feature, 50)) // gravitational force in horizontal direction var force = 0 for(var f in nearby_features) { var dist = Distance($feature, f) var dx = Geometry(f).X - Geometry($feature).X force -= dx / (dist * dist) } // magical number dependent on map scale and picture marker size var magic_factor = 100 return force * magic_factor // calculate field OffsetY // load other features var gid = $feature.GlobalID var fs = Filter(FeatureSetByName($datastore, "FeatureClass"), "GlobalID <> @gid") // get nearby features var nearby_features = Intersects(fs, Buffer($feature, 50)) // gravitational force in vertical direction var force = 0 for(var f in nearby_features) { var dist = Distance($feature, f) var dy = Geometry(f).Y - Geometry($feature).Y force -= dy / (dist * dist) } // magical number dependent on map scale and picture marker size var magic_factor = 100 return force * magic_factor   Without offsets:   With offsets:   But it only works for a fix scale. When you zoom out, the images overlap again:   ... View more

A working, but basic approach: Join the Attachment table to the feature class. You can now choose the DATA field of the attachment table as input for the picture marker   Basically, that's it. To make it prettier: Set size and quality, set position to "Center bottom"   Add a marker layer on top of the picture layer, style it   rotate the whole symbol using a rotation field       Before: After:   I'm sure you could hack together a border around the picture somehow. Unlike labels, symbols don't seem to have options for dynamic placement. Position and offset are either taken as values provided by the user or by a table field.   I haven't found a way to use labels for this task. You can't use the Attachments() and FeatureSetBy*() function in the Arcade label expression, and the DATA field of the joined attachment table is also not available.   I thought I had something using a Python label expression and trying to return an HTML <img> tag with a data uri, but it doesn't seem to work (it's because there are only a few text formatting tags allowed; I'll still leave the code here, maybe it helps): def FindLabel([GlobalID]): import arcpy import base64 att_table = 'path:/to/database.sde/Fotos__ATTACH' sql = "REL_GLOBALID = '{}'".format([GlobalID]) cur = arcpy.da.SearchCursor(att_table, ['CONTENT_TYPE', 'DATA'], sql) for row in cur: b64 = base64.encodebytes(row[1]) data_uri = 'data:{};base64,{}'.format(row[0], b64) #return data_uri[:30] # this returns the start of the data_uri correctly return '<img src="{}"/>'.format(data_uri) # this returns without error, but doesn't do anything return "N/A"   Don't know anything about JScript, maybe you can do something with that. ... View more

Actually, if you use this expression, you can use it for all geometry types: // base url of your Dashboard // if there's no "?" in the URL, add one at the end, else add "&" var url = "https://company.maps.arcgis.com/apps/dashboards/123?" //var url = "https://company.maps.arcgis.com/apps/dashboards/index.html?id=123&" // how much do you want to zoom out? var buffer_dist = 200 // use the extent parameter var ext = Extent(Buffer($feature, buffer_dist)) var ext_par = "extent=" + Concatenate([ext.xMin, ext.yMin, ext.xMax, ext.yMax, ext.spatialReference.wkid], ",") return url + ext_par ... View more

When there are no related features, you call First() on an empty feature set, which will return null. You just have to check the size of the feature set before calling First() on it: var relationship = FeatureSetByRelationshipName($feature, 'Device_Hydrant_To_Inspection', ['hast_assetid'], false); // check size of FeatureSet, return null if empty if(Count(relationship) == 0) { return null } return First(relationship).hast_assetid   ... View more