nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Enhanced-Search-Widget-for-FlexViewer Part III

RobertScheitlin__GISP

All,

Here is a new thread to post questions and discuss the Enhanched Search Widget. The old thread was getting too long.

Vind meer berichten getagd met

Accepted answers

All comments

alexis_s

Thanks Robert for the quick reply and answers to my questions. I will definitely look at the topology of the parcels and see if that solves the issue of non-selection. Thanks for the explanation on what each one does.

MarciaElam

Thank you Robert.

Marcia,

So the way the widget works is that once a search is completed th widget displays the results in the widget results view and when you click on one of those results it will zoom you to that result. If you hve set the layers symbology in the layer tag (as covered in the the extensive pdf documentation), then your symbology for the search results will show as what ever you configured (most of the time people set it to something different than the layers symbology that is already displaying in the map for that layer). If you have made the mistake of providing the wrong symbology type of that layers geometry type (i.e you are search a point layer and you have the layer symbology set to SimpleFillSymbol for a polygon) than it will not draw anything on the map. If you are using the fixed of floating datagrid with the widget than you will also get the option of using the datagrids subselection color (all of this is covered in the pdf and their are examples in the eSearchWidget.xml that is packaged with the widget download).

BrentFoster

Hi Robert,

When using the URL Search Configuration, when I specify a parameter that cannot be found, instead of returning 'Features Selected: 0', I get "Index '0' specified is out of bounds.' If I run the same search and enter the well number manually into the esearch widget, it behaves normally. This only occurs when attempting to pass the parameter thru the URL address. If I pass a valid parameter thru the URL, the esearch widget works properly and zooms to the selected well. It only returns the 'out of bounds' error if I pass a parameter that doesn't exist in the feature. Is there something i'm missing? Shouldn't it simply return the message 'Features Selected: 0'?

Here is an example of the URL i'm using.

https://gis-prd-01/wellsearch/index.html?esearch=30025368360001=&showdatagrid=true

Thank you for a wonderfully useful tool.

RobertScheitlin__GISP

Brent,

What version are you running (hold the Alt key and click on widget title)?

ErwanCaradec

Hi Robert !
I'm back to FlexViewer, upgrading from 2.4 to 3.6...

About EnhancedSearch and Identify widgets, did you ever try to make the widgets config files dependent with sublayers ?

My problems :
- I have many different map configuration files which often use the same services/layers, parts of config file are often identical for a sublayer.
- The esearch config file use the layerid value, all config files have to be updated when you add/remove/move a layer in a service.
- The identify use the layer name, all config files have to be updated when a layer name change.

The idea would be to add a optional tag "widgetconfig" for sublayer tag in the main config file (this may need a MapManager modification). And if the value exists the widgets woul'd load the part of config.

<layer label="..." type="..." url="..." alpha="..." visible="...">
<sublayer id="1" popupconfig="...">
    <widgetconfig name="esearch" file="path_to_subconfigfile" />
    <widgetconfig name="identify" file="path_to_subconfigfile" />
<sublayer/>
<sublayer id=".../>
</layer>

Erwan

RobertScheitlin__GISP

Erwan,

That sounds like a good idea but I stay away from changes to the core viewer when it comes to widgets as I don't want one of my widgets dependent on the custom recompiled viewer.

BrentFoster

Brent,

What version are you running (hold the Alt key and click on widget title)?

I'm using version 3.5.2 of the esearch widget, dated 10-15-2013. Running the 3.5 version of the Flex Viewer.

RobertScheitlin__GISP

Brent,

