Enabling Instant Search for a Map Service
How do you go about enabling Instant Search for a map service within an existing viewer?
We are currently on Essentials 4 & Viewers have updated all sites to the latest versions.
I keep getting the message ' The Instant Search feature is not currently enabled' when clicking on the Instant Search tab.
Any suggestions?
-
You have to download and install the Instant Search module on your server for it to be enabled. The module was only released recently.
http://blog.geocortex.com/2014/03/31/instant-search-is-here/
0 -
Thanks for the reply Mark! Got it downloaded and installed on our servers now & have already created a few indexes.
Have you utilized the instant search function yet? I have got it working on a few of our map services within some our sites, but have not been able to replicate the drop pins appearing on map from the records returned from the search. (this was done on the instant search video posted earlier this month.
Let me know if you have any suggestions.
0 -
I have done some testing on some really basic mapservices and it works ok. My real mapservices have 200+ layers so I dont think Instant search will be feasable unless I can target specific layers out of a mapservice to include in the index.
The push pins are are avaialable with the latest silverlight and html viewers. The latest viewers were realeased with instant search. You will have to dowload the latest viewer and use it for th epushpins.
0 -
Mark,
How come you don't think the Instant Search will work for you services? I also have 100s of layers, and wanted to use Instant Search... Seems to me the only issues with that many layers would be the index storage size and the time to create the index... Am I missing something?
Mike Hargreaves
0 -
Its not that it wont work, it is how long it takes to create. Also how often the index is rebuilt. I need the indexes built every night as the data changes daily.
Dont get me wrong, I think instant search is really cool and the end users will love it. For satic data that does not change much, it would be great, and number of layers would not really matter.
This is what would make instant search better for me:
- Ability to schedule when the index is built, and have it built fast.
- Choose which layers in a map service to include in instant search.
- Be able to search on related data, either datlink search tables or relationships in map service
0 -
Maybe I'm just not seeing it, but I am unable to figure out how to enable push pins anywhere (even with the latest viewer download/update).
Any suggestions where this functionality would be enabled from?
0 -
Mark,
It sounds like most of that is coming. I was thinking you already had some control as to how often it was created, but I could be wrong. You say you have 200 layers, but how many features? Are you doing it for a City, or a County, or...? How long did it take to create your index? I agree that individual layer update would be useful, and the ability to schedule at night, using most of the server power - much better to have a nightly update.
Mike
0 -
Hi Mike,
I cant see anywhere to schedule the frequency of the build. The only information i have is from the video recording http://support.geocortex.com/introducing-instant-search at the 8 min mark it says "Indexes are updated weekly".
The data is for county size with approx 70,000 features for a parcel layer. Point layers can have 200,000 features. So i wouldnt think it we be overly huge, just a lot of layers(200+). I have kicked off a build on my largest service, it has been running for 10 hours and instant search window says 22% complete file size of Data folder is 5GB. This is on a low spec test server so results could be misleading. I will just let this keep running and see what happens. (previously I had cancelled this build). Testing on your own server with your own data will give you a better indication.
0 -
Hi Alex, I have not upgraded the viewers so have not tested the pushpin functionality. The pushpins are not visible for me on v2.0 of silverlight viewer. I think you need v2.1
0 -
Would add that we also need control over the time update schedule. We currently update our data every 2 hours. The dataset isn't huge and our servers are quite fast, so would need control here.
0 -
It took me more than a few hours to create an index on one of our mapping applications lots of features between the >45K address points, 38K parcels and the other layers including hydro and soils.
I wasn't smart about it I just pushed the button and let it rip. I paused it after 2 hours since it seemed to be stuck on 22% turned it back on again when I came in the morning and
it went much faster after that. I was warned that it would take some time to run the first time.
This was after tweaking the memory in the config file. Works realy well minus the way I have it configured. The map markers pop up just fine for me. You have to enable them in the backend to get them to show up and you can change the color by finding the icon and using photoshop if you aren't into red.
0 -
Hi,
I'm also getting "The Instant Search feature is not currently enabled." in Essentials 4.2 Is this still a separate module/install?
Thanks
0 -
Our users would like to search for a set of asset IDs (across many layers), using GlobalSearch and -say- type each serial number with a coma-delimited character/
Out of curiosity, is there a way to invoke Instant Search or ElasticSearch from a Workflow? (elasticsearch.Net.dll)
0
Please sign in to leave a comment.
Comments
13 comments