Intuitive configuration

You can configure how your Intuitive suggestions are formatted.

Format:

IntuitiveSearchMaxPicklist={Maximum picklist size}

Default:

10

Purpose:

This defines the maximum picklist size that can be returned by the Intuitive Search engine, however, this can be overridden by the Threshold setting. There is no maximum value for this setting.

If the Intuitive Search engine returns more results than the set value, then the lowest-scoring addresses will be removed from the flattened picklist. In the instance of equally scoring addresses being returned, then the picklist will be truncated to the value defined.

Example:

IntuitiveSearchMaxPicklist=100

This setting applies to Australia and New Zealand data only.

Format:

[identifier]EnableEnhancedLayout={String}

Default:

Yes

Purpose:

This allows you to prepend unmatched leading information to address lines

Example:

AUSEnableEnhancedLayout=Yes

This keyword applies to Australia, New Zealand and FRX data only.

Format:

MatchToInBetweenRangeNumber={boolean}

Default:

True

Purpose:

This keyword is used to determine whether an input will match to a range of addresses - for example, whether 17 High Street will match to 13-26 High Street, given that the rest of the address is the same.

Example:

MatchToInBetweenRangeNumber=true

This tells Pro API that it should match an input that is found in a premises range.

The following settings relate to intuitive picklist configuration. They will work in conjunction with and be applied per layout:

Format:

IntuitiveAddressLineCount={Integer}

Purpose:

Defines the number of lines in the Intuitive picklist. To enable the setting, the value has to be set to 1. The address elements are specified by IntuitiveAddressLine1

Example:

IntuitiveAddressLineCount=1

Format:

IntuitiveAddressLine1=W,

Purpose:

Specifies the address elements that will appear in the Intuitive picklist.

W signifies that the number that follows is the maximum width of the line in characters.

is a comma separated list of dataset-specific element codes. By specifying an element code, you force Pro API to place that element on that line (if the element exists in the matched address).

Example:

IntuitiveAddressLine1=W160,U21,...,C11

Format:

IntuitiveUseExtendedRetention={Yes/No}

Purpose:

Allows you to display unmatched input text in Intuitive search results.

Example:

IntuitiveUseExtendedRetention=Yes

Format:

IntuitiveElementSeparator={Default separator} {Element code {separator}}

Purpose:

Specifies which address elements should be separated by additional characters in the Intuitive picklist.

You can specify the element separator for individual elements using {separator}.

The format is: {prefix separator^suffix separator} where ^ is the value for that element.

Note that {separator} will override {Default separator} for the specified elements.

Example:

IntuitiveElementSeparator={ } P11{, ^} L31{, ^} L11{, ^ } C11{, ^-}

Format:

{Country 3 letter ISO code}VirtualPicklist={Yes/No}

Default:

False

Purpose:

This option activates for Intuitive engine creation of virtual picklist elements based on dataplus file.

The Virtual Picklist Feature is implemented in Pro API 7.73 and shall work only in the New Zealand DataFusion set with the NZLPHY dataplus file. When enabled, the feature shall return Physical Addresses based on the Rural Delivery address search.

Example:

NZDVirtualPicklist=yes