Menu

Hotel mapping: giving one hotel one ID across supplier feeds
📰

Hotel mapping: giving one hotel one ID across supplier feeds

DEV Community: backend·Travelexe edge91·16 days ago
#8ksCVuUE
#devtobackend#devto#dev#hotel#mapping
Reading 0:00
15s threshold

Disclosure: written by the TraveleXe team. We build Syncro, the hotel and room mapping system mentioned below.

If you sell hotels from more than one supplier, you've seen this: the same hotel appears four times in your search results, with four slightly different names, two addresses and coordinates 80 metres apart. Your "cheapest price" sort is now comparing a hotel against itself.

That's the hotel mapping problem. Here is how it's usually solved, and what we learned building it.

The problem in one table

Supplier Name Address Lat, Lng

A Grand Palm Resort & Spa 12 Beach Rd 25.1180, 55.1350

B The Grand Palm Resort Beach Road 12 25.1186, 55.1342

C GRAND PALM RESORT AND SPA DUBAI Jumeirah Beach Rd, 12 25.1179, 55.1351

A human sees one hotel. A database sees three.

Step 1: one canonical ID

The core design decision is a canonical record per physical property, with every supplier's hotel code linked to it.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.