In Desktop software, we have the Make Query Layer tool that allows us to perform all sorts dynamic joining and filtering of Geodatabase data to visualize data from multiple feature classes or tables without having to duplicate the data storage. I would find it incredibly handy to have the same capability within web maps using Arcade FeatureSets. If we can define a FeatureSet in popups and label expressions and use them to dynamically access data from multiple layers, could we take it one more step and add functionality to give a map creator the option to say "Add Arcade Layer"? I'm thinking there would need to be requirements that only one spatial field be included in the output and that all the geometries in the final spatial field have consistent coordinate systems etc. But I can see great benefit in being able to add a layer to a map that (for example) combines features from multiple point feature service layers that all have a common status that needs attention so that they could be shown as a single layer in a web map. I can think of many other scenarios that would be useful here too and I would say that there's justification for it because of all the same reasons the "Make Query Layer" tool exists.
Considering the fact that much of my work both in my job and on this site involves Arcade, it's really odd that I never had this idea.
But now that you suggested it: YES, PLEASE.
Query Layers and Database Views are great tools and do a lot of the heavy lifting in my applications, but there is only so much you can do with SQL. Arcade enables us to do more complex calculations. We regularily use Arcade Featuresets in Dashboards and Popups, displaying them on maps, both in the online Map Viewer and in ArcGIS Pro, is the next logical step.
@JohannesLindner, good to hear that it's of value to someone else. I am able to do quite a bit with SQL. However, I think this enables similar things in the web that we cannot currently do. It might be good, however to move away from doing some of the things I've been doing in SQL considering that ESRI is now storing complex geometries such as arcs and multipatch in a separate column called gdb_geomattr_data which makes SQL query layers a bit more cumbersome as the SHAPE column may only contain a simplified version of the actual feature. So having Arcade Layers in Pro and the Web would be beneficial.
I really need FeatureSetbyName or FeatureSetbyID in my Style Expression, such as Pop up expression...!
This would help with arcade driven category/date selector actions. Right now you can return custom arcade dataset in a selector but your custom featureset returned in the selector may not have matching data to match actions to the layer in the map since it cannot be presented in the same arcade expression. Up vote!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.