@ferrybig/cgeodata-reader
    Preparing search index...

    Parameters of a search index (Appendix B.11); every one has a recommended default (DEFAULT_SEARCH_INDEX_OPTIONS).

    interface SearchIndexOptions {
        hashExp?: number;
        topCount?: number;
        topBlockExp?: number;
        areaTieBreak?: boolean | "auto";
    }
    Index
    hashExp?: number

    2^hashExp shared lists for non-Latin trigrams (1-24).

    topCount?: number

    Places per short-query entry; 0 leaves the table out (0-255).

    topBlockExp?: number

    2^topBlockExp entries per short-query table block (0-24).

    areaTieBreak?: boolean | "auto"

    Which order to build the short-query table in, as SearchOptions.areaTieBreak would rank a search: "auto" by area when the reader has a locate index (CGeoDataReader.placeAreas()), true by area (rejecting without one), false plainly. A reader only answers from the table when it ranks the same way, so build it the way the index will be used: with "auto", after the locate index.