Functionality of undocumented NamedSearchOptions

[metin.kahraman]

Hello everybody,

I am looking for ways beyond SEARCH_FUZZY to improve the "hit rate" of xLocate, when adress data is "imperfect".

It looks like native-alternative.xml has a bunch of NamedSearchOptions which sound like they could have an impact.

The following are of particular interest:

1. FieldWeight.*
2. FrequencyFiltering
3. PreferFirstWordMatches
4. PreferStreetOnCityStreetConflicts
5. Score.MaxDeltaToBest
6. Score.MinFieldScore
7. Weight.MinSubwordWeight
8. Weight.MissingWordFactor
9. Weight.Threshold

However they are usually undocumented. Does anybody have any experience with these?
What do they affect? Which ones help most?

Regards

Metin

[Joost]

These options are undocumented by design. To properly understand all these options it requires a more intimate knowledge of the algorithm then we are willing to share. For details we will share please see http://xserver.ptvgroup.com/forum/viewt ... f=11&t=665 . Also keep the comment bocajo made in that thread in mind: if you have issues that may require these parameters we prefer you contact PTV support to work out if we can improve the setting for your use case.

Also one thing to keep in mind: our default settings are in place to give you the best result possible back. I have very rarely seen cases where we needed to change these settings.

[Bernd Welter]

Little side note:
if you need to improve result quality contact consulting, not support.
At least in Germany consulting takes care of knowhow transfer while support deals with errors...