Destructor.

Creates an iterator object to iterate the matching landmarks or landmark categories.

This function can also be called during a search in order to read the matches encountered so far. Note that the iterator will not iterate any new matches. If new matches are found, a new iterator must be created.

If a sort preference was specified when the search was started, the landmarks/categories will be sorted when the search is complete but the items are not necessarily sorted if this function is called during a search.

Note: If the client has set display data and resets the display data during a search, the sort order in the iterator might be incorrect.

The client takes ownership of the returned iterator object.

Note that the iterator iterates matches in CPosLandmarkSearch . It cannot be used after the search object has been deleted. Make sure to delete the iterator first.

Retrieves the maximum number of search matches limit.

By default the maximum number of matches is unlimited.

Two-phased constructor.

The client takes ownership of the returned search object.

Returns the number of matches so far in the search.

This function can also be called during a search operation.

Display data can be used as an alternative way to get result from a database search. Landmarks or categories are added to the display data collection during a search depending on the search type.

This function may replace the combination of using MatchIteratorL and reading landmark or category data. Result data is read already during the search and no duplicate access to database is needed.

The display data object will be reset each time a new search is started. No items during the search are removed from the collection. New found matches can be added every time next search step is completed, see CPosLmDisplayData::NewItemIndex .

Note: The database index of displayable data items in CPosLmDisplayData will be set to 0 as it has no meaning in a single database search.

The client owns the display data object. If the client deletes it during a search, this may lead to unexpected errors. The client must call UnsetDisplayData before it deletes the display data object.

Note: If the client resets the display data during a search, the sort order in the iterator might become incorrect.

Sets the maximum number of search matches limit.

If the limit is set, the search operation will stop when this limit is reached.

By default the maximum number of matches is unlimited.

If a new value for maximum number of matches is set when a search is ongoing, it will not affect the current search. The new maximum will be utilized in the next search.

Starts a search for landmark categories.

The criterion which defines whether a landmark category is a match or not is passed as input to this function.

The client takes ownership of the returned operation object.

This function requires ReadUserData capability.

Starts a search for landmarks.

The client takes ownership of the returned operation object.

This function requires ReadUserData capability.

Starts a search for landmarks.

This overload of the StartLandmarkSearchL function lets the client define the sort order for the search matches. Only sorting by landmark name is supported.

The client takes ownership of the returned operation object.

This function requires ReadUserData capability.

Unsets display data. No further data will be added to the display data that was set with SetDisplayData .