GERS: Global Property IDs for Hospitality and Travel

The Problem

The travel and hospitality ecosystem is hampered by inconsistent place identifiers and fragile data flows. Property records live in bespoke cross-reference tables, content updates arrive unpredictably, and multiple, conflicting sources of truth create reservation mismatches, repeated manual harmonization, and slow partner onboarding. Vendor-specific data formats, isolated legacy platforms, and largely manual workflows stretch deployment timelines and bog down technical teams. At the same time, regulatory and trust requirements are evolving fast and exposing operators to emerging fraud techniques and complex cross-party data exchange challenges, which drive up compliance burdens and operating costs. The result is lost revenue, higher expenses, poorer guest experiences, and reduced ability to innovate across hotels, hostels, motels, guest houses, restaurants, cafes, bars, golf courses, spas, car rental agencies, information centers and other points of interest.

GERS: One Canonical ID for Every Place

GERS solves the root problem by removing ambiguity about what a place actually is. Instead of dozens of id systems, one-off cross-reference tables, and fragile reconciliation processes, GERS provides a single, persistent identifier for every physical place. That persistent ID becomes the connective tissue across maps, PMSs, booking engines, delivery networks, public registries, and AI agents. When every dataset references the same stable place key, joins become a simple, repeatable operation rather than a costly, error-prone engineering project.

How GERS Solves the Problem in Practice

The practical tooling around GERS is what makes the promise real. Overture publishes a large global places dataset together with bridge files, changelogs, and developer documentation so teams can match records with a single-column join, inspect results in a no-code Explorer, and consume versioned updates. That reduces time to market, shrinks integration costs, and cuts the volume of manual reconciliation work. Aligning GERS with travel industry schemas increases the likelihood that amenities, availability, and transactional hooks can flow through automated pipelines, which makes partner onboarding faster and system behavior more predictable for guests.

Beyond bookings and guest communications, stable place identifiers enable various cross-industry workflows:

  • Accurate pickup and dropoff coordination with ride-hailing and car rental partners
  • Reliable last-mile delivery and supplier logistics
  • Location-aware incident response and public safety coordination
  • Consistent identifiers for payments, insurance and financial reconciliation
  • Better planning and data sharing with tourism boards and urban authorities
  • Seamless accessibility services for guests with special needs
  • Improved coordination for events, catering and on-site vendors
  • Consolidated guest reviews from multiple platforms for attribution and unified feedback analysis

Trust, Compliance and AI Benefits

GERS also strengthens data reliability and trust, which matters for security, compliance, and AI. Deterministic place identifiers let you anchor facts and transactions to a known real-world object, improving auditability and reducing the surface for spoofing or mismatched information. A shared place ID simplifies multiparty data exchange because every participant can point to the same canonical reference instead of inventing bespoke mappings. For AI use cases, stable identifiers improve grounding and traceability, lowering the risk of inconsistent or fabricated answers.

Preserve Local Governance while Adopting GERS

Adopting GERS is not a substitution for domain governance. The best practice is to treat GERS as the canonical place layer and build hospitality-specific metadata, permissioning, and temporal state on top. That pattern preserves local authoritative control while unlocking broad interoperability, lower operating cost, and new capabilities such as publishing property-authoritative agent endpoints. For hotels and venue operators, the result is fewer integration headaches, more consistent guest experiences, and a scalable foundation to build next-generation services that actually interoperate across the travel ecosystem.

Standards in Action

Overture Maps partners with the OpenTravel Alliance to develop registry schema extension standards for the travel industry. inHotel is an active contributor to the task force, helping define open extensions that attach travel and hospitality attributes to the base place identifiers.

GERS Property ID & Location Intelligence Services from inHotel

