Geocoding Guide for Finland - API - REST - SOAP

Transcription

Spectrum Technology Platform
Version 11.0
Table of Contents
1 - Geocode Address Global
Adding an Enterprise Geocoding Module Database
Resource for Great Britain
4
Resource for Australia
5
Adding an Enterprise Geocoding Module Global
Database Resource
7
2 - Input
Input Fields
Address Input Guidelines
Single Line Input
Street Intersection Input
11
41
94
100
3 - Geocode Address Global
Options
Geocoding Options
Matching Options
Data Options
106
111
129
4 - Output
Address Output
Geocode Output
Country-Specific Output
Result Codes
Result Codes for International Geocoding
133
160
160
171
174
5 - Reverse Geocode Address
Global
Input
Options
Output
182
183
188
1 - Geocode Address
Global
Geocode Address Global provides street-level geocoding for many
countries. It can also determine city or locality centroids, as well as postal
code centroids. Geocode Address Global handles street addresses in the
native language and format. For example, a typical French formatted
address might have a street name of Rue des Remparts. A typical German
formatted address could have a street name Bahnhofstrasse.
Note: Geocode Address Global does not support U.S. or U.K. addresses.
To geocode U.S. addresses, use Geocode US Address. To geocode
U.K. addresses, use Geocode Address GBR.
The countries available to you depends on which country databases you
have installed. For example, if you have databases for Canada, Italy, and
Australia installed, Geocode Address Global would be able to geocode
addresses in these countries in a single stage. Before you can work with
Geocode Address Global, you must define a global database resource
containing a database for one or more countries. Once you create the
database resource, Geocode Address Global will become available.
Geocode Address Global is an optional component of the Enterprise
Geocoding Module.
In this section
Adding an Enterprise Geocoding Module Database Resource for Great
Britain
4
Adding an Enterprise Geocoding Module Database Resource for
Australia
5
Adding an Enterprise Geocoding Module Global Database Resource
7
Geocode Address Global
Resource for Great Britain
Whenever you install a new database resource or modify an existing database resource you must
define it in the Management Console in order for it to become available on your system. This
procedure describes how to add or modify a database resource for the Enterprise Geocoding Module
for Great Britain.
To create a Geocode Address GBR database resource:
1. If you haven't already done so, install the dataset files on your system. For instructions on installing
databases, see the Spectrum™ Technology Platform Installation Guide.
2. In Management Console, under Resources, choose Spectrum Databases.
3. Click the Add button
click the Edit button
to create a new database or select an existing database resource then
to change it. You can also create a new database resource by copying
an existing one, by clicking the Copy button
.
4. If you are creating a new database, enter a name for the database resource in the Name field.
The name can be anything you choose. If you are creating a new database by copying an existing
one, rename the default name as needed. You cannot modify the name of an existing database
resource, because any services or jobs that reference the database resource by its original name
would fail.
5. In the Pool size field, specify the maximum number of concurrent requests you want this database
to handle.
The optimal pool size varies by module. You will generally see the best results by setting the
pool size between one-half to twice the number of CPUs on the server, with the optimal pool size
for most modules being the same as the number of CPUs. For example, if your server has four
CPUs you may want to experiment with a pool size between 2 (one-half the number of CPUs)
and 8 (twice the number of CPUs) with the optimal size possibly being 4 (the number of CPUs).
When modifying the pool size you must also consider the number of runtime instances specified
in the dataflow for the stages accessing the database. Consider for example a dataflow that has
a Geocode US Address stage that is configured to use one runtime instance. If you set the pool
size for the US geocoding database to four, you will not see a performance improvement because
there would be only one runtime instance and therefore there would only be one request at a
time to the database. However, if you were to increase the number of runtime instances of
Geocode US Address to four, you might then see an improvement in performance since there
would be four instances of Geocode US Address accessing the database simultaneously, therefore
using the full pool.
Tip: You should conduct performance tests with various settings to identify the optimal pool
size and runtime instance settings for your environment.
Spectrum Technology Platform 11.0
4
6. In the Module field, select International Geocode Great Britain.
7. In the Type field, select Geocode Address GBR.
to install a new dataset. In the Name field, specify a name for the dataset.
In the Path field specify the folder that contains the dataset files. You can type in a partial path
and click the Browse button
to drill down into the file structure to locate the datasets you need.
Datasets are typically found in: <InstallLocation>\IGEO-<CountryCode>\\data, where
<InstallLocation> is the directory you specified when you installed the datasets and <CountryCode>
is the two-letter country code. Some countries may have multiple datasets in the data directory,
some of which you may have licensed and some you may have not. Only specify the location of
the data you have licensed.
Note: You must enter the datasets in the order you want them. Reordering datasets is currently
not supported in Management Console. You can reorder them in Enterprise Designer or
from the command line. Management Console will honor the new order.
Note: If you are specifying a path for a user-defined database you must specify a path to a
Pitney Bowes provided database first. The first path in all database resources must be a
path for a Pitney Bowes provided database.
9. If you have additional datasets to add, click the Add button
, otherwise click Save.
10. Click OK to leave the Add Database page.
Resource for Australia
Whenever you install a new database resource or modify an existing database resource you must
define it in Management Console in order for it to become available on your system. This procedure
describes how to add or modify a database resource for the Enterprise Geocoding Module for
Australia.
To create a Geocode Address AUS database resource:
1. If you haven't already done so, install the database files on your system. For instructions on
installing databases, see the Spectrum™ Technology Platform Installation Guide.
.
5
would fail.
to handle.
6. In the Module field, select International Geocode Australia.
7. In the Type field, select Geocode Address AUS.
to install a new dataset. In the Name field, specify a name for this database
resource. In the Path field specify the folder that contains the database files. You can type in a
partial path and click the Browse button
you need.
to drill down into the file structure to locate the datasets
Datasets are typically found in: <InstallLocation>\IGEO-<CountryCode>\\data, where
<InstallLocation> is the directory you specified when you installed the datasets and <CountryCode>
the data you have licensed.
For the Australia Geocoded National Address File (G-NAF) database, you must specify separate
database resources for the GNAF123 and GNAF456 folders. We recommend that you use both
databases to validate the existence of addresses but only use the GANF123 for parcel-level
geocoding. If you do not require parcel-level geocodes you can use the GANF456 database for
geocoding.
6
from the command line. Management Console will honor the new order.
Note: If you are specifying a path for a user-defined database you must specify a path to a
Pitney Bowes provided database first. The first path in all database resources must be a
path for a Pitney Bowes provided database.
9. If you have additional datasets to add, click the Add button
Adding an Enterprise Geocoding Module Global Database
Resource
Unlike other stages, the Geocode Address Global and Reverse Geocode Global stages are not
visible in Management Console or Enterprise Designer until you define a database resource. New
stages are created for each global database resource that you define. For example, if you define
one database resource containing databases for Mexico and Canada, and another database resource
containing data for Australia and Singapore, you would see two Geocode Address Global stages,
one capable of geocoding addresses in Mexico and Canada and the other capable of geocoding
addresses in Australia and Singapore. You would also see two Reverse Geocode Global stages,
one for Mexico and Canada and one for Australia and Singapore.
Note: • Australia, Canada, France, Germany, and Japan have large geocoding databases. Do not
put more than one or two of these in the same database resource.
• If you are running the Spectrum™ Technology Platform server on a 64-bit machine, database
resources should contain no more than eight to ten countries. If you require more, Java
memory settings need to be modified. For assistance, contact technical support.
To create a Geocode Address Global database resource:
1. If you haven't already done so, install the database files on your system. For instructions on
installing databases, see the Spectrum™ Technology Platform Installation Guide.
.
7
would fail.
to handle.
6. In the Module field, select InternationalGeocoder GLOBAL.
7. In the Type field, select Geocode Address Global.
to install a new dataset. In the Name field, specify a name for this dataset.
This name can be anything you choose. In the Path field specify the folder that contains the
datasets for the country you selected. You can type in a partial path and click the Browse button
to drill down into the file structure to locate the datasets you need. When you click OK, the
dataset for the country will be visible in the database resource list on the Add Database page.
The datasets are typically found in: <InstallLocation\IGEO-<CountryCode>\data where
<InstallLocation> is the directory you specified when you installed the datasets, <CountryCode>
the datasets you have licensed.
If you are adding more than one dataset for a particular country, each dataset must be located
in a separate directory. For example, if you are adding a street dictionary and a point dictionary
for the same country, you could specify:
<InstallLocation>\IGEO-<CountryCode>\data\Street_dict
<InstallLocation>\IGEO-<CountryCode>\data\Point_dict
where Street_dict and Point_dict refer to the street dictionary and point dictionaries, respectively.
8
Note: Do not put datasets on a network drive. Doing so can cause performance problems.
9. If you have additional datasests to add, click the Add button
10. If you have additional countries to add, click the Add button
each dataset. When finished, click Save.
and specify a name and path to
By adding multiple countries to the same database resource, you will create a Geocode Address
Global stage that can geocode addresses for each country in one stage.
from the command line. Managment Console will honor the new order.
12. If there are any open Enterprise Designer sessions, click the refresh button to see the new stage.
9
2 - Input
Geocode Address Global takes an address or intersection as input. To
obtain the best performance and the most possible matches, your input
address lists should be as complete as possible, free of misspellings and
incomplete addresses, and as close to postal authority standards as
possible. Most postal authorities have websites that contain information
about address standards for their particular country.
In this section
Input Fields
Single Line Input
11
41
94
100
Input
Input Fields
Geocode Address Finland takes an address or intersection as input. For Finland, Geocode Address
Global takes an address or intersection as input. To obtain the best performance and the most
possible matches, your input address lists should be as complete as possible, free of misspellings
and incomplete addresses, and as close to postal authority standards as possible. Most postal
authorities have websites that contain information about address standards for their particular
country.
NAVTEQ data is available for Finland. For NAVTEQ data, note the following:
Data © 1987 - 2015 HERE. All rights reserved.
Based upon electronic data © National Land Survey Sweden.
Fuente: INEGI (Instituto Nacional de Estadística y Geografía)
The following table lists the input fields used for geocoding locations in Finland.
Note: Specify input using the DataTable class. For information on the DataTable class, see the
"API Fundamentals" section.
Note: If you are using the API, specify input using the DataTable class. The fields described below
are the valid column names in the DataTable class. For information on the DataTable class,
see the "API Fundamentals" section of the Spectrum™ Technology Platform API Guide.
Table 1: Input Fields for Finland
Field Name
Description
columnName
Parameter
AddressLine1
One of the following:
Data.AddressLine1
• The address line containing the street name and building number. For Japanese
addresses, the block and lot number. For addresses in the U.K., this can
contain a building name. For example:
Appeldam
Oranjestad
Rua Jose Anchieta
Luanda
11
Input
Field Name
Description
columnName
Parameter
University City Road
Dubai
ARE also supports the Arabic character set:
‫طريق المدينة الجامعية‬
‫دبي‬
Rruga Shoti
Kurbin
25 De mayo 465
Vied ma, Rio Negro
4360 DUKES RD
KALGOORLIE WA 6430
Florian 3
9020 Enthalpy in Kirsten
Masterstroke 26
1070 Wanderlust
Boulevard Du 28 Novembre
Bujumbura
Rue 1823
Cotonou
Rue 28.263
Ouagadougou
Shaik Khalifa Bin Mohammad Street
Al Moharraq
BHR also supports the Arabic character set:
‫شارع الشيخ خليفة بن محمد‬
‫المحرق‬
Mickey St
Nassau New Providence
14th Street
San Ignacio
Radnor Drive
Hamilton
Calle 15
Santa Cruz de la Sierra
rue America do soul, 100
Guarantor 85070
12
Input
Field Name
Description
columnName
Parameter
Bonnetts Road
Saint Michael
Kushimbara Road
Gaborone
330 Main St
Toronto ON M1B 3V4
1 Rue Halimand
1003 Lausanne
Datsun Rd
1000 Beijing
Cale Alamos 321
1000
Avenue du Docteur Jamot
Douala
Boulevard Patrice Lumumba
Kinshasa
Avenue Coutassi
Brazzaville
Ruta 125
40405 Santo Domingo
Calle 30Ciudad de la Habana
Perdiou 11
Strovolos
KrehlíkovA 92
62700 BRNO
Mulder 2
71665 Vanishing an red Eng
Favrskovvej, 56
6670 Holst ed
Ruta 125
40405 Santo Domingo
Calle 30
Ciudad de la Habana
Gamal Soliman Abu Soliman Street
Abou Ilghait
13
Input
Field Name
Description
columnName
Parameter
EGY also supports the Arabic character set:
‫شارع جمال سليمان ابو سليمان‬
‫أبو الغيط‬
Paso De la Castellated 210
28036 Madrid
Ora 18
10132
Storm Robertson 18
00120 Helsinki
9, rue Paul Lafayette
93217 ST DENIS CEDEX
Avenue Gabriel Lendoye
Libreville
Milton Place
Victoria Street
Windsor SL4 1EG
Mamleshie Road
Accra
2 Anti Missoula
19003
GRC also supports the Greek Cyrillic character set.
2 Ακτή Μιαούλη
Μαρκοπούλου Μεσογαίας
7 Avenida
Villa Nueva
North Road
Georgetown
8 Hong Cheung Street
Eastern District
Pasaje B
San Pedro Sula
Šukljeva Ulica 7
10362 Zagreb
Szegedi Gergely Utca 13
Debrecen 4000
J1 Pecenongan
Gambir
14
Input
Field Name
Description
columnName
Parameter
Gunjur Road
Bangalore South 560017
7 Irvine Court
Dublin 3
Jamila Street
Baghdad
Salthamrar 1
112 REYKJAVÍK Iceland
belvedere aldo nardi 1
00010 Sant'angelo Romano
Queen Street 1
Kingston
Al Ebshehi Street
Amman
JOR also supports the Arabic character set:
‫شارع طرابلس;;السل‬
‫شارع‬
Tokyo Central Post Office
5-3, Yaesu 1-Chome
Chuo-ku, Tokyo 100-8994
JPN supports the Kanji and Latin character sets.
100-8994
5 3
Taratibu Street
Mombasa
First Circular Road
Green Belt
KWT also supports the Arabic character set:
‫طريق الدائري االول‬
‫الحزام االخضر‬
Shaikh Sabah Il-Salem Il-Sabah Street
Beirut
LBN also supports the Arabic character set:
‫شارع الشيخ صباح السالم الصباح‬
‫بيروت‬
Mpilo Road
Maseru
15
Input
Field Name
Description
columnName
Parameter
Ûnijas iela 11A
LV-1039
Riga
Nemencines pl 39
10001
2 Travessa Nova
Nossa Senhora do Carmo
Avenue Moukhtar Soussi
28630 Ain Harrouda
Calle Naranjo 7
89600 Altamira TAMPS
Rue 97
Bamako
Triq il-Kanun
Santa Venera
1. bokeljske brigade
Bar
Avenida 24 De Julho
Maputo
Rue Ely ould Mohamed
Nouakchott
Victor Hugo Street
Beau Bassin
Presidential Way
Lilongwe
Jalan Chowrasta
10100 Seksyen 15
Katanga Street
Swakopmund
Avenue de I'Afrique
Niamey
Limpopo Street
Abuja
39 Avenida NE
Managua
16
Input
Field Name
Description
columnName
Parameter
Raadhuisstraat 52
1016 Amsterdam
Breidablikkvegen 28
3711 Skien
Flat 2/31 Kings Road
Mount Roskill
Auckland 1041
Arab League Street
Masqat
OMN also supports the Arabic character set:
‫شارع جامعة الدول العربية‬
‫مسقط‬
Avenida 4 De Julio
Ciudad de Panamá
Calle Felipe 101 31
Lima
Pleasant Drive
Caloocan City
Plac Teatralny 13
45-056 Opole
Rua Miguel Bombarda 49
8200 Albufeira
Ahmed Bin Mohammad Bin Thany Street
Doha
QAT also supports the Arabic character set:
‫شارع احمد بن محمد بن ثاني‬
‫الدوحة‬
BULEVARDUL 1907 61
Giurgiu
Myakininskaya 5-ya ulitsaKrasnogorsk
RUS also supports the Russian Cyrillic character set:
Мякининская 5-я 53 улица
Красногорск
Avenue De La Gendarmerie
Kigali
King Faisal Bin Abdel Aziz Road
Hafr Il-Batin
17
Input
Field Name
Description
columnName
Parameter
SAU also supports the Arabic character set:
‫طريق الملك فيصل بن عبدالعزيز‬
‫حفر الباطن‬
Rue GY 501
Dakar
1 Holland Grove Road
278790 Bukit Timah
Calle Padres Aguilar
San Salvador
Henrystraat 8
Paramaribo
Ulica Dimitrija Tucovića 204
Žabalj
Recka 182
Boldog 92526
Potocnikova ulica 12
1000
Envägen 4
43091 Hönö
Mbangweni Street
Mbabane
Lak Kaeo Phatthana Rd
Ban Chan 41000
De La Marina Boulevard
Lomé
Angelina
San Juan-Laventille
Rue Aflatoun
Ben Arous
1646 Sokak 1
06020 Sancaktepe
22 Wulong Street
Longtan Township
Kiyungi Street
Dar es Salaam
18
Input
Field Name
Description
columnName
Parameter
Rubaga Road
Kampala
Krymskaya Str. 74
Odessa
UKR also supports the Cyrillic character set:
Кримська вул. 74
Одеса
Calle Ing Juan Alberto Capurro 997
Montevideo
calle Valdez
Valencia
Taiz Road
Ibb
YEM also supports the Arabic character set: ‫الطريق الدائريصنعاءأمانة العاصمة‬
Gaborone Street 94
Klipfontein View
Freedom Way
Kitwe
Skirwith Road
Bulawayo
• This field can also contain the full address. For more information, see Single
Line Input on page 94
• For all countries except Argentina, Great Britain, and Japan, this field can
contain a street intersection. To specify a street intersection, use double
ampersand (&&) to separate the streets. For more information, see Street
Intersection Input on page 100.
For France, an input street address can include a numbered range. For example,
consider an input address of 104-106 rue de Charenton. The returned candidate
includes two address ranges, and the 104 close match is from the 100-106 range.
Alphanumeric ranged addresses are also handled (for example, you could input
a alphanumeric ranged address like 2A-4B. If the geocoding database has
alphabetic values for the input house number, the geocoder returns the house
number as it exists in the database (with or without the alphabetic character). If
the geocoder cannot confirm alphabetic values for the input house number, it
returns the alphabetic value that was provided on input (as long as the house
number matched).
AddressLine2
The second address line of a two-line address. For example:
19
Input
Field Name
Description
columnName
Parameter
Data.AddressLine2
26 WELLINGTON ST E
SUITE 500
TORONTO ON M5E 1S2
Minton Place
Victoria Street
Windsor SL4 1EG
This field is not used with countries included with the Africa bundle (Product Code
XA1), Middle East bundle (Product Code XM1), or Latin America bundle (Product
Code XL1). These databases generally have less comprehensive address
coverage.
This field is not used in this country.
City
Data.City
The city or town name. For most countries, your input address should use the
official city name or alias. For Argentina, Austria, Bahamas, Czech Republic,
Indonesia, Italy, Mexico, Portugal, Spain, Slovenia, and Switzerland, you can
use the town name or alias. For example, for the town of Praha, the aliases of
Praag, Prag, Prague, Praga are all supported. For example, "Ciudad Autónoma
de Buenos Aires" and "Buenos Aires" are recognized as aliases for Capital
Federal. For example, Wien and Vienna are aliases and both names can be used
on input. When you geocode, the input name is returned with the candidate. For
example: if you use Wien on input, Wien is returned in the output. If you use
Vienna on input, Vienna is returned in the output. For example, Losanna is one
of the aliases for Lausanne. The alias can be either a local alternative name or
a language alternative (Basque or Catalan). The city name returned will match
the name specified in input. For example, Xàbia is an alias of Jávea. If the input
address uses Jávea, then Jávea will be returned; if the input address uses Xàbia,
then Xàbia will be returned. For Finland, Finnish, Swedish, and other language
aliases are supported for major post town names. For example, Grankulla is an
alias for Kauniainen. Italian and German town name aliases are recognized. For
example, Arécio is an alias for Arezzo. Likewise, Neumarkt is an alias for Egna.
For example, either Miguel Hidalgo or Mexico City can be used. For example,
either Reahel instead of Rohel can be used. For example, Lisbon, Lisbonne,
Lissabon, and Lisbona are aliases for Lisboa. For example, Lubiana, Liubliana,
and Laibach are aliases for Ljubljana.
Note: In Argentina, Buenos Aires Federal District is not part of Buenos Aires
province. If your input specifies only "Buenos Aires", Spectrum™
Technology Platform returns candidates in both the Federal District and
in the region of Buenos Aires.
For provincial capitals in Argentina, you can use the word Capital as well as the
actual capital name. For example, input of "Capital, MZA" is equivalent to
"Mendoza, MZA".
20
Input
Field Name
Description
columnName
Parameter
Some areas in France are generally recognized as cities even though they are
not truly administrative cities. These areas represent Artificial City Areas, or
Virtual Towns. For a listing of supported virtual towns, see Address Guidelines
for France on page 53.
For Indonesia, this field contains the subdistrict. For example, Jakarta is an alias
for Jakarta Utara.
The subdistrict (tambon).
For Thailand, this field contains the subdistrict (tambon).
This field contains the municipality subdivision (oaza).
The city and county can be swapped on input. That is, if a city appears in either
the City input field or in the County input field, the geocoder will still return the
correct candidate. Similarly, a locality can be entered in either the Locality or City
input field.
County
The meaning of county varies by country.
Data.County
The Local Government Authority (LGA) name.
The majority of countries in the Africa database (XA1) do not use a county or
equivalent as part of an address.
The majority of countries in the Middle East database (XM1) do not use a county
or equivalent as part of an address.
The majority of countries in the Latin American database (XL1) do not use a
county or equivalent as part of an address.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ABW (Aruba)—Not used
AGO (Angola)—Not used
ARE (United Arab Emirates)—Not used
ALB (Albania)—Not used
ARG (Argentina)—Department
AUS (Australia)—The Local Government Authority (LGA)
AUT (Austria)—Province
BDI (Burundi)—Not used
BEL (Belgium)—Province
BEN (Benin)—Not used
BFA (Burkina Faso)—Not used
BHR (Bahrain)—Not used
BHS (Bahamas)—Not used
BLZ (Belize)—Not used
BMU (Bermuda)—Not used
BOL (Bolivia)—Not used
BRA (Brazil)—Not used
21
Input
Field Name
Description
columnName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
BRB (Barbados)—Not used
BRN (Brunei Darussalam)—Not used
BWA (Botswana)—Not used
CAN (Canada)—Not used
CHE (Switzerland)—Province
CHL (Chile)—District
CHN (China)—Not used
CMR (Cameroon)—Not used
COD (Congo, Democratic Republic of)—Not used
COG (Congo)—Not used
CRI (Costa Rica)—Not used
CUB (Cuba)—Not used
CYP (Cyprus)—Not used
CZE (Czech Republic)—District name or alias
DEU (Germany)—Kreis
DNK (Denmark)—Province
DOM (Dominican Republic)—Not used
ECU (Ecuador)—Not used
EGY (Egypt)—Not used
ESP (Spain)—Province
EST (Estonia)—District
FIN (Finland)—Not used
FRA (France)—Department
GAB (Gabon)—Not used
GBR (Great Britain)—Not used
GHA (Ghana)—Not used
GRC (Greece) —District
GTM (Guatemala)—Not used
GUY (Guyana)—Not used
HKG (Hong Kong)—Not used
HND (Honduras)—Not used
HRV (Croatia)—Province
HUN (Hungary)—District
IDN (Indonesia)—Regency/City
IND (India)—District
ISL (Iceland)—Not used
IRL (Ireland)—Province
IRQ (Iraq)—Not used
ITA (Italy)—Province
JAM (Jamaica)—Not used
JOR (Jordan)—Not used
JPN (Japan)—City (shi)
22
Input
Field Name
Description
columnName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
KEN (Kenya)—Not used
KNA (St Kitts and Nevis)—Not used
KWT (Kuwait)—Not used
LBN (Lebanon)—Not used
LSO (Lesotho)—Not used
LTU (Lithuania)—County
LVA (Latvia)—District
MAC (Macau)—Not used
MAR (Morocco)—Not used
MEX (Mexico)—Province
MKD (Macedonia)—Not used
MLI (Mali)—Not used
MLT (Malta)—Not used
MNE (Montenegro)—Not used
MOZ (Mozambique)—Not used
MRT (Mauritania)—Not used
MUS (Mauritius)—Not used
MWI (Malawi)—Not used
MYS (Malaysia)—Not used
NAM (Namibia)—Not used
NER (Niger)—Not used
NGA (Nigeria)—Not used
NLD (The Netherlands)—Province
NOR (Norway)—District (fylke/counties)
NZL (New Zealand)—Region
OMN (Oman)—Not used
PAN (Panama)—Not used
PER (Peru)—Not used
PHL (Philippines)—District
POL (Poland)—District (poviat)
PRT (Portugal)—Not used
PRY (Paraguay)—Not used
QAT (Qatar)—Not used
ROU (Romania) —Not used
RUS (Russia) —District
RWA (Rwanda)—Not used
SAU (Saudi Arabia)—Not used
SEN (Senegal)—Not used
SGP (Singapore)—Not used
SLV (El Salvador)—Not used
SRB (Serbia)—Not used
SUR (Suriname)—Not used
23
Input
Field Name
Description
columnName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
SVK (Slovakia)—Town
SVN (Slovenia)—Region
SWE (Sweden)—Kommun
SWZ (Swaziland)—Not used
TGO (Togo)—Not used
THA (Thailand)—District (amphoe)
TTO (Trinidad and Tobago)—Not used
TUN (Tunisia)—Not used
TUR (Turkey)—District
TWN (Taiwan)—Not used
TZA (Tanzania)—Not used
UGA (Uganda)—Not used
UKR (Ukraine)—District
USA (United States) —Not used
URY (Uruguay)—Not used
VEN (Venezuela)—Region
XKX (Kosovo)—Not used
YEM (Yemen))—Not used
ZAF (South Africa)—District
ZMB (Zambia)—Not used
ZWE (Zimbabwe)—Not used
This field is not used with countries included with the African bundle (Product
Code XA1). These African countries generally have less comprehensive address
coverage.
This field is not used with countries included with the Middle East bundle (Product
Code XM1). These African countries generally have less comprehensive address
coverage.
This field is not used with countries included with the Latin American database
(Product Code XL1). These African countries generally have less comprehensive
address coverage.
Note: If you enter addresses with the Andorran country code (AND), only
Andorran addresses are returned, including the AND country code. If
you enter an Andorran with a country code of Spain (ESP), you will still
get Andorran candidates, but with the ESP country code.
The department name.
The region name.
The region name or alias. For example, Osrednjeslovenska/Ljubljana.
The district name.
The district (amphoe) name.
24
Input
Field Name
Description
columnName
Parameter
The district (povia) name.
The district (okres) name or alias.
The regency/city name.
The kommun name.
The district name.
The city (shi) name.
FirmName
Company or place name. For example:
Data.FirmName
Pitney Bowes
4360 Dukes Rd
Kalgoorlie WA 6430
Toronto Star Building
1 Yonge St
Toronto ON M5E 1E5
Pitney Bowes Semco Equipamentos e Serviços Ltda.
Rua Dom Aguirre, 438
3º andar. Vila Sofia
São Paulo, SP 04671-903
Pitney Bowes
Immeuble Le Triangle
9, rue Paul Lafargue
Pitney Bowes
Grafinger Straße 2
81671 München
Pitney Bowes Software Ltd
Minton Place
Victoria Street
Windsor, Berkshire SL4 1EG
Pitney Bowes
72 Apollo Drive
Rosedale
North Shore City 0632
Auckland
A place name, such as a building name or company name.
25
Input
Field Name
Description
columnName
Parameter
Aravali Vihar Police Station
Alwar 301030
Grand Hotel Reykjavik
Sigtun 38 Reykjavik 105
This field is not used with countries included with the Africa bundle (Product Code
XA1). These countries generally have less comprehensive address coverage.
Code XM1). These countries generally have less comprehensive address
coverage.
(Product Code XL1). These countries generally have less comprehensive address
coverage.
HouseNumber
Data.HouseNumber
The building number. You may get better parsing results for some countries if
you put the house number in this field instead of AddressLine1. Not every country
includes house number data.
The Africa and Middle East countries do not generally have house numbers in
the data source.
Some countries covered in the Latin America database have house number data.
See Address Guidelines for Latin America for details of Latin America house
number and postal coverage.
For the best results, use the HouseNumber input field for these countries when
using multi-line input: India, Singapore, Malaysia, Thailand, and Turkey.
Note: The house number specified in the HouseNumber field takes precedence
over any house number specified in the AddressLine1 field.
LastLine
The last line of the address.
Data.LastLine
• Rua Jose Anchieta
Luanda
Rruga Shoti
Kurbin
Al Raha Beach Street>
Abu Dhabi
25 De mayo 465
Vied ma, Rio Negro
26
Input
Field Name
Description
columnName
Parameter
4360 DUKES RD
KALGOORLIE WA 6430
Florian 3
9020 Enthalpy in Kirsten
Masterstroke 26
1070 Wanderlust
Boulevard Du 28 Novembre
Bujumbura
Rue 1823
Cotonou
Rue 28.263
Ouagadougou
Road 3960
Madinat Hamad
Mickey St
Nassau New Providence
rue America do soul, 100
Guarantor 85070
Kushimbara Road
Gaborone
330 Main St
Toronto ON M1B 3V4
1 Rue Halimand
1003 Lausanne
Cale Alamos 321
1000
Datsun Rd
1000 Beijing
Avenue du Docteur Jamot
Douala
Boulevard Patrice Lumumba
Kinshasa
Avenue Coutassi
Brazzaville
Versailles
Limassol
27
Input
Field Name
Description
columnName
Parameter
KrehlíkovA 92
62700 BRNO
Mulder 2
71665 Vanishing an red Eng
Favrskovvej, 56
6670 Holst ed
154 Anwar Al Sadat Street
2nd Ismailia
Paso De la Castellated 210
28036 Madrid
Ora 18
10132
Storm Robertson 18
00120 Helsinki
9, rue Paul Lafayette
Avenue Gabriel Lendoye
Libreville
Milton Place
Victoria Street
Windsor SL4 1EG
Mamleshie Road
Accra
2 Anti Missoula
19003
GRC also supports the Greek Cyrillic character set
2 Ακτή Μιαούλη
Μαρκοπούλου Μεσογαίας
8 Hong Cheung Street
Eastern District
Šukljeva Ulica 7
10362 Zagreb
Szegedi Gergely Utca 13
Debrecen 4000
28
Input
Field Name
Description
columnName
Parameter
J1 Pecenongan
Gambir
Gunjur Road
Bangalore South 560017
7 Irvine Court
Dublin 3
Jamila Street
Baghdad
Borgartun 34
105 REYKJAVÍK
belvedere aldo nardi 1
00010 Sant'angelo Romano
Al Ebshehi Street
Amman
Taratibu Street
Mombasa
230 Street
Abdullah Al Mubarak - West Jleeb
Pierre Gemayel Street
Beirut
Mpilo Road
Maseru
Ûnijas iela 11A
LV-1039
Riga
Nemencines pl 39
10001
2 Travessa Nova
Nossa Senhora do Carmo
Avenue Moukhtar Soussi
28630 Ain Harrouda
Calle Naranjo 7
89600 Altamira TAMPS
29
Input
Field Name
Description
columnName
Parameter
Rue 97
Bamako
Trig San Gorg
Luqa
Svetog Save
Berane
Avenida 24 De Julho
Maputo
Rue Ely ould Mohamed
Nouakchott
Victor Hugo Street
Beau Bassin
Presidential Way
Lilongwe
Jalan Chowrasta
10100 Seksyen 15
Katanga Street
Swakopmund
Avenue de I'Afrique
Niamey
Limpopo Street
Abuja
Raadhuisstraat 52
1016 Amsterdam
Breidablikkvegen 28
3711 Skien
Flat 2/31 Kings Road
Mount Roskill
Auckland 1041
Al Mujamma Street
Muscat
Pleasant Drive
Caloocan City
Plac Teatralny 13
45-056 Opole
30
Input
Field Name
Description
columnName
Parameter
Rua Miguel Bombarda 49
8200 Albufeira
Street 656
Al Rayyan
BULEVARDUL 1907 61
Giurgiu
Myakininskaya 5-ya ulitsa
Krasnogorsk
RUS also supports the Russian Cyrillic character set:
Мякининская 5-я 53 улица
Красногорск
Avenue De La Gendarmerie
Kigali
Ali AL Qabsi Street>
Riyadh
Rue GY 501
Dakar
1 Holland Grove Road
278790 Bukit Timah
Recka 182
Boldog 92526
Cretinjska
Belgrade
Potocnikova ulica 12
1000
Envägen 4
43091 Hönö
Mbangweni Street
Mbabane
Lak Kaeo Phatthana Rd
Ban Chan 41000
De La Marina Boulevard
Lomé
31
Input
Field Name
Description
columnName
Parameter
Rue Aflatoun
Ben Arous
1646 Sokak 1
06020 Sancaktepe
22 Wulong Street
Longtan Township
Kiyungi Street
Dar es Salaam
Rubaga Road
Kampala
Krymskaya Str. 74
Odessa
UKR also supports the Cyrillic character set:
Кримська вул. 74
Одеса
Calle Ing Juan Alberto Capurro 997
Montevideo
calle Valdez
Valencia
Taiz Road
Ibb
Gaborone Street 94
Klipfontein View
Freedom Way
Kitwe
Kirwith Road
Bulawayo
Locality
Data.Locality
The meaning of locality varies by country. Generally a locality is a village in rural
areas or it may be a suburb in urban areas. When used, a locality typically appears
on the lastline of the address with the postcode.
African and Middle East countries do not use a locality or equivalent as part of
an address. However there is no penalty if state/province is used in input address.
• ABW (Aruba)—Not used
• AGO (Angola)—Not used
• ARE (United Arab Emirates)—Not used
32
Input
Field Name
Description
columnName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ARG (Argentina)—Neighborhood or barrio
AUS (Australia)—Not used
AUT (Austria)—Not used
BEL (Belgium)—Not used
BRA (Brazil)—Locality
CAN (Canada)—Dissemination Area and Enumeration Area (DA and EA)
CHE (Switzerland)—Not used
CHL (Chile)—Locality or Alias
CHN (China)—Locality
CZE (Czech Republic)—Locality
DEU (Germany)—Not used
DNK (Denmark)—Not used
ESP (Spain)—Locality
EST (Estonia)—Locality
FRA (France)—Not used
GBR (Great Britain)—Locality
GRC (Greece) —Locality
HKG (Hong Kong) —Locality
HRV (Croatia)—Settlement
HUN (Hungary)—Locality
33
Input
Field Name
Description
columnName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
IDN (Indonesia)—Village
IND (India)—Locality
IRL (Ireland)—Not used
ITA (Italy)—Locality
JPN (Japan)—City district (chome)
LTU (Lithuania)—Locality
LVA (Latvia)—Locality
MAC (Macau) —Locality
MEX (Mexico)—Locality
NIC (Nicaragua)—Not used
NLD (The Netherlands)—Not used
NOR (Norway)—Not used
NZL (New Zealand)—Suburb
PHL (Philippines)—Locality
POL (Poland)—Not used
PRT (Portugal)—Locality
ROU (Romania)—Sector used in city of Bucharest
34
Input
Field Name
Description
columnName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
RUS (Russia)—Locality
SVK (Slovakia)—Locality or Alias
SVN (Slovenia)—Locality or Alias
SWE (Sweden)—Not used
THA (Thailand)—Not used
TUR (Turkey)—Locality
TWN (Taiwan)—Locality
UKR (Ukraine)—Locality
URY (Uruguay)—Locality
VEN (Venezuela)—Not used
YEM (Yemen)—Not used
ZAF (South Africa)—Locality
PostalCode
The postal code in the appropriate format for the country.
Data.PostalCode
Albania uses a four-digit postal code.
The Africa and Middle East databases generally do not have postal code data.
Some countries covered in the Latin America database have limited postal code
data. See Address Guidelines for Latin America for details of Latin America
house number and postal coverage.
Australia uses a four-digit postal code system. In general, the first digit represents
a state or territory, the second digit represents a region with a state, and digits
three and four representing towns. For more information, see Address Guidelines
for Australia on page 43.
35
Input
Field Name
Description
columnName
Parameter
Austria uses a four-digit postal code system. The first two numbers represent
the sector and the last two numbers designate the delivery point within the sector.
Belgium and Luxembourg use a four-digit postal code. The first two digits
designate the sorting area (with the first digit usually representing the region)
The next two digits represent the post office and delivery office.
For Brazil, use the complete eight-digit postcode for the most accurate results
(a single close match candidate). However, you can use a five-digit postcode.
Brunei Darussalam uses six-character alphanumeric postal code. The first letter
represents the daereh (district) and the second letter represents the mukim
(village). The first two digits represent the village code and the last two digits
represent the post office.
Switzerland uses a four-digit postal code beginning with a number between 1
and 9. Liechtenstein postcodes range from 9480 to 9499.
Chile uses a seven-digit postal code beginning with a number between 1 and 9.
Canada uses a six-character postal code. The first three characters are typically
separated from the second three with a space. The first three characters are the
FSA, the second three are the LDU. Street address geocoding only requires the
FSA while postal code geocoding requires the full postal code (FSALDU). Choose
whether you wish to have a space between the first three and last three characters
of the postal code. Keeping this consistent speeds up the geocoding process.
China has a six-digit postcode system. The first two digits represent the province.
The third digit and fourth digits represent the district and city/town. The final two
digits represent the postal delivery zone or prominent location. Larger provinces
or cities might be assigned more than one block of codes. For example,
Guangdong Province is assigned 51 and 52 as the first two digits.
Note: For China, postal centroid geocoding requires the complete six-digit
postcode. However, when a postal code is provided as part of an address
for street geocoding, only four-digit postal codes are accepted and
returned.
Cyprus uses a four-digit postal code.
Czech Republic has a five-digit postal code system. Postal codes are typically
separated by a space between the third and fourth numbers, but variations in
spacing or no spacing in postal codes is supported.
Denmark uses a four-digit postal code beginning with a number between 1 and
9.
Spanish postcodes are composed of five digits (Andorra postcodes. are in the
format AN###.) You must enter a complete postcode.
Estonia uses a five-digit postal code system.
Finland uses a five-digit postal code. The first two digits designate the post town
or municipal area. The last three digits represent the destination post office.
36
Input
Field Name
Description
columnName
Parameter
France uses a five-digit postal code. You must enter a complete postcode. The
first two digits usually represent the department. The digits 00 represent military
addresses and there are also special digit for overseas territories. The last three
digits represent the local delivery area. In the larger cities (Paris, Lyon Marseille),
the last two digits represent the arrondissement. For example, in the postcode:
33380, 33 is the department 380 is the delivery area.
Greece uses a five-digit postal code system.
Croatia uses a five-digit postal code system. The first two digits represent the
top level administrative subdivision (county). Zagreb city and Zagreb county both
share the 10 postal code range.
Hungary has a four-digit postal code system. The first digit is for the postal region.
Indonesia has a five-digit postal code system.
India has a six-digit postal code system.
In Ireland, postal data is available only for Dublin. For street-level geocoding,
enter the full postcode in the format Dublin#, where # ranges from 1-24 (and one
district known as Dublin6W). For postal centroid geocoding (or postal centroid
fallback) use only the postal number as input. For example, specify the PostalCode
as 3 rather than Dublin3. Only the postcode number is returned for postal centroid
geocoding or fallback.
Iceland uses a three-digit postal code system.
Italy uses a five-digit postal code system. The first three numbers represent the
province and the last two numbers designate the delivery point.
Japan uses a seven-digit numeric postal code system in the format: 999-9999.
Latvia uses a four-digit postal code system. The first two numbers represent the
routing area and the last two numbers designate the post office. Postal codes
cannot begin with 0, 22-29, 35, 49, 55 or 58-99.
Lithuania uses a five-digit postal code system. The LT prefix is allowed but is not
required.
Malaysia uses a five-digit postal code system.
Mexico uses a five-digit postal code system.
Macedonia uses a four-digit postal code.
Malta uses an alphanumeric postal code. The first three letters represent the
locality. This is followed by four digits.
Montenegro uses a five-digit postal code. The first two numbers represent the
district and the last three represent the post office.
Netherlands uses a postal code system of four digits followed by two letters. The
first two numbers represent the city and region. The last two numbers and two
letters designate the specific house number range. The letters represent a
37
Input
Field Name
Description
columnName
Parameter
distribution code. You can geocode using the four digits only or you can include
the two-letter distribution code.
Norway uses a four-digit postal code. The first two digits designate the geographic
area.
New Zealand uses a four-digit postal code. The first digit represents the
geographic region. The second and third digits represent the postal sort area.
The last digit represents a specific urban area, rural delivery or PO box lobby.
Poland uses a five-digit postal code in the format 99-999. The first digit represents
the postal district. The second digit represents a major subdivision of that district.
The three numbers after the dash represent the delivery post office. For large
municipalities, the last three digits can represent a particular street, section of a
street, or sometimes a specific address.
Portugal uses a four-digit postal code beginning with a number between 1 and
9. More recently, Portugal instituted a seven-digit postcode with a dash and three
additional digits following the first four digits. The geocoder ignores the additional
three digits and returns the four-digit postal code.
Romania uses a six-digit postal code system.
Russia uses a six-digit postal code system.
Serbia uses a five-digit postal code.
Singapore uses a six-digit postal code system. The first two numbers represent
the sector and the last four numbers designate the delivery point within the sector.
Every building in Singapore has a unique postal code.
South Africa uses a four-digit postal code system
Slovakia uses a five-digit postal code system.
Slovenia uses a four-digit postal code system.
Sweden uses a five-digit postal code beginning with a number between 1 and 9.
There is typically a space between the first three digits (the outward sorting part
of the postcode) and the last two digits (the inward sorting part).
Thailand uses a five-digit postal code system.
Turkey uses a five-digit postal code system. Postal codes are typically separated
by a space between the third and fourth numbers, but the geocoder can handle
variations in spacing or no spacing in postal codes.
Taiwan uses a three-digit postal code system.
In the United Kingdom, each address is associated with an alphanumeric code
up to seven characters in length. Each postcode includes an average of 15
addresses. In some cases, where a customer receives a substantial amount of
mail, for example, a business, the postcode pertains to just that one address (a
large-user postcode).
Kosovo uses a five-digit postal code.
38
Input
Field Name
Description
columnName
Parameter
StateProvince
The meaning of State/Province varies by country.
Data.StateProvince
Countries in the Africa, Middle East, and Latin America databases do not use a
state/province or equivalent as part of an address. However there is no penalty
if state/province is used in input address.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ARG (Argentina)—Region or province
AUS (Australia)—State
AUT (Austria)—Region
BHS (Bahamas)—District
BRA (Brazil)—State
CAN (Canada)—Province
CHL (Chile)—State
CHN (China)—Province
CZE (Czech Republic)—Region name or alias. For example, the region HLAVNÍ
MESTO PRAHA can be aliased as Prag.
DEU (Germany)—Bundesland
ESP (Spain)—Region
EST (Estonia)—Not used
FIN (Finland)—Region (län)
FRA (France)—Region
GBR (Great Britain)—Region
GRC (Greece) —Region
HKG (Hong Kong) —Province
HRV (Croatia)—Not used
39
Input
Field Name
Description
columnName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
HUN (Hungary)—County (megye)
IDN (Indonesia)—Province
IND (India)—State
ITA (Italy)—Region
JPN (Japan)—Prefecture
LTU (Lithuania)—Not used
LVA (Latvia)—State
MAC (Macau) — State
MEX (Mexico)—State
MYS (Malaysia)—State (negeri)
PHL (Philippines)—State
POL (Poland)—Province (voivodship)
PRT (Portugal)—Region
ROU (Romania)—Not used
RUS (Russia) —Region
40
Input
Field Name
Description
columnName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
SVK (Slovakia)—Not used
SVN (Slovenia)—Not used
SWE (Sweden)—Region (lan)
THA (Thailand)—Province (changwat)
TUR (Turkey)—Province
TWN (Taiwan)—County or Special Municipality
UKR (Ukraine)—Region (oblast)
URY (Uruguay)—Department
VEN (Venezuela)—State
ZAF (South Africa)—State
Follow these suggestions to ensure that your street input data is in the best format possible for
optimal geocoding.
Address Guidelines for Albania
The Albania geocoder supports address locations in Albania. Follow these guidelines to provide
input that Geocode Address Global can successfully geocode. For additional information on Albania
addresses, see the Albania Post website: http://www.en.postashqiptare.al/
• Required fields—Addresses must contain a either a city or postal code.
41
Input
• Thoroughfare types—Thoroughfare types and their common abbreviations are recognized and
fully supported on input and output.
• Common words and abbreviations—The geocoder recognizes common words, directionals,
house number indicators, and abbreviations used in addresses and can geocode these addresses
successfully.
Address Guidelines for Argentina
optimal geocoding. For additional information on Argentine addresses, see the Correo Argentino
website: http://www.correoargentino.com.ar/.
• Required fields—If you are using the standard TomTom database, addresses must contain a
city. For the NAVTEQ database, addresses can contain either a city or postal code.
fully supported in input addresses. Examples of typical thoroughfare types are:
Avendia
Avendia
Av
Calle
C
Clle
Lateral Ruta
Lat Ruta
LR
Ruta Provincia
RP
RP
Ave
Avda
LR
• Numbers, numeric equivalents, and ordinals—Numbered streets are mapped to the named
equivalents. For example, you can input Calle 5 or Calle cinco and get the same returned
candidates. Ordinals are also recognized in input addresses. The following numbers and equivalents
are recognized as part of a street name input:
1,UNO,PRIMERO,PRIMER,PRIMERA
5,CINCO,QUINTO,QUINTA
For example, an input street name of "25 de Mayo" is recognized and handled the same way as
"Veinticinco de Mayo".
• Proper names and dates in street and town names—Proper names and dates are often used
in Argentina addresses, and these are handled by MapMarker Argentina. For example, an input
street name of "Juan F. Ibarra" is recognized and handled the same way as "Juan Felipe Ibarra".
• Directionals in addresses—The following directionals are recognized in input addresses: Norte,
Oriente, Este, Sur, Oueste, Occidente, Poniente, N, E, S, O, NE, NO, SE, SO, Noreste, Sudeste,
Noroeste, Sudoeste.
42
Input
• Abbreviations in addresses—A number of common abbreviations can be used in input addresses.
Geocode Address ARG will recognize the abbreviations and geocode successfully. For example,
following is a small sample of equivalent abbreviations. This is not a complete list of address
abbreviations.
Bario
BAR
Ciudad
CD
CD.
Colonia
COL
COL.
Doctor
DR
Francisco
FCO
Manza
MZA
Note: For Argentina, you must use NAVTEQ data for postal geocoding.
Address Guidelines for Australia
The Enterprise Geocoding Module offers several AUS databases including the PSMA street G-NAF
point databases. Contact your sales representative for more information about licensing these
databases. Your Enterprise Geocoding Module database release notes identify the current database
vintages.
Follow these guidelines to provide input that Geocode Address Global can successfully geocode.
For additional information on Australia addresses, see the Australia Post website:
www.auspost.com.au.
• Required fields—Addresses must contain either a city or a postal code.
• House numbers and unit information—The house number pinpoints the location of the address.
Unit input can be in one of two formats, as shown in the following examples:
• Flat 2, 17 Jones St.
• Apt 19, 123 Main St., where Apt is the unit type and 99 is the unit number. In this format, you
must specify a valid unit type, otherwise the address will not be geocoded correctly. For a listing
of valid unit types, see www.auspost.com.au.
• 99-123 Main St. For an address derived from the G-NAF database, this address is a unique
house number and is geocoded as a single delivery point, not as a range.
43
Input
• Directional suffixes—Use directional suffixes wherever possible. This is especially true in towns
and cities that consist mainly of numbered streets. These streets can only be distinguished by
their directional suffixes and street types. They also distinguish addresses on streets that change
direction. For example: 123 Queen St W and 123 Queen St E would have very different coordinates.
• Street types—These distinguish different streets of the same name. For example, Main Avenue
and Main Street are two entirely different entities. Using types is not essential, but it adds precision
to your data. For a listing of street types, see www.auspost.com.au.
• City/suburb name—Enter the city/suburb name in the City field. Note that all input addresses
must contain either a city or a postal code. If the geocoder does not make a close match on the
street in the specified suburb, it can make a close match on the Local Government Area (LGA).
Local Government Area (LGAs) do not encompass all of Australia. For example, LGAs do not
cover extensive northern parts of South Australia, a large part of the Northern Territory, and the
Australian Capital Territory. An LGA can include a number of official suburbs. It is best to use the
suburb name for geocoding purposes, but it is possible to get a match on the LGA (or to return
LGA information) in geocoded results.
• Postal code—All postcodes consist of four digits. While there are exceptions, the general format
of postcodes is as follows:
Note: These are general guidelines, and there are exceptions to these postcode number ranges.
• Digit 1 represents the state or territory, within the following general conventions:
2
NSW
2600 and 2900
ACT
3
VIC
4
QLD
5
SA
6
WA
7
TAS
0
NT
44
Input
• Digit 2 represents a region within the state. State or territorial capitals usually have a 0 or 1 as
the second digit.
• Digits 3 and 4 represent towns. Major towns usually have a 0 as the last digit (or sometimes as
the last two digits).
Address Guidelines for Austria
For additional information on Austrian addresses, see the Austria Post website: http://www.post.at/.
• State abbreviations—State abbreviations are supported. The following table lists the Austrian
states and their abbreviations.
Burgenland
Bgl
Kärnten
Ktn
Niederösterreich
NÖ
Oberösterreich
OÖ
Salzburg
Sbg
Steiermark
Stm
Tirol
Tirol
Vorarlberg
Vbg
Wien
Wien
45
Input
• Thoroughfare types—Austrian thoroughfare types and their common abbreviations are recognized
and fully supported on input and output.
equivalents. Ordinals are also recognized in input addresses.
• Common words and abbreviations—Common words, directionals, house number indicators,
and abbreviations used in addresses are recognized.
Address Guidelines for Bahamas
For additional information on Bahamian addresses, see the Postal Service in the Bahamas website:
http://bahamas-guide.info/travel.basics/postal.services/
• Required fields—Addresses must contain a city. Postal codes are not used in Bahamas.
successfully.
Note: Postal geocoding is not available with Bahamas.
Address Guidelines for Belgium
The Belgium geocoder supports locations in Belgium and Luxembourg. Follow these guidelines to
provide input that Geocode Address Global can successfully geocode. For additional information
on Belgium and Luxembourg addresses, see the Belgium Post website: http://www.bpost.be/.
• Supported languages—Dutch, French, and German language aliases and address formats are
supported.
• Thoroughfare types—Belgian thoroughfare types and their common abbreviations are recognized
and fully supported on input and output. Dutch, French, and German thoroughfare types are also
supported.
and abbreviations used in addresses are supported.
46
Input
Address Guidelines for Brazil
optimal geocoding. For additional information on Brazilian addresses, see the Correios Brazil website:
http://www.correios.com.br/default.cfm.
• Thoroughfare types—Thoroughfare types (pre and post thoroughfare types) and their common
abbreviations are recognized and fully supported on input and output. Following is a partial list of
recognized thoroughfare types.
ALAMEDA=AL,ALAMEDA,ALUA LALA
ACESSO=AC,ACESSO
ARCO=ARCO
AUTO-ESTRADA=AUTO-EST,AUTO-ESTRADA
AVENIDA=AV,AVDA,AVE,AVENIDA
AZINHAGA=AZINHAGA
BAIRRO=BAI,BAIRRO
BALUARTE=BALUARTE
BECO=BECO
Many others are also recognized.
equivalents. Ordinals are also recognized in input addresses. For example, the following are all
recognized in an input address:
um, first, one, 1st, primera, primeiras, primeiro
dois, second, two, 2nd, segunda, segundos
Many other numeric designations are also recognized.
• Directionals in addresses—The following directionals are recognized in input addresses: norte,
do norte, setentrional, sul, do sul, meridional, leste, este, do leste, do este, oriental, oeste, do
oeste, ocidental
and abbreviations used in addresses are supported. This is a partial list of common words and
abbreviations that are recognized. Many other common words are also handled.
Articles of speech
dos, das, do, da, de, d, dom, uma, e, o, n, sn, sa, ie a, os, as, ao, em, no, na, nos,
nas, ao, andar, andares, ander, apart, apartment, flat, apartmento, apto, apt, ap,
ato, casa, cs, cob, unit (and many other common articles of speech)
Common words
os, nova, novas, na, no, nas, nos, um
47
Input
Common abbreviations
aeroporto=aerop
internacio=intern,int
internacional=int
international=int
conselheiro=cnso
desembargador=des
regente=reg
limitado=ltda,ltdo,ltd
(and many other abbreviations)
Address Guidelines for Canada
The Enterprise Geocoding Module offers several CAN databases including NAVTEQ street and
point databases and the TomTom point database. Contact your sales representative for more
information about licensing these databases. Your Enterprise Geocoding Module database release
notes identify the current database vintages.
optimum geocoding.
• Post Office Box numbers—P.O. Boxes and Rural Route addresses are not geocodable. Geocode
Address CAN will honor this user input and attempt to output Boxes and Rural Route information,
but it will not be used for geocoding purposes.
• Highway addresses—Highway addresses (such as Hwy 401) are geocoded.
• House numbers and apartment letters—Remove spaces between house number and apartment
letter. 123 A Main Street does not geocode correctly because the geocoder assumes that the
name of the street is A. Two workaround options are available:
• Do not include the apartment letter.
• Delete the space between house number and apartment letter: 123A Main Street geocodes
because the geocoder ignores the A.
• House numbers and unit information—The house number pinpoints the location of the address.
Unit input can be in one of two formats, as shown in the following examples:
• 99-123 Main St, where 99 is the unit number. In this format, do not specify the unit type. The
number 99 could be a suite, apartment, unit, floor or any valid unit type.
• 123 Main St. Apt 99, where Apt is the unit type and 99 is the unit number. In this format, you must
specify a valid unit type (such as Apt or Suite), otherwise the address will not be geocoded correctly.
• Directional suffixes—Use directional suffixes wherever possible. This is especially true in towns
and cities, such as Calgary, which consist mainly of numbered streets. These streets can only be
distinguished by their directional suffixes and street types. They also distinguish addresses on
streets that change direction. For example: 123 Main St W and 123 Main St E have very different
coordinates.
48
Input
• Street types—These distinguish different streets of the same name. For example, Main Avenue
and Main Street are two entirely different entities. Using types is not essential, but it adds precision
to your data. For a list of valid street types see www.canadapost.com.
• City name—Do not abbreviate city names. If the city is unknown, you may leave it blank, although
this may affect the accuracy of the geocode.
• Province name—You may use the full province name (for example, Ontario), but using the
two-character abbreviation (ON) is recommended to reduce the likelihood of input errors.
Address Guidelines for Chile
For additional information about the Chilean postal system, see the Correos Chile website:
http://www.correos.cl/.
• Required fields—Addresses must contain a street name and either a town or postcode.
• Abbreviations in addresses—The geocoder recognizes common words, directionals, house
number indicators, and abbreviations used in addresses and can geocode these addresses
successfully.
• Numbers, Numeric Equivalents, and Ordinals—Numbered streets are mapped to the named
Address Guidelines for China
For additional information about the Chinese postal system, see the China Post website:
http://www.chinapost.cn/.
successfully.
Address Guidelines for Croatia
For additional information on Croatian addresses, see the Postal Service in the Croatia website:
http://www.posta.hr/
49
Input
successfully.
Address Guidelines for Czech Republic
For additional information on Czech addresses, see the Czech Republic Postal Service website:
http://www.ceskaposta.cz/en/.
• Aliases for town, district, and region names—Aliases for town, district, and region names are
supported.
abbreviations are recognized and fully supported on input and output.
Address Guidelines for Cyprus
The Cyprus geocoder supports address locations in Cyprus. Follow these guidelines to provide
input that Geocode Address Global can successfully geocode. For additional information on Cyprus
addresses, see the Cyprus Post website:
http://www.mcw.gov.cy/mcw/postal/dps.nsf/index_en/index_en?OpenDocument
successfully.
Address Guidelines for Denmark
For additional information about the Denmark postal system, see the Post Danmark website:
http://www.postdanmark.dk/.
50
Input
• Supported languages—Danish and English language aliases are supported for major
town/municipality names. For example, Copenhagen (English) is equivalent to København (Danish).
fully supported on input and output. Following is a list of recognized thoroughfare types. This is
not a complete list. Additional thoroughfare types may also be recognized.
ALLÉ=alle
ANLAEG=anlaeg
ANLEAG=anleag
BAKKEN=bakken
BANEN=banen
BASTION=bastion
BOUL=boulevard
BOULEVARD=bulevardi
BRO=bro
BROEN=bro
BUEN=buen
BULEVARDI=bulevardi
DAMMEN=dammen
DOSSERING=dossering
GAARD=garrd
GADE=gade
GANGEN=gangen
GARD=gard
GÂRD=gard
GET=get
HAVE=have
HAVN=havn
HOEJEN=hojen
HOJEN=højen
HøJEN=højen
HOLMEN=holmen
HUSET=huset
KAER=kaer
KEAR=kear
KRAENTEN=kraeten
KREANTEN=kreanten
LAENGEN=laengen
LEANGEN=leangen
MARKEN=marken
PARK=parken
PARKEN=parken
PASSAGEN=passagen
PLADS=plads
SIDEN=siden
STIEN=stien
51
Input
STRAEDE=straede
STREADE=streade
SVINGET=svinget
TOFTEN=toften
TORV=torv
VAENGE=vaenge
VANGEN=vangen
VARDEN=varden
VEANGE=veange
VEJ=vej
Address Guidelines for Estonia
For additional information about the Estonia postal system, see the Estonian Post website:
http://www.post.ee/.
• Thoroughfare types—Estonian Thoroughfare types and their common abbreviations are
recognized and fully supported on input and output.
successfully.
Address Guidelines for Finland
For additional information about the Finland postal system, see the Posti kuluttajille website:
http://www.posti.fi/. Finnish postal codes are managed by Itella Corporation. For information, see
http://www.itella.fi/english/servicesandproducts/addressservices/postalcodeproducts/.
• Thoroughfare types—Finnish thoroughfare types and their common abbreviations are recognized
and fully supported on input and output. Swedish thoroughfare types are also supported.
52
Input
Address Guidelines for France
The Enterprise Geocoding Module offers several FRA databases including NAVTEQ street and
vintages.
For additional information about the French postal system, see the La Poste website:
http://www.laposte.com/.
• Virtual town names—Some areas are generally recognized as cities even though they are not
truly administrative cities. These areas represent Artificial City Areas, or Virtual Towns. Since
these virtual town names are commonly used by the public, they are supported and treated as
aliases for any of the encompassed towns. Returned candidates have the correct real town in
place of the input virtual town.
Note: Virtual town names are supported in TomTom database only. The NAVTEQ databases
(streets or points) do not support virtual town names.
Table 2: Virtual Towns in France
Virtual Town Name
Encompassed Real Towns
Défense (La)
Part of: Nanterre, Puteaux, Courbevoie
Sophia Antipolis
Part of: Valbonne, Mougins, Vallauris, Antibes, Biot
Cergy-Pontoise
Menucourt, Courdimanche, Puiseux-Pontoise, Osny,
Pontoise, Cergy, Vauréal, Neuville-sur-Oise,
Saint-Ouenl'Aumône, Jouy-le-Moutier, Eragny
Marne-la-Vallée
Bry-sur-Marne, Villiers-sur-Marne, Noisy-le-Grand,
Champs-sur-Marne, Emerainville, Noisiel, Lognes,
53
Input
Virtual Town Name
Encompassed Real Towns
Croissy-Beaubourg, Torcy, Collégien, Ferrières, BussySaint-Georges, Bussy-Saint-Martin,
Saint-Thibault-des-Vignes, Gouvernes, Conches,
Guermantes, Jossigny, Lagny-sur-Marne, Montévrain,
Chanteloup-en-Brie, Serris, Chessy, Coupvray,
Magny-le-Hongre, Bailly- Romainvilliers
Saint-Quentin-en-Yvelines
Elancourt, Verrière (La), Trappes, Montigny-le- Bretonneux,
Guyancourt, Voisins-le-Bretonneux, Magnyle- Hameau
Sénart
Tigery, Combs-la-Ville, Lieusaint, Moissy-Cramayel,
Saint-Pierre-du-Perray, Savigny-le-Temple, Réau, Nandy,
Cesson, Vert-Saint-Denis
Evry
Evry, Bondoufle, Courcouronnes, Lisses
Etang de Berre
Fos-sur-Mer, Miramas, Vitrolles, Istres
Isle-d'Abeau
Four, Isle d’Abeau (L’), Saint-Quentin-Fallavier, Vaulx-leMilieu, Villefontaine
• Common words and abbreviations—The geocoder handles common abbreviations that are
used in French addresses. It supports all the official French street type abbreviations plus a number
of unofficial street types to help improve geocoding efficiency. A partial list is:
Table 3: Common French Address Abbreviations
Street Type or Name
Abbreviation
Hauts
No abbreviation.
appartement
APP, APT, APPART
Saint
ST
54
Input
Street Type or Name
Abbreviation
Sainte
STE
rue
r
Charles de Gaulle
CDG
Regiment D’Infanterie de Marine
RIMA
Division Blindée
DB
• Directionals in addresses—Abbreviated street directionals are also handled on input and the
returned candidate displays the complete directional.
Table 4: Street Directionals
N
N.
Nord
S
S.
Sud
E
E.
Est
O
O.
Ouest
NE
N.E.
Nord-Est
SE
S.E.
Sud-Est
NO
N.O.
Nord-Ouest
55
Input
SO
S.O.
Sud-Ouest
• Ordinals and numbered street names—Input addresses can include ordinals such as 1er, 2e,
2nd, 2nde, 3e. All subsequent ordinal street names are designated with "e" or "ème". You can
also specify numbers in street names or express the numbers as words. For example, the following
street names are equivalent and can both be geocoded as part of an input address:
Rue du 4 septembre
Rue du quatre septembre
• House numbers with letters—House numbers can include letters, such as 85B Ave des
provinces.
• Postal box (BP) addresses—The geocoder can handle Postal Box (Boite Postale) addresses.
For the following input address, a close match candidate is returned with a result code of
S5HPNTSC-A.
AddressLine1: BP 112 2 Avenue CDG
PostalCode: 78150
City: Le Chesnay
Note that in this example, the street name CDG is returned as Charles de Gaulle and the
postcode is corrected. The BP itself is not returned.
• CEDEX addresses—The geocoder does not use CEDEX for geocoding but CEDEX will not
interfere with geocoding. CEDEX can be entered in AddressLine1, City, or PostalCode fields. The
CEDEX itself is not returned but the complete postcode is returned. For the following input address,
a close match candidate is returned with a result code of S5HPNTS--A.
AddressLine1: 17 Rue Louise Michel
PostalCode: 92301 CEDEX
City: Levallois-Perret
The postcode is returned but not a postal centroid (there is no Z in the ninth position of the return
code). The CEDEX itself is not returned.
• Paris address formats and arrondissements—Paris addresses typically have a different input
format. The house number appears after the street name rather than before the street name. The
geocoder handles this input format and geocodes correctly. Arrondissements (the last two digits
of the postcode) can be entered and the complete locality and postcode information is returned.
For the following input address, a close match candidate is returned with a result code of
S5HPNTSCZA.
AddressLine1: 7 Rue Beranger
PostalCode: 75003
City: Paris
The returned Locality field includes the arrondissement (district) information. The Paris region
includes 20 arrondissements, which are represented by the last two digit of the postcode (the first
56
Input
three digits are 750). A Paris address may be written with the last two digits only. For the following
input address, a close match candidate is returned with a result code of S5HPNTSC-A
AddressLine1: 51 Rue Lafitte
PostalCode: 09
City: Paris
The complete postcode (75009) is returned even though 09 (representing the ninth arrondissement)
was entered.
• Military addresses—Military addresses (including typical military address abbreviations) are
handled. The first two digits usually represent the department. The digits 00 represent military
addresses.
• Monaco addresses—The geocoder handles Monaco addresses. You can specify Monaco (or
the MCO or MC country codes) in the StateProvince input field. If you input a Monaco address as
France, the geocoder attempts to identify this and returns the Monaco candidate if possible. All
Monaco postcodes begin with the number 98.
• Overseas Territories addresses—The geocoder covers several French overseas territories. The
geocoder recognizes the unique French territorial ISO codes, and you can use these codes with
input addresses. The territories use the French 5 digit postal code system, but each territorial
postal code starts with 3 unique digits. The accompanying table summarizes the ISO codes, data
vintages, and unique postal codes of the covered French territories.
Table 5: French Overseas Territories
Territory Name
ISO 3116-1 Alpha-2
ISO 3116-1 Alpha-3
First 3 Digits of Postal
Code
Guadeloupe
GLP
GP
971
Martinique
MTQ
MQ
972
French Guiana
GUF
GF
973
Réunion
REU
RE
974
Mayotte
MYT
MY
976
You can also use the country code for France (FRA or FR). In that case, you can get candidates
from France, Monaco, and the territories if that city/town name occurs in both France and in one
or more of the territories. However if you explicitly specify MCO or a territorial country code, you
will get candidates from the specified country only, and not from France.
• Placename Support for User Dictionaries—If your user dictionary includes placenames, you
can geocode these placenames and that information is returned with candidates.
57
Input
• Additional Fields for Address Range and User Dictionaries—Additional fields can be created
and returned for both Address Range and Point user dictionaries. These additional fields can
contain any special information associated with an address. You cannot geocode using additional
fields, but additional field content is returned with each candidate
• Address point data— The FRA NAVTEQ Points database includes address point data. Address
point candidates return an S8 result code.
Address Guidelines for Great Britain
The Enterprise Geocoding Module offers several GBR databases including CodePoint, AddressPoint,
and AddressBase Premium. The AddressPoint, and AddressBase Premium databases are point-level
databases. Contact your sales representative for more information about licensing these databases.
Your Enterprise Geocoding Module database release notes identify the current database vintages.
optimum geocoding. For additional information on British addresses, see the Royal Mail website:
http://www.royalmail.com/.
• Street addresses—If you provide a street address, and either a town and state, or a postcode,
you can perform an address geocode. The geocoder will match your full address record against
its comprehensive geocoding database. Minor misspellings in street addresses are corrected in
the returned candidates.
• Post Office Box numbers—You can enter PO Box input in AddressLine1 in the format: [PO Box
or Post Box ] [number]. The number typically ranges from one digit to a maximum of six digits.
The acceptable formats for PO Box include the following. These formats are not case sensitive.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
PO BOX
P.O. BOX
P.O.BOX
PO.BOX
POST BOX
POST BOX Number
POST BOX No
POST BOX #
POST OFFICE BOX
POBOX
POB
POSTBOX
P.BOX
PBOX
P BOX
BOX
58
Input
• Locality—UK addresses may contain two localities – dependent locality and double dependent
locality, both of which you can enter in the Locality input field:
• Dependent Locality—Distinguishes an address when there are identically named thoroughfares
within the same postal town. For example, Winford, Bristol.
• Double Dependent Locality—Distinguishes addresses between similar or identically named
thoroughfares within the same locality. This can typically be a business park, estate park or
airport. For example, Brunel Way, Cranford Estate, Millbrook, Southampton.
A locality alias is not part of the postal address but can be used to help find addresses were the
town or postcode is unknown. For example, Rycote Lane, Rycote.
• Postal code—If you enter the postcode in the LastLine input field, you may use either the full
postcode or just the post district as long as other street information or post information is present.
If you enter the postcode in the PostalCode input field, you must use the complete postcode.
Providing both the town and postcode can produce better results. The geocoder corrects postcode
information and adds postcodes if your input does not already include them.
• Northern Ireland addresses—The AddressPoint, CodePoint, AddressBase Plus, and AddressBase
Premium databases include the same Northern Ireland data, accurate to the postcode centroid
level. The AddressPoint, AddressBase Plus, and AddressBase Premium databases are
supplemented with Northern Ireland postcode data from the Royal Mail source. This Northern
Ireland data has postcode centroid (result code S3) accuracy only. That is the highest level of
geocoding accuracy available for Northern Ireland addresses, even with the AddressPoint,
AddressBase Plus, and AddressBase Premium point database sources.
Address Guidelines for Germany
The Enterprise Geocoding Module offers several DEU databases including the NAVTEQ point
database. Contact your sales representative for more information about licensing these databases.
For additional information about the German postal system, see the Deutsche Post website:
http://www.deutschepost.de/.
Addresses must contain either a city or a postal code.
German addresses may contain some or all of the following address elements.
Table 6: German Address Elements
Address Element
Field
Example
Street address
AddressLine1
Muldenweg 2
59
Input
Address Element
Field
Example
Ort
City
Vaihingen an der Enz
Kreis
County
Ludwigsburg
Bundesland
StateProvince
Baden-Württemberg
Postcode
PostalCode
71665
Address Guidelines for Greece
For additional information on Greece addresses, see the Hellenic Post website: http://www.elta.gr.
successfully.
Address Guidelines for Hong Kong
For additional information on Hong Kong addresses, see guidelines on the Hong Kong postal website
http://www.hongkongpost.hk/en/about_us/tips/correct_address/index.html.
• Required fields — Addresses must contain a city. HKG does not consider postal codes in
addresses.
fully supported in input addresses.
• Common words and abbreviations — Common words, directionals, house number indicators,
• Numbers and numeric equivalents—Numbered streets are mapped to the named equivalents.
Note: Postal geocoding is not available with Hong Kong.
60
Input
Address Guidelines for Hungary
For additional information about the Hungarian postal system, see the Magyar Posta website:
http://posta.hu/.
• House number, floor number, and apartment numbers—The geocoder supports street
addresses with house number, floor, and apartment information. For example:
AddressLine1: Kavics utca 13 II/3
PostalCode: 1025
City: Budapest
This is interpreted as house number 13, floor Roman numeral 2, apartment number 13. This could
also be input as: Kavics utca 13 II em 3 ajtó.
Address Guidelines for Iceland
For additional information on Icelandic addresses, see the Iceland Post website:
https://www.postur.is/en/.
successfully.
Address Guidelines for India
The Enterprise Geocoding Module offers several IND databases including the TomTom street and
point databases and the Lepton database. Contact your sales representative for more information
about licensing these databases. Your Enterprise Geocoding Module database release notes identify
the current database vintages.
61
Input
For additional information about the India postal system, see the India Post website:
http://www.indiapost.gov.in.
• Common words and abbreviations in addresses—The geocoder recognizes common words
that are used in street names, directionals, building identifiers, and Points of Interest and can
successfully geocode addresses that use these common words. Common abbreviations are also
recognized within addresses.
• Point of Interest—The India geocoder can return S8 close match candidates based on a
placename combined with any valid locational input (town, locality, or postcode). Points of Interest
(POI) can include restaurants, hotels, police stations, banks, ATMs, hospitals, schools, stores,
and other businesses and organizations. Input placenames can be geocoded correctly even if
they include numbers, hyphens, various types of punctuation, abbreviations, or minor misspellings.
POI candidates also return sub locality, if that information is available in the data.
• Sub locality—The India geocoder can return SL sub locality candidates. This indicates a sub
locality (block or sector) street level match. An SL result code also requires a match on other
geographic input fields (city, district, or state).
• Street level geocoding— Street geocoded India addresses can return candidates based on
Placename/Point of Interest (S8 result code), sub locality (SL result code), and street centroid (S4
result code). Depending on your requirements, you may prefer to see some or all of these
candidates. These returns are controlled by API s and by selections in the Management Console
interface. See Matching Options on page 111 for coverage of the ReturnPOIWithStreet,
ReturnSublocalityCandidates, ReturnStreetCandidates, and other India-specific preferences.
• Address Point data— TomTom data starting with 2012.09 vintage includes address point data.
Address point candidates return an S8 result code.
Note: To take advantage of some features of the IND geocoder (including sub locality candidates
and address point data) you must use India Enterprise Geocoding Module data 2013.Q2 or
newer. The updated data vintages provide improved address matching, return sub locality
and place name with Exact match mode candidates, and return extended precision codes
along with other additional fields. See India Output on page 169 for details on the additional
fields that are unique to the India geocoder.
Address Guidelines for Indonesia
For additional information about the Indonesian postal system, see the Pos Indonesia website:
62
Input
http://www.posindonesia.co.id/. You can also see and search for Indonesian postcodes at
http://kodepos.posindonesia.co.id/.
• Required fields—Addresses must contain a street name and either a subdistrict, regency/city,
or postcode.
successfully.
Address Guidelines for Ireland
For additional information about the Ireland postal system, see the An Post website:
http://www.anpost.ie.
• Required fields—Addresses must contain a city. IRL has very limited postal code data.
abbreviations are recognized and fully supported on input and output. Following is a partial list of
recognized thoroughfare types. Many others are also recognized.
Table 7: Thoroughfare Types in Ireland
Pre Thoroughfare Types
Post Thoroughfare Types
Áirse
Street (Also: St.,ST,STR)
Ard
Terrace (Also: TCE)
Arda
Third
Ardán
Track (Also: TRK,TCK)
Ascaill
Vale
Barra
Valley
63
Input
Pre Thoroughfare Types
Post Thoroughfare Types
Bealach
View
Bogha
Village
Bóithrín
Walk (Also: WK)
Bóthar
Way (Also: WY)
Brí
Wood(s)
Bruach
Yard (Also: Yd.)
Búlbhard
• Common words and directionals—The geocoder recognizes common words and directionals
used in addresses and can geocode these addresses successfully. This is a partial list of common
words and directionals that are understood by the geocoder. Many other common words are also
handled.
an, na, a
Cuar, Circular
Cros, Cross
Thoir, East
Tosaigh, Front
Laistigh, Inner
Beag, Little
Lower
Main
Middle
Military
Nua, New
Thuaidh, North
Sean, Old
Lasmuigh, Outer
ear
Dara, Second
64
Input
Theas, South
Third
Uachtarach, Uacht, Upper
Thiar, West
Iartharach, Western
Saint, St, Naomh
retail, park, business, center, centre, shopping, office, mills,
shop, service, outlet
saint, station
The
Park
House
Building, Blgs
House, Hse, Hses
branch
• Directionals—The geocoder recognizes the following directionals: North, N, Nth, South, S, Sth,
East, E, Est, West, W, Wst, NE, NW Sea SW Lower, LW, LR, Upper, UP, Upp, Uppe, upr, Thuaidh,
Thoirm, Thiar, Theas
• Common abbreviations—The geocoder recognizes common abbreviations used in addresses
and can geocode these addresses successfully. This is a partial list of abbreviations that are
understood by the geocoder. Many other common abbreviations are also handled.
Table 8: Common Abbreviations
Word
Abbreviation
saint
st., st
great
gt., gt
north
n, nth
south
s, sth
east
e, est
west
w, wst
65
Input
Word
Abbreviation
northeast
ne
northwest
nw
southeast
se
southwest
sw
lower
lw, lr
upper
up, upp, uppe
mount
mnt, mt
and
&
football
f
club
c
limited
ltd
park
pk
estate
est
gardens
gdns
66
Input
Word
Abbreviation
building
bld
industrial
ind
industries
ind
number
num
center
cnt, centre
centre
cnt, center
country
co
market
mrkt
square
s
o+connell
oconnell
equivalents. Ordinals are also recognized in input addresses. For example, the following are all
recognized in an input address: um, first, one, 1st, primera, primeiras, primeiro dois, second, two,
2nd, segunda, segundos.
Address Guidelines for Iraq
For additional information about the Iraqi postal system, see the website: http://www.iraqipost.net/.
67
Input
Address Guidelines for Italy
For additional information about the Italy postal system, see the Posteitaliane website:
http://www.poste.it/.
• German language addresses—German address formats (common in the South Tyrol area of
Italy) are handled and geocoded correctly. Typical German thoroughfare types and abbreviations
are supported. For example, the street name Marienstraße could be abbreviated as Marienstr,
and the same candidate is returned. Note that regardless of whether strasse or straße is entered
as input, strasse is returned in the output candidate.
• Aliases for regions, localities, and provinces—Aliases can be used on input. For example,
Tuscany is an alias for the region of Toscana. When you geocode, the returned candidate matches
the user input. That is, if aliases were used then aliases are returned.
• Regions and provinces—For street geocoding, region names (which are entered in the
StateProvince field) are not used for geocoding purposes, but are returned. Province abbreviations
consisting of two letters are returned in the County field. Italy has 20 regions and 110 provinces.
• PO boxes—Post Office Box numbers are not used for address matching or geocoding purposes,
but this does not interfere with matching or geocoding. The PO Box information is not returned.
The following formats are recognized:
Casella Postale
CP
abbreviations are recognized and fully supported on input and output. Both Italian and German
thoroughfare formats are supported.
• Common words, abbreviations, and directionals—The geocoder recognizes common words,
directionals, house number indicators, and abbreviations used in addresses and can geocode
these addresses successfully.
equivalents. For example, if you enter the street name Via 42 Martiri, the street name
QUARANTADUE MARTIRI is returned. Ordinals are also recognized in input addresses.
Address Guidelines for Japan
For information on Japanese addresses, see the Japan Post website: http://www.post.japanpost.jp.
A typical Japanese address looks like this:
68
Input
The elements of this address are described in the following table.
Table 9: Japanese Address Elements
Address Element
Field Name
Prefecture
StateProvince
City (Shi)
County
Municipality Subdivision (Oaza)
City
City District (Chome)
Locality
Block/lot number
AddressLine1
Example
Block and lot numbers are the most
specific address elements. Japanese
addresses do not typically have street
names.
For multiline addresses in Kanji, the general pattern is to enter the postal code on the first line. On
the second line, enter the other address elements starting from largest (prefecture) to smallest. The
name of the recipient, business, or organization is entered on the third line. For example:
100-8994
69
Input
5 3
For multiline addresses using Western conventions, the order of address elements is reversed. For
example:
Tokyo Central Post Office
5-3, Yaesu 1-Chome
Chuo-ku, Tokyo 100-8994
Japanese addresses can be returned in the character set in which the address was entered. This
means that addresses entered in English (Latin character set) are returned in English and Japanese
addresses are returned in Japanese (Kanji character set).
By convention, Kanji Japanese addresses are written with the largest administrative division first
followed by the smaller area divisions, with the lot number last. English translated addresses can
maintain this Japanese addressing order. However, in some business practices the English translated
addresses are written with the smaller administrative units first in keeping with Westernized address
conventions. The Enterprise Geocoding Module accepts English language addresses in either
addressing convention. For example, either of the following address formats are acceptable.
Tokyo Shibuya-ku Hiroo 1-1-39
1-1-39 Hiroo, Shibuya-ku, Tokyo
Handling House Number Matches
In Japan given the irregular shape of street blocks and house numbers not being linear the next
closest number does not necessarily mean the closest house geographically. So, instead of returning
an address with the next closest house number a result without a house number is returned.
Handling House Number Matches
In Japan given the irregular shape of street blocks and house numbers not being linear the next
closest number does not necessarily mean the closest house geographically. So, instead of returning
an address with the next closest house number a result without a house number is returned.
Kyoto Addresses
In the city of Kytoto, the chome (an urban ward or district, AreaName 4) is a name rather than
numeric. This makes it more difficult to distinguish the chome from other numeric addreess elements.
Consider the following address:
Nishikubo Keihokuakashicho Ukyo-ku Kyoto-shi Kyoto-fu 601-0273
In this address, the data for the matching address contains the address elements:
AN4 (chome): Nishikubo
AN3 (subcity): keihokuakeshichou
AN2 (city): Kyoto-shi Ukyo-ku
There are other examples in which the source data for Kyoto addreesses does not have a chome
or for which a chome is present but no subcity (AreaName3) exists.
70
Input
Sapporo Addresses
Addersses In the city of Sapporo have a unique format than is different than the format for other
Japanese cities. Consider the following addresses:
5-26 Minami 2 Jo Nishi 6 Chome Sapporo
This address is interpreted as follows:
Minami 2 Jo -> means 2 blocks south of intersection
Nishi 6 Chome -> means 6 blocks west of intersection
Minami 2 Jo Nishi -> these combine to form the subcity name (AN3)
The directionals used in Sapporo addresses are;
KITA – north
MINAMI – south
NISHI – west
HIGASHI – east
There are many other variations of Sapporo addresses, including variable placement of chome,
reversal of chome and jo, and presence/absence and placement of block/lot. These factors can
make it difficult to return Sapporo addresses with exact accuracy.
Handling Concatenated Area Names
The AreaName3 (subcity) in addresses can appear as separate words, hyphenated, or concatenated.
For example:
ogi machi
ogi-machi
ogimachi
All of these variations can be recognized and the correct candidate is returned.
It is also common for addresses to be entered without spaces between the areanames. For example:
MASHIKO 2070 HAGAGUNMASHIKOMACHI TOCHIGI 3214299
This can be recognized and geocoded. The same address with a space between the AreaName3
(subcity) and AreaName2 (city) is also handled correctly:
MASHIKO 2070 HAGAGUN MASHIKOMACHI TOCHIGI 3214299
Handling WHATEVER COMES NEXT
.
71
Input
Address Guidelines for Latvia
For additional information about the Latvia postal system, see the Latvias Pasts website:
http://www.pasts.lv.
fully supported on input and output. The following table shows is a partial list of recognized
thoroughfare types. Many others are recognized.
Pre-Thoroughfare Types
AUGUSTA=AUGUSTA
KÂRÏA=KÂRÏA,K
KRIÐJÂÒA=KRIÐJÂÒA,KR
Post-Thoroughfare Types
ALEJA=ALEJA
BULVARIS=BULVARIS, BULVÂRIS, BOULEVARD, BLVD
CEÏÐ=CEÏÐ
DAMBIS=DAMBIS
GATVE=GATVE
IELA=IELA,STREET,STR
KRASTMALA=KRASTMALA
LAUKUMS=LAUKUMS
LINIJA=LINIJA
MAGISTRALE=MAGISTRALE
PIEKRASTE=PIEKRASTE
PROSPEKTS=PROSPEKTS
SETA=SETA
ÐOSEJA=ÐOSEJA
ÐÍÇRSIELA=ÐÍÇRSIELA
ÐÍÇRSLINIJA=ÐÍÇRSLINIJA
LAUKUMS=LAUKUMS
This is a partial list. Additional thoroughfare types are
recognized.
successfully.
72
Input
Address Guidelines for Lithuania
For additional information about the Lithuania postal system, see the Lietuvos paštas website:
http://www.post.lt.
successfully.
Address Guidelines for Macau
For additional information on Macau addresses, see the Macau Post website:
http://www.macaupost.gov.mo/.
• Required fields—Addresses must contain a city. MAC does not consider postal codes in addresses.
successfully.
Note: Postal geocoding is not available with Macau.
Address Guidelines for Malaysia
For information on Malaysian addresses, see the Pos Malaysia website: www.pos.com.my.
Some Malaysian addresses do not require a city or a postal code. For certain addresses, the
geocoder can obtain a geocode by using only street information, which can be a combination of
address number and street name, without any town or postal code.
73
Input
Address Guidelines for Malta
The Malta geocoder supports address locations in Malta. Follow these guidelines to provide input
that Geocode Address Global can successfully geocode. For additional information on Malta
addresses, see the Malta Post website: http://www.maltapost.com/
successfully.
Address Guidelines for Mexico
optimum geocoding. For additional recommendations about the Mexican postal system, see the
Correos de México website http://www.sepomex.gob.mx/Paginas/Home.aspx.
• Aliases for cities—You can input aliases for city names and still get a close match. For instance,
you could enter "Coyoacán" or "Miguel Hidalgo" and it would match to Mexico city.
Table 10: Aliases for Mexican Cities
Alias
Town
Mexico City/Ciudad de Mexico
La Magdalena Contreras
Álvaro Obregón
Azcapotzalco
Benito Juárez
Ciudad Madero
Coyoacán
Cuajimalpa de Morelos
Cuauhtémoc
Gustavo A. Madero
Iztacalco
Iztapalapa
Miguel Hidalgo
Milpa Alta
Tláhuac
Tlalpan
74
Input
Alias
Town
Venustiano Carranza
Xochimilco
Ciudad López Mateos
Atizapán de Zaragoza
Las Tortugas
Emiliano Zapata
Naucalpan
Naucalpan de Juárez
San Bernardo
San Bernardo Mixtepec
• Aliases for states—You can use state aliases and get a close match. For example, if you enter
"YUC" it would match to Yucatán.
Table 11: Aliases for Mexican States
State
Alias
Aguascalientes
AGS/AG/AGU
Baja California
Bassa California/Neder-Californië/BC/BJ/BN/ BAJ/B C
Baja California Sur
Bassa California del Sud/BCS/BS/BAS/B C S
Campeche
CAM/CP/CM
Chiapas
CHIS/CH/CU/CHP
Chihuahua
CHIH/CI/CL/CHU
75
Input
State
Alias
Colima
COL/CL/CH
Coahuila de Zaragoza
COAH/CU/CS/COA/CZ/C Z/Coahuila
Distrito Federal
Distretto Federale/DF/MDF/D F
Durango
DGO/DG/DUR
Guanajuato
GTO/GJ/GT/GUA
Guerrero
GRO/GR/GUE
Hidalgo
HGO/HG/HID
Jalisco
JAL/JA
México
Mexico/Mexiko/Meksiko/Messico/MEX/EM/MX
Michoacán de Ocampo
MICH/MH/MC/MIC/MO/M O/Michoacan
Morelos
MOR/MR
Nayarit
NAY/NA
Nuevo León
NL/NUE/N L
Oaxaca
OAX/OA
76
Input
State
Alias
Puebla
PUE/PU/PUB
Querétaro Arteaga
QRO/QA/QE/QDA/Q A/Queretaro
Quintana Roo
QROO/QR/QI/QRO/Q R/Q Roo
San Luis Potosí
San Luis Potosí
Sinaloa
SIN/SI
Sonora
SON/SO
Tabasco
TAB/TA/TB
Tamaulipas
TAMPS/TM/TAM
Tlaxcala
TLAX/TL/TLX
Veracruz de Ignacio de la Llave
VER/VZ/VE/VCL/Veracruz
Yucatán
Yucatan/YUC/YC/YU
Zacatecas
ZAC/ZT/ZA
• Numbers, numeric equivilants, and ordinals—Numbered streets are mapped to the named
equivalents. For example, you can input Calle 5 or Calle cinco and get the same returned
candidates. Ordinals are also recognized in input addresses. For example, the following are all
recognized in an input address: 5, CINCO, QUINTO, and QUINTA.
77
Input
• Directionals—The following directionals are recognized in input addresses: Norte, Oriente, Este,
Sur, Oueste, Occidente, Poniente, N, E, S, O, NE, NO, SE, SO, Noreste, Sudeste, Noroeste, and
Sudoeste.
• Address point data— The MEX NAVTEQ Points database includes address point data. Address
Address Guidelines for Montenegro
The Montenegro geocoder supports address locations in Montenegro. Follow these guidelines to
provide input that Geocode Address Global can successfully geocode. For additional information
on Montenegro addresses, see the Montenegro Post website: http://www.postacg.me/
successfully.
Address Guidelines for Netherlands
For additional information on Netherlands addresses, see the TNT Post website:
http://www.postnl.com//.
• Aliases for cities—Locality, town, and province aliases can be used on input. When you geocode,
the better matched input name (the official name or alias) is returned with the candidate.
• Post office box numbers—Post Office Box numbers are not used for address matching or
geocoding purposes, but this does not interfere with matching or geocoding. The PO Box information
is not returned. The following formats are recognized: Postbus, PostFach.
successfully.
78
Input
Address Guidelines for New Zealand
For additional information on New Zealand addresses, see the New Zealand Post website:
http://www.nzpost.co.nz/.
• Aliases for suburbs—The geocoder supports locally used suburb names in addition to the officially
recognized suburb names. For example, Rosedale is an alias of the official suburb name of Hargest.
successfully.
Address Guidelines for Norway
For additional information on Norway addresses, see the Posten Norge website:
http://www.posten.no/.
• Common words, abbreviations, and directionals—The geocoder recognizes common words,
directionals, house number indicators, and abbreviations used in addresses and can geocode
these addresses successfully. Following is a list of common words that are recognized. Other
other common words and abbreviations may also be recognized.
Common words
av, bak, bakerst de, dei, den, det e, ei, ein, eit, en, et for,
foran, fra, gammel i, imellom, Industriebygget, inntil, kort
lang, lille, lita, lite, liten. med, mellom nær, nærmest, nest,
ny og, over, overfor, på små, stor, til, under ved, ved siden
av
Sankt=St
Directionals
nord, øst, syd, vest
79
Input
• Numbers, equivalents, and ordinals—Numbered streets are mapped to the named equivalents.
Ordinals are also recognized in input addresses
Address Guidelines for Philippines
For additional information on Philippines addresses, see the Philippine postal website
http://www.philpost.gov.ph/www.philpost.gov.ph/.
• Required fields — Addresses must contain a city. PHL does not consider postal codes in
addresses.
fully supported in input addresses.
• Common words and abbreviations — Common words, directionals, house number indicators,
• Numbers and numeric equivalents—Numbered streets are mapped to the named equivalents.
Note: Postal geocoding is not available with Philippines.
Address Guidelines for Poland
For additional information on Poland addresses, see the Polish Post website:
http://www.poczta-polska.pl/.
successfully.
Address Guidelines for Portugal
The Enterprise Geocoding Module offers several PRT databases including the NAVTEQ point
database. Contact your sales representative for more information about licensing these databases.
80
Input
For additional information on Portugal addresses, see the CTT Portugal Post website:
http://www.ctt.pt.
successfully.
• Address point data— The PRT NAVTEQ Points database includes address point data. Address
Address Guidelines for Romania
For additional information on Romanian addresses, see the Romanian Post website:
http://www.posta-romana.ro/en For easy postal code lookup, see http://coduri.posta.co/en.
successfully.
Address Guidelines for Russia
For additional information on Russian addresses, see the Russian Post website:
http://www.russianpost.ru/
successfully.
81
Input
Address Guidelines for Serbia
The Serbia geocoder supports address locations in Serbia. Follow these guidelines to provide input
that Geocode Address Global can successfully geocode. For additional information on Serbia
addresses, see the Serbia Post website: http://www.posta.rs/default-eng.asp
successfully.
Address Guidelines for Singapore
For additional information on Singapore addresses, see the Singapore Post website:
http://www.singpost.com.
• PO box addresses—Post Office Box numbers are not used for address matching or geocoding
purposes, but this does not interfere with matching or geocoding. The PO Box information is not
returned. The following formats are recognized: P O Box, Locked Bag Service.
thoroughfare types. Others may also be recognized.
Table 12: Thoroughfare Types
Pre-thoroughfare types
lorong=lorong, lrg, lor, lorang
jalan=jalan, jln, jl
lengkong=lengkong, lkg
kallang=kallang
mount=mount, mt
upper=upper, upp
Post-thoroughare types
track=trk,tck
street=st
82
Input
road=rd
drive=dr
crescent=cr,cres,crescent,cresent
boulevard=bvd,blvd,bouleyard,boulvard
hill=hill
gate=gate
mall=mall
avenue=ave,av,avnue
link=lk
lane=l
walk=wk
green=grn
highway=hwy
quay=quay, qy
parkway=pwy
successfully. This is a partial list of common words, abbreviations, and directionals that are
recognized. Other common words may also be recognized.
Table 13: Common Words
Category
Words
Common words
and, ltd, international, industrial, plc, group, co, front, by,
bay
Articles of speech
the, at, a, an, blk
Building identifiers
center, centre, building, house, place, court, galleria, hotel,
park, complex, mart, temple, bank, exchange, station,
community, area, mosque, depertment, department, post
office, shrine, chambers, masjid, apartments, complex,
bureau, resort, lodge, harbour
monastery, convent, restaurant, golf course, estate,
campus, institute, university, facility, tunnel, libraray,
society, mansion, hub, beach, church, park, kiosk, mission,
83
Input
Category
Words
condominium, warehouse, hall, laboratories, hospital,
corporation, fire post, terminal, workshop, headquarters,
cemetery
plaza, villa, garden, gardens, tower, station, hall, lodge,
cottages, cottage, village, gurdwara, place
AYE=Ayer Rajah Expressway
BKE=Bukit Timah Expressway
CTE=Central Expressway
ECP=East Coast Parkway
KJE=Kranji Expressway
KPE=Kallang-Paya Lebar Expressway
PIE=Pan Island Expressway
SLE=Seletar Expressway
TPE=Tampines Expressway
Ctrl=Central
E=East
S=South
W=West
N=North
JLN=Jalan
CR=Crescent
GR=Grove
L=Lane
WK=Walk
LRG=Lorong
TG.=TANJONG
Directionals in addresses
North, N, Nth, South, S, Sth, East, E, Est, West, W, Wst,
NE, NW, SE, SW, T1, T2
84
Input
Address Guidelines for Slovakia
For additional information about the Slovakian postal system, see the Slovakia Post website:
http://www.posta.sk/.
• Required fields—Addresses must contain a street name and either a town or a postal code.
successfully.
Address Guidelines for Slovenia
For additional information about the Slovenia postal system, see the Slovenia Post website:
http://www.posta.si.
• Thoroughfare types—Slovenian thoroughfare types and their common abbreviations are
recognized and fully supported on input and output.
successfully.
Address Guidelines for South Africa
For additional information on South African addresses, see the South African Postal Service website:
http://www.postoffice.co.za/.
• Required fields—Addresses must contain a city. ZAF does not consider postal codes in addresses.
thoroughfare types. Many others are also recognized.
85
Input
Pre-thoroughfare types
alley=steeg
avenue=av,ave,avn,avenu
boulevard=blvrd,blvd,bvld,kringweg
close=cl,clse
corner=cor
court=crt,ct
crescent=cres,cr,singel,single,sgl,sng
drive=dr,dri,drv
road=roads,pad,ro,roa,rd,rds
freeway=freewa,fwy
highway=highwa,hwy
lane=ln
place=pl,plek
square=sq,square,plein
street=straat,str,strs,sts,stre,stree,streets,st
stret=stret
hill=heuwel
market=mark
promenade=wandelweg
way=weg
cul-de-sac=doodloopstraat,cul de sac
rylaan=rylaan,laan,rln
Post-thoroughfare types
Most pre-thoroughfare types can also be used as
post-thoroughfare types. Some additional post-thoroughfare
types may be recognized.
successfully. This is a partial list of common words and abbreviations that are recognized. Many
other common words are also handled.
Category
Words
Common words
h/v,hv,hoek van,cor,cn,c/r,corner,co,cnr.,cnr,corner of,c/o
Pre-address indicators
plaza, centre, office, building, mall, square, market, clinic,
school, lodge, estate, estates, floor, shop, store, station,
hospitaal, hospital, mine, shaft, airport, lughawe, mart,
arcade, department, complex, stand, shopping, unit, villa
86
Input
Category
Words
Towns
port, t1, t2, t3, t4, t5, t6, v1, v2, v3, v4, v6, unit, hill, proper,
ah, sp, industrial, municipality, township, city, last,
agricultural, plots, plotte, new, rural, area, nature, reserve,
estate, golf, school, course, institute, farms, farm, plaas,
mine
Surname-joining words
van, den, de, le, la, du, der, AH, du, von, van der, van den,
vander, vanden, mac
Articles of speech
the, at, a, an
Suburb indicators
proper, tide, glen, rand, nature, reserve, country, club, golf,
course, lake, lakes, kloof, view, valley, ah, ah., yard, village,
gardens, bazaar, ridge, township, tuine, industrial,
industrieël, industrieel, central, hill, natuurpark, grounds,
gronde, rif, heights, hoogte, club, sanctuary, grove, deep,
estate, estates, rail, flats, willows, farm, plaas, manor,
acres, interchange
doctor=dr, ductor, docter
professor=prof
dominee=ds
president=pres
saint=st
second=sec
third=thrd
fifth=fid
seventh=sev
eighth=eig
ninth=nin
captain=capt
general=genrl
extention=phase, ext, uitbreiding, utibrei, uitbr, sw
january=jan, januarie
february=feb, februarie
march=mar, maart
april=apr
may
june=jun, junie
july=jul, julie
august=aug, augustus
september=sep
october=oct, oktober
87
Input
Category
Words
november=nov
december=dec, desember
Directionals
noord, north, noordoos, north east, noordwes, north west,
no., nw., ne., oos, east, wes, west, nne., ene., ese., sse.,
ssw., wsw., wnw., nnw., westelike, western, suidelike,
southern, noordelike, northern, oostelike, eastern, suid,
south, suidoos, south east, suidwes, south west, sw., se.
Address Guidelines for Spain
For additional information about the Spain postal system, see the Spanish postal service website:
http://www.correos.es/.
• Supported languages—If a street has a Spanish name and Basque or Catalan alternate name,
the returned candidate street name will match the input. That is, if a Basque or Catalan street
name is used on input, then the Basque or Catalan alternate street name is returned as a close
match candidate. If the Spanish street name is input, the Spanish street name is returned.
• Abbreviations in addresses—The geocoder handles common abbreviations that are used in
Spanish addresses. This includes abbreviations for building types, floor indicators, titles, and
articles of speech. The geocoder also supports all the official Spanish street type abbreviations
plus a number of unofficial street types to help improve geocoding efficiency. Abbreviated street
directionals are also handled on input and the returned candidate displays the complete directional.
For example, input of Arroya Guadalpia N returns the street Arroya Guadalpia Norte.
N,Norte, Nort
North
S,Sur, Sud
South
E,Este, Est
East
O,Oeste, Oest
West
88
Input
Address Guidelines for Sweden
The Enterprise Geocoding Module offers several SWE databases including the NAVTEQ street and
vintages.
For additional information on Sweden addresses, see the Post Norden website:
http://www.posten.se/.
fully supported on input and output. Following is a list of some recognized thoroughfare types.
This is a partial list, and other thoroughfare types are also recognized.
ALLE, ALLÉ, BACKE, BULEVARDI, BULEVARD
DALLEN, ESPLANADI, GATAN, GATTAN, GATA
GATE, GATEN, GRANDEN, GRAND, GRÄND
GÅRD, GARD, KATU, KUJA, LERIG
LIDEN, PARKEN, PARK, PLAN, PORTTI
PROMENADEN, PROMENADER, RACE, RÅDE, RADE
RINNE, STIGEN, STIG, STRAND, SKOG
TIE, TORG, VAG, VAGEN, VÄGEN
VÄG, VAGAN, VÄGAN
successfully. Following is a list of some common words that are recognized. This is a partial list,
and other common words and abbreviations are also recognized.
andra, at, åt, av, bak, bakom, de, del
den, dens, emellan, en, for, för, fore, för
framfor, framföre, framme, fran, från, gamla, gammal, gammalt
i, in, infor, införe, intill, kort, lang, lång
liten, litens, med, mellan, motliggande, narheten, närheten
narmast, närmast, nord, Norra, ny, nya, och, ost
Ostra, Östra, over, över, pa, på, sidan, sma
små, Sodra, Södra, stor, syd, till, till, under
vast, väst, Vastra, Västra, via
• Address point data— The SWE NAVTEQ Points database includes address point data. Address
89
Input
Address Guidelines for Switzerland
The Switzerland geocoder supports locations in Switzerland and Liechtenstein. Follow these
guidelines to provide input that Geocode Address Global can successfully geocode. For additional
information on Swiss addresses, see the Swiss Post website: http://www.swisspost.ch/. For
additional information on the Liechtenstein postal system, see the Liechtenstein Post Corp website:
http://www.post.li/.
• Thoroughfare types—German, French, and Italian thoroughfare types and their common
abbreviations are recognized and fully supported on input and output. Over 300 thoroughfare
types are recognized.
• Common words and abbreviations—You can use German, French, and Italian common words,
directionals, house number indicators, and abbreviations that are typically used in addresses.
equivalents in German, French, or Italian. Ordinals are also recognized in input addresses.
Address Guidelines for Taiwan
For additional information on Taiwanese addresses, see the Taiwan Post website:
http://www.post.gov.tw/post/internet/u_english/index.htm
successfully.
Address Guidelines for Thailand
For additional information on Thailand addresses, see the Thailand Post website:
http://www.thailandpost.com.
90
Input
successfully.
Address Guidelines for Turkey
For additional information on Turkish addresses, see the Turkey PTT website: http://www.ptt.gov.tr.
fully supported on input and output. Examples of typical thoroughfare types and their abbreviations
are: Bulvar, Bulvari (boulevard) Cadde, Caddesi, Cd, Cad (avenue, lane) Mahalle, Mahallesi, Mah
(neighborhood, quarter) Sokak, Sk, Sokagi (street) Yolu, Yol (way, road) This is not a complete
list. Other thoroughfare types are also recognized.
successfully. This is a partial list of common words and abbreviations that are recognized. Many
other common words are also handled.
Category
Words
Articles of speech
ve
Directionals
Words representing north, south, east, west, northwest,
northeast, southeast, southwest
Buildings
bina, binasi, apartman ,kurma, yap; ev, konut, mesken ,ev
halki, yurt;zemin, taban, pist, kat
Area names
semt, semti, ent, sehir, kasaba, sehir halki, büyük kasaba
Levels or positions
yukarida, asagida, asagi, altta, üzerinde, altinda, arkasinda,
içinde, moda, ön, yanindaki, arasinda, sol, sag
91
Input
Category
Words
House number indicators
hayir., rakam, sayi, numara, miktar
DR (Doctor), Prof (Professor), IST (Istanbul)
Address Guidelines for Ukraine
For additional information on Ukrainian addresses, see the Ukrposhta website:
http://www.ukrposhta.com/www/upost_en.nsf/
• Required fields—Addresses must contain a city. UKR does not consider postal codes in addresses.
successfully.
Note: Postal geocoding is not available with Ukraine.
Address Guidelines for Uruguay
For additional information on Uruguayan addresses, see the Uruguay Postal Service website:
http://www.correo.com.uy/index.asp
• Required fields—Addresses must contain a city. URY does not consider postal codes in addresses.
successfully.
Note: Postal geocoding is not available with Uruguay.
92
Input
Address Guidelines for Venezuela
For additional information on Venezuelan addresses, see the IPOSTEL website:
http://www.ipostel.gob.ve/
• Required fields—Addresses must contain a city. House numbers are not available in the data.
VEN does not consider postal codes in addresses.
and abbreviations used in addresses and can geocode these addresses successfully.
Note: Postal geocoding is not available with Venezuela.
Address Guidelines for Yemen
For additional information about the Iraqi postal system, see the website: http://www.iraqipost.net/.
Address Guidelines for Africa
Geocode Address Global with the Africa database provides street-level, city, or geographic geocoding
for many African countries. These countries are bundled as the Africa database (Product Code
XA1).
Follow these guidelines to provide input that Geocode Address Global can successfully geocode
African addresses.
• Required fields—Addresses must contain a city.
successfully.
Note: Postal geocoding is generally not available with the African database. Morocco (MAR) is the
only country in the XA1 Africa database that has postal code data, and therefore the only
country in this database that supports postal geocoding.
93
Input
If the input includes a state/province or locality and that input is matched, it does contribute to a
higher candidate ranking. However, there is no penalty if state/province or locality is omitted or
unmatched.
Single Line Input
Instead of entering each address element in separate fields, you may enter the entire address in
the AddressLine1 input field.
For all countries except Japan, you can enter addresses in one or more of these single-line formats.
Note: Not all formats work may work for every country.
StreetAddress;PostalCode;City
StreetAddress;City;PostalCode
StreetAddress;City
StreetAddress;City;StateProvince;PostalCode
StreetAddress;Locality
StreetAddress;County;City
PostalCode;StreetAddress
PostalCode;StreetAddress;City
City;PostalCode;StreetAddress
Where:
• StreetAddress can be house number and street name in either order (with street type immediately
before or after the street name).
• City is the city or town. For Indonesia and Thailand, this is the subdistrict.
• Locality is the locality name. For Indonesia, this is the village.
• County is the county (or ename. For Chile, Philippines, and Thailand, this is the district. For
Indonesia, this is the regency/city.
• StateProvince is the postal abbreviation for the state or province.
• PostalCode is the complete postcode. For Brazil, PostalCode should be the complete eight-digit
postcode for the most accurate results. However, you can use a five-digit postcode.
Note: Not all of these address elements are used in every country.
Other single-line formats may also be acceptable for many countries.
94
Input
The matching accuracy for single line input is comparable to that of structured address input. The
performance of single line input addresses may be slightly slower than that of structured address
input.
For best results, use delimiters (comma, semicolon, or colon) between each address element. For
example,
Appeldam Oranjestad
Rua JOSE Anchieta;Luanda
University City Road Dubai
‫طريق المدينة الجامعية دبي‬
Capital Federal;Av. Corrientes;3702
18 Merivale St,South Brisbane,QLD,4101
Alser Strasse 16,1090,Wien
Boulevard Du 28 Novembre;Bujumbura
Sint-Jacobsstraat,49;8900;YPRES
Rue 1823; Cotonou
Rue 28.263 Ouagadougou
Shaikh Khalifa Bin Mohammad Street Al Moharraq
‫شارع الشيخ خليفة بن محمد المحرق‬
27 Guadeloape Street, Nassau
14th Street San Ignacio
Radnor Drive Hamilton
Calle 15 Santa Cruz de la Sierra
AV BICO TORTO,SERRA,29168334
Bonnetts Road Saint Michael
Kushimbara Road;Gaborone
26 Wellington Street East;Toronto;ON;M5E 1S2
1 Rue Halimand;1003;Lausanne
Camino Nueva La Rural 3905 9200000 Cerrillos
Yayingshi Rd,5100
Avenue du Docteur Jamot;Douala
Boulevard Patrice Lumumba;Kinshasa
95
Input
Avenue Coutassi;Brazzaville
Ruta 125 40405 Santo Domingo
Calle 30 Ciudad de la Habana
Krehlíkova 92,Brno 62700
schulstrasse 22,Dresden,01328
Gettrupvej 41,Holsted,6670
Calle 7 71101 San Cristobal
Hermano Miguel 2 Quito
Gamal Soliman Abu Soliman Street, Abou Ilghait
‫شارع جمال سليمان ابو سليمان أبو الغيط‬
Paseo de la Castellana 210,Madrid
Põhja Puiestee 23,10111
Framnäsvägen 16;02230;Espoo
131 rue de la République;La Défense
Avenue Gabriel Lendoye;Libreville
Flat 69 Victoria Street,Windsor,SL4 1EH
Leoforos Achaion 145 19009 Agia Triada
7 Avenida Villa Nueva
North Road Georgetown
Ignjata Joba 6, Dubrovnik, 20000
Pasaje B San Pedro Sula
Szegedi Gergely Utca 13,Debrecen,4000
JL Pecenongan, 10120
Gunjur Road,Marattahalli,560017
7 Irvine Court,East Wall
Jamila Street;Baghdad
Salthamrar 1 112 Reykjavík
Via del Canneto,03011
Queen Street 1 Kingston
Al Ebshehi Street Amman
96
Input
Taratibu Street;Mombasa
Wellington Road St. Peter Basseterre
First Circular Road, Green Belt
‫طريق الدائري االول الحزام االخضر‬
Shaikh Sabah Il-Salem Il-Sabah Street, Beirut
‫بيروت;شارع الشيخ صباح السالم الصباح بيروت‬
Mpilo Road; Maseru
Slengiu gatve 19, Klaipeda, 91001
Jâtnieku 79;Daugavpils;LV-5410
1 Rua Do Delegado;Nossa Senhora do Carmo
Avenue Moukhtar Soussi; 28630 Ain Harrouda
Urión 30,Col. Tlatilco,02860,Mexico,D.F.
Rue 97;Bamako
Avenida 24 De Julho;Maputo
Rue Ely ould Mohamed;Nouakchott
Victor Hugo Street Beau;Bassin
Presidential Way;Lilongwe
Jalan Chowrasta;10100;Seksyen 15
Katanga Street;Swakopmund
Avenue de I'Afrique;Niamey
39 Avenida NE Managua
Limpopo Street;Abuja
Dijkerstraat 40,Weert,6006
Ovre Varg Vei 17,3124,Tonsberg
56 Namata Road;One Tree Hill;Auckland;2001
Arab league Street, Masqat
‫شارع جامعة الدول العربية مسقط‬
Avenida 4 De Julio Ciudad de Panamá
Calle Felipe 101 31 Lima
Pleasant Drive, Caloocan City
97
Input
1 Maja 34;58260;Bielawa
Rua Alegre 79;4150;Porto
Artigas 2801 Asunción
Ahmed Bin Mohammad Bin Thany Street, Doha
‫شارع احمد بن محمد بن ثاني الدوحة‬
BULEVARDUL 1907 61 Giurgiu
53 Myakininskaya 5-ya ulitsa; 143420; Krasnogorsk
Avenue De La Gendarmerie;Kigali
King Faisal Bin Abdel Aziz Road, Hafr Il-Batin
‫طريق الملك فيصل بن عبدالعزيز حفر الباطن‬
Rue GY 501; Dakar
Boat Quay,Downtown Core,040000
Calle Padres Aguila, San Salvador
Henrystraat 8 Paramaribo
Brezová 6 Sliac 90000
celjskih knezov 9,3000,Celje
Frescativägen 33,10405,Stockholm
Mbangweni Street; Mbabane
Samsen Rd;Tanon Nakorn Chaisri;10300
De La Marina Boulevard;Lomé
Angelina San Juan-Laventille
Rue Aflatoun Ben;Arous
1631 4 Sokak 14,06020,Sancaktepe
202 Rueilong Road, 806, Cianjhen District
Kiyungi Street;Dar es Salaam
Rubaga Road; Kampala
Sadovyi provulok 24 Irpin
Calle Dr Teofilo Diaz, Colón Centro y Noroeste, Montevideo
calle Valdez Valencia
590 Lighthouse,Fynnlands
98
Input
Freedom Way, Kitwe
Kirwith Road, Bulawayo
If the input address is missing delimiters, spaces are recognized as separators and internal parsing
rules identify address elements. In the example above, the address would still successfully geocode
even if some or all of the delimiters were missing in the input.
Note: Non-delimited or partially-delimited single line addresses may take longer to geocode and
may not produce the same results as delimited single line input. This is especially true for
addresses with multi-word street names or cities. To optimize single line geocoding, use
delimiters between address elements (particularly between street name and city).
Punctuation is ignored for geocoding purposes.
Format for Japan
Japanese addresses are typically written in single line format, without any delimiters to separate
address fields. The typical format is:
<prefecture><city><municipality subdivision><city
district><block><lot><other>
where:
•
•
•
•
•
•
•
prefecture = ken
city = shi
municipality subdivision = oaza
city district = chome
block = numbered city block (ban)
lot = sub blocks or building number (go)
other = building names, flat numbers, or other identifiers. This information is ignored by the Japan
geocoder.
Note: Block and lot numbers are the most specific address elements in Japan. Japanese addresses
typically do not have street names.
Table 16: Example Japanese Addresses
Address
Description
Chome, block, and lot separated by a hyphens.
Block and lot separated by hyphen, chome indicated by
chome identifier.
99
Input
Address
Description
Chome, block, and lot separated by their identifiers.
Guidelines for Single Line Input
• For Great Britain, single line input is supported with the CodePoint (CP) and AddressPoint (AP)
datasets. Single line is not supported with the Streets (TomTom source) dataset.
• For Germany, France, and New Zealand, yYou must specify a value in either the PostalCode field
or the City field in order for single line input to successfully geocode.
• For Canada, iIf you omit the postal code and country, the geocoder still geocodes the address
based on street address, city, and province.
• Punctuation is generally ignored, however you may improve results and performance by using
separators (commas, semicolons, etc.) between different address elements.
• The country is not required. Each country geocoder assumes that the address is in its country.
• Firm information (placename, building name, or government building) is returned if available.
If you enter a street intersection as input, the geocoder will provide the coordinates of the intersection.
Note: Intersection geocoding is supported with the United Kingdom (GBR) Streets database. The
Streets data set (TomTom source) is packaged and licensed as a separate bundle.
Intersection geocoding is not available with the UK CodePoint or AddressPoint databases.
CodePoint (CP) is packaged with the EMEA bundle and AddressPoint (AP) is packaged and
licensed as a separate bundle.
Note: Intersection geocoding is not supported by the databases for Africa (XA1), Middle East
(XM1), or Latin America (XL2). The countries covered in these bundles have less
comprehensive street level coverage and very limited postal code coverage.
To enter an intersection, specify the two street names separated by a double ampersand (&&) in
AddressLine1. For some countries, the word AND can also be used to delimit intersections. The &&
delimiter can be used for all countries. For example:
AddressLine1: Rruga Myslym Shyri && Rruga Ibrahim Rugova
City: Tirana
AddressLine1: Calle esmeralda && Calle Marcelo T. Alvea
City: Cordoba
100
Input
AddressLine1: Ocean Ave && New South Head Rd
City: Woollahra
AddressLine1: Flurstraße && Batloggstraße
PostalCode: 6780
AddressLine1: Handelsstraat && Montoyerstraat
City: Brussel
Bass Lane && Frobisher Drive
City: Freeport
AddressLine1: AVENIDA VINTE E OITO DE MARÇO && AVENIDA JOSÉ ALVES AZEVEDO
PostalCode: 280
AddressLine1: Yonge && Wellington
City: Toronto
AddressLine1: Grüssenweg && Rührbergweg
City: Pratteln
AddressLine1: Avenida Los Carrera && Calle Peyronet
City: Quilpué
AddressLine1: Ruyi Rd && Huangge South Rd
PostalCode: 5180
AddressLine1: Goethe && Versailles
City: Limassol
AddressLine1: KREHLÍKOVA && ŠMAHOVA, BRNO
City: BRNO
AddressLine1: Muldenweg && Lorenzenstraße
City: Vaihingen an der Enz
AddressLine1: Østre Vindingevej && Naturparken
City: Roskilde
AddressLine1: Calle de Mérida && Calle del Perú
City: Salamanca
AddressLine1: Telliskivi && Rohu
City: Põhja-Tallinn
AddressLine1: Kalkkilahdentie && Saramäentie
PostalCode: 73410
AddressLine1: Chemin du Prieuré && Rue de la Montcient
City: Seraincourt
High Street && Winchester Road
City: Southampton
101
Input
AddressLine1: Akti Miaouli && Agias Marinas
City: Markopoulo Mesogaias
GRC also supports the Cyrillic character set:
AddressLine1: Ακτή Μιαούλη & Αγίας Μαρίνας
City: Μαρκοπούλου Μεσογαίας
Lai King Hill Road && Wa Lai Path
Kwai Tsing District
Addressline1: Ðure Kuntića && Prigorska ulica
City: Zagreb
AddressLine1: Síklaki hegy utca && Berek utca
City: Aszód
AddressLine1: JALAN PUSPO WARNO TENGAH && JALAN PUSPO WARNO SELATAN
PostalCode: 50142
AddressLine1: Arjunlal Road && Tilak Road
City: Ahmadabad City
AddressLine1: Mourne Rd && Comeragh Rd
City: DUBLIN
AddressLine1:Vegamótastigut&& Laugavegut
City:Reykjavik
AddressLine1:AL amerat&& Mansour
City:Bagdadh
AddressLine1: Via Balilla && Via Roma
City: Sant'Angelo Romano
AddressLine1: Zien Al Abedeen && Fatimea Bent Al Hasan
City: Amman
AddressLine1: Artoju gatve && Bražuoles gatve
City: Vilnius
AddressLine1: SKARNU IELA && KALKU IELA
City: Riga
Rua Norte && Patio Novo
Macau
AddressLine1: calle 5 && union
City: Naucalpan de Juárez
AddressLine1: Svetog Save && Mitropolita Pajsije
City: Berane
AddressLine1: JALAN MAWAR && JALAN BAKAWALI
PostalCode: 47100
102
Input
AddressLine1: Kruisbergstraat && Iepenstraat
PostalCode: 6444
City: Brunssum
AddressLine1: Wesselvegen && Tollmo
City: Skien
AddressLine1: Admiral Beatty Av && Hardley Av
City: Mount Roskill
AddressLine1: G. Tuazon && Calabash B
City: Manila City
AddressLine1: Grodkowska && Augustyna Kordeckiego
City: Nysa
AddressLine1: Caminho da Veiga && Caminho da Aveleira
City: Ponte de Lima
AddressLine1: Strada Metei Millo && Calea VictorieiCity: Bucharest
AddressLine1: Aleksandra Matrosova ulitsa && Sampsoniyevskiy Bol'shoy
City: Vyborgskaya Storona
RUS also supports the Cyrillic character set.
AddressLine1: Александра Матросова улица && Лесной проспект
Locality: Выборгская сторона
AddressLine1: Seng Poh Road && Seng Poh Lane
City: Bukit Merah
AddressLine1: Cretinjska && Hilandarska
City: Bukit Merah
AddressLine1: Opatovská && Mlynská
City: Trencín
AddressLine1: Plešivica pri Žalni && Lobcek
PostalCode: 1290
AddressLine1: Storgatan && Backagatan
City: Grimsås
AddressLine1: Soi Nok Kaew Noi 1 && Nak Niwat Rd
City: Lat Phrao
AddressLine1: ILERI SOKAK && ORDULAR SOKAK
PostalCode: 06570
AddressLine1: Yongsing Street && Wulong Street
City: Longan Township
AddressLine1: Revolyutsii vulytsya && Malynovs'koho vulytsya
City: Irpin
103
Input
AddressLine1: Avenida Luis A De Herrera && Calle Galatea
City: Montevideo
AddressLine1: Avenida Fuerzas Armadas && Avenida Urdaneta
City: Caracas
AddressLine1: Zubayr && Taiz
City: Sana'a
AddressLine1: Ferreira Street && Schlebusch Street
City: Henneman
Note: The double ampersand (&&) can always be used as an street intersection separator. For
some countries, you can use additional symbols or words to delimit street intersections.
All close match criteria are enforced for intersection geocoding, just as for any street level geocoding.
104
3 - Geocode Address
Global Options
Geocode Address Global includes geocoding, matching, and data options.
In this section
Geocoding Options
Matching Options
Data Options
106
111
129
Geocode Address Global Options
Geocoding Options
The following table lists the options that control how a location's coordinates are determined.
Note: As the EGM Module transitions its administrative tasks to a web-based Management Console,
labels for the options may use different wording than what you see in Enterprise Designer.
There is no difference in behavior.
Table 17: Default Geocoding Options for Finland
Option Name
Description
optionName
Parameter
Geocode level
Specifies how precisely you want to geocode addresses. One of the following:
GeocodeLevel
Street address
Option.GeocodeLevel
StreetAddress
Postal centroid
PostalCentroid
The geocoder attempts to geocode addresses to a street
address, but some matches may end up at a less precise
location such as a postal code centroid, intersection, or
shape path.
This option is not available for this country. For Argentina,
you must use NAVTEQ data for postal geocoding. The
majority of African countries and Middle Eastern countries
do not include postal code data, and therefore do not
support postal centroid geocoding.If postal code data is
available, the geocoder attempts to geocode addresses to
the most precise postal code it finds. The advantage of
postal code centroid matching is the speed of the operation.
The disadvantage of postal code matching is that the
geocoder only examines the PostalCode field. If you use
street address precision, the geocoder looks at both the
street name and the PostalCode field and attempts to return
street-level coordinates and optionally fall back to postal
code coordinates.
Geographic
centroid
The geocoder attempts to geocode addresses to the
geographic centroid of a city or state. This option is not
GeographicCentroid available for the United Kingdom (GBR).
106
Option Name
Description
optionName
Parameter
Address point interpolation
Interpolation
Option.Interpolation
Geographic centroid
FallbackToGeographic
Option.FallbackToGeographic
Postal centroid
FallbackToPostal
FallbackToPostal
Option.FallbackToPostal
Specifies whether to perform address point interpolation. This option only works if
you have a point database, installed. This option is available for selected countries
only.
Address point interpolation uses point data to refine geocode results. By default,
the geocoding process estimates the location of an address based on the street
numbers at either end of street segment. For example, if a street segment runs
from 100 Main St. to 200 Main St., then a request for 150 Main St. will return a
location in the middle of the segment. With interpolation, the geocoder finds the
position of 180 Main St. in the point data, and it is about two-thirds of the way down
the street. Using this information, the geocoder can estimate the position of 150
Main St. based on 100 and 180 Main St. In this case, the geocoder estimates the
location of the address slightly away from the center of the segment.
Y
Yes, perform address point interpolation.
N
No, do not perform address point interpolation.
Specifies whether to attempt to determine a geographic region centroid when an
address-level geocode cannot be determined. This option is not available for the
United Kingdom (GBR).
Y
Yes, determine a geographic centroid when an address-level centroid
cannot be determined. Default.
N
No, do not determine a geographic centroid when an address-level
centroid cannot be determined.
Specifies whether to attempt to determine a postal code centroid when an
address-level geocode cannot be determined.For Argentina, you must use NAVTEQ
data for postal geocoding.
This option is not available for Bahamas, Hong Kong, Macau, Philippines, Uruguay,
and Venezuela. For Argentina, you must use NAVTEQ data for postal
geocoding.The majority of African countries and Middle Eastern countries do not
include postal code data, and therefore do not support postal centroid geocoding.
Y
Yes, determine a postal code centroid when an address-level centroid
cannot be determined. Default.
N
No, do not determine a postal code centroid when an address-level
centroid cannot be determined.
107
Option Name
Description
optionName
Parameter
Offset from street
OffsetFromStreet
Option.OffsetFromStreet
Indicates the offset distance from the street segments to use in street-level
geocoding. The distance is specified in the units you specify in the Units field
OffsetUnits option.
Note: Offset is not supported for the United Kingdom (GBR) or Japan (JPN).
The default value varies by country. For most countries, the default is 7 meters.
For Austria, Germany, and Australia the default is 10 meters.
The offset distance is used in street-level geocoding to prevent the geocode from
being in the middle of a street. It compensates for the fact that street-level geocoding
returns a latitude and longitude point in the center of the street where the address
is located. Since the building represented by an address is not on the street itself,
you do not want the geocode for an address to be a point on the street. Instead,
you want the geocode to represent the location of the building which sits next to
the street. For example, an offset of 50 feet means that the geocode will represent
a point 50 feet back from the center of the street. The distance is calculated
perpendicular to the portion of the street segment for the address. Offset is also
used to prevent addresses across the street from each other from being given the
same point. The following diagram shows an offset point in relation to the original
point.
Street coordinates are accurate to 1/10,000 of a degree and interpolated points
are accurate to the millionths of a degree.
Offset from corner
OffsetFromCorner
Option.OffsetFromCorner
Specifies the distance to offset the street end points in street-level matching. The
distance is specified in the units you specify in the Units field OffsetUnits option.This
value is used to prevent addresses at street corners from being given the same
geocode as the intersection.
The default value varies by country:
• 12 meters—Australia (AUS), Austria (AUT), Germany (DEU)
108
Option Name
Description
optionName
Parameter
• 7 meters—For other supported countries, the default offset is 7 meters.
The following diagram compares the end points of a street to offset end points.
Units
OffsetUnits
Option.OffsetUnits
Specifies the unit of measurement for the street offset and corner offset options.
•
•
•
•
•
•
•
•
Feet
Feet
Miles
Miles
Meters
Meters
Kilometers
Kilometers
The default is Meters.
Point type
This option is available for Australia only.
GNAFPointType
For street address matching, specifies whether to return the parcel latitude/longitude
or the street frontage latitude/longitude. This option is available only if you have
the G-NAF database installed, and the database selected in the Database list on
the Data tab includes the G-NAF database. This option only affects addresses
matched to the G-NAF database.
Option.GNAFPointType
Parcel
P
In a street address match, return the exact location of the parcel.
This is the standard G-NAF point which is the exact authoritative
point returned by the G-NAF database. Default.
Street
frontage
In a street address match, return the street frontage point for the
parcel. The street frontage point is 12.5 meters from the front
109
Option Name
Description
optionName
Parameter
boundary of the parcel. Street frontage points are more suitable
for routing applications.
S
Return 8 decimal places of parcel
latitude/longitude
This option is available for Australia only.
Specifies whether to return the original latitude and longitude, precise up to eight
Return8DecimalPlaceParcelLatLong digits after the decimal. This is the latitude/longitude that the candidate matched
to in the G-NAF database. These are the original coordinates directly from the
Option.Return8DecimalPlaceParcelLatLong
G-NAF data prior to truncation or rounding. This option is available only if you have
the G-NAF database installed, and the database selected in the Database list on
the Data tab includes the G-NAF database. This option only affects addresses
matched to the G-NAF database.
Coordinate system
CoordinateSystem
Option.CoordinateSystem
Y
Yes, return the original latitude/longitude, up to eight digits after the
decimal.
N
No, do not return the original latitude/longitude.
A coordinate system is a reference system for the unique location of a point in
space. Cartesian (planar) and Geodetic (geographical) coordinates are examples
of reference systems based on Euclidean geometry. Spectrum™ Technology
Platform supports systems recognized by the European Petroleum Survey Group
(EPSG).
Each country supports different coordinate systems. Depending on the country,
you have one or more of the following options:
Return Parsed Address
IncludeInputs
EPSG:4230
Subset of WGS84.
EPSG:4283
Also known as the GDA94 coordinate system.
EPSG:4301
Also known as the Tokyo coordinate system.
EPSG:4326
Also known as the WGS84 coordinate system.
EPSG:27200
Also known as the NZGD49 coordinate system.
EPSG:27700
Also known as the British National Grid system.
Specifies whether to return the formatted input street address and each input
address element in a separate field. This feature can help you understand how the
input address was parsed and identify specific input elements that could not be
geocoded. For example, a returned HouseNumber.Input could contain an invalid
house number in your input address.
110
Option Name
Description
optionName
Parameter
Option.IncludeInputs
You can specify parsed input returns for a specific country. For example, a REST
API example for Canada is:
Option.CAN.IncludeInputs=Y
Note: Data vintage must be 2014 Q4 or newer to get Parsed Address Input
returns. Also note that Parsed Address Input elements are not returned
for every country.
Parsed Address Input elements are returned in separately labeled fields names
with a .Input extension. For example:
•
•
•
•
•
•
•
•
FormattedInputStreet.Input
City.Input
Country.Input
HouseNumber.Input
Locality.Input
PostalCode.Base.Input
StreetName.Input
StreetSuffix.Input
Other labeled fields are possible depending on the input address, country, and
data source.
Note: Parsed Address Input elements are not returned for every country. Also,
because Geocode Address World geocodes to the geographic or postal
level only (not street address), this does not return Parsed Address Input
For many countries, if part of the input address could not be recognized as a
specific address element, this content is returned in UnparsedWords.Input.
For intersection addresses, the first entered street is returned in StreetName.Input
and the second entered street name is returned in IntersectionStreet2.Input.
Matching Options
Matching options let you set match restrictions, fallback, and multiple match settings so that the
matching can be as strict or relaxed as you need. The strictest matching conditions require an exact
match on house number, street name, postal code and no fallback to postal code centroids. The
geocoder looks for an exact street address match within the postal code in the input address.
Relaxing the conditions broadens the area in which it searches for a match. For example, by relaxing
111
the postal code, the geocoder searches for candidates outside the postal code but within the city
of your input address.
Table 18: Default Matching Options for Finland
Option Name
Description
optionName
Parameter
Keep multiple matches
KeepMultimatch
Option.KeepMultimatch
MaxCandidates
Option.MaxCandidates
ReturnRanges
Option.ReturnRanges
Return ranges
MaxRanges
Option.MaxRanges
Specifies whether to return results when the address matches to multiple candidates
in the database. If this option is not selected, an address that results in multiple
candidates will fail to geocode.
If you select this option, specify the maximum number of candidates to return using
the MaxCandidates option (see below). next to the check box. Specify -1 (minus one)
to return all possible candidates.
Y
Yes, return candidates when multiple candidates are found. Default.
N
No, do not return candidates. Addresses that result in multiple candidates
will fail to geocode.
If you specify KeepMultimatch=Y, this option specifies the maximum number of results
to return. The default is 1. Specify -1 (minus one) to return all possible candidates.
Specifies whether to return address range information. If you enable this option, the
output field Ranges will be included in the output.
A range is a series of addresses along a street segment. For example, 5400-5499
Main St. is an address range representing addresses in the 5400 block of Main St. A
range may represent just odd or even addresses within a segment, or both odd and
even addresses. A range may also represent a single building with multiple units,
such as an apartment building.
Y
Yes, return address range information.
N
No, do not return address range information. Default.
If you choose to return ranges, this option specifies the maximum number of ranges
to return for each candidate. Since the geocoder returns one candidate per segment,
112
Option Name
Description
optionName
Parameter
Maximum ranges per candidate
and since a segment may contain multiple ranges, this option allows you to see the
other ranges in a candidate's segment.
MaxRangeUnits
If you choose to return ranges, this option specifies the maximum number of units
(for example, apartments or suites) to return for each range.
Option.MaxRangeUnits
Maximum units per range
For example, if you were to geocode an office building at 65 Main St. containing four
suites, there would be a maximum of four units returned for the building's range (65
Suite 1, 65 Suite 2, 65 Suite 3, and 65 Suite 4. If you were to specify a maximum
number of units as 2, then only two units would be returned instead of all four.
Expand candidates
This option applies to U.K. addresses only.
ExpandCandidates
Specifies whether to return multiple close matches (one for each delivery point on the
street). By default, if a street has multiple addresses/delivery points, Geocode Address
GBR returns a single close match, with each individual delivery point available as a
range.
Option.ExpandCandidates
Close matches only
CloseMatchesOnly
Option.CloseMatchesOnly
Match mode
Specifies whether to return only those geocoded results that are close match
candidates. For example, if there are 10 candidates and two of them are close
candidates, and you enable this option, only the two close matching candidates would
be returned instead of all 10. To specify what is considered a close match, use the
MustMatchClose match criteria options. Address candidates are ranked according
to how closely the input address matches these preferences.
Y
Yes, return only close matches.
N
No, do not return only close matches. Default.
Specifies how to determine whether a candidate is a close match. One of the following:
MatchMode
Custom
Option.MatchMode
CustomMode
Exact
ExactMode
This option allows you to specify which parts of a candidate
address must match the input address to be considered a close
match. Use the MustMatch<Element> optionsClose match
criteria check boxes to specify the address elements you want.
This is the default value for most countries.
All of a candidate address's elements must match in order for
the candidate to be considered a close match.
Note that for IND, Exact match mode returns the sub locality
and place name information
113
Option Name
Description
optionName
Parameter
Close
CloseMode
Relaxed
RelaxedMode
All input
Only the candidate address's house numberstreet name and
town must match in order for the candidate to be considered a
close match. For Chile, China, Great Britain, Estonia, India,
Indonesia, Latvia, Lithuania, Slovakia, Slovenia, Taiwan, and
South Africa, only the street name and town must match.
All candidate addresses are considered a close match. This is
the default value for Japan.
Specifies whether candidates must match all non-blank input fields to be considered
a close match. For example, if an input address contains a city and postal code, then
candidates for this address must match the city and postal code to be considered a
close match.
MustMatchInput
Option.MustMatchInput
House number
Y
Yes, a candidate must match all input to be considered a close match.
N
No, a candidate does not have to match all input to be considered a close
match. Default.
Specifies whether candidates must match the house number to be considered a close
match.
MustMatchHouseNumber
Option.MustMatchHouseNumber
House number data is not available for every country.
The Africa and Middle East countries do not generally have house numbers in the
data source.
Some countries covered in the Latin America database have house number data.
See Address Guidelines for Latin America for details of Latin America house
number and postal coverage.
If you select this option you should also require an exact match on street name. This
option does not significantly affect performance. It does, however, affect the type of
match if the candidate address corresponds to a segment that does not contain any
ranges. The type of match can also be affected when the house number range for a
candidate does not contain the input house number. If you relax the house number,
you should set the maximum ranges to be returned to a value higher than 0.
Y
Yes, a candidate must match the house number to be considered a close
match.
N
No, a candidate does not have to match the house number to be
considered a close match.
114
Option Name
Description
optionName
Parameter
Street
MustMatchStreet
Option.MustMatchStreet
Specifies whether candidates must match the street name to be considered a close
match.
This option is not used for this country.
If a close match is found, the geocoder attempts expanded street name manipulation,
which looks for candidates with names that sound like the input address or that are
spelled improperly. This slows down performance but increases the match rate . If
the geocoding database is indexed, the performance impact is reduced.
Locality
MustMatchLocality
Option.MustMatchLocality
Y
Yes, a candidate must match the street name to be considered a close
match.
N
No, a candidate does not have to match the street name to be considered
a close match.
Specifies whether candidates must match the locality (or equivalent) to be considered
a close match. The meaning of Locality varies for different countries.
If you do not require exact matches on locality, the geocoder searches on the street
address matched to the particular postal code, and considers other localities that do
not match the name, but do match the postal code.
The majority of African and Middle East countries do not use locality or equivalent as
part of an address. If a locality is matched it can contribute to a higher candidate
ranking, but there is no penalty if locality is omitted or unmatched.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
115
Option Name
Description
optionName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
116
Option Name
Description
optionName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
117
Option Name
Description
optionName
Parameter
•
•
•
•
•
•
•
•
City
MustMatchCity
Option.MustMatchCity
Y
Yes, a candidate must match the locality to be considered a close match.
N
No, a candidate does not have to match the locality to be considered a
close match.
Specifies whether candidates must match the city to be considered a close match.
For Japan, this field specifies whether the candidate must match the municipality
subdivision (oaza). If you do not require exact matches on city, the geocoder searches
on the street address matched to the particular postal code, and considers other cities
that do not match the name, but do match the postal code.
Specifies whether candidates must match the municipality subdivision (oaza) to be
considered a close match. If you do not require exact matches on city, the geocoder
searches on the street address matched to the particular postal code, and considers
other cities that do not match the name, but do match the postal code.
County
MustMatchCounty
Option.MustMatchCounty
Y
Yes, a candidate must match the city to be considered a close match.
N
No, a candidate does not have to match the city to be considered a close
match.
Specifies whether candidates must match the county (or equivalent) to be considered
a close match. The meaning of county varies for different countries.
The majority of countries in the Africa database (XA1) do not use a county or equivalent
as part of an address.
The majority of countries in the Middle East database (XM1) do not use a county or
The majority of countries in the Latin American database (XL1) do not use a county
•
•
•
•
118
Option Name
Description
optionName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
119
Option Name
Description
optionName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
120
Option Name
Description
optionName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
State/Province
Y
Yes, a candidate must match the county to be considered a close match.
N
No, a candidate does not have to match the county to be considered a
close match.
Specifies whether candidates must match the state or province (or equivalent) to be
MustMatchStateProvince
Option.MustMatchStateProvince
This option is not used for this country.
The majority of African and Middle East countries do not use a state/province or
equivalent as part of an address. If a state/province is matched it can contribute to a
higher candidate ranking, but there is no penalty if state/province is omitted or
unmatched.
• AGO (Angola)—Not used
• ARE (United Arab Emirates)—Not used
• ARG (Argentina)—Region or province
121
Option Name
Description
optionName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CHL (Chile)—State
IND (India)—State
122
Option Name
Description
optionName
Parameter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
123
Option Name
Description
optionName
Parameter
•
•
•
•
Postal code
Y
Yes, a candidate must match the state or province to be considered a
close match.
N
No, a candidate does not have to match the state or province to be
Specifies whether candidates must match the postal code to be considered a close
match. If you do not require exact match on postal codes, the geocoder searches a
wider area for a match. While this results in slower performance, the match rate is
higher because the request does not need to match exactly when it compares match
candidates.
MustMatchPostalCode
Option.MustMatchPostalCode
Specifies whether candidates must match the postal code to be considered a close
match. If you do not require exact match on postal codes, the geocoder searches a
wider area for a match. While this may result in slower performance, the match rate
is higher because the request does not need to match exactly when it compares match
candidates.
This field is not used in this country. For Argentina, you must use NAVTEQ data for
postal geocoding. The majority of African countries and Middle Eastern countries do
not include postal code data, and therefore do not support postal centroid geocoding.
Some countries covered in the Latin America database have postal code data. See
Address Guidelines for Latin America for details of Latin America house number
and postal coverage.
For India, the Postal code must match preference can be used for geographic
geocoding. This can produce better geographic matched candidates. For other
countries, Postal code match preference can be used with street or postal geocoding
only.
Y
Yes, a candidate must match the postal code to be considered a close
match.
N
No, a candidate does not have to match the postal code to be considered
a close match.
Prefer postal code over city
This option applies only to Australian addresses.
PreferPostalCodeOverCity
Specifies whether to return a close match when the postal code and street match
exactly but the city does not. If you enable this option, the City input field is ignored
Option.PreferPostalCodeOverCity
124
Option Name
Description
optionName
Parameter
if the postal code and street address are an exact match. If you do not enable this
option, there may be situations where street address and postal code input are an
exact match but the city name is not, and close matches are not returned.
For example, without this option enabled, the following input address would return no
close matches:
5 East St
GLENROY VIC 3046
With this option enabled, this same input address would return the following close
match:
5 EAST ST
HADFIELD VIC 3046
Y
Yes, return close matches if the postal code and street address are an
exact match and ignore the city input.
N
No, do not return close matches if the postal code and street address are
an exact match and the city is not. Default.
Candidate must have LDU
This option applies only to Canadian addresses.
MustMatchFullPostalCode
Specifies whether a candidate address must have a full postal code (FSA and LDU)
to be considered a close match.
Option.MustMatchFullPostalCode
Canadian postal codes are divided into two sections: the Forward Sortation Area
(FSA) and the Local Delivery Unit (LDU). For example, the postal code M6H 2P8 has
an FSA of M6H and an LDU of 2P8. Some candidate addresses may contain only
the FSA. This option allows you to prevent such addresses from being classified a
close match.
Y
Yes, the candidate address must contain a full postal code to be considered
a close match.
N
No, the candidate address does not have to contain a full postal code to
be considered a close match. Default.
Postal district
This option applies only to U.K. addresses.
MustMatchPostalDistrict
Specifies whether the postal district portion of the postcode must match in order for
the match to be considered a close match.
Option.MustMatchPostalDistrict
UK postcodes are divided into two sections: the outward code, which is to the left of
the space, and the inward code, which is to the right. The outward code represents
the postal district. For example, in the postcode CB3 OHH, the postal district is CB3,
which is Cambridge.
125
Option Name
Description
optionName
Parameter
First two postal code digits
This option applies only to Spanish addresses.
MustMatch2DigitPostalCode
Specifies whether the first two digits of the postcode must match in order for the match
to be considered a close match.
Option.MustMatch2DigitPostalCode
Return point of interest matches
with street matches
ReturnPOIWithStreet
Option.ReturnPOIWithStreet
This option applies only to Indian addresses.
Specifies whether to return both point of interest (POI) matches and street matches
when both street and POI information are provided in the input. If you select this
option, a POI candidate is returned with candidates that matched on street name. A
sub locality candidate returns an S8 result code. If you set this option to No, only
street information is returned.
Y
Yes, return POI information when both POI and street information are
provided on input. Default.
N
No, do not return POI information when both POI and street information
are provided on input.
Prefer point of interest matches
PreferPOIOverStreet
If you specify ReturnPOIWithStreet=Y enable the Return point of interest
matches with street matches option, the default behavior is to list the street name
matches first in the list of candidates (in other words, preferring the street matches).
However you can choose to return POI candidates first using this option. Consider
the following example:
Option.PreferPOIOverStreet
FirmName: India Gate
AddressLine1: Lodi Road
City: Delhi
If POIs are returned and street names preferred (the default settings), the following
candidates are returned in the order listed. Note that the street name candidates are
at the top with the India Gate POI candidate (S8 result code) listed last. If POIs were
preferred over street candidates, the India Gate candidate would be listed first.
StreetName FirmName PostalCode Locality
City
ResultCode
Lodi Road
100003
Lodi Colony Delhi
S4-PNTSC-A
Lodi Road
100013
Nizamuddin Delhi
West
S4-PNTSC-A
126
Option Name
Description
optionName
Parameter
StreetName FirmName PostalCode Locality
City
ResultCode
Lodi road
Delhi
S8H----C-A
India Gate
100013
India Gate
Return sub locality candidates
Y
Yes, return POI candidates first in the list of candidates.
N
No, do not return POI first in the list of candidates. Return street matches
first. Default.
ReturnSublocalityCandidates
Specifies whether to return a sub locality (block or sector) match. A sub locality
candidate returns an SL result code, and requires a match on other geographic input
Option.ReturnSublocalityCandidates
fields (city, district, or state). You can combine this with the Return street candidates
preference to get both SL and S4 candidates.
Y
Yes, return sub locality SL candidates. Default.
N
No, do not return sub locality candidates.
Return street candidates
ReturnStreetCandidates
Specifies whether to return a street match. A street candidate returns an S4 result
code. You can combine this with the Return sub locality candidates preference to get
both S4 and SL candidates.
Option.ReturnStreetCandidates
Y
Yes, return street S4 candidates. Default.
N
No, do not return street candidates.
Return locality candidates
ReturnLocalityCandidates
Specifies whether to explicitly return a geographic locality (G4) match in preference
to a town (G3) candidate.
Option.ReturnLocalityCandidates
Y
Yes, prefer geographic G4 candidates. Default.
N
No, do not prefer G4 candidates.
If both Return locality candidates and Return town candidates are true (the default in
Management Console), it is possible that only a town or a locality candidate will be
returned, even though both types of geographies exist.
127
Option Name
Description
optionName
Parameter
Return town candidates
ReturnTownCandidates
Specifies whether to explicitly return a geographic town (G3) match in preference to
a locality (G4) candidate.
Option.ReturnTownCandidates
Y
Yes, prefer geographic G3 candidates. Default.
N
No, do not prefer G3 candidates.
If both Return town candidates and Return locality candidates are true (the default
Management Console), it is possible that only a town or a locality candidate will be
returned, even though both types of geographies exist.
Place Name
MustMatchPlaceName
Specifies whether a candidate address must match the place name to be considered
a close match.
Option.MustMatchPlaceName
Sort candidates using locale
Y
Yes, the candidate address must match the place name to be considered
a close match. Default.
N
No, the candidate address does not have to match the place name to be
This is a Reverse geocoding option that applies to Greece, Russia, Ukraine, and any
other country that supports dual character sets (such as the Middle East countries).
SortCandidatesUsingLocale
Specifies whether candidates are sorted and returned based on the input language.
Option.SortCandidatesUsingLocale That is, if the input was in Russian, the Russian character candidate is returned first
followed by the English language candidate. This will override the dictionary order.
Y
Yes, candidates are sorted and returned based on input language.
N
No, candidates are returned in the order that the dictionary was added to
the database, regardless of input language.
You may want to use a balanced strategy between match rate and geographic precision. That is,
you may want to geocode as many records as possible automatically, but at the same time want to
minimize the number of weaker matches (false positives). For example, false positives can occur
when the geocoder:
• finds a street that sounds like the input street.
• finds the same street in another city (if postal code match is not required).
• finds the street but with a different house number (if house number is not required).
The following settings may achieve a good balance between match rate and precision:
128
•
•
•
•
•
CloseMatchesOnlyClose matches only—Specify "Y"Select this option.
Close match criteria—Select House number and Street only.
MustMatchHouseNumber—Specify "Y".
MustMatchStreet—Specify "Y".
FallbackToPostalPostal centroid—Specify "N"Do not select this fallback level.
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 Pitney Bowes 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 19: Default Data Options for Finland
optionName
Description
Option Name
Parameter
Database
Database
Specifies the database to be used for geocoding. Only databases that have been
defined in the Management Console are available.
Option.Database
Database preference
Specifies which geocoding databases to use. One of the following:
DatabasePreference
Prefer custom database
Option.DatabasePreference
PreferCustom
Use both standard databases and custom
databases, but give preference to candidates from
custom databases. Use this option if you feel your
129
optionName
Description
Option Name
Parameter
custom database is superior to the standard
database.
Prefer standard database
PreferStandard
databases, but give preference to candidates from
standard databases.
Use custom databases only Use only custom databases. Ignore standard
databases.
CustomOnly
Use standard databases only Use only standard databases. Ignore custom
databases.
StandardOnly
Use both custom and
standard databases
Both
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 on page 174.
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.
130
optionName
Description
Option Name
Parameter
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.
131
4 - Output
The geocoder returns the latitude/longitude, standardized address, and
result indicators. Result indicators describe how well the geocoder matched
the input address to a known address and assigned a location; they also
describe the overall status of a match attempt. If you are using the API, t
T he output returned is in the DataTable class. For information on the
DataTable class, see the "API Fundamentals" section of the Spectrum™
Technology Platform API Guide .
In this section
Address Output
Geocode Output
Result Codes
133
160
160
171
174
Output
Address Output
The address may be identical to the input address if the input address was accurate, or it may be
a standardized version of the input address, or it may be a candidate address when multiple matches
are found.
Note: Australia has several unique output fields related to the Australian Geocoded National
Address File database. See Australia G-NAF Database Output on page 160 for details.
Note: Canada has several unique output fields. database. See Canada Output on page 166 for
details.
Note: UK has several unique output fields. See United Kingdom Output on page 167 for details.
Note: India has several unique output fields. See India Output on page 169 for details.
Note: Netherlands has a unique output fields. See Netherlands Output on page 169 for details.
Note: New Zealand has several unique output fields. See New Zealand Output on page 170 for
details.
Table 20: Address Output for Finland
Field Name
Description
columnName
Response Element
AddressLine1
First line of the address.
AddressLine2
Second line of the address.
ApartmentLabel
The type of unit, such as apartment, suite, or lot.
ApartmentLabel.Input
The type of unit, such as apartment, suite, or lot as it was input.
133
Output
Field Name
Description
columnName
Response Element
ApartmentNumber
Unit number.
ApartmentNumber.Input
Unit number as it was input
City
The municipality name.
For Japan, the municipality subdivision (sub-city)
City.Input
The municipality name as it was input. For Japan, the municipality subdivision
(sub-city)
Country
The three-letter ISO 3166-1 Alpha 3 country code.
For Aruba, the country code is ABW
For Angola, the country code is AGO
For United Arab Emirates, the country code is ARE.
For Argentina, the country code is ARG.
For Australia, the country code is AUS.
For Austria, the country code is AUT.
For Bahrain, the country code is BHR.
For Belgium, the country code is BEL.
For Burundi, the country code is BDI.
For Benin, the country code is BEN.
For Burkina Faso, the country code is BFA.
For Bahamas, the country code is BHS
For Belize, the country code is BLZ
For Brazil, the country code is BRA.
For Bermuda, the country code is BMU
For Bolivia, the country code is BOL
For Botswana, the country code is BWA.
For Barbados, the country code is BRB
134
Output
Field Name
Description
columnName
Response Element
For Canada, the country code is CAN.
For Switzerland, the country code is CHE.
For Chile, the country code is CHL.
For China, the country code is CHN.
For Cameroon, the country code is CMR.
For Democratic Republic of Congo, the country code is COD.
For Congo, the country code is COG.
For Costa Rica, the country code is CRI
For Cuba, the country code is CUB
For the Czech Republic, the country code is CZE.
For Germany, the country code is DEU.
For Denmark, the country code is DNK.
For Dominican Republic, the country code is DOM
For Ecuador, the country code is ECU
For Spain, the country code is ESP
For Egypt, the country code is EGY
For Estonia, the country code is EST
For Finland, the country code is FIN
For France, the country code is FRA
For Gabon, the country code is GAB
For the United Kingdom, the country code is GBR
For Ghana, the country code is GHA.
For Greece, the country code is GRC
For Guatemala, the country code is GTM
For Guyana, the country code is GUY
For Hong Kong, the country code is HKG
For Honduras, the country code is HND
For Croatia, the country code is HRV
For Hungary, the country code is HUN.
For Indonesia, the country code is IDN
For India, the country code is IND
For Ireland, the country code is IRL
135
Output
Field Name
Description
columnName
Response Element
For Iraq, the country code is IRQ
For Iceland, the country code is ISL
For Italy, the country code is ITA
For Jamaica, the country code is JAM
For Japan, the country code is JPN
For Jordan, the country code is JOR
For Kenya, the country code is KEN
For Saint Kitts and Nevis, the country code is KNA
For Kuwait, the country code is KWT
For Lebanon, the country code is LBN
For Lesotho, the country code is LSO
For Lithuania, the country code is LTU
For Latvia, the country code is LVA
For Macau, the country code is MAC
For Morocco, the country code is MAR
For Mexico, the country code is MEX
For Mali, the country code is MLI.
For Mozambique, the country code is MOZ
For Mauritania, the country code is MRT
For Mauritius, the country code is MUS
For Malawi, the country code is MWI
For Malaysia, the country code is MYS
For Namibia, the country code is NAM
For Niger, the country code is NER
For Nigeria, the country code is NGA
For Nicaragua, the country code is NIC
For the Netherlands, the country code is NLD
For Norway, the country code is NOR
For New Zealand, the country code is NZL
For Oman, the country code is OMN
For Panama, the country code is PAN
For Peru, the country code is PER
136
Output
Field Name
Description
columnName
Response Element
For Poland, the country code is POL
For Philippines, the country code is PHL
For Portugal, the country code is PRT
For Paraguay, the country code is PRY
For Qatar, the country code is QAT
For Romania, the country code is ROM
For Russia, the country code is RUS
For Rwanda, the country code is RWA
For Saudi Arabia, the country code is SAU
For Senegal, the country code is SEN
For Singapore, the country code is SGP
For El Salvador, the country code is SLV
For Slovakia, the country code is SVK
For Slovenia, the country code is SVN
For Suriname, the country code is SUR
For Sweden, the country code is SWE
For Swaziland, the country code is SWZ
For Togo, the country code is TGO
For Thailand, the country code is THA
For Trinidad and Tobago, the country code is TTO
For Tunisia, the country code is TUN
For Turkey, the country code is TUR
For Taiwan, the country code is TWN
For Tanzania, the country code is TZA
For Uganda, the country code is UGA
For Ukraine, the country code is UKR
For United States, the country code is USA
For Uruguay, the country code is URY
For Venezuela, the country code is VEN
For Yemen, the country code is YEM
For Zambia the country code is ZMB
For Zimbabwe the country code is ZWE
137
Output
Field Name
Description
columnName
Response Element
For South Africa, the country code is ZAF
Addresses for countries that do not have a dedicated geocoding stage return the
country code associated with the input address. For example, Vatican City
addresses return VAT in the Country field, regardless of whether VAT or ITA (Italy)
was passed as the country code. Similarly, addresses in Martinique return MTQ
(rather than FRA) in the Country field.
AND (Andorra)—Addresses from Andorra are geocoded by Geocode Address
ESP (Spain) .
GIB (Gibraltar)—Addresses from Gibraltar are geocoded by Geocode Address
ESP (Spain) .
GLP (Guadeloupe) — Addresses from Guadeloupe are geocoded by Geocode
Address FRA (France).
GUF (French Guiana ) — Addresses from French Guiana are geocoded by
Geocode Address FRA (France).
MCO (Monaco)—Addresses from Monaco are geocoded by Geocode Address
FRA (France).
MTQ (Martinique) — Addresses from Martinique are geocoded by Geocode
MYT (Mayotte) — Addresses from Mayotte are geocoded by Geocode Address
FRA (France).
REU (Réunion) — Addresses from Réunion are geocoded by Geocode Address
FRA (France).
SMR (San Marino)—Addresses from San Marino contain ITA (Italy) in the Country
field.
VAT (Vatican City)—Addresses from Vatican City contain ITA (Italy) in the Country
field.
Country.Input
The three-letter ISO 3166-1 Alpha 3 country code as it was input.
For Aruba, the country code is ABW
For Angola, the country code is AGO
For United Arab Emirates, the country code is ARE.
For Argentina, the country code is ARG.
For Australia, the country code is AUS.
For Austria, the country code is AUT.
For Bahrain, the country code is BHR.
For Belgium, the country code is BEL.
138
Output
Field Name
Description
columnName
Response Element
For Burundi, the country code is BDI.
For Benin, the country code is BEN.
For Burkina Faso, the country code is BFA.
For Bahamas, the country code is BHS
For Belize, the country code is BLZ
For Brazil, the country code is BRA.
For Bermuda, the country code is BMU
For Bolivia, the country code is BOL
For Botswana, the country code is BWA.
For Barbados, the country code is BRB
For Canada, the country code is CAN.
For Switzerland, the country code is CHE.
For Chile, the country code is CHL.
For China, the country code is CHN.
For Cameroon, the country code is CMR.
For Democratic Republic of Congo, the country code is COD.
For Congo, the country code is COG.
For Costa Rica, the country code is CRI
For Cuba, the country code is CUB
For the Czech Republic, the country code is CZE.
For Germany, the country code is DEU.
For Denmark, the country code is DNK.
For Dominican Republic, the country code is DOM
For Ecuador, the country code is ECU
For Spain, the country code is ESP.
For Egypt, the country code is EGY.
For Estonia, the country code is EST.
For Finland, the country code is FIN.
For France, the country code is FRA.
For Gabon, the country code is GAB.
For the United Kingdom, the country code is GBR.
For Ghana, the country code is GHA.
139
Output
Field Name
Description
columnName
Response Element
For Greece, the country code is GRC.
For Guatemala, the country code is GTM
For Guyana, the country code is GUY
For Hong Kong, the country code is HKG.
For Honduras, the country code is HND
For Croatia, the country code is HRV.
For Hungary, the country code is HUN.
For Indonesia, the country code is IDN.
For India, the country code is IND.
For Ireland, the country code is IRL.
For Iceland, the country code is ISL.
For Iraq, the country code is IRQ
For Italy, the country code is ITA.
For Jamaica, the country code is JAM
For Japan, the country code is JPN
For Jordan, the country code is JOR
For Kenya, the country code is KEN.
For Saint Kitts and Nevis, the country code is KNA
For Kuwait, the country code is KWT.
For Lebanon, the country code is LBN.
For Lesotho, the country code is LSO.
For Lithuania, the country code is LTU.
For Latvia, the country code is LVA.
For Macau, the country code is MAC.
For Morocco, the country code is MAR.
For Mexico, the country code is MEX.
For Mali, the country code is MLI.
For Mozambique, the country code is MOZ.
For Mauritania, the country code is MRT.
For Mauritius, the country code is MUS
For Malawi, the country code is MWI.
For Malaysia, the country code is MYS.
140
Output
Field Name
Description
columnName
Response Element
For Namibia, the country code is NAM.
For Niger, the country code is NER.
For Nigeria, the country code is NGA.
For Nicaragua, the country code is NIC
For the Netherlands, the country code is NLD.
For Norway, the country code is NOR.
For New Zealand, the country code is NZL.
For Oman, the country code is OMN.
For Panama, the country code is PAN
For Peru, the country code is PER
For Poland, the country code is POL.
For Philippines, the country code is PHL.
For Portugal, the country code is PRT.
For Paraguay, the country code is PRY
For Qatar, the country code is QAT.
For Romania, the country code is ROM.
For Russia, the country code is RUS.
For Rwanda, the country code is RWA.
For Saudi Arabia, the country code is SAU.
For Senegal, the country code is SEN.
For Singapore, the country code is SGP.
For El Salvador, the country code is SLV
For Slovakia, the country code is SVK.
For Slovenia, the country code is SVN.
For Suriname, the country code is SUR
For Sweden, the country code is SWE.
For Swaziland, the country code is SWZ.
For Togo, the country code is TGO.
For Thailand, the country code is THA.
For Trinidad and Tobago, the country code is TTO
For Tunisia, the country code is TUN.
For Turkey, the country code is TUR.
141
Output
Field Name
Description
columnName
Response Element
For Taiwan, the country code is TWN
For Tanzania, the country code is TZA.
For Uganda, the country code is UGA.
For Ukraine, the country code is UKR
For United States, the country code is USA
For Uruguay, the country code is URY
For Venezuela, the country code is VEN
For Yemen, the country code is YEM
For Zambia the country code is ZMB
For Zimbabwe the country code is ZWE
For South Africa, the country code is ZAF.
Addresses for countries that do not have a dedicated geocoding stage return the
country code associated with the input address. For example, Vatican City
addresses return VAT in the Country field, regardless of whether VAT or ITA (Italy)
was passed as the country code. Similarly, addresses in Martinique return MTQ
(rather than FRA) in the Country field.
AND (Andorra)—Addresses from Andorra are geocoded by Geocode Address
ESP (Spain) .
GIB (Gibraltar)—Addresses from Gibraltar are geocoded by Geocode Address
ESP (Spain) .
GLP (Guadeloupe) — Addresses from Guadeloupe are geocoded by Geocode
GUF (French Guiana ) — Addresses from French Guiana are geocoded by
Geocode Address FRA (France).
MCO (Monaco)—Addresses from Monaco are geocoded by Geocode Address
FRA (France).
MTQ (Martinique) — Addresses from Martinique are geocoded by Geocode
MYT (Mayotte) — Addresses from Mayotte are geocoded by Geocode Address
FRA (France).
REU (Réunion) — Addresses from Réunion are geocoded by Geocode Address
FRA (France).
SMR (San Marino)—Addresses from San Marino contain ITA (Italy) in the Country
field.
VAT (Vatican City)—Addresses from Vatican City contain ITA (Italy) in the Country
field.
142
Output
Field Name
Description
columnName
Response Element
County
The majority of countries in the Africa database (XA1) do not use a county or
The majority of countries in the Middle East database (XM1) do not use a county
The majority of countries in the Latin American database (XL1) do not use a county
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
143
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
144
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
145
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
This field is not used with countries included with the African bundle (Product Code
XA1). These African countries generally have less comprehensive address
coverage.
Code XM1). These African countries generally have less comprehensive address
coverage.
(Product Code XL1). These African countries generally have less comprehensive
address coverage.
Note: If you enter addresses with the Andorran country code (AND), only
Andorran addresses are returned, including the AND country code. If you
enter an Andorran with a country code of Spain (ESP), you will still get
Andorran candidates, but with the ESP country code.
The region name.
The region name or alias. For example, Osrednjeslovenska/Ljubljana.
The district name.
The kommun name.
The district name.
FirmName
Name of the company or a place name.
FirmName.Input
Name of the company or a place name as it was input.
146
Output
Field Name
Description
columnName
Response Element
FormattedInputStreet.Input
The street as it was input.
Geocoder.MatchCode
HouseNumber
The buildinglot number for the matched location.
For Japan, this field contains the lot number.
HouseNumber.Input
The buildinglot number for the matched location as it was input
HouseNumberHigh
The highest house number of the range in which the address resides.
HouseNumberLow
The lowest house number of the range in which the address resides.
HouseNumberParity
Indicates if the house number range contains even or odd numbers or both.
IntersectionStreet2.Input
IsCloseMatch
Language
E
Even
O
Odd
B
Both
U
Unknown
The second street in an intersection address as it was input.
Indicates whether candidate is a close match.
For reverse geocoded candidates, the two-character language code is returned.
For GRC, RUS, and JPN, the user's locale determines the language of the returned
candidates for reverse geocoding. This can be Greek, Russian, or Japanese for
GRC, RUS, and JPN respectively. English is the default locale.
147
Output
Field Name
Description
columnName
Response Element
LastLine
Complete last address line (city, state/province, and postal code).
Latitude
Latitude of the candidate.
LeadingDirectional
Street directional that precedes the street name. For example, the N in 138 N Main
Street.
LeadingDirectional.Input
Street directional that precedes the street name as it was input.
Locality
The meaning of locality varies by country. Generally a locality is a village in rural
areas or it may be a suburb in urban areas. When used, a locality typically appears
on the lastline of the address with the postcode.
African and Middle East countries do not use a locality or equivalent as part of an
address. However there is no penalty if state/province is used in input address.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
148
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
149
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
150
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
•
Locality.Input
The locality as it was input.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
151
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
152
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ROU (Romaina)—Sector used in city of Bucharest
153
Output
Field Name
Description
columnName
Response Element
LocationPrecistion
A code describing the precision of the geocode. See the table of Result Codes
on page 171 for details of LocationPrecision codes.
Longitude
Longitude of the candidate.
NumberOfCandidateRanges
Indicates the number of ranges of which the candidate is a member. A candidate
may be a part of multiple ranges if the candidate is a street instead of a building.
To specify the number of ranges to return for each candidate, use the MaxRanges
option.To specify the number of ranges to return for each candidate, use the
Maximum ranges per candidate option.
NumberOfRangeUnits
Indicates the number of units included in the range. A unit is an address within a
building, such as an apartment or office suite. To specify the number of units to
return for each range, use the MaxRangeUnits option.To specify the number
of units to return for each range, use the Maximum units per range option.
PostalCode
The postcode for the address. The format of the postcode varies by country.
Postcode data is not available for every country.
PostalCode.Addon
The second part of a postcode. For Canadian addresses this will be the LDU. This
field is not used by most countries.
PostalCode.Addon.Input
The second part of a postcode as it was input. For Canadian addresses this will
be the LDU. This field is not used by most countries.
PostalCode.Base
The first part of a postcode. For Canadian addresses this will be the FSA. This
PostalCode.Base.Input
The first part of a postcode. For Canadian addresses this will be the FSA. This
PreAddress
Miscellaneous information that appears before the street name.
154
Output
Field Name
Description
columnName
Response Element
PrivateMailbox
This field is not currently used.
Ranges
This is a list field containing the address ranges that exist on the street segment
where the candidate address is located.
A range is a series of addresses along a street segment. For example, 5400-5499
Main St. is an address range representing addresses in the 5400 block of Main St.
A range may represent just odd or even addresses within a segment, or both odd
and even addresses. A range may also represent a single building with multiple
units, such as an apartment building.
The Ranges field contains the following sub-fields:
Address
This is a list filed that contains sub-fields for any
address elements (AddressLine1, City, and so on)
that are different from the candidate's address.
AdditionalFields
A listing of country-specific information related to the
address. The information contained in
AdditionalFields varies by country.
HouseNumberHigh
The highest address number for the range.
HouseNumberLow
The lowest address number for the range.
SegmentParity
Indicates the side of the street where the range is
located. One of the following:
HouseNumberParity
0
It is not known which side of the street the
range is located on.
1
The range is on the left side of the street.
2
The range is on the right side of the street.
Indicates whether the range contains odd or even
address numbers. One of the following:
0
The range contains both odd and even
address numbers.
1
The range contains odd address numbers
2
The range contains even address numbers.
-1
It is not known whether the range contains
odd or even house numbers.
155
Output
Field Name
Description
columnName
Response Element
TotalRangeUnitsReturned The number of unit ranges returned for the address.
A unit is an address within a building, such as an
apartment or suite.
RangeUnits
A list of the ranges of units within the building. An
example of units are apartments or suites.
Address
This is a list filed that contains
sub-fields for any address
elements (AddressLine1, City,
and so on) that are different from
the candidate's address.
UnitNumberHigh The highest unit number.
UnitNumberLow The lowest unit number.
SegmentCode
A unique ID that identifies a street segmentan individual address. In Japan, this is
the Jusho code. A Jusho Code is a point ID that represents a unique address.
SegmentParity
Indicates which side of the street has odd numbers.
StateProvince
L
Left side of the street
R
Right side of the street
B
Both sides of the street
U
Undetermined
Countries in the Africa, Middle East, and Latin America databases do not use a
state/province or equivalent as part of an address. However there is no penalty if
state/province is used in input address.
•
•
•
•
•
•
•
•
156
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CHL (Chile)—State
IND (India)—State
157
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
158
Output
Field Name
Description
columnName
Response Element
•
•
•
•
StreetDataType
The default search order rank of the database used to geocode the address. A
value of "1" indicates that the database is first in the default search order, "2"
indicates that the database is second in the default search order, and so on.
The default database search order is specified in the Management Console.
StreetName
For most countries, this contains the street name.
In Japan, this contains the block. Japanese addresses typically do not have street
names.
StreetPrefix
The type of street when the street type appears before the base street name.
StreetSuffix
The type of street when the street type appears after the base street name.
TrailingDirectional
Street directional that follows the street name. For example, the N in 456 3rd St.
N.
UnitNumberHigh
The highest unit number of the range in which the unit resides.
UnitNumberLow
The lowest unit number of the range in which the unit resides.
Return Parsed Address
The formatted input address can be returned along with a separate returned field
for each input address element. Parsed Address Input elements are returned in
separately labeled fields names with a .Input extension. See Result Codes on
page 171
159
Output
Geocode Output
Table 21: Geocode Output for Finland
Field Name
Description
columnName
Response Element
CoordinateSystem
The coordinate system used to determine the latitude and longitude coordinates. A
coordinate system specifies a map projection, coordinate units, etc. An example is
EPSG:4326. EPSG stands for European Petroleum Survey Group.
Latitude
Seven-digit number in degrees and calculated to four decimal places (in the format
specified).
Longitude
Seven-digit number in degrees and calculated to four decimal places (in the format
specified).
The following topics describe output that's unique to specific countries.
Australia G-NAF Database Output
The following table lists output fields that are unique to the Australian Geocoded National Address
File (G-NAF®) database. G-NAF is an optional database that is available for all six states and two
territories. G-NAF is the only authoritative Australian national index of locality, street and number,
validated with geographic coordinates.
160
Output
Table 22: Australia G-NAF Output
columnName
Description
Field Name
Response Element
AUS.GNAF_ADDRESS_CLASS
AUS.GNAF_CONFIDENCE
The Address_Class is constructed using a combination of
elements from the G-NAF Data Dictionary source tables.
The components of the Address_Class field are:
A
Alias address record
P
Principal address record
PP
Principal primary address record
PS
Principal secondary address record
AP
Alias primary address record
AS
Alias secondary address record
A number indicating how many G-NAF datasets the address
is found in. A higher confidence level means that the same
address was found in more data contributor sources. One
of the following:
<number> The number of datasets the address was found
in, minus 1. For example, a value of 0 indicates
that the address was found in one contributor's
dataset, a value of 1 indicates that the address
was found in two contributors' datasets, a value
of 2 indicates that the address was found in
three contributors' datasets, and so forth.
-1
AUS.GNAF_EIGHT_DECIMAL_PLACE_LATITUDE
The address could not be found in any G-NAF
dataset.
The parcel latitude, precise to eight digits after the decimal.
This is the latitude that the candidate matched to in the
G-NAF database. These are the original coordinates directly
from the G-NAF data prior to truncation or rounding.
This field is only returned if you specify
Return8DecimalPlaceLatLong=Y check the Return eight
decimal places for parcel latitude/longitude box on the
Geocoding tab.
161
Output
columnName
Description
Field Name
Response Element
AUS.GNAF_EIGHT_DECIMAL_PLACE_LONGITUDE
The parcel longitude, precise to eight digits after the decimal.
This is the longitude that the candidate matched to in the
G-NAF database. These are the original coordinates directly
from the G-NAF data prior to truncation or rounding.
This field is only returned if you specify
Return8DecimalPlaceLatLong=Y check the Return eight
decimal places for parcel latitude/longitude box on the
Geocoding tab.
AUS.GNAF_GEOCODE_LEVEL
A number indicating the level o f geocode for the address.
Every principal address within the G-NAF database has at
least a locality level geocode. They may also have a street
level geocode and a point level geocode.
AUS_GNAF_PARCEL_ID
0
No geocode.
1
Parcel level geocode only (no locality or street
level geocode).
2
Street level geocode only (no locality or parcel
level geocode).
3
Street and parcel level geocodes (no locality
geocode).
4
Locality level geocode only (no street or parcel
level geocode).
5
Locality and parcel level geocodes (no street level
geocode).
6
Locality and street level geocodes (no parcel level
geocodes).
7
Locality, street and parcel level geocodes.
The Parcel ID field is the generic parcel id field provided by
custodial data, and represents a Lot on Plan description
that is useful for government agencies. The exact format
varies. G-NAF source data has over 7 million records with
a Parcel_ID. The Australia geocoder supplements this to
populate over 12,730,000 G-NAF records with a Parcel_ID
field.
162
Output
columnName
Description
Field Name
Response Element
AUS.GNAF_PID
The G-NAF Persistent Identifier (G-NAF PID) is a
14-character alphanumeric string that uniquely identifies
each G-NAF address. The PID is constructed from a
combination of the major address fields of the G-NAF
Dictionary. An example of a G-NAF PID is:
GAVIC411711441
AUS.GNAF_RELIABILITY
A number indicating the geocode precision. Reliability is
related to the dictionary used to determine the geocode.
Data with geocoded reliability levels 1, 2, and 3 is contained
in the GNAF123 Dictionary. This is point (parcel) level
geocoded data. Data with geocoded reliability levels 4, 5,
and 6 is contained in the GNAF456 Dictionary. This contains
non-parcel centroid geocoded data.
1
Geocode accuracy recorded to appropriate surveying
standard. For example, this could apply to an address
level geocode that was manually geocoded. Geocode
resolution is sufficient to place the centroid within
address site boundary with a GPS.
2
Geocode accuracy sufficient to place centroid within
address site boundary. For example, this could apply
to an address level geocode that was automatically
calculated as the centroid of the corresponding
cadastre parcel.
3
Geocode accuracy sufficient to place centroid near
(or possibly within) address site boundary. For
example, this could apply to an address level geocode
that was automatically calculated by calculating where
on the road the address was likely to appear based
upon other bounding geocoded addresses.
4
Geocode accuracy sufficient to associate address site
with a unique road feature. For example, this could
apply to a street level geocode that was automatically
calculated by using the road centreline reference data.
5
Geocode resolution sufficient to associate address
site with a unique locality or neighborhood. For
example, this could apply to a locality level geocode
that was automatically calculated as the centroid of
the locality.
163
Output
columnName
Description
Field Name
Response Element
6
Geocode resolution sufficient to associate address
site with a unique region. For example, this could apply
to a locality level geocode that was derived from
topographic feature.
AUS.GNAF_SA1
The Statistical Area Level 1 (SA1) field as the second
smallest geographic area defined in the Australian Statistical
Geography Standard (ASGS). Mesh Block is the smallest
unit. The SA1 is designed for use in the Census of
Population and Housing as the smallest unit for the
processing and release of Census data. An SA1 is
represented by a unique seven digit code.
AUS.LEVEL_NUMBER
The number of a floor or level in a multistory building. For
example,
Floor 2 , 17 Jones Street
The G-NAF database includes level information for some
Australian states. Level information may be associated with
unit information, but not necessarily. If the G-NAF database
contains multiple records with the same level, the level
information is returned only if the input address contains
unique content (such as a unit number). If the G-NAF
dictionary has level information for an address, that
information is returned with the matched candidate.
The correct level information is returned (when available)
even if the input address did not include level information,
or if the input had the wrong level information. If the input
address has level information but the G-NAF database does
not include level information for the matching address, then
the input level information is discarded since it is not
validated in the G-NAF data.
AUS.LEVEL_TYPE
The label used for a floor of a multistory building. For
example, "Level" or "Floor". In this example, the level type
is "Level":
Suite 3 Level 7, 17 Jones Street
In this example, Suite 3 is a unit.
The G-NAF database includes level information for some
Australian states. Level information may be associated with
164
Output
columnName
Description
Field Name
Response Element
unit information, but not necessarily. If the G-NAF database
contains multiple records with the same level, the level
information is returned only if the input address contains
unique content (such as a unit number). If the G-NAF
dictionary has level information for an address, that
information is returned with the matched candidate.
The correct level information is returned (when available)
even if the input address did not include level information,
or if the input had the wrong level information. If the input
address has level information but the G-NAF database does
not include level information for the matching address, then
the input level information is discarded since it is not
validated in the G-NAF data.
AUS.MESH_BLOCK_ID
A Meshblock is the smallest geographic unit for which
statistical data is collected by the Australian Bureau of
Statistics (ABS). Meshblocks usually contain a minimum of
20 to 50 households. This is about one fifth the size of a
Collection District (CD). You can use the Meshblock ID to
do additional attributions against your own data.
AUS.LOT_NUMBER
Lot numbers are returned for G-NAF candidates because
some rural addresses do not have adequate physical or
house number information.
AUS.GEOCONTAINMENT
This specifies whether the returned coordinates are inside
or outside the address boundary. Values are YES for
coordinates within, or NO for coordinates outside the
boundary. Candidates with a G-NAF Reliability Level of 2
are considered within the address site boundary. Candidates
with a G-NAF Reliability Level of 3 are generally considered
within the address site boundary, although exceptions may
exist.
AUS.GEOFEATURE
This field returns a geocode feature type if that was not
provided in other G-NAF fields. GEOFEATURE corresponds
to Geocode Types (GEOCODE_TYPE_AUT Codes) that
are described in the PSMA Data Product Description Version
2.7 (Aug. 2012).
165
Output
columnName
Description
Field Name
Response Element
AUS.STREET_TYPE_ABB
This is an abbreviation for the street type. For example, EX
is an abbreviation for Extension and FTRL is an abbreviation
for Firetrail.
Canada Output
The following table lists output fields that are unique to Canada.
Table 23: Canada-Specific Output
columnName
Description
Field Name
Response Element
CAN.Census_CD
The Census Division (CD) in which the address is located.
For more information on Census Divisions, see:
http://www12.statcan.ca/english/census01/Products/Reference/dict/geo008.htm
on the Statistics Canada website
CAN.Census_CMA
The Census Metropolitan Area (CMA) in which the address
is located. For more information on Census Metropolitan
Areas, see
on the Statistics Canada website.
CAN.Census_CSD
The Census Subdivision (CSD) in which the address is
located. For more information on Census Subdivisions, see
CAN.Census_CT
The Census Tract (CT) in which the address is located. For
more information on Census Tracts, see
166
Output
columnName
Description
Field Name
Response Element
CAN.Census_DA
The Dissemination Area (DA) in which the address is
located. For more information on Dissemination Areas, see
United Kingdom Output
The following table lists output fields that are unique to the United Kingdom.
Table 24: United Kingdom Output
columnName Field Name
Description
GBR.AP_STATUS_FLAG
AddressPoint status flag. This field is only returned if you
are using the Address Point database. This status flag
defines the quality and accuracy of each address in the
Address Point database. For example, 0354. For more
information, see the Address Point User Guide available
at www.ordnancesurvey.co.uk.
GBR.DEPENDENT_STREET_NAME
Addresses in the United Kingdom may contain two street
names: a main street name and dependent street name.
Some addresses may not contain a street name at all.
GBR.DEPENDENT_LOCALITY
Dependent locality name. A dependent locality is a large
village or district, for example, Wimbledon.
GBR.DOUBLE_DEPENDENT_LOCALITY
Double dependent locality name. A double dependent
locality is a small village or subdistrict.
167
Output
columnName Field Name
Description
GBR.HISTORIC_POSTCODE
If the input address contained an old postal code that has
been replaced by a new postal code, this field contains the
old postal code.
GBR.ALIASED_LOCALITY
A locality that is not part of the postal address.
GBR.OSAPR
Ordnance Survey AddressPoint Reference (OSAPR). Each
address from the Address Point database has a unique
OSAPR. OSAPRs are always 18 characters long and start
with the letters AP. For example, APMM918D7LQ65VG005.
UPRN
The UPRN (Unique Property Reference Number) is returned
with every AddressBase Premium candidate, except for
Northern Ireland addresses. The UPRN is a unique identifier
that provides a persistent reference to a unique property,
regardless of changes in the property name, status,
subdivision, use (such as from single occupancy to multiple
occupancy), or demolition of the property. All historic,
alternative, and provisional addresses are recorded against
the same UPRN.
RPC
The RPC (Representative Point Code) is returned with every
AddressBase Premium candidate, except for Northern
Ireland addresses. The RPC is an additional returned field
that identifies the positional accuracy of the candidate. RPC
describes the accuracy of the coordinates allocated to the
address.
BLPU_STATE_CODE
The BLPU_STATE_CODE is returned with AddressBase
Premium candidates, except for Northern Ireland addresses.
This code describes the physical nature of the property or
land object. BLPU_STATE_CODE values can be 1 (under
construction); 2 (in use); 3 (unoccupied); 4 (no longer
existing; or 6 (Planning permission granted).
LOGICAL_STATUS_CODE
The LOGICAL_STATUS_CODE is returned with
AddressBase Premium candidates, except for Northern
Ireland addresses. This code describes the life cycle status
of the property. An address can have a
LOGICAL_STATUS_CODE of 1 (approved); 3 (alternate);
6 (provisional);or 8 (historical).
168
Output
India Output
For India, Exact match mode returns the available sub locality and place name information, in
addition to other standard address elements.
The following table lists output fields that are unique to India. These are returned as Additional Fields
values with the candidate.
Table 25: India-Specific Output
columnName
Description
Field Name
Response Element
ExtendedPrecisionCode
Candidates can return an ExtendedPrecisionCode in
additional fields. The value is PSLS, where each character
represents match for place name, sub locality, locality and
state respectively. When a field is not matched, the character
at corresponding position is replaced with a hyphen. For
example, "PS-S" represents matches on place name, sub
locality and state, with no match on locality.
POI_CATEGORY
POI Candidates return the POI_CATEGORY in additional
field. This describes type POI type (such as a Bank, ATM,
or Restaurant).
ISRURAL
G4 candidates now return as ISRURAL identifier in
additional fields. This indicates whether a G4 candidate
represents a rural region (village). Yes means is a village
candidate, No means it is not.
Netherlands Output
The following table lists output fields that are unique to the Netherlands database.
169
Output
Table 26: Netherlands Output
columnName
Description
Field Name
Response Element
EXTENDED_POST_CODE
Contains a candidate's 6-digit postal code, if available. It is
used for both forward and reverse geocoding.
New Zealand Output
The following table lists output fields that are unique to New Zealand.
Table 27: New Zealand-Specific Output
columnName
Description
Field Name
Response Element
NZL.NZL_MESHBLOCK_ID
A Meshblock is the smallest geographic unit for which
statistical data is collected by Statistics New Zealand.
Meshblocks vary in size from part of a city block to large
areas of rural land.
NZL.ALIASED_SUBURB
An alternative to the officially-recognized suburb name.
NZL.KEY_UFI
The Unique Identifier (UFI) identifies the street segment that
the geocoded address belongs to. UFIs are up to 7-digit
numbers, assigned by New Zealand Post, that uniquely
identify each postal delivery point. The UFI is always
returned if available, but you cannot use the UFI for input.
170
Output
Result Codes
Result codes contain information about the success or failure of the geocoding attempt, as well as
information about the accuracy of the geocode.
Table 28: Result Code Output for Finland
Field Name
Description
columnName
Response Element
Geocoder.MatchCode
Indicates how closely the input address matches the candidate address. For more
information, see Result Codes for International Geocoding on page 174.For more
information, see Match Codes.
IsCloseMatch
Indicates whether or not the address is considered a close match. An address is
considered close based on the "Close match criteria" options on the Matching tab.
MultiMatchCount
Y
Yes, the address is a close match.
N
No, the address is not a close match.
For street address geocoding, the number of matching address positions found for
the specified address.
For intersection geocoding, the number of matching street intersection positions
found for the specified addresses.
Status
Status.Code
Reports the success or failure of the match attempt
null
Success
F
Failure
If the geocoder could not process the address, this field will show the reason.
171
Output
Field Name
Description
columnName
Response Element
•
•
•
•
•
•
•
Status.Description
Internal System Error
No Geocode Found
Insufficient Input Data
Multiple Matches Found
Exception occurred
Unable to initialize Geocoder
No Match Found
If the geocoder could not process the address, this field will show a description of
the failure.
Problem + explanation
Returned when Status.Code = Internal System
Error.
Geocoding Failed
Returned when Status.Code = No Geocode
Found.
No location returned
Returned when Status.Code = No Geocode
Found.
No Candidates Returned
The geocoder could not identify any candidate
matches for the address.
Multiple Candidates Returned The address resulted in multiple candidates. In
and Keep Multiple Matches order for the candidate address to be returned,
not selected
you must specify KeepMultimatch=Y select
the Keep multiple matches option.
LocationPrecision
A code describing the precision of the geocode. One of the following:
0
No coordinate information is available for this candidate
address.
1
Interpolated street address.
2
Street segment midpoint.
3
Postal code 1 centroid.
4
Partial postal code 2 centroid.
5
Postal code 2 centroid.
6
Intersection.
7
Point of interest. This is a placeholder value. Spectrum
databases do not have POI data, so it is not possible to get
this return.
172
Output
Field Name
Description
columnName
Response Element
8
State/province centroid.
9
County centroid.
10
City centroid.
11
Locality centroid.
12 - 15
For USA, 12 indicates point ZIP precision. A point ZIP is a
(LocationPrecision 5-digit ZIP Code that represents a unique ZIP such as a single
codes)
site, building, or organization.For AUS, 12 indicates a single
close match to a postal (PO Box) location. This can be
generated from the standard Street Range database only (not
the G-NAF dictionary).For IND, 12 indicates a sub locality
(block or sector) match. This is more specific than other
geographic matches (city, district, or state).
For most countries, LocationPrecision codes 12 through 15
are reserved for unspecified custom items.
StreetDataType
12
Point ZIP precision. A point ZIP is a 5-digit ZIP Code that
represents a unique ZIP such as a single site, building, or
organization.
12
Single close match to a postal (PO Box) location. This can be
generated from the standard street range database only (not
the G-NAF database).
12
Sub locality (block or sector) match. This is more specific than
other geographic matches (city, district, or state).
13
Additional point precision for unspecified custom item.
14
15
16
The result is an address point.
17
The result was generated by using address point data to
modify the candidates segment data.
18
The result is an address point that was projected using the
centerline offset feature. You must have both a point and a
street range database to use the centerline offset feature, and
thereby return LocationPrecision 18.
The default search order rank of the database used to geocode the address. A value
of "1" indicates that the database is first in the default search order, "2" indicates
that the database is second in the default search order, and so on.
173
Output
Field Name
Description
columnName
Response Element
The default database search order is specified in the Management Console.
Candidates returned by Spectrum geocoders return another class of return codes that are referred
to as International Geocoding Result Codes. Each attempted match returns a result code in the
Geocoder.MatchCode output field.
International Street Geocoding Result Codes (S Codes)
Street level geocoded candidates return a result code beginning with the letter S. The second
character in the code indicates the positional accuracy of the resulting point for the geocoded record.
Table 29: Street (S ) Result Codes
S Result Code
Description
S1
Single close match with the point located at postal code centroid. For Canada, this is an FSA
centroid. For Japan, S1 indicates that the candidate matched to prefecture, but not to anything
more precise.
S2
Single close match, point located at ZIP+2 centroid. (USA only) For Japan, S2 indicates that
the candidate matched to prefecture and city, but not to anything more precise.
S3
Single close match with the point located at postal code centroid. For Canada, this is an
FSALDU centroid. For Japan, S3 indicates that the candidate matched to prefecture, city, and
municipality subdivision (such as chome, oaza).
S4
Single close match with the point located at the street centroid. For databases vintage 2014
Q4 or newer, the input house number is returned with the candidate even if no such house
number was found. The S4 code is followed by letters and dashes indicating match precision.
For Japan, S4 indicates that the candidate matched to prefecture, city, municipality subdivision,
and subarea, but not to anything more precise.See Interpreting S Result Codes on page 176
174
Output
S Result Code
Description
S5
Single close match with the point located at a street address position. For Japan, S5 indicates
that the candidate matched block but the lot was not provided on input. The S5 code is followed
by letters and dashes indicating match precision. For information about these letters, see
Interpreting S Result Codes on page 176.
S6
Single close match with the point located at centroid of geometry postal code. (For examrple,
large buildings having their own codes.).
S7
Single match with the point located at an interpolated point along the candidate's street segment.
When the potential candidate is not an address point candidate and there are no exact house
number matches among other address point candidates, the S7 result is returned using address
point interpolation. The point is interpolated according to the next highest or lowest address
point candidate that both intersects the segment and whose house number is contained within
the range of houses of the original candidate. By using known address reference points on the
street segment, the S7 point can be adjusted to a more accurate position. For Japan, S7
indicates that the candidate matched block but the lot was not provided. In these cases, the
block includes the building number so a lot number is not needed. For Australia, the S7-------G
result code is also used for single matches with G-NAF Reliability level of 3. The reliability level
is returned in the output field AUS.GNAF_Reliability. For more information, see Australia
G-NAF Database Output on page 160
S8
Single close match with the point located at either the single point associated with an address
point candidate or at an address point candidate that shares the same house number. No
interpolation is required. S8 returns are possible with point databases only.
For Australia, the S8-------G result code is also used for single matches with G-NAF Reliability
levels of 1or 2 (the highest level of G-NAF Reliability. The reliability level is returned in the
output field AUS.GNAF_Reliability.
For Japan, S8 indicates that the candidate matched to a sub blocklot number (pin point).
SG
For Australia, single close match with the point at the center of a locality, or Locality level
geocode derived from topographic feature. An SG-------G result code is associated with G-NAF
Reliability Level 5 (locality or neighborhood) or with Level 6 (unique region). The reliability level
is returned in the output field AUS.GNAF_Reliability. For more information, see Australia
G-NAF Database Output on page 160.
SP
For Australia, single close match to a postal (PO Box) location. This can be generated from
the Street Range Address database only (not the G-NAF database).
SL
Sub locality. The SL result code is used for India only. This indicates a sub locality (block or
sector) street level match. An SL result code also requires a match on other geographic input
fields (city, district, or state).
SX
Single close match with the point located at street intersection.
175
Output
Interpreting S Result Codes
For S (street geocoded) international result codes, eight additional characters describe how closely
the address matches an address in the database. The characters appear in the order listed in the
following table. Any non-matched address elements are represented by a dash.
For example, the result code S5--N-SCZA represents a single close match that matched the street
name, street suffix direction, town, and postcode. The dashes indicate that there was no match on
house number, street prefix direction, or thoroughfare type. The match came from the Street Range
Address database. This record would be geocoded at the street address position of the match
candidate.
Category
Description
Example
H
House number
18
P
Street prefix direction
North
P is present if any of these conditions are satisfied:
• The candidate pre-directional matches the input
pre-directional.
• The candidate post-directional matches the input
pre-directional after pre- and post-directionals are
swapped.
• The input does not have a pre-directional.
N
Street name
Merivale
T
Street type
St
S
Street suffix direction
W
S in result code is present if any of these conditions are
satisfied:
• The candidate post-directional matches the input
post-directional.
• The candidate pre-directional matches the input
post-directional after pre- and post-directionals are
swapped.
• The input does not have a post-directional.
176
Output
Category
Description
Example
C
City name
South Brisbane
Z
Postal code
4101
L
Sublocality. The SL result code is used for for India only. Block-9 Sector-3
This indicates a sublocality (block or sector) match when
a street match (S4) or point match (S8) was not possible.
An SL result code also requires a match on other
geographic input fields (city, district, or state).
In India, street name information is often not available, but
a sublocality can be a very small area. Therefore an SL
match can be more precise than a street centroid S4 match.
A, G, or U
Database type used to obtain the match.
A
• A—Street Range Address database.
• G—G-NAF Point Address Dictionary (Australia only).
• U—Customer (user-defined) database.
International Postal Geocoding Result Codes (Z Codes)
Matches in the Z category indicate that a match was made at the postcode level. A postcode match
is returned in either of these cases:
• You specified to match to postal code centroids. The resulting point is located at the postal code
centroid with the following possible accuracy levels.
• There is no street level close match and you specified to fall back to postal code centroid.
Table 30: Postal (Z) Result Codes
Z Result Code
Description
Z1
Postal Code centroid match.
Z2
ZIP+2 centroid match (US centric)
177
Output
Z Result Code
Description
Z3
Full postal code centroid match. For Canada, this is an FSALDU centroid.
Postal level geocoded candidates return a result code beginning with the letter Z. Finland can
generate a Z1 result code. Country-specific geocoders can often generate more accurate postcode
results (with Z2 or Z3 result codes).
If the postal candidate comes from a user dictionary, the letter U is appended to the result. For
example, Z1U indicates a postal centroid match from a custom user dictionary.
International Geographic Geocoding Result Codes (G Codes)
Geographic level geocoded candidates return a result code beginning with the letter G. The numbers
following the G in the result code provides more detailed information on the accuracy of the candidate.
Table 31: Geographic (G) Result Codes
G Result Code
Description
G1
State or province centroid. match.
For Japan, this indicates a prefecture (ken) match.
G2
County (district or region) centroid match.
For Japan, this indicates a city (shi) match.
G3
City or town (municipality) centroid match.
For Japan, this indicates a sub-city (oaza) match.
For Australia, Local Government Authority (LGA) information can be returned from
the Street Range Address Database only (not the G-NAF database).
G4
Locality (village, suburb, or neighborhood) centroid match.
For Japan, this indicates a city district (chome) match.
If the geographic candidate comes from a user dictionary, the letter U is appended to the result
code. For example, G4U indicates a locality centroid match from a custom user dictionary.
178
Output
Reverse Geocoding Codes (R Codes)
Matches in the R category indicate that the record was matched by reverse geocoding. The second
two characters of the R result code indicate the type of match found. R geocode results include an
additional letter to indicate the dictionary from which the match was made.
Example reverse geocoding codes:
Table 32: Reverse Geocoding (R) Result Codes
Reverse Geocoding Code
Description
RS8A
Point/parcel level precision for reverse geocoding. Candidate returned from address
dictionary.
RS8G
Point/parcel level precision. Candidate returned from Australia G-NAF dictionary
with G-NAF Reliability level of 1 or 2.
RS7G
Candidate returned from Australia G-NAF dictionary with G-NAF Reliability level of
3.
RS5A
Interpolated street candidate for reverse geocoding. Candidate returned from address
dictionary.
RS4A
Street centroid candidate for reverse geocoding. Candidate returned from address
dictionary.
RS4G
Candidate returned from Australia G-NAF dictionary with a G-NAF Reliability level
of 4 (associated with a unique road feature)
RSGG
Candidate returned from Australia G-NAF dictionary with G-NAF Reliability Level 5
(locality or neighbourhood) or with Level 6 (unique region.)
RSLA
Candidate returned from India address dictionary with a sublocality (block or sector)
match. In India, street name information is often not available, but a sublocality can
be a very small area. Therefore an RSLA match can be more precise than a street
centroid RS4 match.
179
Output
If the reverse geocoded candidate comes from a user dictionary, the letter U is appended to the
result. For example, RS8U indicates a point/parcel level reverse geocode match from a custom user
dictionary.
Non-match Codes
The following result codes indicate no match was made:
• N—No close match.
• NX—No close match for street intersections.
• ND—Spectrum™ Technology Platform could not find the geocoding database for the given postal
code or municipality/state/province.
• NG—The user marks these records during interactive geocoding as non-geocodable. The Location
Utility Service does not attempt to match these records again until the code is removed. [Does
not apply to Spectrum™ Technology Platform]
180
5 - Reverse Geocode
Address Global
Reverse Geocode Address Global determines the address for a given
latitude/longitude point. Reverse Geocode Address Global can determine
addresses in many countries. The countries available to you depends on
which country databases you have installed. For example, if you have
databases for Canada, Italy, and Australia installed, Reverse Geocode
Address Global would be able to geocode addresses in these countries in
a single stage.
Note: Reverse Geocode Address Global does not support U.S. addresses.
To geocode U.S. addresses, you must use Reverse Geocode US
Location. That performs reverese geocoding specifically for USA
addresses.
For Great Britain (GBR), reverse geocoding is available with the
Streets dataset only. GBR Reverse geocoding is not available with
the CodePoint or AddressPoint datasets.
Before you can work with Reverse Geocode Address Global, you must
define a global database resource containing a database for one or more
countries. Once you create the database resource, Reverse Geocode
Address Global will be available.
In this section
Input
Options
Output
182
183
188
Reverse Geocode Address Global
Input
Reverse Geocode Address Global takes longitude and latitude as input.
For GRC, RUS, and JPN, the user's locale determines the language of the returned candidates for
reverse geocoding. This can be Greek, Russian, or Japanese for GRC, RUS, and JPN respectively.
English is the default locale.
Note: Specify input using the DataTable class. For information on the DataTable class, see the
"API Fundamentals" section.
Table 33: Reverse Geocode Global Input
Field Name
Format
Description
String
The latitude of the point for which you want address information.
String
The longitude of the point for which you want address information.
String
columnName
Parameter
Latitude
Data.Latitude
Longitude
Data.Longitude
Country
Data.Country
• The name of the country in English.
• The two-character ISO 3116-1 alpha-2 country code.
• The three-character ISO 3116-1 alpha-3 country code.
182
Options
Geocoding Options
Table 34: Default Geocoding Options for Finland
Option Name
Description
optionName
Parameter
Search distance
SearchDistance
The radius from the input coordinates in which to search for an address. Street
segments and points within the radius are considered. The default search radius is
150 meters and the maximum search radius is 1600 meters.
Option.SearchDistance
Units
The units in which the search distance is specified. One of the following:
Units
•
•
•
•
•
•
•
•
Option.Units
Offset from street
OffsetFromStreet
Option.OffsetFromStreet
Feet
Feet
Miles
Miles
Meters
Meters
Kilometers
Kilometers
Indicates the offset distance from the street segments to use in street-level geocoding.
The distance is specified in the units you specify in the Units field OffsetUnits option.
The default value varies by country. For most countries, the default is 7 meters.
For Austria, Germany, and Australia the default is 10 meters.
The offset distance is used in street-level geocoding to prevent the geocode from
being in the middle of a street. It compensates for the fact that street-level geocoding
returns a latitude and longitude point in the center of the street where the address
is located. Since the building represented by an address is not on the street itself,
183
Option Name
Description
optionName
Parameter
you do not want the geocode for an address to be a point on the street. Instead, you
want the geocode to represent the location of the building which sits next to the
street. For example, an offset of 50 feet means that the geocode will represent a
point 50 feet back from the center of the street. The distance is calculated
perpendicular to the portion of the street segment for the address. Offset is also
used to prevent addresses across the street from each other from being given the
same point. The following diagram shows an offset point in relation to the original
point.
Street coordinates are accurate to 1/10,000 of a degree and interpolated points are
accurate to the millionths of a degree.
Offset from corner
OffsetFromCorner
Option.OffsetFromCorner
Specifies the distance to offset the street end points in street-level matching. The
distance is specified in the units you specify in the Units field OffsetUnits option.This
value is used to prevent addresses at street corners from being given the same
geocode as the intersection.
The default value varies by country:
• 12 meters—Australia (AUS), Austria (AUT), Germany (DEU)
• 7 meters—For other supported countries, the default offset is 7 meters.
The following diagram compares the end points of a street to offset end points.
184
Option Name
Description
optionName
Parameter
Units
OffsetUnits
Option.OffsetUnits
Specifies the unit of measurement for the street offset and corner offset options.
•
•
•
•
•
•
•
•
Feet
Feet
Miles
Miles
Meters
Meters
Kilometers
Kilometers
The default is Meters.
Coordinate system
CoordinateSystem
Option.CoordinateSystem
A coordinate system is a reference system for the unique location of a point in space.
Cartesian (planar) and Geodetic (geographical) coordinates are examples of
reference systems based on Euclidean geometry. Spectrum™ Technology Platform
supports systems recognized by the European Petroleum Survey Group (EPSG).
Each country supports different coordinate systems. Depending on the country, you
have one or more of the following options:
EPSG:4230
Subset of WGS84.
EPSG:4283
Also known as the GDA94 coordinate system.
EPSG:4301
Also known as the Tokyo coordinate system.
EPSG:4326
Also known as the WGS84 coordinate system.
EPSG:27200
Also known as the NZGD49 coordinate system.
EPSG:27700
Also known as the British National Grid system.
185
Matching Options
Table 35: Default Matching Options for Finland
Option Name
Description
optionName
Parameter
Keep multiple matches
KeepMultimatch
Option.KeepMultimatch
MaxCandidates
Option.MaxCandidates
Sort candidates using locale
SortCandidatesUsingLocale
Specifies whether to return results when the coordinates match to multiple candidate
addresses in the database. If this option is not selected, coordinates that results in
multiple address candidates will fail to geocode.
If you select this option, specify the maximum number of candidates to return using
the MaxCandidates option (see below) using the Option.MaxCandidates option (see
below) next to the check box.
Y
Yes, return candidates when multiple candidates are found. Default.
N
No, do not return candidates. Addresses that result in multiple candidates
will fail to geocode.
If you specify KeepMultimatch=Y, this option specifies the maximum number of
results to return. The default is 1. Specify -1 (minus one) to return all possible
candidates.
This is a Reverse geocoding option that applies to Greece, Russia, Ukraine, and
any other country that supports dual character sets (such as the Middle East
countries).
Option.SortCandidatesUsingLocale Specifies whether candidates are sorted and returned based on the input language.
That is, if the input was in Russian, the Russian character candidate is returned first
followed by the English language candidate. This will override the dictionary order.
Y
Yes, candidates are sorted and returned based on input language.
N
No, candidates are returned in the order that the dictionary was added
to the database, regardless of input language.
186
Data Options
The Data tab allows you to specify which databases to use in reverse geocoding. Databases contain
the address and geocode data necessary to determine the address for a given point. The following
table lists the options available for specifying the search order of databases.
Table 36: Default Data Options for Finland
optionName
Description
Option Name
Parameter
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.
187
Output
Table 37: Reverse Geocode Address Global Output Fields
columnName
Description
Field Name
Response Element
AddressLine1
First line of the address.
AddressLine2
Second line of the address.
ApartmentLabel
The type of unit, such as apartment, suite, or lot.
ApartmentNumber
Unit number.
City
The municipality name.
County
Data.County
The majority of countries in the Africa database (XA1) do
not use a county or equivalent as part of an address.
The majority of countries in the Middle East database (XM1)
do not use a county or equivalent as part of an address.
The majority of countries in the Latin American database
(XL1) do not use a county or equivalent as part of an
address.
•
•
•
•
•
188
columnName
Description
Field Name
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
189
columnName
Description
Field Name
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
190
columnName
Description
Field Name
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
This field is not used with countries included with the African
bundle (Product Code XA1). These African countries
generally have less comprehensive address coverage.
This field is not used with countries included with the Middle
East bundle (Product Code XM1). These African countries
generally have less comprehensive address coverage.
This field is not used with countries included with the Latin
American database (Product Code XL1). These African
191
columnName
Description
Field Name
Response Element
countries generally have less comprehensive address
coverage.
Note: If you enter addresses with the Andorran country
code (AND), only Andorran addresses are returned,
including the AND country code. If you enter an
Andorran with a country code of Spain (ESP), you
will still get Andorran candidates, but with the ESP
country code.
The region name.
The region name or alias. For example,
Osrednjeslovenska/Ljubljana.
The district name.
The kommun name.
The district name.
Distance
The distance from input location in meters. If the input
coordinates are an exact match for the address, the value
is 0.
FirmName
Name of the company or a place name.
Geocoder.MatchCode
Indicates how closely the input coordinates match the
candidate address. For more information, see Reverse
Geocoding Codes (R Codes) on page 179.
HouseNumber
The buildinglot number for the matched location.
192
columnName
Description
Field Name
Response Element
HouseNumberHigh
The highest house number of the range in which the address
resides.
HouseNumberLow
The lowest house number of the range in which the address
resides.
HouseNumberParity
Indicates if the house number range contains even or odd
numbers or both.
Language
E
Even
O
Odd
B
Both
U
Unknown
For reverse geocoded candidates, the two-character
language code is returned.
For GRC, RUS, and JPN, the user's locale determines the
language of the returned candidates for reverse geocoding.
This can be Greek, Russian, or Japanese for GRC, RUS,
and JPN respectively. English is the default locale.
LastLine
Complete last address line (city, state/province, and postal
code).
LeadingDirectional
Street directional that precedes the street name. For
example, the N in 138 N Main Street.
Locality
The meaning of locality varies by country. Generally a
locality is a village in rural areas or it may be a suburb in
urban areas. When used, a locality typically appears on the
lastline of the address with the postcode.
Data.Locality
African and Middle East countries do not use a locality or
equivalent as part of an address. However there is no
penalty if state/province is used in input address.
193
columnName
Description
Field Name
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CAN (Canada)—Dissemination Area and Enumeration
Area (DA and EA)
194
columnName
Description
Field Name
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
195
columnName
Description
Field Name
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
NumberOfCandidateRanges
Indicates the number of ranges of which the candidate is a
member. A candidate may be a part of multiple ranges if
the candidate is a street instead of a building. To specify
the number of ranges to return for each candidate, use the
MaxRanges option.To specify the number of ranges to
return for each candidate, use the Maximum ranges per
candidate option.
196
columnName
Description
Field Name
Response Element
NumberOfRangeUnits
Indicates the number of units included in the range. A unit
is an address within a building, such as an apartment or
office suite. To specify the number of units to return for each
range, use the MaxRangeUnits option.To specify the
number of units to return for each range, use the Maximum
units per range option.
PostalCode
The postcode for the address. The format of the postcode
varies by country. Postcode data is not available for every
country.
PostalCode.Addon
The second part of a postcode. For Canadian addresses
this will be the LDU. This field is not used by most countries.
PreAddress
Miscellaneous information that appears before the street
name.
PrivateMailbox
This field is not currently used.
SegmentCode
A unique ID that identifies a street segmentan individual
address. In Japan, this is the Jusho code. A Jusho Code is
a point ID that represents a unique address.
SegmentParity
Indicates which side of the street has odd numbers.
L
Left side of the street
R
Right side of the street
B
Both sides of the street
U
Undetermined
StateProvince
Data.StateProvince
Countries in the Africa, Middle East, and Latin America
databases do not use a state/province or equivalent as part
197
columnName
Description
Field Name
Response Element
of an address. However there is no penalty if state/province
is used in input address.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CHL (Chile)—State
CZE (Czech Republic)—Region name or alias. For
example, the region HLAVNÍ MESTO PRAHA can be
aliased as Prag.
IND (India)—State
198
columnName
Description
Field Name
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
199
columnName
Description
Field Name
Response Element
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
StreetDataType
The default search order rank of the database used to
geocode the address. A value of "1" indicates that the
database is first in the default search order, "2" indicates
that the database is second in the default search order, and
so on.
The default database search order is specified in the
Management Console.
StreetName
For most countries, this contains the street name.
In Japan, this contains the block. Japanese addresses
typically do not have street names.
StreetPrefix
The type of street when the street type appears before the
base street name.
StreetSuffix
The type of street when the street type appears after the
base street name.
TrailingDirectional
Street directional that follows the street name. For example,
the N in 456 3rd St. N.
200
columnName
Description
Field Name
Response Element
UnitNumberHigh
The highest unit number of the range in which the unit
resides.
UnitNumberLow
The lowest unit number of the range in which the unit
resides.
201
Notices
Copyright
© 2016 Pitney Bowes Software Inc. All rights reserved. MapInfo and Group 1 Software are trademarks
of Pitney Bowes Software Inc. All other marks and trademarks are property of their respective
holders.
USPS® Notices
Pitney Bowes Inc. holds a non-exclusive license to publish and sell ZIP + 4® databases on optical
and magnetic media. The following trademarks are owned by the United States Postal Service:
Link
CASS, CASS Certified, DPV, eLOT, FASTforward, First-Class Mail, Intelligent Mail, LACS ,
Link
Link
NCOA , PAVE, PLANET Code, Postal Service, POSTNET, Post Office, RDI, Suite
, United
States Postal Service, Standard Mail, United States Post Office, USPS, ZIP Code, and ZIP + 4.
This list is not exhaustive of the trademarks belonging to the Postal Service.
Link®
Pitney Bowes Inc. is a non-exclusive licensee of USPS® for NCOA
processing.
Prices for Pitney Bowes Software's products, options, and services are not established, controlled,
or approved by USPS® or United States Government. When utilizing RDI™ data to determine
parcel-shipping costs, the business decision on which parcel delivery company to use is not made
by the USPS® or United States Government.
Data Provider and Related Notices
Data Products contained on this media and used within Pitney Bowes Software applications are
protected by various trademarks and by one or more of the following copyrights:
©
Copyright United States Postal Service. All rights reserved.
©
2014 TomTom. All rights reserved. TomTom and the TomTom logo are registered trademarks of
TomTom N.V.
©
1987 - 2014 HERE. All rights reserved.
Fuente: INEGI (Instituto Nacional de Estadística y Geografía)
Based upon electronic data © National Land Survey Sweden.
©
Copyright United States Census Bureau
©
Copyright Nova Marketing Group, Inc.
Portions of this program are © Copyright 1993-2007 by Nova Marketing Group Inc. All Rights
Reserved
©
Copyright Second Decimal, LLC
©
Copyright Canada Post Corporation
This CD-ROM contains data from a compilation in which Canada Post Corporation is the copyright
owner.
©
2007 Claritas, Inc.
The Geocode Address World data set contains data licensed from the GeoNames Project
(www.geonames.org) provided under the Creative Commons Attribution License ("Attribution
203
Copyright
License") located at http://creativecommons.org/licenses/by/3.0/legalcode. Your use of the
GeoNames data (described in the Spectrum™ Technology Platform User Manual) is governed by
the terms of the Attribution License, and any conflict between your agreement with Pitney Bowes
Software, Inc. and the Attribution License will be resolved in favor of the Attribution License solely
as it relates to your use of the GeoNames data.
ICU Notices
Copyright © 1995-2011 International Business Machines Corporation and others.
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of the Software and that both the
above copyright notice(s) and this permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS.
IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE
BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES,
OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising
or otherwise to promote the sale, use or other dealings in this Software without prior written
authorization of the copyright holder.
204
3001 Summer Street
Stamford CT 06926-0700
USA
www.pitneybowes.com
©2016 Pitney Bowes
All Rights Reserved

Geocoding Guide for Finland - API - REST - SOAP

Transcription

Similar documents

Entreprise Location Intelligence Brochure

Batch Production of Driving Distances and Times Using SAS® and

PRICE TOTAL $ FIBA Shot Clock *pair

Informer: The History of American Crime and Law Enforcement

Whitepages Pro Caller Identification API

Johnny Cash Returns to `Stamping Ovation`

Bowler Pledge Form

Carpe Salesem

Automaalit

Quarterly NL May 2010-b