Geocoding in GlobalSearch is a good idea?
Looking through the Administrator and Developer Guide, it appears that finding an address (aside from using an explicit workflow), the only way to search for an address is through the Global Search.
Maybe I'm in the minority here, but I don't personally feel like this is the best idea. Here's why...
I know that many applications now, strive to mimic Google in having a single textbox for finding anything you want. This works in most cases, but even Google realizes that it's not the best example of searching for specific content, ala Images, maps, web pages, etc. When you search for say, an address... You have the option for clicking the maps tab. If you want images, you can click the images tab, if you want sites, you can choose to look only in sites. I don't particularly care to have the addresses for geocoding go into my global search textbox.
I find it's a better experience if users have a button or a space where they know they can search for an address... IE a button, that brings up a place for them to enter their address. Yes, I could still have this and bring up the global search, but they're going to get layers that match those addresses if the layers are configured as such.
It seems like there should still be a forwardGeocode command. Not sure why this was removed?
0
-
Hi Erik,
If you do not like have the Global Search do the geocoding, then your only other option would be to create a workflow.
You can create a workflow that has a display form where the user can enter in an address. Then it would submit that directly to the geocoder. This way, you can control what gets returned. If you want an example of how to build something like this, please take a look at our code gallery example here:
https://support.geocortex.com/essentialsGSCCodeGallery?sub-nav=codegall&main-nav=essentials&#!/feedtype=SINGLE_ARTICLE_SEARCH_RESULT&id=kA4600000004EXX
I hope this helps
Carmen0
Please sign in to leave a comment.
Comments
1 comment