METHOD OF GENERATING IMPROVED MAP DATA FOR USE IN NAVIGATION DEVICES

• US 20100030459A1
• Filed: 08/15/2007
• Published: 02/04/2010
• Est. Priority Date: 08/15/2006
• Status: Abandoned Application

• Current Assignee: TomTom International BV (TomTom NV)
• Original Assignee: TomTom International BV (TomTom NV)
• Inventors: Jurgens, Sven, Geelen, Pieter, Jones, Rory
• Application Number:
  US12/310,069
• Publication Number:
  US 20100030459A1
• Time in Patent Office: Days
• US Class Current: 701/200
• CPC Class Codes: G01C 21/26 specially adapted for navigation in a road network
• CPC Class Codes: G01C 21/3837 Data obtained from a single source
• CPC Class Codes: G01C 21/3856 Data obtained from user input
• CPC Class Codes: G06Q 50/01 Social networking

Abstract

In one embodiment of the present invention, an end-user can input a correction to a map error, directly on the device. The device is then able to use the correction without external processing of the correction. Hence, it is no longer necessary for an end-user to simply report errors to the map vendor over a web link, then wait for that map vendor to verify the error, update its maps and finally supply the end-user with updates—a cycle that can take months and sometimes years to complete. Instead, in one example embodiment, the navigation device can use the correction immediately. End-users can also share correction with other end-users and also with a shared remote server that aggregates, validates and distributes corrections.

Claims

1. Map data suitable for use with an electronic navigation device, the map data being structured to (i) enable an end-user to input a correction to the map data, directly on the device;

and (ii) to allow use of the correction without processing of the correction external to the device.

2. The map data according to claim 1, wherein the map data is structured as a database and multiple nodes in the map database are structured such that each node has a field or attribute to hold a correction input by an end-user.

3. The map data according to claim 1, wherein the map data is structured as a database and multiple segments in the map database are structured such that each segment has a field or attribute to hold a correction input by an end-user.

4. The map data according to claim 1, wherein the device is adapted to share one or more map corrections input to that device with other navigation devices;

and the device is adapted to download or otherwise receive map corrections created by different end-users operating the other navigation devices and wherein the map data is structured to hold those map corrections created by the different end-users.

5. The map data according to claim 1, wherein the map data is structured such that a map correction is categorised according to the user community for which it is applicable so that downloads of corrections to a navigation device can be limited to the applicable category or categories.

6. The map data according to claim 5, wherein the categories include at least one:

All users;

All motorists;

Heavy goods vehicle drivers;

Motorcyclists;

Limited speed vehicle drivers;

Pedestrians; and

Bicycles.

38. The map data according to claim 1, wherein a correction is at least one of the following:

associated with a level of trust;

automatically used by the device for route planning performed by the device;

associated with a unique identifier, associated with an identifier that is unique to the device;

associated with a time stamp defining when the correction was input; and

stored in a modular format that enables the correction to be applied in a routing algorithm independently of other corrections.

39. The map data according to claim 1, wherein the correction is at least one of:

to block a street;

to unblock a street;

to change a speed or speed limit applicable to a street;

to rename, move, add, delete, alter the telephone associated with or re-categorise a POI;

to add or change a name applicable to a city, part of a city, street or a part of a street;

to change a direction of traffic property of a road;

to add a road or connect two roads;

to add a turn restriction to a road;

to remove a turn restriction;

to add or modify house numbers, to mark a road as a toll road;

to remove an indication that a road is a toll road;

to add or modify signpost information for a road;

to modify motorway exit numbers;

to modify a postcode associated with a location;

to add or modify a height, weight or width restriction;

is compressed for OTA distribution, securely encoded; and

is encoded in a way that is not specific to any one supplier of the map data.

40. The map data according to claim 1, wherein the correction does not permanently affect the map data stored on the device.

41. The map data according to claim 40, wherein the correction is automatically removable if the area related to the fix has changed in a new release of the map data.

42. The map data according to claim 1, wherein the correction is sent to a server which aggregates other corrections sent to it to produce improved map data.

43. The map data according to claim 42, wherein corrections are analysed as to source, applicability and trustworthiness to produce improved map data.

44. The map data according to claim 1, wherein the user can associate a correction with one or more transportation types.

45. The map data according to claim 1, wherein the correction is to block access for at least one of:

a motor vehicle;

pedestrians;

heavy goods vehicles; and

bicycles.

7-37. -37. (canceled)