Hello, Would like to know how Esearch and Elocate are integrated. I dont know if this gonna work for me: I have very large non-spatial table related to feature class, user searches non-spatial table first
How the intergration works is you perfrom a eLocate widget search for an address or Address Inspector (address lookup) and the results are added to the map. The eSEarch Widget sees these results and enables a special button on the graphical search view to allow you to search a layer (not a table as it has no geometry to intersect with the eLocate results) based on the graphic(s) from the eLocate widget.
I was wondering how hard it would be to add "map it" button for ESearch widget, for non spatial data with x,y columns already where? I am in Python mode most of the time, would like to learn flex.
I was wondering how hard it would be to add "map it" button for ESearch widget, for non spatial data with x,y columns already where? I am in Python mode most of the time, would like to learn flex.
Laurynas Gedminas
I also created geoprocessing tool widget which queries the non-spatial data and outputs the spatial layer on the flex client, but it seems you cant see the layer attributes on attribute table widget, or ESearch. Is it not possible to view output layer in tabular form in these widgets?
For the Attribute widget you will need to add the spatial layer as a FeatureLayer (not a GraphicsLayer) and then it should show up. If it does not show the attributes but does create a new tab in the Attribute widget, this is a bug that will be fixed in the 3.2 release of the viewer scheduled for release this March. No the eSearch widgets datagrids are not designed to show any layers attributes, just layers though the eSearch.
Adding a button to the eSearch for mapping no spatial data with an X and Y field would not be to hard but if you have no background in Flex/ActionScript then it becomes a much harder thing to accomplish.
