Latest Contributions by AndrewBryson1

I haven't spent a lot of time working with python toolboxes in my career (no real need for them), but recently I've had to adapt what was meant to be a standalone script into a toolbox, after discovering a bug that affects CIM (v2) FeatureLayer objects that are accessed outside of an ArcGIS Pro application. My tool is designed to be run on an .aprx that contains small scale transportation maps (and associated layouts) with inset areas marked on them, alongside separate large scale maps (and associated layouts) covering the inset areas. The idea is to take each polyline layer in the small scale map and break it into two layers. Layer one retains the existing symbology, but is masked inside the bounds of the inset areas. Layer two is a copy of layer one with a definition query applied (limiting it to features that intersect the inset area), no layer mask, and reduced line weights for less visual clutter. My workflow in the standalone script went something like this: #1 Make the new layer, add it to the map, and move it to the correct location result = arcpy.management.MakeFeatureLayer(old_layer, new_name) pro_map.addLayer(result.getOutput(0)) new_inset_layer = pro_map.listLayers(new_name)[0] pro_map.moveLayer(old_layer, new_inset_layer, "AFTER") #2 Apply the Unique Values renderer to the new layer arcpy.management.ApplySymbologyFromLayer(new_inset_layer, old_layer) At this point, we need to bring in the CIM. ApplySymbologyFromLayer sets the new layer's renderer without issue, but it defaults to using the literal values from the attribute fields as labels for the symbol classes. That's no good; this is a Unique Value renderer with multiple fields and grouped values. We don't want a label that reads: Unpaved Road, SR; Unpaved Road, 4; Unpaved Road, 5; Unpaved Road, NA we just want it to say Unpaved Road. But we can pull those settings over from the old layer, too, using the CIM: #2A Copy labels inset_cim = new_inset_layer.getDefinition('V2') inset_cim.renderer.groups[0].classes = old_layer.getDefinition('V2').renderer.groups[0].classes From there, it's a relatively straightforward process of looking up the different symbol classes in a symbol dictionary that specifies the updated line weights and colors. (I could see how setting up a .lyrx template and retrieving the desired symbology from there might be easier than using a dictionary, but I was having fun learning the ins and outs of the CIM) So I've got a solution, but now I'm wondering: how does the derived output parameter(s?) even begin to fit into this picture? As already noted, there isn't a ton of documentation out there (maybe even less than there is for the CIM!) and this thread is one of the few links that come up when I search for help. (P.S. I would agree that this issue has not really been 'solved' in a meaningful way. I have no problem with Esri saying "We don't consider this a bug and we don't plan to fix it," but then they should at least provide with some clear, detailed examples of how the derived parameters workaround is intended to work.) ... View more

Chelsea, Do you have any experience using the ArcGIS Assistant to edit the JSON of a web map or web feature layer? I recommend it to people all the time, as the level of control it gives you is really unparalleled; and while I haven't ever used it to solve this particular problem, I'd be very surprised if it can't do the exact thing you're asking about. Below is some sample JSON I had on hand. It's from a webmap I was working on recently. This is the section that specifies the graduated color symbology for a layer of census tracts, based on a tract's Score_State attribute: "layerType": "ArcGISFeatureLayer", "layerDefinition": { ... "visualVariables": [ { "maxSliderValue": 21, "minSliderValue": 0, "theme": "above-and-below", "type": "colorInfo" } ] }, "type": "classBreaks", "visualVariables": [ { "type": "colorInfo", "field": "Score_State", "stops": [ { "color": [ 117, 113, 114, 255 ], "value": 6 }, { "color": [ 188, 184, 180, 255 ], "value": 10 }, { "color": [ 218, 230, 213, 255 ], "value": 13 }, { "color": [ 158, 187, 81, 255 ], "value": 17 }, { "color": [ 93, 122, 6, 255 ], "value": 20 } ] }   Using the Assistant, I think you should be able to set up your symbology the way you want it by either of two routes. You could either use a text editor to type the exact values you want into the "stops" array (lines 20 - 66 above); or you could work in the Map Viewer to create the symbology you want in another feature layer (one with a greater number of features) and then copy and paste the JSON from that layer into your 4-precinct layer. I hope this workaround helps! ... View more

Having the exact same issue. I've tried every tool in my toolkit, from editing the JSON with ArcGIS Assistant to rebuilding the entire dashboard from scratch, but the problem persists. Selecting features on the map filters the values displayed in the serial chart, and selecting features in the category selector filters both the features displayed on the map and the values displayed in the serial chart, but I lose the ability to select features on the map whenever the category selector is active. ... View more

UPDATE: Problem resolved! I needed to clean the original dataset better: the crash locations were generated via linear referencing, and there were a number of non-located points that had not been removed and were presumably interfering with the algorithm that determines the optimal symbol size based on density/extent. I'll leave this here in case anyone else in future has the same issue... ... View more