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 2.1

RobertScheitlin__GISP

All Here is my next widget in the FlexViewer 2.1 series

Special thanks to Erwan Caradec for contributing to this code.

The Enhanced Search Widget extends the standard search widget with a floating data grid and a new spatial query w/buffering.

http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e

Encontre mais publicações marcadas com

Accepted answers

All comments

CynthiaMatney

Cynthia,

Hmm... I was actually refering to the one that you are attempting to use the domain for. I need to see how you are setting that expression up.

Sorry - I changed it above.

RobertScheitlin__GISP

Cynthia,

Hmm... I was actually refering to the one that you are attempting to use the domain for. I need to see how you are setting that expression up.

CynthiaMatney

This is the only part I have changed on the xml.

<layer>
<enableexport>true</enableexport>
            <name>Zoning</name>
            <url>http://maps/ArcGIS/rest/services/Layers/Zoning/MapServer/0</url>
            <expressions>
             <expression alias="Zoning Code"
              textsearchlabel="Search Zoning Code [ Example: R-1A ]:"
              field="ZONECLASS" usedomain="true">upper(ZONECLASS) = upper('[value]')</expression>
             <expression alias="Zoning Name"
              textsearchlabel="Search Zoning Name [ Example: SUBURBAN RESIDENTIAL DISTRICT ]:"
              field="ZONEDESC" usedomain="true">upper(ZONEDESC) = upper('[value]')</expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Zoning</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>ZONECLASS</titlefield>
            <linkfield linkprefix="" linksuffix="">URL</linkfield>
   <icon isfield="true" iconprefix="" iconsuffix=""></icon>
            <fields all="false">
                <field name="ZONECLASS" alias="Zoning Code"/>
                <field name="ZONEDESC" alias="Zoning Name"/>
                <field name="ACRES" alias="Acres"/>
                <field name="URL" alias="URL"/>
            </fields>
        </layer>

RobertScheitlin__GISP

Cynthia,

Now can I see your SearchWidget.xml

CynthiaMatney

Fields:
OBJECTID (Type: esriFieldTypeOID, Alias: OBJECTID)
ZONECLASS (Type: esriFieldTypeString, Alias: Zoning Classification, Length: 10, Domain: Coded Values: [Agriculture District: A], [Suburban Residential District: R-1A], [Low-Density Single-Family Residential District: R-1B], ...29 more... )
ZONEDESC (Type: esriFieldTypeString, Alias: Zoning Description, Length: 100, Domain: Coded Values: , [R-1A: Surburban Residential District], [R-1B: Low-Density Single-Family Residential District], ...29 more... )
ACRES (Type: esriFieldTypeDouble, Alias: ACRES)
SHAPE (Type: esriFieldTypeGeometry, Alias: SHAPE)
URL (Type: esriFieldTypeString, Alias: URL, Length: 200 )
ZONE_OFF (Type: esriFieldTypeString, Alias: Official Zoning, Length: 20 )
SHAPE.area (Type: esriFieldTypeDouble, Alias: SHAPE.area)
SHAPE.len (Type: esriFieldTypeDouble, Alias: SHAPE.len)

RobertScheitlin__GISP

Cynthia,

Can you go to your REST Service Directory and copy some of the lines like this and paste them for me to review:

Fields:

    * OBJECTID (Type: esriFieldTypeOID, Alias: OBJECTID)
    * Local_ID (Type: esriFieldTypeString, Alias: Local ID, Length: 10 )
    * Bin (Type: esriFieldTypeInteger, Alias: Bin)
    * Length_ (Type: esriFieldTypeDouble, Alias: Length)
    * B_Road_W (Type: esriFieldTypeDouble, Alias: Bridge Roadway Width (Curb to Curb))
    * Deck_W (Type: esriFieldTypeDouble, Alias: Deck Width (Out to Out))
    * Approach_R_W (Type: esriFieldTypeDouble, Alias: Approach Roadway Width)
    * Span_Num (Type: esriFieldTypeSmallInteger, Alias: Number of Spans)
    * M_Span_L (Type: esriFieldTypeDouble, Alias: Max Span Length)
    * Deck_Cond_C (Type: esriFieldTypeString, Alias: Deck Condition Code, Length: 5, Domain: Coded Values: , [9: 9 - Superior to present desirable criteria], [8: 8 - Equal to present desirable criteria], ...8 more... )

