Navigation Data Standard

from Wikipedia, the free encyclopedia

Navigation Data Standard ( NDS ; German navigation data standard ) is a standardized format for map databases in navigation systems , developed on the basis of quality requirements of the automotive industry jointly by automotive manufacturers and suppliers. The current version is version 2.5.3 from March 13, 2018. The registered association NDS eV is responsible for the development. Members of the association are automobile manufacturers , providers of geodata and manufacturers of navigation systems .

The aim of the NDS development is a standardized binary database format that enables the exchange of map data between different navigation systems. In NDS, map data and navigation software are separated so that different navigation products for end users can be developed on the basis of NDS. In addition to this interoperability, NDS supports incremental updates, digital rights management and offers a high degree of compactness.

NDS-based navigation products have been on the market since 2012, including from BMW , Daimler and Volkswagen .

aims

The aim of NDS is to develop a world-leading industrial standard that meets the quality requirements of the automotive industry. The format should:

  • Find diverse applications in the navigation industry and are used by leading manufacturers of navigation systems
  • Be interoperable for different systems
  • Support map updates
  • Can be used worldwide
  • Meet the specific requirements of different countries

The quality requirements of the automotive industry include that:

  • NDS is jointly developed by leading automotive manufacturers and suppliers.
  • NDS supports all use cases in the automotive industry for map data.
  • NDS supports advanced navigation technologies such as eHorizon, autonomous driving and cloud applications.
  • The widespread use and implementation in various systems ensure that the standard is continuously checked and further developed.

In order to achieve this goal, NDS has set itself the following goals:

  • Ensure quick integration of extensions and changes to the standard
  • Ensure easy applicability and efficient implementation of the standard in order to promote global use in automotive applications
  • Ensure legal protection of the use of NDS
  • Offer certification of navigation databases for NDS compliance

In order to promote the acceptance of the standard, NDS supports development projects that use NDS, among other things through tools and technical consulting. In addition, the standard is constantly being technically developed, and new members are being recruited for the standardization consortium.

NDS architecture

NDS uses the SQLite database format . An NDS database can consist of several product databases, which in turn can be divided into individual update regions. This structure enables flexible but consistent updates as well as the integration of databases from different manufacturers in a common NDS database.

Within a product database there are functional modules (building block), levels (layers) and the geodata itself. Map data is organized in adjacent tiles. A magnification level, the level, determines the edge length of a tile. At level 0, a tile spans half the earth (east or west of Greenwich). From one level to the next, the geographical edge length of the tile is practically halved, i.e. the area shown is quartered. More precisely, the length and width angles of the tile are halved from one level to the next. For example, in level 13 a tile covers approx. 2.4 * 2.4 km. WGS84 is used as the card system.

Product database

An NDS product database is supplied by a specific manufacturer and has its own version control. This means that it can be updated independently of other product databases. Within a product database there are one or more functional modules, e.g. B. Data for route calculation or map display. A product database covers a specific geographic area, which can be divided into individual update regions. Example of a product database: "Europe Basic Navigation" from TomTom .

Update region

An update region represents a geographic area within a product database whose geodata can be updated independently of other regions. The concept of the update regions thus enables incremental and partial updates of defined geographic areas within an NDS database. Example: Within the "Europe basic navigation" product, each European country is modeled by its own update region.

Functional modules

Functional modules in NDS format

All geospatial data within an NDS database belong to a specific functional module. Each module covers certain functions, e.g. B. Names for entering a destination, route calculation, map display, etc. In order for certain tasks of a navigation system to be able to be fulfilled, the navigation software has to summarize and evaluate data from different modules. So z. B. for the calculation and display of a route data from the modules for route calculation and map display are combined.

An update region can contain multiple functional modules. Therefore, there can be multiple instances of the same module in a product database with multiple update regions. Example: In a European database there is a module of the type "Basic Map Display" (map display) for the update region France and a module of the type "Basic Map Display" for the update region Germany.

Tools and Documentation

The NDS database structures as well as the rules regarding interoperability and updates are described in the NDS documentation. In addition, the NDS consortium provides its members with various tools for the development, validation and certification of map databases:

  • NDS SQLite reference implementation
  • Relational DataScript (RDS tool): Code generator for database access classes in Java and C ++
  • Certification Bench: Validation of NDS databases for NDS conformity on the basis of detailed test cases; Issuing NDS certificates
  • Investigation Modules: Tool for testing NDS databases on hardware
  • Database Inspector: Desktop tool for visualizing NDS databases

Members and committees

The members of the NDS e. V. are companies or associations.

The NDS members each appoint representatives who represent the member in the various NDS bodies. NDS has the following bodies:

  • Management (Board): Legal representative of the NDS eV
  • General Assembly (GA): Forum for all NDS members. The General Assembly monitors the work of the NDS bodies, approves budgets and sets the annual membership fees
  • Steering Committee (SC): responsible for managing the work in the NDS committees
  • Technical Committee (TC): responsible for deciding technical issues
  • NDS working groups (WG): work on individual technical topics such as B. the further development of the database format, autonomous driving and hybrid navigation
  • Validation and Certification Board: coordinates the development of validation tools and organizes the issuance of NDS certificates

Individual evidence

  1. ^ NDS Association. In: www.nds-association.org. Retrieved November 2, 2016 .
  2. Navigation Data Standard . NDS eV . Retrieved March 10, 2015.
  3. OpenStreetMap wiki . OpenStreetMap . Retrieved March 25, 2015.
  4. ^ The NDS Standard . NDS eV . Archived from the original on February 13, 2015. Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice. Retrieved February 13, 2015. @1@ 2Template: Webachiv / IABot / www.nds-association.org
  5. Navigation Data Standard (NDS): Soon to be an industry standard? . all-electronics.de . Retrieved March 10, 2015.
  6. How easy is it getting there? On the way - NDS success stories from 2014 . nds-association.org . Retrieved March 10, 2015.
  7. NDS (Navigation Data Standard) . TomTom . Retrieved April 24, 2018.