• Created by Teun Hendriks 

Prior revisions of answers

Proposal 1 (item before meeting14 Apr 2026 )

Short Summary Answer

GERS is a Global Entity Referencing System that assigns stable, long‑lived identifiers to real‑world transportation entities such as road segments. It enables consistent matching and integration of geospatial data across different digital maps and versions, reduces fragmentation caused by map updates, and supports interoperable data layering across systems and providers.

Why the need for a stable global entity reference system?

Digital maps evolve continuously. Road geometries may shift, attributes such as speed limits or surface types may change, and modeling rules differ between map providers. As a result, map‑specific identifiers are frequently regenerated, breaking continuity for downstream applications such as traffic management, analytics, or infrastructure monitoring.

Without a stable reference layer, each data update requires costly re‑matching and conflation. A global entity reference system addresses this by providing persistent identifiers that remain stable across map changes, enabling data to be associated with the same real‑world entity over time, even as map representations evolve.

How does GERS address differences between maps?

Different maps represent the same road in different ways. Segmentation rules, topology, and attribute modeling can vary significantly between providers or even between map versions of the same provider.

GERS addresses these differences by:

• Defining entities using decision‑point‑based segmentation rather than attribute‑driven splitting.
• Preserving identity independently of minor geometric changes.
• Applying linear referencing to model attribute changes without fragmenting the base entity.

This allows different maps to align their data to the same real‑world entity reference, even when their geometries or attributes are not identical.

Stakeholder Relevance / Rationale

Relevance and rationale for using GERS as a stable location referencing method for various stakeholders can be summarized as follows:

• Public Authorities:  Supports interoperable use of road network data across National Access Points, traffic management systems, and analytics platforms; reduces dependency on proprietary map identifiers.
• Content Providers:  Enables stable anchoring of traffic, infrastructure, and regulatory data to real‑world entities across multiple maps and updates; reduces re‑conflation effort.
• Service Providers: Facilitates consistent service behavior across map changes; enables long‑term data reuse and cross‑platform integration.
• OEMs: Supports persistent referencing of ADAS, navigation, and road attribute data across vehicle lifecycles and map updates.

Detailed Explanation

Linear Referencing and Entity Stability

GERS uses linear referencing principles to separate entity identity from attribute variation. Instead of splitting road geometry for every change (e.g. speed, lighting, surface), attributes are referenced along a stable base entity.

This approach:

• Minimizes identifier churn
• Improves long‑term data consistency
• Reduces downstream recalculation and validation effort

Tools and Ecosystem Support

GERS is supported by tooling that enables practical adoption:

• Map sectioning services to build consistent base entities

• Entity registries and explorers to inspect GERS IDs

• Global Entity Matching tools (e.g. TomTom GEM) to align external datasets with GERS‑identified entities

These tools allow both public and private datasets to participate in a shared reference framework.

Use Cases

• Traffic and Incident Management: Persistent association of events with road entities across map updates
• Infrastructure Analytics: Long‑term tracking of road attributes and performance
• Data Integration Platforms: Combining datasets from multiple sources without repeated conflation
• Standards and Reference Architectures: Providing a practical model for stable referencing concepts

Technical Considerations

• Map Dependency: GERS is map‑agnostic but requires digital map data to construct and maintain entity definitions
• Segmentation Rules: Decision‑point‑based segmentation is critical for stability
• Attribute Modeling: Best results are achieved when attribute changes use linear referencing rather than geometry splitting
• Governance: Long‑term stability depends on consistent application of modeling rules

Decision Guide

Implementation Notes

• GERS complements, rather than replaces, dynamic location referencing methods such as OpenLR
• GERS is best used as a foundational reference layer for storing and integrating geospatial data
• External datasets should be matched to GERS IDs using dedicated matching tools
• Attribute changes should be modeled using linear referencing where possible

References & Tools

For understanding GERS as a method, the following references are useful:

• 
  

• Overture Maps Foundation – GERS documentation
• TomTom Global Entity Matcher (GEM)

Comments