Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Current »

2.1.1. SEARCH BY LOCATIONS

GP Travel HUB offers several alternatives of searching vendors by location.

Search by

Context

Description

Search example

City and country code

GEO context (one supplier)

When the CodeContext is "GEO.<supplierCode>" then the CityName Code and CountryName Code must be specified in GEO context, and then the search request goes only to the supplier specified. So, you can send a request to the particular supplier, even if you don’t know supplier-specific City and Country Codes.

<VehLocSearchCriterion>
   <Address>
      <CityName Code="28211" CodeContext="GEO.supplierCode"/>
      <CountryName Code="US" CodeContext="GEO.supplierCode"/>
   </Address>
</VehLocSearchCriterion>

supplier context (one supplier)

Allows to specify city and country codes of certain supplier and get offers only from this supplier. You can use this case if you know exact location codes from suppliers and would like to get offers only from some supplier.

<VehLocSearchCriterion>
   <Address>
      <CityName Code="1113" CodeContext="supplierCode"/>
      <CountryName Code="13" CodeContext="supplierCode"/>
   </Address>
</VehLocSearchCriterion>

customer context

If it is agreed to support customer context, GP Travel HUB can do search by customer-specific city and country codes. In this case your application can provide your own city and country code, GP Travel HUB will resolve it via GEO-tree and send requests to supplier.

<VehLocSearchCriterion>
   <Address>
      <CityName Code="NYC" CodeContext="ABC.supplierCode"/>
      <CountryName Code="USA" CodeContext="ABC.supplierCode"/>
   </Address>
</VehLocSearchCriterion>
  • In this example "ABC" is a customer identifier. Ask about your specific identifier during integration.

Country code

GEO context (one supplier)

When the CodeContext is "GEO.<supplierCode>" then the CountryName Code must be specified in GEO context, and then the search request goes only to the supplier specified. So, you can send a request to the particular supplier, even if you don’t know supplier-specific Country Code.

<VehLocSearchCriterion>
   <Address>
      <CountryName Code="US" CodeContext="GEO.supplierCode"/>
   </Address>
</VehLocSearchCriterion>

supplier context (one supplier)

Allows to specify country code of certain supplier and get offers only from this supplier. You can use this case if you know exact location codes from suppliers and would like to get offers only from some supplier.

<VehLocSearchCriterion>
   <Address>
      <CountryName Code="1287" CodeContext="supplierCode"/>
   </Address>
</VehLocSearchCriterion>

customer context

If it is agreed to support customer context, GP Travel HUB can do search by customer-specific country codes. In this case your application can provide your own country code, GP Travel HUB will resolve it via GEO-tree and send requests to supplier.

<VehLocSearchCriterion>
   <Address>
      <CountryName Code="USA" CodeContext="ABC.supplierCode"/>
   </Address>
</VehLocSearchCriterion>
  • In this example "ABC" is a customer identifier. Ask about your specific identifier during integration.

City code

GEO context (one supplier)

When the CodeContext is "GEO.<supplierCode>" then the CityName Code must be specified in GEO context, and then the search request goes only to the supplier specified. So, you can send a request to the particular supplier, even if you don’t know supplier-specific Country Code.

<VehLocSearchCriterion>
   <Address>
      <CityName Code="28211" CodeContext="GEO.supplierCode"/>
   </Address>
</VehLocSearchCriterion>

supplier context (one supplier)

Allows to specify city code of a certain supplier and get offers only from this supplier. You can use this case if you know exact location codes from suppliers and would like to get offers only from some supplier.

<VehLocSearchCriterion>
   <Address>
      <CityName Code="1113" CodeContext="supplierCode"/>
   </Address>
</VehLocSearchCriterion>

customer context

If it is agreed to support customer context, GP Travel HUB can do search by customer-specific city acodes. In this case your application can provide your own city code, GP Travel HUB will resolve it via GEO-tree and send requests to supplier.

<VehLocSearchCriterion>
   <Address>
      <CityName Code="NYC" CodeContext="ABC.supplierCode"/>
   </Address>
</VehLocSearchCriterion>
  • In this example "ABC" is a customer identifier. Ask about your specific identifier during integration.

2.1.2. SEARCH BY AIRPORT

You have an opportunity to search vendor locations in a certain airport. For this type of search Airport should be specified as IATA Airport code with CodeContext=“IATA.supplierCode”.

<VehLocSearchCriterion>
   <RefPoint Code="LGW" CodeContext="IATA.supplierCode"/>
</VehLocSearchCriterion>

2.1.3. SEARCH BY COORDINATES

Allows to perform search, specifying latitude and longitude of a point as well as radius of search.

<VehLocSearchCriterion>
   <Position Latitude="53.35" Longitude="-6.23"/>
   <Radius Distance="50" DistanceMeasure="km"/>
</VehLocSearchCriterion>

2.1.4. SEARCH BY PICKUP POINT

Allows to search for a particular Pickup Point if you already know it.

<VehLocSearchCriterion>
   <PickUpLocation LocationType="Point" LocationCode="71" CodeContext="supplierCode"/>
</VehLocSearchCriterion>

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.