2.1. POSSIBLE SEARCH OPTIONS
2.1.1. SEARCH BY LOCATIONS
GP Travel HUB offers several alternatives for searching transfers by location. If the same city is specified in the TransferDeparture and TransferDestination elements then transfer search will be performed into this city. In other cases (when different cities are specified in TransferDeparture and TransferDestination elements), a search for transfer will be performed from one city to another.
| Search by | Description | Search example |
---|---|---|---|
1 | City code from supplier context (one supplier) | Allows to specify city code of certain supplier and get transfer offers only from this supplier. You can use this case if you know the exact location codes from suppliers and would like to get offers only from some suppliers. | <Criterion>
<TransferDeparture CodeContext="supplierCode" LocationCode="PAR" LocationType="City"/>
<TransferDestination CodeContext="supplierCode" LocationCode="PAR" LocationType="City"/>
</Criterion> |
2 | City code from GEO context (one supplier) | When the CodeContext is "GEO.<supplier>" then the LocationCode 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 Code (as described in p.1 above). | <Criterion>
<TransferDeparture CodeContext="GEO.supplierCode" LocationCode="29603" LocationType="City"/>
<TransferDestination CodeContext="GEO.supplierCode" LocationCode="29603" LocationType="City"/>
</Criterion> |
3 | City code from customer context | If it is agreed to support customer context, GP Travel HUB can search by customer-specific city codes. In this case your application can provide your city code, GP Travel HUB will resolve it via GEO-tree and send requests to the supplier.
| <Criterion>
<TransferDeparture CodeContext="ABC.supplierCode" LocationCode="29603" LocationType="City"/>
<TransferDestination CodeContext="ABC.supplierCode" LocationCode="29603" LocationType="City"/>
</Criterion>
|
2.1.2. SEARCH WITH AIRPORT
With any type of search listed below Airport should be specified as IATA Airport code with CodeContext=“IATA.supplierCode”.
| Search by | Description | Search example | |
---|---|---|---|---|
1 | Airport - City and vice versa | by GEO code | Allows to search transfers by city code from GEO context and airport code. GP HUB returns information about all transfers from the selected city or airport. | |
by supplier code | Allows to search transfers by city code from supplier context and airport code. GP HUB returns information about all transfers from the selected city or airport. | |||
2 | Airport - Hotel and vice versa | by GEO code | Allows to search transfers from an Airport to a particular Hotel or vice versa. Hotel code should always be specified in the supplier context. | |
3 | Airport-Airport | by IATA Airport code | Allows to search transfers between airports (CodeContext=“IATA.supplierCode” only). | |
4 | Airport only | by IATA Airport code | In this type of search, GP HUB returns all available transfers from the selected Airport (CodeContext=“IATA.supplierCode” only). | |
5 | Airport - Geo coordinates and vice versa | by IATA Airport code | Allows to search for transfers from the airport to a specific point by specifying latitude and longitude coordinates. |
2.1.3. SEARCH BY TRANSFERCODE
It is possible to search for Transfer needed with the help of TransferCode. It should always be in CodeContext=“supplierCode”.
2.1.4. SEARCH BY CATEGORY CODE
Allows to specify a particular transfer category the user is interested in.
2.1.5. SEARCH BY COORDINATES
Search by | Description | Search example | |
---|---|---|---|
Coordinates | Allows to perform search, specifying latitude and longitude of a point. |
| |
In case of a request with supplier code, we pass the coordinate data in a request to the supplier. | by supplier context |
Note: This functionality supported for limited suppliers. Please check with GP Travel HUB development if you are interested in a specific supplier.