reference:system-architecture:data-provider-integrations
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| reference:system-architecture:data-provider-integrations [2025/08/25 13:32] – [4. TeleAtlas (TomTom, automotive)] runarbe | reference:system-architecture:data-provider-integrations [2025/08/25 14:17] (current) – [5. Open Street Map (data source for many)] runarbe | ||
|---|---|---|---|
| Line 127: | Line 127: | ||
| ===== 5. Open Street Map (data source for many) ===== | ===== 5. Open Street Map (data source for many) ===== | ||
| + | |||
| + | ==== 5.1 Steps to establish a data provider agreement ==== | ||
| + | |||
| + | The process of establishing an agreement to provide addressing data to OpenStreetMap (OSM) involves several steps, including initial engagement, requirements assessment, legal and compliance review, and any necessary negotiations. OSM operates as a collaborative project rather than a traditional commercial data provider, so the approach is slightly different from a typical service agreement. | ||
| + | |||
| + | === Initial engagement === | ||
| + | |||
| + | MoHUP can initiate contact with the OpenStreetMap community by reaching out to the local OSM chapter in Oman or engaging with the global community through their online forums or the OSM Foundation. OpenStreetMap' | ||
| + | |||
| + | === Requirements assessment === | ||
| + | |||
| + | To contribute addressing data to OSM, MoHUP must ensure that their data meets the criteria set out by OSM, which typically includes data accuracy, relevance, and compliance with OSM's guidelines for data contributions. Detailed information regarding contribution standards can be found on the OSM Wiki at https:// | ||
| + | |||
| + | === Legal and compliance review === | ||
| + | |||
| + | MoHUP should conduct a legal review to ensure that the data they wish to contribute complies with Oman's legal frameworks, particularly regarding privacy and data sharing laws. It is also important to assess compatibility with OSM's licensing terms, which are outlined under the Open Database License (ODbL). More details on compliance and licensing can be found at https:// | ||
| + | |||
| + | === Negotiation (if any) === | ||
| + | |||
| + | Since OpenStreetMap operates as a volunteer-driven project, there may not be traditional negotiations. However, MoHUP may engage with the community to discuss how to best integrate and maintain their data, ensuring mutual understanding and cooperation. | ||
| + | |||
| + | ==== 5.2 Implementation ==== | ||
| + | |||
| + | Data can be provided to OpenStreetMap through their platform using tools such as JOSM (Java OpenStreetMap Editor) or the iD editor available on the OSM website. MoHUP should ensure that the data they upload conforms to OSM’s data model and tagging schemes, facilitating easy integration into the existing map structure. Volunteer community members or dedicated data import guidelines (https:// | ||
| + | |||
| + | ==== 5.3 Monitoring and review ==== | ||
| + | |||
| + | The monitoring and review process involves regular checks to ensure data accuracy and relevance. Since changes can be made by any OSM contributor, | ||
reference/system-architecture/data-provider-integrations.1756128762.txt.gz · Last modified: by runarbe