Aligned with our mission to support people in travel and hospitality through AI, we provide a GERS management service for hotels, hostels, restaurants, cafes, bars, car rental stations, golf courses, spas, tour operators and other venues. We help companies discover their GERS ID, map and verify property records, maintain authoritative metadata, associate AI agent endpoints and manage change so partners and AI agents can join reliably. We do this because geospatial grounding is essential for AI agents to truly represent a property, anchor answers to the correct location and preserve authoritative context for transactions and recommendations.

Learn more

What is GERS and who publishes it?

GERS is the Global Entity Reference System: an open, universal system of persistent identifiers for geospatial entities (places, buildings, roads, addresses) published by the Overture Maps Foundation. It is explicitly designed to be an open registry that makes joining datasets and onboarding data much simpler.

Does GERS only cover hotels and lodging properties?

No. GERS covers all geospatial entities across industries - everything from buildings and roads to places used by automotive, logistics, urban planning, local search, and more. That broad scope is exactly what allows hotels, restaurants, golf courses and wellness centers to interoperate with car rental systems, mapping platforms, public administration datasets and many others.

Has the industry tried unique hotel property identifiers before?

Yes. The hospitality sector has seen multiple attempts and working groups across associations and projects to define hotel-specific identifiers, including work on unique hospitality identifiers and other registry efforts over many years. Those efforts document the problem and the need, but they do not negate the arrival of a global open standard like GERS.

Why does GERS make previous hotel-only registries less compelling or irrelevant today?

GERS provides an open, maintained, and large-scale global reference that already assigns persistent IDs to billions of entities and supplies tooling to join data. When you have an open global backbone that covers hotels and everything around them, creating a separate, proprietary or industry-only registry duplicates work and fragments interoperability. The faster route is to adopt and interconnect with GERS.

Is GERS production-ready for hotel use now?

Yes. Overture published GERS with documentation, tooling and bridge files that let organizations join their existing records to GERS IDs via a single-column join, which is exactly the practical onboarding pattern hotels and vendors need. That means hotel tech stacks can begin mapping to GERS immediately.

Do hospitality-only ID projects offer registry management features that GERS lacks?

GERS already includes the core registry primitives: persistent IDs, changelogs, reference maps and bridge files for joinability. Many registry-management features (versioning, pointers, permissioned links) are planned to be implemented as layers that reference GERS IDs. Building a separate registry for functionality that can sit on top of GERS would create duplication rather than leveraging a global standard.

Do ownership, sub-units, timeshares, or changing management need a hospitality-native ID and permission model?

These are real operational needs: ownership relationships, sub-units and dynamic control do require identity, permissioning and temporal state management. But that does not require replacing a global ID system. Best practice is to reference GERS IDs as the canonical place identifier and layer hospitality-specific identity, ownership metadata, permission pointers and temporal state on top. That preserves global interoperability while solving hospitality complexity locally.

Can GERS bridge or extension layers preserve the hotel’s “authoritative source of truth”?

Yes. You can maintain an authoritative hotel registry or internal record and publish pointers that map that record to the GERS ID for the physical place. That keeps your control of the authoritative data while gaining universal joinability with all other datasets that use GERS. Overture explicitly supports bridge files and linking patterns for this purpose.

Is GERS open and free to adopt?

Yes. GERS is part of Overture’s open map data initiative and is released as open data with published documentation and datasets. That openness eliminates licensing friction and vendor lock-in that can arise from closed or paid registries.

What requirements do hotels have for permissions and privacy as related to a unified property ID?

Permissioning and privacy controls are orthogonal to the existence of a global ID. The right pattern is to use GERS as the neutral identifier while implementing access control, privacy-preserving pointers, authentication and consent at the layer that holds the sensitive data. That model avoids duplicating identifiers while keeping private data protected under your governance.

As GERS takes hold as a global standard, do hospitality-only IDs or vendor bespoke IDs still serve a useful purpose?

Yes, hospitality-focused projects can add value by building domain-specific metadata, permissions, and workflows that reference GERS IDs. The pragmatic approach is not to avoid GERS but to interconnect: publish pointers or records that resolve to GERS IDs. That keeps global interop intact while offering hospitality-specific features.

