https://github.com/opengeospatial/Overture-Maps-GERS
https://github.com/opengeospatial/Overture-Maps-GERS
Last synced: 5 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/opengeospatial/Overture-Maps-GERS
- Owner: opengeospatial
- Created: 2025-08-04T20:45:27.000Z (12 months ago)
- Default Branch: main
- Last Pushed: 2026-06-30T22:09:46.000Z (19 days ago)
- Last Synced: 2026-06-30T23:11:24.771Z (19 days ago)
- Language: HTML
- Size: 2.03 MB
- Stars: 2
- Watchers: 2
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: history.md
Awesome Lists containing this project
- awesome-gers - opengeospatial/Overture-Maps-GERS
README
# Draft OGC GERS Framework Community Standard
## The standardization problem
Numerous datasets/resources with geospatial content reference the same real-world entities but use their own semantics, conventions, identifiers, and vocabulary, making them difficult to merge and combine.
## What is the GERS Framework?
The framework as originally defined by the [Overture Maps Foundation](https://overturemaps.org) provides a model for generating, cataloguing, and
leveraging the use of unique, persistent identifiers for real-world entities such as buildings, places, and roads in their open map data.
These IDs and associated components of the Framework facilitate data interoperability and sharing by enabling different datasets to be
easily connected and enriched using a common reference. As such, the Frameowrk defines a number of components to leverage the value of the unique identifiers.
NOTE: The unique identifiers as generated and used in the context of the GERS Framework are _not meant_ to replace any existing feature identifiers. Instead, they are meant to augment
existing data and associated identifers.
## Who supports using/implementing the GERS framework?
The use of unique IDs and the associated support framework is supported by a diverse community of over 40 organizations, including Amazon Web Services (AWS), Meta, Microsoft, TomTom, and Esri. These companies have committed to and depend on the implementations of the framework. Many of the Overture Maps supporting organizations are also OGC Member organizations.
## What does a GER ID look like?
GERS IDs as defined in the Framework Community Standard use the [UUID - Universally Unique Identifier](https://en.wikipedia.org/wiki/Universally_unique_identifier) format. Every ID is structured following the standard UUID format (e.g., 12345678-1234-5678-1234-567812345678), making them:
* Globally unique
* System-agnostic
* Easy to implement in any database or application
* Compatible with existing UUID tools and libraries
Why it matters:
* Universal compatibility: UUIDs work in every modern database and programming language
* No collisions: Guaranteed uniqueness across all systems
* Standard tooling: Leverage existing UUID libraries and utilities
## OGC Justification Document
A draft version of the Community Standard justification document can be viewed here:
* [GERS Community Standard Justification](https://github.com/opengeospatial/Overture-Maps-GERS/blob/main/gers-justification/gers-work-item-justification.adoc)
## General
This repository contains files and documents for the OGC Overture GERS Community Standard activity
* The OGC GERS Community Standard Justification Document
* Draft GERS Framework Community Standard
* Issues for discussion and resolution related to the proposed changes.
* Response to comments received during the public comment period.
## Structure
`sources/`::
source of documents, images, and models