I am interested in seeing the fields that have domains.

CynthiaMatney

I have the newest Enhanced Serach Widget downloaded 2.2.7f - One of my layers I want to be able to search is my zoning layer. It works fine until I try to use the domain "usedomain="true'... I run my viewer and when I open the search window it shows up as it should - shows my domain values of my zoning layer in a dropdown box. However, when I click on one to search (ie: "R-1A") - it returns no values. If I take out the line "usedomain" then type in "R-1A" myself - then values are returned. Any ideas?
Thanks!

NestorNavarro

Thanks Robert !!

It is a great widget and the resizing is a nice touch.
Only thing I need is for the API to handle one to many relationships and everyone would be happy.

Nestor.

RobertScheitlin__GISP

Nestor,

There was another things fixed but since you has version 2.2.3 installed at one point it is not an issue for you so I would say you can wait for the next version (although I am not sure what else could be added to this widget at this point).

NestorNavarro

Looked at 2.2.7f and I see we are on the same page. Was that the only change from 2.2.7?
If so, I am leaving it alone until the next upgrade.

Thanks ..

Nestor.

NestorNavarro

Nestor,
There was an issue with 2.2.7 I have it fixed in 2.2.7f

Hey Robert.

I have not loaded 2.2.7f yet but the problem was resolved once I put the following line in from the 2.2.3 xml:

<info>widgets/InfoTemplates/InfoPopupWidget.swf</info>

No more errors after that.

I will check out 2.2.7f. Thanks !!

Nestor.

RobertScheitlin__GISP

I'm using the uncompiled version.
All I did was replace the old folder with the new version folder, recompile, clear the cache and that was it, started getting the error. Then I tried it with my xml including your changes such as the enable export true elements and I get the same error. What is that error anyway?

I will replace it with the old version again (2.2.3) and see if it works normally again.

Nestor.

Nestor,
There was an issue with 2.2.7 I have it fixed in 2.2.7f

RobertScheitlin__GISP

Lisa,

Must be a something simple. I did a search for 2003 using your map service and zoom to the same area and don't have that issue.

Lisa.jpg

LisaArnold

All,

New version is available.

Version 2.2.7 - 02/04/2011

* Added ability to define a simple marker symbol for point or the current picture marker symbol.

Hi Robert,

Thanks for adding in the ability to have a simple marker symbol for point data. I have implemented 2.2.7 and commented out my picturesymbol code. I am seeing something odd in my results though. I have point data symbolized in different colors, for all but one of the colors the simple marker symbol appears on top of the point. For all my points which are grey, its like I am only seeing the outline of the simple marker symbol and can still see my colored grey point in it. I attached a screen shot and put my code lines below. As a not, I switched my style to circle instead of square, but the same thing happens with the square. Any ideas on what might be happening here?

<simplemarkersymbol style="circle" size="12" color="0x00ffff" alpha="0.5" xoffset="0" yoffset="0" angle="0">
      <outline style="solid" color="0x00ffff" alpha="1" width="1"/>
     </simplemarkersymbol>
     <!--<picturemarkersymbol url="assets/images/tick.png" height="16" width="16" xoffset="0" yoffset="0" />-->

2011-02-07_gpd.png

RobertScheitlin__GISP

Nestor,

Are you copying the whole eSearch folder? The addition of an assets folder was made in between version 2.2.3 and 2.2.7.

The 2124 error means: #2124: Loaded file is an unknown type.

NestorNavarro

I'm using the uncompiled version.
All I did was replace the old folder with the new version folder, recompile, clear the cache and that was it, started getting the error. Then I tried it with my xml including your changes such as the enable export true elements and I get the same error. What is that error anyway?

I will replace it with the old version again (2.2.3) and see if it works normally again.

Nestor.

RobertScheitlin__GISP

Nestor,

I just downloaded it and added the uncompiled src to a clean flex viewer 2.2 and I got no errors...
Are you using the compiled version? If so which one?

NestorNavarro

All,

New version is available.

Version 2.2.7 - 02/04/2011
* Added the ability to resize the floating data grid.
* Fixed an issue with disable/enable export option in the data grid on a layer by layer basis.
* Fixed issue with symbology alpha and color being set to 0 or 0x000000.
* Added ability to define a simple marker symbol for point or the current picture marker symbol.

