Technique for structuring a navigation database

Patent metadata

Field	Value
Publication number	US-9280567-B2
Application number	US-201213669585-A
Country	US
Kind code	B2
Filing date	Nov 6, 2012
Priority date	Nov 7, 2011
Publication date	Mar 8, 2016
Grant date	Mar 8, 2016

Abstract

A technique of structuring a navigation database is provided, wherein the navigation database includes at least route link data for a predetermined geographic area. A method implementation of the technique includes organizing route link data associated with the predetermined geographic area into at least one routing cluster; providing the at least one routing cluster with a cluster identifier; and storing the at least one routing cluster together with the cluster identifier in the navigation database.

First claim

What is claimed is:

1. A method of structuring a navigation database, wherein the navigation database comprises at least route link data for a predetermined geographic area, comprising:
organizing route link data associated with the predetermined geographic area into at least one routing cluster;
providing the at least one routing cluster with a cluster identifier; and
storing the at least one routing cluster together with the cluster identifier in the navigation database,
wherein the predetermined geographic area is further partitioned into tiles,
wherein the organizing step further comprises, for each tile, organizing route link data associated with the tile into at least one routing cluster, and
wherein the at least one routing cluster is addressable by at least one index structure comprising the cluster identifier that is provided to the navigation database.

2. The method according to claim 1 , wherein the at least one index structure associated with the routing clusters is organized independently from the tile structure.

3. The method according to claim 1 , wherein each routing cluster is provided with at least one route link.

4. The method according to claim 1 , wherein a number of route links organized within the at least one routing cluster does not exceed an upper threshold value.

5. The method according to claim 1 , wherein a number of routing clusters depends on a route link density.

6. The method according to claim 1 , further comprising:
re-organizing route link data organized in at least one routing cluster into at least one new routing cluster; and
storing the at least one new routing cluster in the database.

7. The method according to claim 6 , wherein the at least one new routing cluster is provided with a cluster identifier.

8. The method according to claim 1 , wherein each route link within the at least one routing cluster is provided with a route link identifier.

9. The method according to claim 8 , wherein the size of the route link identifier is determined by the upper threshold value indicative of the maximum number of route links organizable within a cluster.

10. The method according to claim 1 , wherein the navigation database further comprises at least one of map display data, destination entry data, POI data, TMC data and other enhanced navigation data.

11. The method according to claim 10 , wherein the at least one of map display data, destination entry data, POI data, TMC data and other enhanced navigation data are organized into variable navigation data clusters.

12. A computer program product with program code for carrying out the method according to claim 1 , when the computer program product is executed on a computer device.

13. The computer program product of claim 12 , which is stored on a non-transitory computer-readable medium.

14. A navigation database comprising;
at least route link data for a predetermined geographic area, wherein the predetermined geographic area is partitioned into tiles, wherein for each tile the at least route link data associated with the tile are organized into at least one routing cluster with cluster identifier, and wherein the navigation database further comprises at least one index structure comprising the cluster identifier via which the at least one routing cluster is accessible.

15. The navigation database according to claim 14 , wherein the at least one routing cluster is a flexible routing cluster comprising a variable number of route links.

16. The navigation database according to claim 14 , wherein the cluster identifier is a permanent identifier.

17. A navigation device comprising the navigation database of claim 14 .

Assignees

• Elektrobit Automotive Gmbh

Inventors

• Fischer Sebastian
• Dormann Holger

Classifications

• G06F17/30289 Primary

  Physics · mapped topic

• G01C21/32

  Structuring or formatting of map data · CPC title

• G01C21/3881 Primary

  Tile-based structures · CPC title

• G06F16/21 Primary

  Design, administration or maintenance of databases · CPC title