Static Data Mapping

One of the most important aspects of a successful XML integration is the data mapping. Some decisions on this have to be made very early on during the design and development process in order to achieve the best results. It is therefore important that the IT, sales and marketing teams of both companies work closely together to understand the challenges and find the most suitable solutions. We have listed here a few areas that require particular attention. The technical specifications for all of these issues can be found on this site; this document is intended to provide a summary and to highlight areas that need to be considered BEFORE the development process can start.

IATA City Codes

GTA uses IATA and non-IATA city codes. The reason for this lies in the fact that we provide many properties, tours and transfers in destinations far away from any airport for which no IATA code exists.

In the past many of our clients have asked us whether we could provide a mapping table that would map all non-IATA GTA city codes to the existing IATA airport and/or city codes. Unfortunately we have as yet not been able to come up with the right logic for that without the risk that a customer ends up in a completely different city when booking a hotel than he thought he would stay in.

To give an example, there are 15 IATA codes and over 50 GTA city codes for places in Austria and only 8 of them are matching. If we take the city of St. Wolfgang the closest airport to this town is Salzburg, about 50km away, so we could map the GTA city code for St. Wolfgang 'STWO' to the IATA code 'SZG'. However, we are worried that our clients then perform a price and availability search for the IATA code 'SZG' and we return also properties in St. Wolfgang additionally to all the properties in Salzburg itself, your customer might choose to book a property in St. Wolfgang without realising that it is 50km away from Salzburg.

Please be aware that not all IATA city codes are directly recognised in GTA; i.e.: Kaunas (IATA: KUN), in this case the GTA city code would be KAUS and no results would be returned at all if the code KUN is being used.

Clients will therefore need to import all GTA city codes and map them to the destinations they are selling or create them as new destinations in their systems. While the import can be done by the IT team there are commercial considerations to be made for which sales and marketing teams need to be involved.

GTA Item Codes

GTA uses item codes that are only unique in conjunction with our city codes. For example, the GTA item code for the ROYAL NATIONAL HOTEL in London is ‘ROY2’; this needs to be used in conjunction with our city code for London, which is ‘LON’. Failure to do so might result in the wrong hotel being booked as we also have a hotel in Edinburgh with the code ‘ROY2’ which is for the ROYAL BRITISH HOTEL’ which in turn needs to be used in conjunction with our city code for Edinburgh which is ‘EDI’.

Therefore GTA hotel code ‘INT’ will be returned in Berlin, in Buenos Aires, in Chicago, in Melbourne, in New York, in Prague, in Riyadh, in Shanghai and in Tokyo and in many other cities. For this reason it is very important to read the hotel codes together with the city codes.

Geocodes

In order to provide the greatest flexibility we offer the facility to perform searches using geo-codes and radius or bounding box.

Below is an example for geocode with radius:

Below an example for a geocode bounding box:

         

City Codes

There are four main destination types for which it is necessary to use geo-code searches or multiple city codes: 

  1. Well known regions
  2. Islands
  3. Cities with outlying airports
  4. Cities with two or more distinct and separate areas

If inventory should be retrieved for a geographical region that contains several cities it is not possible to retrieve the entire inventory with a request for a single GTA city code. Instead, it is necessary to either use a search by geo-code or to send multiple requests for all the GTA city codes within the region.

Example 1 - Well known regions:

The Black Forest Region, Germany

Containing the following GTA city codes: 

CityCode Location

BAD3

Bad Peterstal

DONA

Donaueschingen

FREU

Freudenstadt

HCHE

Hochenschwand

QFB

Freiburg

TITI

Titisee

VILI

Villingen-Schwenning

 

 

 

 

 

Example 2 - Islands:           

Bali, Indonesia

Containing the following GTA city codes: 

CityCode Location

AMAN

Bali-Manggis

BNEG

Bali-Negara

BTUB

Bali-Batubelig Beach

DCAN

Bali-Canggu

DENR

Bali-Denpasar

ECAN

Bali-Candi Dasa

GIAY

Bali-Gianyar

JIMB

Bali-Jimbaran Bay

KROB

Bali-Kerobokan

KUTB

Bali-Kuta Beach

LEGI

Bali-Legian Beach

LMBO

Lembongan Island

MNDU

Bali-Munduk Village

NUSA

Bali-Nusa Dua

SANH

Bali-Sanur Beach

SIGJ

Bali-Singaraja

SMIN

Bali-Seminyak

TABN

Bali-Tabanan

TUBA

Bali-Tuban Beach

UBUD

Bali-Ubud

ULUW

Bali-Uluwatu

Example 3 - Cities with outlying airports:           

London, United Kingdom

Containing the following GTA city codes: 

CityCode Location

CROY

London-Croydon

LGW

London Gatwick

LHR

London Heathrow

LON

London

LTN

London Luton

STN

London Stansted

 

 

 

 

Example 4 - Cities with two or more distinct and separate areas:

Dubai, United Arab Emirates

Containing the following GTA city codes: 

CityCode Location

DESR

Dubai-Desert

DXB

Dubai City

JUME

Dubai-Jumeirah


Destination Mapping Suggestions

Islands Area Codes

Destination Codes

GTA Property List

We will download our static data on the 1st of every month and input this into an Excel file, for your reference. This can be helpful in double checking your mapping.

 

 

Docs Navigation