Page History
...
Proposal 2 (item before meeting )
Short Summary Answer
GERS is 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. GERS is developed and governed within the Overture Maps Foundation, where it is used to provide stable entity identifiers for Overture’s open transportation datasets. At the same time, GERS is designed to be map‑agnostic and reusable beyond Overture: the identifiers can be associated with equivalent entities in other digital maps, allowing datasets referenced via GERS to be exchanged, compared, or integrated across different map ecosystems.
...
Digital maps evolve continuously, and their representations change over time. 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 repeated and costly re‑matching and conflation. A global entity reference system addresses this by providing 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.
...
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 provides the following benefits:
- Minimizes identifier churn
- Improves long‑term data consistency
- Reduces downstream recalculation and validation effort
...
Within this approach, all geometry segments between two such decision points are are merged into a single GERS entity and assigned a unique identifier. This ensures that a road section remains consistently identifiable over time, independent of how many attributes may change along it. Minor geometric shifts (e.g. due to map updates causing slight positional differences) do not affect the identity, as long as the underlying topology remains unchanged. By By basing segmentation on network topology rather than on attribute variation, GERS creates a stable reference layer that aligns with how users conceptually perceive roads—as connected sections between intersections—while minimizing unnecessary fragmentation of identifiers across map versions and providers.
...
Within each stable GERS section, attribute variation is handled using linear referencing offsets, rather than by splitting the underlying geometry. Instead of assigning a new identifier every time an attribute changes (e.g. speed limit, surface type, lighting), GERS retains a single section ID and expresses changes as positions along that section, see figure below.
These offsets indicate where along the section a specific an attribute begins and ends. As a result, multiple attribute changes can coexist on the same base entity without affecting its identity. This avoids repeated segmentation and preserves the continuity of the road section, while still allowing precise localization of changes. This This separation of of entity identity (the section) and attribute variation (offset-based references) reduces identifier churn, avoids costly recalculation of dependent data (such as traffic flow or direction), and supports consistent data association across map updates and datasets.
...
Where a correspondence is found, the external data can directly inherit the existing GERS IDs. Where no match exists—indicating missing or newly identified road geometry—the system identifies these gaps and assigns assigns new GERS identifiers to previously unmatched sections, thereby extending the reference network. Once assigned, these GERS identifiers act as stable anchors that allow the dataset to interoperate enable interoperability with other map ecosystems. The result is that data originally tied to a specific geometry (e.g. latitude/longitude or proprietary IDs) becomes referenced to a shared, map‑agnostic entity layer, enabling integration, exchange, and reuse across platforms.
...
- 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
| Requirement | GERS suitability | Notes |
|---|---|---|
| Long‑term stable entity identifiers | Excellent |
| GERS assigns identifiers to topological road sections between decision points, so they remain stable despite attribute changes and minor geometry updates. | ||
| Cross‑map data interoperability | Excellent | GERS provides a shared, map‑agnostic reference layer that enables alignment of data across different map models and providers. |
| Reduction of re‑conflation effort | Excellent | GERS reduces re‑conflation by maintaining stable IDs and using linear referencing instead of splitting the geometry for each attribute change. |
| Real‑time message encoding | Not the primary purpose | GERS is designed for persistent referencing and interoperability rather than for dynamic, on‑the‑fly message encoding. |
| Compact transmission format | Not applicable | GERS focuses on stable identification and integration, and therefore does not aim to provide a compact or bandwidth‑efficient encoding format. |
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.
...
- Home - Overture Maps Foundation
GERS - Global Entity Reference System | Overture Maps - Overture Maps Foundation
- TomTom Global Entity Matcher (GEM)
- GERS Tutorial | Overture Maps Documentation
- Using the GERS "system" | Overture Maps Documentation
Comments
| 1 | |||
| 2 | |||
| 3 |
Proposal 1 (item before meeting )
...
