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.

[RichardSterling]

OK, so i think explaining it in the forum clarified in my mind that it must be a field name issue. A little mystifying as I was using the same field names in the expressions and values section as in the fields section.

I remade the table with slightly amended field names and the widget works as desired. So I am happy and thank you for your response.

[TimothyGoddard]

Robert,

Its been a while since i last talked with you.  I've got an application that im migrating over from flex 2.4 and your earlier esearch widget.  I'm working on getting it to work the way i want while having to learn the new coding.  I'm under a bit of a time crunch and was hoping you could point out what i need to fix.

I've attached the following xml i'm working with.  my problems are:

in my layers that have attributes that i would like to be able to have hyperlinks to my coding is not working example "PHOTOLINKS" field should be a hyperlink.  I've been reading the pdf about hyperlinks and such and am not getting it. When i do a graphical search the fields show the fully hyperlink but it does not link and it does not show the alias i tried creating.

Also my text search syntax and coding is wrong as well.  I would like then to be able to do a word search in the hyperlink field for any word in the hyperlink.

If you can help me figure this out then i think i can duplicate this in my other layers.

Thank you in advance for your help.

Tim Goddard

[RobertScheitlin__GISP]

Tim,

   Sure your issue with the link is that you now have to have the link field name in a CDATA block. And the issue with your expression is you have the wildcard part of % in your expression but you are using the equal sign and not the LIKE operator like you should be using.

[TonySturgill]

Hey Robert,  I cannot figure out what I am doing wrong with the eSearch widget.   When creating buffers they seem about 2/3 the size they should be and when you do a search entities the search selects points that are outside of the buffer (like the shown buffer is to small). I saw the other post and my spatialreference seems to be set correctly:

   </printdatagrid>
    <keepgraphicalsearchenabled>true</keepgraphicalsearchenabled>
    <autozoomtoresults>true</autozoomtoresults>
    <popupsdisabled>false</popupsdisabled>
    <enabledatagridinteractionwithwidget>true</enabledatagridinteractionwithwidget>
    <toleranceforpointgraphicalselection>6</toleranceforpointgraphicalselection>
    <tolerancebydefault>false</tolerancebydefault>
    <spatialreference>102100</spatialreference>
    <zoomscale>2400</zoomscale>
    <csvseparator>,</csvseparator>

Where else can I look to solve the problem.   The scale bar is showing the right distance.

[RobertScheitlin__GISP]

Tony,


  When I use the

<spatialreference>102003</spatialreference>

as comes in the eSearchWidget.xml by default it works great for me as far as getting a 3 mile buffer that measures 3 miles using the Draw or eDraw widget. Each projection has some distortion either shape, area, length so the WKID of 102003 is probably best for you unless you want to use the 1983 UTM WKID for your area.

[TonySturgill]

Thanks Robert that worked.   All my services say they use spatial reference 102100 (which is WGS 1984 Web Mercator).   Just curious why does 102003 work?

[RobertScheitlin__GISP]

Tony,

   Because 102003 is "USA Contiguous Albers Equal Area Conic" whch means that it will have less distortion in shape and area in the US than using a world projection like WebMercator.

[TonySturgill]

Thanks Robert!

[jaysistoza]

Hello Robert,
Thanks to your new eSearch widget.  It allows us to easily navigate around our new flex app.  But there are certain features we'd like to enable or enhance if possible.  The two features particularly are:  The ability to EDIT and add an additional halo around the selected shape.
I would really appreciate if you could please provide some guidance in enabling those features.
Thanks in advance,
Jay

[J_B__K_]

Hi Robert & all !

At first - you are doing such a great work for the community, your widgets, your approach,... I appreciate it!

To my problem - when using graphical search (choose the exact tool, let´s say polygon, then "draw" a polygon), the tool (drawing polygon) stay active after completing search. Is there a way how to disable this? How to turn cursor "back to pan" automatically after drawing a polygon?

(v3.5.4)

Thank you!