Destination mapping solutions
Links supplier destination codes to a country → province → district → resort area hierarchy and to IATA codes.
Location and POI verifies every hotel's coordinates by comparing the data from different suppliers, and calculates the distance to the beach, airport, centre and public transport. Nearby points of interest (POI) come with the same region codes as destination mapping. The product will launch soon; you can apply for early access from the quote page.
{
"hm_id": "HM-1048213",
"location": {
"lat": 36.8541,
"lon": 31.0552,
"status": "verified",
"rejected": [
{ "supplier": "B", "reason": "lat_lon_swapped" },
{ "supplier": "C", "reason": "city_center" }
]
},
"destination_id": "TR-07-SERIK-BELEK",
"distances_km": {
"beach": 0.3,
"airport_AYT": 31.5,
"center": 3.8,
"public_transport": 0.4
},
"poi": [
{ "name": "Pine Coast Golf Club", "category": "golf_course", "distance_km": 1.6 },
{ "name": "Belek Lagoon Mall", "category": "shopping_mall", "distance_km": 4.2 }
]
} Every hotel sits at its real location on the map; records piled up in the city centre or with latitude and longitude swapped are filtered out.
Filters such as "close to the beach" or "close to the airport" work with the same data at all hotels.
The same region codes are used in the destination mapping hierarchy, so map and region filters do not contradict each other.
A correct coordinate is also one of the core signals of hotel mapping.
Coordinates from three suppliers for the same hotel
supplier,hotel_code,latitude,longitude,address
A,HTL-88213,36.8541,31.0552,"Belek Mah., Serik, Antalya"
B,40917,31.0552,36.8541,"Belek, Antalya"
C,TR-ANT-551,36.8969,30.7133,"Antalya" Verified location, distances and nearby points
{
"hm_id": "HM-1048213",
"location": {
"lat": 36.8541,
"lon": 31.0552,
"status": "verified",
"rejected": [
{ "supplier": "B", "reason": "lat_lon_swapped" },
{ "supplier": "C", "reason": "city_center" }
]
},
"destination_id": "TR-07-SERIK-BELEK",
"distances_km": {
"beach": 0.3,
"airport_AYT": 31.5,
"center": 3.8,
"public_transport": 0.4
},
"poi": [
{ "name": "Pine Coast Golf Club", "category": "golf_course", "distance_km": 1.6 },
{ "name": "Belek Lagoon Mall", "category": "shopping_mall", "distance_km": 4.2 }
]
} Sample data; the hotel, coordinates, distances and POI names are fictional. Region and airport names are real. Field names are an API v1 draft.
The coordinates different suppliers send for the same hotel are placed side by side under the hotel's HM ID.
Locations that do not match the address are filtered out; the data team verifies uncertain ones.
Distances to the beach, airport, centre and public transport are calculated from the verified coordinate.
Points of interest such as beaches, museums, shopping malls and golf courses come with the destination mapping regions.
The coordinates suppliers send are not always correct. Common errors: every hotel in an area given the coordinate of the city centre, latitude and longitude swapped, or a point that does not match the address. As a result, the map shows the wrong place, a “close to the beach” filter becomes unreliable, and the distances on the hotel page change depending on the supplier.
Location and POI gives every hotel a single verified coordinate, calculated distances and nearby points of interest. The product will launch soon; this page describes how it will work, and the fields and endpoints in the examples are an API v1 draft. For producing coordinates from an address, see the geocoding glossary page.
| Component | What it provides | Sample |
|---|---|---|
| Coordinate verification | Different supplier coordinates are compared and faulty locations are corrected | A record with latitude/longitude swapped is filtered out |
| Distances | Distance to the beach, airport, centre and public transport | 0.3 km to the beach |
| Nearby points | Beaches, museums, shopping malls, golf courses and other notable points | Golf course 1.6 km |
| Region code | The same hierarchy as destination mapping | TR-07-SERIK-BELEK |
Destination mapping ties a hotel to a country → province → district → resort region hierarchy; Location and POI uses the same region codes. A correct coordinate matters for hotel mapping too: location is one of the components of the match score. The general framework is in the hotel mapping guide.
A hotel’s own pool or private beach is not location but hotel amenities data.
For early access, coverage and pricing, you can request a quote.
Request
curl "https://api.hotelmapping.org/v1/hotels/HM-1048213/content?include=location,poi" \
-H "X-API-Key: $HM_API_KEY" Response
{
"hm_id": "HM-1048213",
"location": { "lat": 36.8541, "lon": 31.0552, "status": "verified" },
"destination_id": "TR-07-SERIK-BELEK",
"distances_km": { "beach": 0.3, "airport_AYT": 31.5, "center": 3.8 },
"poi": [
{ "name": "Pine Coast Golf Club", "category": "golf_course", "distance_km": 1.6 }
]
} Code samples are illustrative; field names may change in the v1 release.
Location and POI will launch soon; the exact date has not been shared yet. You can write to us from the quote page for early access.
A POI (point of interest) is a notable place around a hotel, such as a beach, museum, airport, shopping mall or golf course.
Distances to the beach, airport, centre and public transport are calculated from the verified hotel coordinate.
Destination mapping ties a hotel to a country, province, district and resort region hierarchy. Location and POI gives the hotel's exact coordinate, distances and surrounding points. Both use the same region codes.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.