Language
Human language is a complex subject, and it has a lot of influence on how we search for addresses.
Language Introduction
The following table shows which countries support which languages, what the default language is, and which languages are supported by Naurt's parser.
| Country | Supported Languages | Default Language | Parser Support |
|---|---|---|---|
| Australia | English | English | English |
| Canada | English* | English* | English* |
| New Zealand | English | English | English |
| Singapore | English | English | English |
| United Kingdom | English | English | English |
| United States | English | English | English |
| Brazil | Portuguese | Portuguese | Portuguese |
| Germany | German | German | German |
| France | French | French | French |
| Italy | Italian | Italian | Italian |
| Portugal | Portuguese | Portuguese | Portuguese |
| Hong Kong | Chinese | Chinese | |
| Japan | Japanese | Japanese | |
| South Korea | Korean | Korean | |
| Taiwan | Chinese | Chinese | |
| Egypt | English, Arabic | Arabic | English |
| Saudi Arabia | English, Arabic | Arabic | English |
| United Arab Emirates | English, Arabic | Arabic | English |
| Spain | Spanish | Spanish | Spanish |
| Netherlands | Dutch | Dutch | Dutch |
| Austria | German | German | German |
- Canada is a special case - please see the next section.
Canada Special Case
Unfortunately, due to upstream address suppliers, Canadian addresses are mixed English/French. In general, addresses in Québec are in French and addresses elsewhere are in English. Due to upstream restrictions, Canada is only classed in the API as having English support. Therefore, when reverse geocoding in Canada, never specify French otherwise no results will be found.
Searching With an Address
If you include an address in your search, the general rule is that the returned address will be in the same language as the search language.
Some languages support the parser. If you are not using a parsed request, Naurt will attempt to first parse your address using our parser. In general, a parsed address has much better search accuracy than an unparsed address.
If any Arabic is used in searching countries with Arabic support, the entire address search will be considered Arabic, and the parser will not be used. The same is true for any Chinese, Korean or Japanese characters.
Reverse Geocode
When reverse geocoding, there may be a need to specify a language desired. To avoid having mixed languages appear when reverse geocoding, Naurt has selected a default language per country. If no language is specified, the default language in the above template will be used. If forward geocoding, then there is no need to specify a language as it will use whichever language was searched with. Naurt does not offer translation services.
The language specification is done using ISO 639 Language Codes. The currently supported languages are
- AUTO - Default (uses the default language for any country - this option is used if language is not specified)
- AR - Arabic
- EN - English
- PT - Portuguese
- FR - French
- DE - German
- ES - Spanish
- NL - Dutch
- JA - Japanese
- IT - Italian
- ZH - Chinese
- KO - Korean
Please be aware that the language field will under some circumstances cause nothing to be found. For example, using the English language tag in Japan nothing will be found, as there are no English addresses in Japan.
This can be specified using the language field in a request
{
"location": {
"latitude": 24.49,
"longitude": 54.41
},
"language": "EN"
}
If you do not specify a language, then AUTO will be used. In other words
{
"location": {
"latitude": 24.49,
"longitude": 54.41
}
}
is equivalent to
{
"location": {
"latitude": 24.49,
"longitude": 54.41
},
"language": "AUTO"
}
AUTO will use the default language, as specified in the table above.
language can only be used with location and location only. ONLY reverse
geocode requests support language options at present. For all other requests,
using language will return a 400. In forward geocode requests, language is
matched to the search language