Because you are not using the latest version 3.6.5, all I can do is tell you where to fix the issue in code (as I don't go backwards in releases to fix bugs). I will have this fixed for the 3.6 version. Let me know if you are using the source code and I will let you know where to apply the code fix.

BrentFoster

Brent,

Because you are not using the latest version 3.6.5, all I can do is tell you where to fix the issue in code (as I don't go backwards in releases to fix bugs). I will have this fixed for the 3.6 version. Let me know if you are using the source code and I will let you know where to apply the code fix.

Thanks Robert, Yes I can go in and recompile if you have the code specified for me to change. Much thanks for your help.

RobertScheitlin__GISP

Brent,

OK, Here is the code change. In the queryFromURL function find the code block that look like this and add the red text:

                            if(searchResultAC.length > 0){
                                if(typeQ == "layer"){
                                    if(isNaN(zoomScale)){
                                        zoomAll();
                                    }else{
                                        if (map.scale > zoomScale){
                                            map.scale = zoomScale;
                                        }
                                        map.centerAt(searchResultAC[0].point);
                                    }
                                }
                                if(ViewerContainer.urlConfigParams.showdatagrid != null){
                                    if(ViewerContainer.urlConfigParams.showdatagrid == "true" && floatorfixed == "float"){
                                        showGridResults();
                                    }
                                }
                            }

azgis

Robert,

I am upgrading from an earlier version of your widget, and I am encountering a problem with the graphic not showing at all zoom levels. The reason is that the layer in question is part of a tiled basemap that has several group layers that have min and max scales in the parent layers. For example, the layer that I am using in the xml is https://myserver/arcgis/rest/services/Maps/BaseMap/MapServer/110. That layer has a parent layer with a min and max scale (the layer itself does not have a min or max scale, i.e. it is type Feature Layer). In the older versions of the eSearch Widget, the search result graphic was I believe added to a graphics layer, which was added to the map, thus it appeared at all scales.

Could you give me a pointer as to what I may be able to do to get the graphic to not be bound by the min and max scale of its parent layer? The rest service is behind a firewall. I attached a screen shot of the service, where layer 110 is the Feature Layer that is being queried in the widget, and layer 107 is the group layer that has the min and max scale that is limiting the graphic's visibility.

Thanks,
Jim Faron
Katy Independent School District

MapService.jpg

RobertScheitlin__GISP

James,

Sure you just need to set the removeserchlayersminmaxscale attribute in the eSearchWidget.xml (you probabbly don't have it in your old version of the XML, That is why it is always best to take the current version of the XML and add your layers to it).

azgis

Robert,

Wow, I sure missed that. Amazing stuff, as usual.

Thanks!

Jim Faron

RichHammond

Hi Robert,
Long time user, first time question poster. Your search tool is absolutely crucial for our mapping applications. Thank you so much for all of your hard work, and the countless hours you must spend fielding these questions. I just upgraded to 3.6.5, and noticed the new reduced footprint for the export options. I noticed now though that when saving the files, the extension is no longer included for the file. In the past, selecting CSV made ".csv" appended to the file name. Now, nothing is appended, and the user must include the file extension otherwise it gets saved as a unknown file type. Same for text. Is there a new setting in the XML that I'm overlooking to set this?

Also, we have many people using your tool, and I'm always getting questions about added functionality. Just wondering if any of these features are likely to be added anytime soon:

-Export to shapefile
-Export to KML
-"Select from Current Selection" selection method.

Again, thank you for all of your time and effort.

-Rich Hammond
GIS Team Leader
WaterAtlas
University of South Florida

RobertScheitlin__GISP

Rich,

Thanks for reporting the file extension bug. I will release 3.5.6 ASAP to fix this issue. As far as the enhancement questions, exporting to shapefile and/or KML. I have no plans for this type of enhancement (I will continue to support my Flex Widgets, but my focus has shifted to JavaScript, so major enhancement like that are not likely). I currently don't support select from current selection as it is not supported by ArcGIS Server like the add and remove are.

RichHammond

Thank you very much Robert. I look forward to seeing what you put out for the JavaScript environment.

Take care,
Rich

Allen_Zhang_0-1740721217607.png

RobertScheitlin__GISP

All,

A new version is available:

Version 3.6.6 - 5/22/2014
* Fixed URL Query Bug when a search is made and no results are found.
* Fixed csv and txt file extension bug in Fixed datagrid export.

JuliaGalindo

Hi,

I have been using the different versions ArcGIS viewer for flex, now I am using the 3.6 version. I have been able to use part of the Enhanced Search Widget in different projects.
Now I have a File GDB with a feature class and a related table in a web mapping service. I want to query a record from the table and then see the related feature class in the map. I know it is possible using this widget. But I can�??t get the same functionality as the example.
What I did:
I queried the SF incident layer, by incident date (using the example date), then selected one record and check the Incident Priority Service Request, then selected from the Incident Priority Service Request table, the record to see the feature.
Then I did the same in the ArcGIS viewer for flex, without look. These are the steps I followed:

1. I saw the example http://gis.calhouncounty.org/FlexViewer3.6/index.html?config=config-eSearch.xml&esearch=2&slayer=3&exprnum=1.
2. Checked the functionality.
3. Downloaded it and copy to a folder with other widgets
4. Went to the ArcGis Viewer for Flex/settings/advance settings/manage custom widgets
5. Erased the old Enhanced Search Widget
6. Added the new Enhanced Search Widget
7. Created a new application, add an base map from ArcGisOnLine
8. Added the widget
9. Previewed to see the functionality.

Additionally, I have a question, in order to obtain the record and the feature class both should be present in the widget, right? I can not only call the table.

Any help is appreciated!
Thanks,

Julia

RobertScheitlin__GISP

Julia,

So are you saying that you can not get the "SF incident" search to work once you have added the widget to your instance of app builder, or are you saying you are having trouble getting your data to work similarly?

JuliaGalindo

Julia,

So are you saying that you can not get the "SF incident" search to work once you have added the widget to your instance of app builder, or are you saying you are having trouble getting your data to work similarly?

Hi Robert,

Yes I am saying I cannot get to work the SF Incident (I didn�??t change a thing). I downloaded the source code (master branch) from GitHub just to compare with the files downloaded in the zip file. I realized I didn�??t have the file named �??SearchWidgetRelateFloatDG.xml and .swf�?� I really don�??t know if that could be my problem.
Unfortunately I can�??t see if that is the problem, since I don�??t know how to work with flash builder to compile the source code.

Thank you very much for the help!

RobertScheitlin__GISP

Julia,

OK, I have a couple of issues that I need to clear up for you.

If you are using app builder than you have no need to get the source code from Github (as you don't have flash builder).
App Builder does not support managing UI widgets, which the fixed datagrid is. So you will have to add the fixed datagrid to your apps main config.xml manually.

The default eSearchWidget.xml is expecting the fixed datagrid because of this part of the xml <floatorfixed>fixed</floatorfixed>. You can get this to work in the App Builder preview if you change that to "float" instead. But if you want your app to look like my live preview site than you will have to add the fixed datagrid manually. You will find the SearchWidgetFixedDG.swf and xml in the widgets folder under eSearch of your app.

JuliaGalindo

Julia,

OK, I have a couple of issues that I need to clear up for you.
If you are using app builder than you have no need to get the source code from Github (as you don't have flash builder).
App Builder does not support managing UI widgets, which the fixed datagrid is. So you will have to add the fixed datagrid to your apps main config.xml manually.
The default eSearchWidget.xml is expecting the fixed datagrid because of this part of the xml <floatorfixed>fixed</floatorfixed>. You can get this to work in the App Builder preview if you change that to "float" instead. But if you want your app to look like my live preview site than you will have to add the fixed datagrid manually. You will find the SearchWidgetFixedDG.swf and xml in the widgets folder under eSearch of your app.

Robert,

¡Thank you very much!, problem solved!

Regards,

Julia

ThanhThai

Hi Robert,

We recently upgraded the eSearch to version 3.6. There seems to be an issue with the Result Table not displaying the Date Type fields correctly; it is displaying a series of numbers with extra zeros at the end, instead of the actual date. Please see the GPS Date column in the Result Table vs. the popup in the attached screenshot. Could you please review and then advise?

Thanks,

Thanh

DateNotDisplayingCorrectly.JPG

RobertScheitlin__GISP

Thanh,

What does your dateformat for that field in your eSearchWidget.xml look like?

<field name="ORIGINSTDATE" alias="Orig Inst Date" gridfield="true" dateformat="MM/DD/YYY" />

ThanhThai

That was it. Thank you so much, Robert! Have a great day!

pWHISLER

Hi! So I set this up a while ago, looks like I'm using ArcGIS Viewer Version 3.6 and eSearch version Version 3.5.4 - 11/5/2013. I know you don't support the older versions, but I wanted to ask a question before I go through the trouble of upgrading.

you wrote:

Version 3.6.1 - 12/19/2013

Fixed issue With search layer symbology not showing when using a URL search until a selection was made in the datagrid.

And I wanted to know if that is what my problem is, when doing a search, no symbols show up and the map area is not highlighted in the same way the regular search widget acts.

regular search widget:

[ATTACH=CONFIG]34180[/ATTACH]

eSearchWidget:

[ATTACH=CONFIG]34181[/ATTACH]

Capture.PNG

Capture1.PNG

RobertScheitlin__GISP

p WHISLER,

The symbology not showing up would only be related to that fix if you are talking about a URL search. It would be best to show me the layer configuration in your eSearchWidget.xml for the layer in question.

pWHISLER

p WHISLER,

The symbology not showing up would only be related to that fix if you are talking about a URL search. It would be best to show me the layer configuration in your eSearchWidget.xml for the layer in question.

here is one:

<layer>
            <token/>
            <definitionexpression></definitionexpression>
            <enableexport>true</enableexport>
            <name>Search Stops APC</name>
            <url>http://serveripaddress/ArcGIS/rest/services/BusStops/MapServer/154</url&gt;
            <expressions>
                <expression alias="Stops APC" textsearchlabel="List with the selected stops and average daily ridership information at stop level, estimated using LYNX Automated Passenger Data collection for one transit bit period.">
                    <values>
                        <value prompt="[Example: 461 for 46E and 462 for 46W or 4%]"> ROUTE = [value]</value>
                    </values>
                </expression>
    <expression alias="" textsearchlabel="">
                    <values>
                        <value prompt=""></value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select List with the selected stops and average daily ridership information at stop level, estimated using LYNX Automated Passenger Data collection for one transit bit period.</graphicalsearchlabel>
            <spatialsearchlayer>false</spatialsearchlayer>            
   <titlefield>ROUTE</titlefield>
            <fields all="false">
                <field name="BUSSTOPID" alias="Stop Id"gridfield="true" />
                <field name="NAME" alias="Stop Name" gridfield="true"/> 
    <field name="ROUTE" alias="Route"gridfield="true"/>
                <field name="DIR" alias="Direction" gridfield="true"/>
    <field name="DAY_ON" alias="Ave Dayly ON"gridfield="true"/>
                <field name="DAY_OFF" alias="Ave Dayly OFF" gridfield="true"/>
    <field name="NTRIPSAMPL" alias="Number Samples"gridfield="true"/> 
            </fields>
            <links/>
            <zoomscale usegeometry="true" zoompercent="2"></zoomscale>
            <autoopendatagrid>true</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <relates/>
            <symbology>
                <simplefillsymbol color="0xff0000" alpha="0.5">
                    <outline color="0xff0000" alpha="0.8" width="2" />
                </simplefillsymbol>    
            </symbology>
        </layer>

RobertScheitlin__GISP

p whisler,

So your image showed what looks like a point feature yet in your layers XML you are trying to symbolize a polygon...

            <symbology>
                <simplefillsymbol color="0xff0000" alpha="0.5">
                    <outline color="0xff0000" alpha="0.8" width="2" />
                </simplefillsymbol>                
            </symbology>

pWHISLER

p whisler,

So your image showed what looks like a point feature yet in your layers XML you are trying to symbolize a polygon...

            <symbology>
                <simplefillsymbol color="0xff0000" alpha="0.5">
                    <outline color="0xff0000" alpha="0.8" width="2" />
                </simplefillsymbol>                
            </symbology>

Ok, so looking at the documentation, I should use picturemarkersymbol right? I tried this:

<symbology>                
<picturemarkersymbol url="/assets/images/i_search.png" height="30" width="30" xoffset="0" yoffset="0" />      
</symbology>

and that worked! thanks!!!!

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.