If hospitality-only property ID initiatives charge subscription fees, does GERS create a free alternative?

GERS provides a free, open backbone for identifiers and joining that any vendor or hotel can use. That means hotels and vendors have a no-cost path to global identifiers and can choose to build domain services on top of it without mandatory subscription lock-in to an industry-only identifier. The economic choice is significant: choose open commons plus optional value-added services, not forced dependency.

How does GERS help with AI and trustworthy data pipelines?

AI systems need deterministic identifiers to ground facts to the right real-world assets. GERS supplies persistent IDs and changelogs, making it easier to trace, audit and bind data to a place. That improves data retrieval accuracy, auditability and reduces the risk of AI making inconsistent or fraudulent inferences about properties.

What practical steps should a hotel or a hospitality tech vendor take today to benefit from unified property IDs?

Hospitality companies should map their internal property records to GERS IDs using Overture’s bridge files. For hospitality-specific needs, build a metadata layer that references GERS IDs rather than issuing an alternative global identifier. That gives immediate interoperability and keeps future integration costs low.

Won’t GERS slow down hospitality innovation because it is generic?

No. Generic, open primitives accelerate innovation by avoiding reinvention. Having a shared identifier for places lets many teams build complementary services without repeated reconciliation work. Hospitality innovation wins when you standardize the stable stuff and iterate quickly on the domain-specific layers above it.

If I still want a hospitality-specific governance or registry, what is the best design choice?

Design it as a hospitality metadata and governance layer that references GERS IDs. Provide role-based access, verified authoritativeness and change notifications at that layer. That pattern secures hospitality needs while preserving universal joinability and preventing fragmentation.

How can I obtain a global, persistent ID for my hotel?

Use a GERS ID from Overture Maps' Global Entity Reference System, an open worldwide registry of persistent place identifiers that works across mapping, distribution, payments, public datasets and AI pipelines; GERS IDs have already been assigned to a vast number of places, so in many cases your property already has one and you only need to look it up in the GERS dataset. You can self-serve with Overture’s datasets and documentation, have a developer join your records using GERS bridge files, or if you are an inHotel customer, inHotel will map and verify your property's existing GERS ID at no charge.

Does my hotel already have a globally unique property ID?

Yes. Most hotels already have one or more globally unique identifiers: GERS has preassigned IDs for a vast number of places, including bed and breakfasts, hotels, hostels, lodges, golf courses, guesthouses, motels, resorts, serviced apartments and many vacation rentals. Other global systems that likely include IDs for your property are Google Maps (Place IDs) and OpenStreetMap (OSM) IDs. GERS aggregates place data from multiple sources and is purpose-built as a free, open, universal place identifier that supports interoperability both inside and outside hospitality. You can discover your GERS ID in the Overture Maps Explorer (https://explore.overturemaps.org) or by using inHotel’s GERS discovery and management tools.

Why will registries only for hospitality lead to isolation, interoperability challenges and high hidden costs?

A hospitality-only registry fragments place identity and forces every partner into bespoke adapters, repeated reconciliation, prolonged testing, heavier support and audit work, and slow partner onboarding; those hidden integration costs are often very large over time. Custom registries also reduce composability: every new partner or service requires a fresh mapping project, increasing operational risk and blocking fast innovation across industries such as airlines and rail, ride sharing and taxis, car rental and EV charging networks, postal and courier delivery, logistics and freight, mapping and GIS providers, public sector and urban planning, payments and banking, insurance, real estate, tourism platforms and OTAs, telecom and IoT, and AI agent ecosystems. Luckily, that suboptimal approach is becoming obsolete as the world moves toward a shared, open place identifier: Overture Maps’ GERS provides a common backbone and the ecosystem momentum means many platform, data and public-sector partners are aligning on it. Smart hoteliers and hotel tech vendors should stop investing in isolated identifier projects and instead simply embrace GERS.