How do i combine attributes from multiple query sources?
I've got a parcel layer set up in my map with a data link to show additional detail in the results. This works great when identifying on the map, but i need to recreate this in an address search workflow. I have set up a search table in essentials, but haven't figured out how to add the attributes from the search table parameter query results to the featureset results of the parcel layer. Any tips?
0
-
Just a thought - not sure if this applies to your situation...
If the parcel featureclass and related tables are in an enterprise geodatabase (SQL) and you have direct access to that geodatabase. I would consider creating a view that combines the related tables and parcel featureclass. Then using that view as the layer/featureclass in the map service. The view you created will be treated like any other featuclass with the exception of feature editing (which isn't allowed).0 -
Thanks Scott, I started to explore the view route today, it will work, and I like the simplicity, but I was hoping for tips toward a programmatic solution as I have other cases where it will be more necessary to go that route. In this case, it's a cross-database join to a non-spatial table, any insights on performance hit given these factors? 0 -
Cross-database join... Same Server? If so, you'll probably see a performance improvement. These types of relationships are better done closer to the source if possible - less overhead. It also gives you more flexibility in creating dynamic field values like concatenating address or owner name fields into one. Or even things like calculating the age of something based on Now() - a date field. 0 -
No, linked server unfortunately, and no control over that other than to read from it. I'm starting to think it would be best to treat it as "additional info" and link to a report from the main feature results, which is similar to the way it's handled in the City's current web mapping tool anyway. Appreciate your insights, thanks! 0 -
It would help if you were more specific on what you mean by "add the attributes from the search table parameter query results to the featureset results of the parcel layer.". Are you trying to build something like an excel download with two sheets? Are you trying to run analysis using one featureSet against the other? Trying to select features in the viewer? Trying to combine featureSets for further analysis? 0 -
Hi Zack. I merely want to display the additional attributes in the result panel below the existing ones from the main table. The workflow is an address search. Right now I've got it swapped it out to use a view that gives me all the fields I need, but I'd like to solve and undertand how to do the join in the workflow.
I'm also struggling with why this workflow does not honour field display names and displays the actual field names instead. Other workflows I've written use the display name. The only difference I can see is that this workflow uses a combo box as the form selector while the others use list boxes so guessing I need to do some handling for one or many results?
https://geocortex.fallsviewer.ca/Viewer/index.html?viewer=Public
https://geocortex.fallsviewer.ca/Geocortex/Essentials/REST/sites/Public/workflows/Search_Parcel_By_Address0 -
Just for the record. I was able to configure a view that serves our attribute needs and performs acceptably well. I will be revisiting combining search table attributes with a featureset soon and will post any solutions I find here. The display name issue I was having went away when I removed the Layer ID variable in the SelectFeatures Activity. 0
Please sign in to leave a comment.
Comments
7 comments