cj-malone / schema

Overture Maps Schema

Overture Maps Schema

The Overture Maps schema working group is responsible for designing the Overture Maps Data Schema and the Global Entity Reference System (GERS).

Documentation

The contents of this repository are presented in a more human-friendly format at docs.overturemaps.org

Feedback

Please use the Discussions in this repository to provide feedback.

---

Licensing

Copyright Licensing

Each Working Group must specify the copyright license under which it will operate prior to initiating any work on any Draft Deliverable or Approved Deliverable other than source code or datasets. Source code and dataset copyright licenses are discussed below.

Patent License

Each Working Group must specify the patent policy under which it will operate prior to initiating any work on any Draft Deliverable or Approved Deliverable. The patent policy for this Working Group is W3C https://www.w3.org/Consortium/Patent-Policy-20200915/

Source Code

Working Group Participants contributing code to this Working Group must do so in source code form, and agree that those source code contributions are subject to the Developer Certificate of Origin version 1.1, available at http://developercertificate.org/, the license indicated below, and any policies and governance rules included in the source code’s repository. Source code may not be a required element of an Approved Deliverable specification

• MIT License, available at https://opensource.org/licenses/MIT.

Dataset

Working Group Participants contributing data to a dataset to this Working Group agree that those data contributions are subject to the license indicated below. The dataset may not be a required element of an Approved Deliverable specification.

• For Overture data layers which are CDLA Permissive 2.0, there are no restrictions on use of external data other than the attribution requirements of that license.
• For Overture data layers which are ODbL, those layers must adhere to ODbL license terms, specifically whether any referenced data is considered a collective database or a derivative database. See OpenStreetMap Community Guidelines for definitions on the differences.

You are responsible for understanding the licenses relating to data you work with.