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.

[NormBushor]

Hi All,

I am using the advanced search widget and am getting incorrect results when buffering a feature (parcel), if I buffer at 100 feet the buffer graphic drawn is +-70ft, if I change the units to meters I get the same result, it looks like about 70% of my orginal buffer distance.  If I enable graphics and buffer a graphic the buffer distance is fine.  I am using Esearch 3.5 with Server 10.1 sp1.  All my data is published in WGS 84.

Thanks!
norm

[AaronKreag]

Julia-

If I understand you correctly....

Its my impression that what you see in the sample/example is exactly that, a sample.  If I remember correctly, those are very much like placeholders in the widget.  You need to add your own data in the main config and then edit the esearch widget config with your respective data.  If that is not the problem, maybe those sample data sets have changed or been edited.

Aaron

[JuliaGalindo]

Hi Aaron,

Thank you for your reply, yes, I understand what you said, I have to customize the widget. Before doing so, I want to make sure I have the correct widget, because, I need some functionality present in the last widget. I assume, maybe it is a mistake, that, what is available for download is exactly what is present in the online example.
You answer made me go back and review in more detail the Esearch widget download, so I found out that the code I am missing is commented in the eSearchWidget.xml and it can�??t be seen from the inside the application builder (via de widget settings). I will continue to look in that direction�?� to see how to get it work.

Thank again,

Julia-

If I understand you correctly....

Its my impression that what you see in the sample/example is exactly that, a sample.  If I remember correctly, those are very much like placeholders in the widget.  You need to add your own data in the main config and then edit the esearch widget config with your respective data.  If that is not the problem, maybe those sample data sets have changed or been edited.

Aaron

[RobertScheitlin__GISP]

Norm,

   Try setting the spatialreference in the eSearchWidget.xml to this:

<spatialreference>102003</spatialreference>

[RobertScheitlin__GISP]

Julia,

  As you figured out the Calhoun Parcels layer is still in the eSearchWidget.xml Just with a false url as I am not going to publish my map service for every one to play with. Sorry for the confusion.

[NormBushor]

Robert,
You hit the bullseye again.  Thank you! 
I'll research that spatial reference to see why the 102100 wasn't working and this one does.
Your hard work on these widgets is highly appreciated!!!
Regards,
norm

[JuliaGalindo]

Julia,

  As you figured out the Calhoun Parcels layer is still in the eSearchWidget.xml Just with a false url as I am not going to publish my map service for every one to play with. Sorry for the confusion.

Thank you Robert!

[RobertScheitlin__GISP]

All,

   New version available:

Version 3.6.2 - 2/20/2014
* Fix issue with disableinpopup in datagrids.
* Fix issue with UNC links that have icons specified not working in my popups.
* Fix issue with union geoms function and some multi ring polygons.
  Special thanks to Leonardo Araújo for the code contribution.
* Added more configurable messages for widget internationalization.
* You can now configure the buffer graphic to remain visible after the search.

[KummerLaszlo]

Hi Robert,

We at our company are very sorry that QueryBuilder is no longer developed. We used it a lot.
You wrote that the use of eSearch is recommended instead, but I can't find a way to configure
it to work like QueryBuilder. My users want to create their own custom queries and they can not
do that in eSearch. Is there a way to use eSearch like QueryBuilder or could you recommend a widget
that works similar to QueryBuilder and is actively developed?
Thank you in advance.

[RobertScheitlin__GISP]

Kummer,

   eSearch is not like QueryBuilder in the fact that, like you said it does not allow the user to build a query using a GUI. The eSearch Widget does allow for open SQL statement where the user Manually types the whole where clause, including field names and operators. There is not another widget out there that is actively supported that has the features of QueryBuilder widget. The market is very small for a widget that does what QueryBuilder does, so I have not plans for adding this sort of capabilities. The focus of RIA applications is for the user to have little, to no knowledge of GIS, so a widget that is developed for GIS savvy people is not the greatest fit for RIA development.