Zoom To Off-Set in eSearch widget

[deleted-user-iTiq4MAkIxq6]

Please forgive me if I maul the appropriate terminology here, but we'd like to do something in the eSearch widget for Flex Viewer, and I'm curious if we can make it do something a little different.

We'd like to add code so that the scale that would be called by zooming to the extent of the selected geometry gets off-set by a pre-set factor. The end result would be that the scale returned (and ultimately zoomed to by the widget) would not fill the screen, but stand off a bit to give the selected parcel greater context. So we don't want the zoom-to-max-extent effect, and we're dealing with parcels of such variety in size that setting a hard RF scale (1:X) won't work either...the smaller sized parcels are tiny and the large ones still fill the screen.

Has anyone tried or accomplished this? Or, failing that, is there a source of more in-depth documentation on this widget than the PDF that comes with it? That's a great resource, but we seem to be attempting a configuration that exceeds its coverage.

Oh, and by the way, we are using version 2.5.1.4f of the widget.

Thanks!

Eric

[RobertScheitlin__GISP · Accepted solution]

Eric,

   What you are wanting is not in the norm for one of my existing configurable options so no, there is not going to be any more in depth documentation. You would have to modify the code to suit your specific needs. You need to look at the zoomAll function and the clickSearchResult functions.

Don't forget to click the Mark as answer check on this post and to click the top arrow (promote) as shown below:

[deleted-user-iTiq4MAkIxq6]

Robert,

Thanks, that's helpful insight. We love the eSearch tool, but this question arose when one of the assessors with whom we work asked if it was possible. We were casting about without much success so I figured I'd go to the source. 😮

Oh, and one other thing, it seems that there are three different Zoom options, and each works slightly differently. When you click on an individually returned record it zooms to one scale, when you hit the Zoom To command in that box it zooms to another, and when you use the Zoom To command in the pop-up at the select record it seems to zoom to a slightly different scale. And yet, as we looked through the config file, we only saw one control for the zoom. And word of advice in trying to get all three of those zoom options to behave the same way?

Thanks!!!

Eric

[RobertScheitlin__GISP]

Eric,

   I will get them all on the same sheet of music in the next version and look at adding a configurable way to define a zoom offset while I am at it.

[RobertScheitlin__GISP]

Eric,

   Try version 2.5.1.6.

[deleted-user-iTiq4MAkIxq6]

Robert,

Thanks! We're excited with the changes in 2.5.1.6, and with what we can now make the <zoomscale> tag do.

Here's what we're seeing on our end, however, and I want to bounce something by you...press our luck, so to speak.

The zoom function when selecting a record from the returned results now seems to follow the zoomscale percentage to a tee, as does the "Zoom To" button on the mouse-over call-out window for the selected record. The "Zoom" button atop the results window, however, still seems to revert back to a default zoomscale based on returned geometry.

This would actually not be a big deal if it were slightly altered so that selecting a record from the results window and hitting the "Zoom" button observed the zoomscale zoompercent setting while hitting the "Zoom To" button zoomed in to the returned geometry. From an intuitive work-flow perspective I believe having the interactive results and the "Zoom" button returning the zoompercentage makes sense, working together so to speak. Then if one wanted to zero right in on a selected feature they could use the "Zoom To" button on the call-out window associated with it.

Like you, we have to consider the "Mee-Maw and Pee-Paw Factor" when putting these things together, in a sense pandering to a lower common denominator of public tech-sophistication than we all might like. So if there's a way we can make that switch in our configuration, let me know...although I suspect it's probably something on your end (thus my "press out luck" comment earlier).

Whatever happens, thanks so much for developing this wonderful tool, but especially for being so receptive and helpful!!!

Eric

[RobertScheitlin__GISP]

Eric,

   I thought I had all that working the same way so I have a couple of questions for you?

1. What geom type are you using?


2. Do you have tiled (cached) basemaps?

[deleted-user-iTiq4MAkIxq6]

Robert,

We have it hitting a polygon layer (local parcels).

And no, we are not using cached background layers yet. We plan to, but we we're going to cache once we're set on all data and functionality. If we need to go ahead and cache to make things work, however, that's no problem. Just say the word.

Thanks!!!

Eric

[RobertScheitlin__GISP]

Eric,

   I am getting that fixed in the next release.

[deleted-user-iTiq4MAkIxq6]

Robert,

Can't thank you enough for being so responsive...it's been amazing!

Eric