IDEA
|
@JesseLangdon1 There is a good use case for the feature info widget. See our Fishing Access app. When you select a list item, it zooms to the location. You can click or tap View Details, and the view in the pane changes to the Feature Info widget for details. I like having the details in a docked pane on the side like this (on larger screens) because it looks better than the popup and doesn't cover up the map area. I can also disable popups in the map widget (see the map widget Options at the very bottom) and configure an action so that clicking a feature in the map selects a record in the list and filters the Feature Info widget. That all works nicely. The problem for me is this: I want people to be able to click a fishing access feature in the map. However, I have other layers in the map that I would like to have popups for. So I can't disable the popups on the entire map, thus I get the redundancy of the feature info widget and the popup on my primary layer in the app. The best solution seems to be to allow the user to select which layers in the map to enable popups (on the ExB map widget options). I could keep some layers with popups enabled, but disable my primary layer that uses Feature Info.
... View more
01-05-2024
05:55 AM
|
0
|
0
|
190
|
POST
|
I want to add to the discussion (and possibly be corrected if I'm wrong). This gets the more precise midpoint of the feature, but doesn't always return a point on the line if the line is not straight. If you don't need a precise midpoint and you want the coordinates to be on the line, I've found the easier option is to get the number of a paths in the geometry object, and get coordinates from one of those paths closest to the middle. If there are 11 paths in the segment, get the 5 or 6th and use those coordinates. then it's always on the line, and the code is simpler.
... View more
11-14-2023
12:54 PM
|
0
|
0
|
944
|
IDEA
|
Back three years after my original comment on this idea. Still definitely needed.
... View more
10-18-2023
06:45 AM
|
0
|
0
|
610
|
IDEA
|
It would be awesome to have this in the upcoming release.
... View more
09-12-2023
06:46 AM
|
0
|
0
|
422
|
POST
|
Alright, kind of a ridiculous realization here... turns out it has been working, but it wasn't showing the edits 'in real time' for the second rule. This led me to believe that it wasn't working, because the updates were being shown immediately with the first rule. So if anyone is getting frustrated at a rule that should be working... sort your table after the edit, maybe it is working after all. Womp womp 🙂
... View more
07-27-2023
09:10 AM
|
0
|
0
|
472
|
POST
|
I am testing two calculation attribute rules. They are almost exactly the same... the only difference is an if statement that evaluates at the beginning. Both are update triggers. In one rule, which uses $originalFeature and detects changes in geometry, it works as intended. In the second, which uses $originalFeature and detects a change in an attribute, it does not work. The part that apparently does not work is the 'edit' with attribute updates to other features in the same feature class. After some debugging, I've found that what I'm passing to 'updates' is a correctly formatted dictionary. I can't find anything in the code that indicates why it would not work for this rule, but it works fine for the other. I've tried many ways to isolate the issue, but have come up empty. Commented code below. var new_parent_property_id = $feature.ParentPropertyID
var old_parent_property_id = $originalfeature.ParentPropertyID
//see if the parent property id has changed
if (new_parent_property_id != old_parent_property_id) {
//Creates empty array and counter for iterating
var updates = []
var counter = 0
var gid = $feature.GlobalId
//use this filter statement to get all of the records with same parent prop id for the SUM.
var sumfs = Filter($featureset, "ParentPropertyID = @new_parent_property_id")
var newacres = Sum(sumfs, "GIS_TractAcres")
// use this filter statement to exclude the edited record, so that the 'updates' doesn't kick back a cyclical error.
var fs = Filter($featureset, "ParentPropertyID = @new_parent_property_id AND GlobalId <> @gid")
// iterate records and make 'updates' dictionary
for (var f in fs){
updates[counter] = {
'globalID': f.GlobalId,
'attributes':{
'GIS_PropertyAcres': newacres,
}
}
counter++
}
// return a 'result' for the edited record. use 'edit' to modify the attributes of the other features in the table with the same parent prop id.
return {
'result': {
"attributes": {
"GIS_PropertyAcres": newacres,
"longtext":Text(updates)
}
},
// ~~~ This is the part that is apparently not working in this rule. ~~~
'edit': [{
'className': 'Arcade_Rules_Test',
'updates': updates
}]
}
} else {
return "Parent Prop ID didn't change."
} Using ArcGIS Pro 2.9.5 and a file geodatabase.
... View more
07-27-2023
07:35 AM
|
0
|
1
|
515
|
POST
|
I know this is a little old, but I haven't found a solution mentioned online. It's quite an easy solution, but it is not well documented, if it is at all. I had to piece this together from reading different things. It actually does not even involve using the ApplySymbologyFromLayer method. You can use the options given in @DrewFlater response and also use an output name generated in the script. The solution: In your script tool properties, set a parameter and give it the "Derived" type to make it a derived output parameter. I got to this from the documentation on ApplySymbologyFromLayer, directly above the Parameters list. Set the Symbology in that Derived Output parameter to your layer file. Now in the script, you will use SetParameterAsText() to apply your generated output (path to data, layer, etc) to the Derived Output parameter. When you do this, it will apply the symbology that you set on that parameter. See the code below for how I am using it. # APPLIED AFTER MAKE FEATURE LAYER
fl = arcpy.management.MakeFeatureLayer(parcels,prop_name,tmap_exp)
# using SetParameterAsText... first argument is index of your script tool's parameters, and second arg is the feature layer I generated.
arcpy.SetParameterAsText(6,fl)
# APPLIED TO A SHAPEFILE
arcpy.env.workspace = filepath
formatted_name = prop_name.replace(" ","_")
shp = arcpy.management.CopyFeatures(fl,"{}.shp".format(formatted_name))
arcpy.SetParameterAsText(6,shp)
... View more
07-10-2023
06:44 AM
|
0
|
0
|
330
|
POST
|
That's it right there, you nailed it. So previous to the update, ExB zoom included the animation, which I think is a nicer user experience, and seems to be kept in place for Instant Apps. The 'jumpy' is indeed the un-animated zoom between levels. Is there a reason ExB needed to use decimal instead?
... View more
06-29-2023
06:04 AM
|
0
|
3
|
1344
|
POST
|
Hi all - regarding using a data expression with GlobalIDs. I found that when you use a data expression as a data source, and you want to use a GlobalID as a key to filter other elements, you need to make the field type 'esriFieldTypeString' to store it. I tried storying it as a GUID field type and it didn't work, but making it a string did. I also converted the GlobalID to text using Text(), though I don't know if it's necessary, but it worked.
... View more
06-27-2023
08:19 AM
|
1
|
0
|
1223
|
POST
|
Hi @Jianxia, sure, here is a public app where using the scroll wheel on a mouse produces a jumpy experience. https://experience.arcgis.com/experience/368c6b8ebc164f21877eda6aa3aa4fcf/page/fishing/ Zoom in and out buttons zoom smoothly, however. All is smooth on mobile. So really it's a scroll-wheel thing, I guess. Issue exists in Chrome, Edge, and Firefox. Another issue that may or may not be related... when I hover my list now (same app), it flashes each list item. Sometimes you can see the underlying list markup (e.g. {field_name}). Hovering the list did not used to produce that effect. Thanks!
... View more
06-26-2023
06:22 AM
|
0
|
7
|
1375
|
POST
|
Since the most recent update in Experience Builder (June 2023), my maps in experience builder are very jumpy when zooming. The zoom experience was pretty smooth before the update. It also causes the basemap to flash when zooming. The same map zooms smoothly in Map Viewer.
... View more
06-20-2023
05:53 AM
|
2
|
12
|
1699
|
IDEA
|
Here to say that not a week goes by that I don't wish for the single click functionality. The workaround doesn't always solve the problem, since it reloads the embedded content each click. Would really love to see an option for this functionality implemented.
... View more
06-02-2023
05:40 AM
|
0
|
0
|
557
|
IDEA
|
Back here to say that while the labeling can work in some cases, it's tedious compared to what's being suggested, which is to disperse point markers dynamically, for instance with dynamic symbol effects. Please see the Point Displacement renderer in QGIS.
... View more
05-25-2023
06:08 AM
|
0
|
0
|
717
|
Title | Kudos | Posted |
---|---|---|
1 | 06-23-2021 08:32 AM | |
1 | 06-27-2023 08:19 AM | |
2 | 06-20-2023 05:53 AM | |
1 | 01-12-2023 08:08 AM | |
1 | 04-28-2023 12:01 PM |
Online Status |
Offline
|
Date Last Visited |
a week ago
|