NNG

About NNG

NNG LLC is a leading global supplier of embedded and connected software for the automotive industry. Found in over 60 million devices worldwide, its solutions span Navigation, Maps, Connected Services, Cockpit, and Cybersecurity. NNG delivers the next generation of smart, secure, and connected mobility – from the cockpit to the cloud.

NNG map solutions include proprietary global and regional map data for automotive navigation, and its own OSM-based solution, NNG Maps, which was added to the company’s portfolio in 2023.

Usage of OpenStreetMap data

NNG Maps uses all potentially navigation relevant layers of the constantly improving OSM data. From administrative boundaries, highways and their attached attributes (e.g. access, maxspeed), through to several layers that function as entries for POIs (e.g., amenity, office, emergency).

When there are gaps in current OSM data (or if there is an automotive project that requires the improvement of specific data), third-party data sets are sourced, either from open access or paid services.

Third-party and OSM datasets are clearly separated, respecting all relevant licensing requirements of both OSMF and the third-party data owners.

Editing OpenStreetMap data

Our primary focus is on bug fixing.

All map data from providers, be it from a proprietary commercial data source, or OSM, goes through a rigorous, multi-level quality assurance process, comprising automated and manual data tests (map), software integration (map + navi), bench (office environment), and field (on the road) tests.

Data-related issues, found during any phase of the quality assurance process, are collected in internal test reports. After evaluation, depending on the fixability of the issue (complexity, sensitivity, justification source), it is corrected directly in OSM data, so that all potential users will benefit from the improvement, not only NNG customers.

Fixing can mean adding missing data or correcting discrepancies (e.g., those not meeting OSM wiki feature requirements).

Typically affected OSM keys

• geometry
• highway
• access
• relation restrictions
• maxspeed
• layer (bridge, tunnel)
• destination
• name (typo)

Issues that rely highly on local knowledge, or “sensitive data layers” (e.g. administrative boundaries), will only be edited after consultation with local OSM communities, asking either for advice (i.e., is it really an issue?) or contribution (promoting local community edits instead of those from NNG).

In the near future, in addition to distinct bug fixes in OSM data, we are looking to either publish data densification campaigns (MapRoulette) or conduct campaigns of our own (area surveying).

Tools and data sources

The primary data source for finding issues are our internal test reports. In addition to these, we use OSM quality assurance tools, such as osmose or keepright.at.

The identified issues, either from statistical analysis, emulated environments, or field test report checks are compared to the the OSM raw data (in QGIS) to determine if it is really an issue. After justification, the edits are carried out, mostly in JOSM.

Mappers & Contact

All company-wise changesets are marked with #nng.

Our key mapping account is osminng (on osm, edits, contrib, heatmap, chngset com.).

If you have a generic question about specific edits, or our activity in general, feel free to reach out to us at osmspecialist@nng.com. We welcome any suggestions on our editing activity, including ideas and improvements.