Data Options

The Data tab allows you to specify which databases to use in geocoding. Databases contain the address and geocode data necessary to determine the geocode for a given address. There are two kinds of databases: standard databases and custom databases. Standard databases are those supplied by Precisely and based on address and geocoding data from postal authorities and suppliers of geographical data. Custom databases are databases you create to enhance or augment standard databases for your particular needs.

For Australian geocoding, to achieve the best geocoding spatial precision use the G-NAF database. This provides point-level geocoding that places points within the land parcel boundary for a given address. The G-NAF database requires an additional license. Contact your sales representative for more information.

The following table lists the options available for specifying which databases to use and the search order of databases.

Table 1. Default Data Options for Vietnam
optionName Option Name Parameter	Description
Database Database Option.Database	Specifies the database to be used for geocoding. Only databases that have been defined in the Management Console are available.
Database preference DatabasePreference Option.DatabasePreference	Specifies which geocoding databases to use. One of the following: Prefer custom database PreferCustom Use both standard databases and custom databases, but give preference to candidates from custom databases. Use this option if you feel your custom database is superior to the standard database. Prefer standard database PreferStandard Use both standard databases and custom databases, but give preference to candidates from standard databases. Use custom databases only CustomOnly Use only custom databases. Ignore standard databases. Use standard databases only StandardOnly Use only standard databases. Ignore custom databases. Use both custom and standard databases Both Use both standard databases and custom databases. In cases where candidates are returned from both, the standard database is preferred. Default. Note: This option is not available for Great Britain (GBR) because the GBR geocoder does not support custom databases. The results from a custom database have a "U" at the end of the result code. Results from an address database have an "A" at the end of the match score. For example: S5HPNTSCZA is a match score that comes from an address database, while S5HPNTSCZU comes from a custom database. For more information, see Result Codes for International Geocoding.
Override the default database search list	Specifies whether to use the database search list specified in the Management Console. If you choose to override the default database search list you may change the search order of the databases in the Database search list field. You may also remove databases from the search list. If you override the default database search list, changes to the database resources will not be reflected in the database search list, which may cause geocoding to fail. However, if you do not override the default database search order, any changes to the database resources will be automatically reflected by the geocoder.
Database search list DatabaseSearchOrder Option.DatabaseSearchOrder	The name of one or more database resources to use in the search process. Use the database name specified in the Management Console. You can specify multiple database resources. (Not supported for the United Kingdom.) If you specify more than one database, list them in order of preference. The order of the databases has an effect when there are close match candidates from different databases. The close matches that are returned come from the database that is first in the search list. Close matches from lower ranked databases are demoted to non-close matches. You can also use the order of the databases to perform fallback processing if you have an both an address point database and a street-level database installed for the country. List the address point database first and the street database second. If the address cannot be geocoded to the address point level, the geocoder will attempt to geocode it to the street level.