Region-specific content

Last edit: 2022.05.05

Some parts of TomTom data are subject to additional legal terms and conditions. When used, the customer must agree to and follow these additional conditions. Also, for some regions our APIs can have differences in requests and responses compared to the default API behavior. Customers should be aware of these differences before using the region-specific content.

Available region-specific contents

HostnameDescription
kr-api.tomtom.com
  • Hostname, where detailed South Korea data is available.
  • Detailed South Korean data is processed and hosted in South Korea.
    • It may impact the latency for requests sent from outside of South Korea.
  • The service customers are not allowed to download, store, cache nor host the South Korean data outside of South Korea (except for web browser cache).
  • The service customers are not allowed to display any coordinates of any place within South Korea.
  • Response data for South Korea can have additional response data.

Region-specific API changes

Response data for South Korea

South Korea switched from a land lot-based addressing format to a street name-based format in 2011. The old format is still widely used and therefore supported by the Search API, which means both address formats can be found and returned by various Search APIs (geocode, search, and reverse geocode).

Changes to the API response only apply to results of type Point Address. The Search API supports Point Address results with

  1. only a street name-based address.
  2. only a land lot-based address.
  3. both a street name-based address and a land lot-based address.

Street name-based address only

For a Point Address with only a street name-based address, the API response is identical to the default API response.

Land lot-based address only

For a Point Address with only a land lot-based address, the address response object mostly follows the default address object, except for the addition of the following two fields

FieldDescription
landCode
string
Land-lot number.
dependentLocalName
string
Neighbourhood (dong).

Both address formats

Most street name-based addresses have a matching land lot-based address linked to it. To support this dual-addressing scheme, the API response contains the address field, as well as an additional field linkedAddress. The address field contains the street name-based address, while the region-specific linkedAddress field contains the land lot-based address. The linkedAddress field's structure is identical to the address field for land lot-based addresses (see previous section).

An Point Address element in the results array with both address formats present is represented in JSON as follows:

RESULTS ARRAY ELEMENTS FORMAT - JSON
1{
2 "type": "Point Address",
3 "id": "KR/PAD/p0/763729",
4 "score": 3.9,
5 "address": {.. 11 Items ..},
6 "linkedAddress": {
7 "dependentLocalName": "향소리",
8 "landCode": "167-3",
9 "streetName": "석산로119번길",
10 "municipalitySubdivision": "단월면",
11 "municipality": "양평군",
12 "countrySubdivision": "경기도",
13 "postalCode": "12528",
14 "countryCode": "KR",
15 "country": "대한민국",
16 "countryCodeISO3": "KOR",
17 "freeformAddress": "12528 경기도 양평군 단월면 향소리 167-3",
18 "localName": "단월면"
19 },
20 "position": {.. 2 Items ..},
21 "viewport": {.. 2 Items ..},
22 "entryPoints": [.. 1 Item ..]
23}