Good Morning Robert,

Hope all is well.

I replaced version 2.2.3 with 2.2.7 and run it out of the box, with your xml file and no other changes, just to test prior to using my xml file. When I fire off the widget, I get an Error # 2124. I can click OK and the widget works fine otherwise. When I use my xml file I get the same error including no popup when I put the hand cursor over a selected feature.

Any suggestions?

Thanks for the great enhancements ...

Nestor.

RobertScheitlin__GISP

All,

New version is available.

Version 2.2.7 - 02/04/2011
* Added the ability to resize the floating data grid.
* Fixed an issue with disable/enable export option in the data grid on a layer by layer basis.
* Fixed issue with symbology alpha and color being set to 0 or 0x000000.
* Added ability to define a simple marker symbol for point or the current picture marker symbol.

LisaArnold

Lisa,

Currently the only marker symbol that is supported is the picturemarkersymbol. I will look at changing this in the next release.

Thanks for the note Robert. I have started a new thread to try and trouble shoot some of my searching issues. If you get a chance I hope you can check it out. http://forums.arcgis.com/threads/22773-Enhanced-search-widget-sql-queries?p=74539#post74539

Lisa Arnold

PaulTHEDUDELang

Just got your latest, thanks for all you do!

RobertScheitlin__GISP

Paul,

As new versions are released old versions are no longer supported. I can not attempt to maintain so many versions as the current release is 2.2.6. In the 2.2.6 version in the SearchWidget.xml there is the symbols element setting its alpha to 0 should do it:

<symbols>
     <simplefillsymbol color="0xff0000" alpha="0.00001">
      <outline color="0xff0000" alpha="0.8" width="2"/>
     </simplefillsymbol>

PaulTHEDUDELang

I would like to change the selected results to outline only, not red symbol area.
Can someone point me to the correct section?
Using SearchWidget.mxml
Version 2.1.5 * Fixed Issue with graphical included in comments!!

RobertScheitlin__GISP

Lisa,

Currently the only marker symbol that is supported is the picturemarkersymbol. I will look at changing this in the next release.

LisaArnold

Hi Robert,

Is there a way to highlight point data search results just by coloring the point a different color instead of placing a graphic on top of it? I would like the found points to highlight in a similar fashion to the way the polygons are highlighted in this widget - ie the way they are highlighted in ArcMap when points are selected.

In the code below I have changed the color of my polygon fill & outline. I tried commenting out the picturemarkersymbol line which resulted in my points having the binoculars on them again instead of the .png I directed it to. But is there anything I can change here to get the result I'm looking for?

<simplefillsymbol color="0x00ffff" alpha="0.5">
      <outline color="0x00ffff" alpha="0.8" width="2"/>
     </simplefillsymbol>
     <picturemarkersymbol url="assets/images/tick.png" height="16" width="16" xoffset="0" yoffset="0" />
  <simplelinesymbol color="0x00ffff" alpha="0.8" width="2"/>

Thanks for your help.

Lisa Arnold
University of New Mexico

EricVenden

Thank you very much Robert.

Eric V
Gurnee, IL

RobertScheitlin__GISP

All,

There is a new version of the widget out there now 2.2.6

* Added the ability to disable/enable export option in the data grid on a layer by layer basis.
* Fixed issue with sorting data grid columns when layer has a join
* Fixed issue with tooltips hanging for coded value domain combobox when using mouse wheel.
* Changed packaging of widget so that assets are included in widget folder for
easier moving of widget to new versions of the FlexViewer.

EricVenden

Thanks for your response Robert and for looking at this.
I appreciate it.

Eric V
Gurnee, IL

RobertScheitlin__GISP

Eric,

I have been able to confirm that there is an issue with sorting fields in the datagrid that have joined data. I don't currently have a resolution. If I figure out a fix it will be in a future release and will be documented that this bug is fixed.

RobertScheitlin__GISP

Eric,

I will have to do some test environment setup to test the possible join issue. I don't actually use this widget as is the case with most widgets I create. I spend time creating testing and fixing reported bug when I get time but, actually don't use most of them on my site. So I depend on people like you to tell me their unique use of the widgets and issues they find. I will attempt to dig into the possible join issue next week.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

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