oneSearch provides a powerful and fast all-in-one search tool for Map Client users. oneSearch enables searching across a map with one or more map layers and JDBC Search Flow Queries and returns features and layers based on a single text entry search. oneSearch is set to default to the top of the Map Client Search Panel Search drop-down list.

To make oneSearch Queries really fast, they use an Index generated from a map layer or a JDBC connection, which is stored in the solr directory. oneSearch Queries are automatically presented at the top of the Search Panel drop-down list unless a different default query is chosen. Default queries are set using Roles, see here to choose a default Query for a Map.

The oneSearch index stores map layer fields containing:


Number (but not if field name is OBJECTID)




The fields not Indexed by oneSearch are listed here:






BINARY or BLOB types


INFORMATION: Dekho oneSearch Queries leverage the Apache Solr search platform. To read more about this open source enterprise search platform see here.

Step 01> Choose the Map Service Layer to use in the search

Features will be displayed for this service.

Step 02> Select either the Search Layer, or, a Related Table to the Search Layer.

When the Search Layer is selected, Dekho lists the Fields contained in this Layer.

Check the Fields to use as part of the oneSearch. These fields are used to display the results in the Map Client.

[OPTIONAL] When a Related Table is used, select the Data Source and then specify how the Table relates to the Search Layer. That is, what fields will be used to make a join between the data table and the map service layer.

Click the link on the right to add the Linking Fields syntax into the box.

Step 03> Use the where clause builder to create the where clause and then Click OK to add the Where Clause to the Query.

A where clause can be set to minimise the indexing time or reduce the scope of the search.

Step 04> Use the optional Index update Scheduler to run the indexing process on a regular basis. Indexing can be run manually.

Step 05> Click Save to save the oneSearch Query. This does not build the Index though.

Build the oneSearch Index