Method of generating improved map data for use in navigation devices

• US 20080059055A1
• Filed: 08/15/2007
• Published: 03/06/2008
• Est. Priority Date: 08/15/2006
• Status: Active Grant

• Current Assignee: TomTom Navigation B.V (TomTom NV)
• Original Assignee: TomTom Navigation B.V (TomTom NV)
• Inventors: Goddjn, Harold, Geelen, Pieter
• Granted Patent: US 8,972,188 B2
• Time in Patent Office: Days
• US Class Current: 701/201
• 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

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, the navigation device can use the correction immediately. End-users can also share corrections with other end-users and also with a shared remote server that aggregates, validates and distributes correction.

Claims

1. A method of creating map alterations on a navigation device, the method comprising the steps of:

loading a map onto said device;

providing menu driven selection of possible alterations;

receiving input comprising at least one of said alterations; and

generating a map correction comprising said at least one of said alterations.

2. The method according to claim 1, further comprising the steps of:

storing said map data on said device,

storing said correction on said device,

storing said at least one of said alterations on said device, and

determining a route based upon said map data and correction.

3. The method according to claim 2, wherein said step of storing map data further comprises the steps of associating a unique identifier with said stored map data and storing said unique identifier with said stored map data.

4. The method according to claim 2, further comprising the step of storing a time stamp with said correction, said time stamp indicative of when said correction was stored pursuant to said step of storing said correction.

5. The method according to claims 1-4 wherein said correction comprises a format that enables said correction to be applied to map data independently of other corrections.

6. The method according to claims 1-5, wherein said step of correction further comprises storing said correction after said map is upgraded.

7. The method according to claims 1-6, further comprising the step of transmitting said correction to a server.

8. The method according to claims 1-7, further comprising the step of activating an icon or menu option to change map data stored on said device.

9. The method according to claim 8, wherein said step of activating further comprises the step of displaying a lower level options menu comprising one or more icons or other menu options for affecting map data changes.

10. The method according to claims 1-9, further comprising the step of distributing the correction among a plurality of devices.

11. The method according to claims 1-10, wherein said correction is formatted for use only on said device.

12. The method according to claims 1-11, further comprising the step of downloading other corrections, said other corrections originating from other devices.

13. The method according to claim 12, wherein said other devices comprise at least one of a defined community and a map data supplier.

14. The method according to claims 1-13, further comprising the step of determining a type of said correction, said type based upon said correction'"'"'s effect upon said user.

15. The method according to claim 14, wherein said type of said correction comprises:

known end-user inputted corrections;

unknown end-users inputted corrections;

trusted corrections; and

reported corrections.

16. The method according to claims 1-15, wherein said correction comprises blocking a street on a map.

17. The method according to claims 1-16, wherein said correction comprises unblocking a street on a map.

18. The method according to claims 1-17, wherein said correction comprises changing a speed limit on a street on a map.

19. The method according to claims 1-18, wherein said correction comprises at least one of renaming, moving, adding, deleting and re-categorising a POI.

20. The method according to claims 1-19, wherein said correction comprises a modification to a name of at least one of a city, part of a city, street and part of a street.

21. The method according to claims 1-20, wherein said correction comprises a change in of direction of road traffic.

22. The method according to claims 1-21, wherein said correction comprises an addition of a road or a connection of at least two roads.

23. The method according to claims 1-22, further comprising the step of associating a correction with one or more transportation types.

24. The method according to claims 1-23, wherein said correction comprising blocked access for at least one of a motor vehicle;

pedestrian;

heavy goods vehicles and bicycle.

25. The method according to claims 1-24, wherein said correction comprises an added turn restriction.

26. The method according to claims 1-25, wherein said correction comprises a removed turn restriction.

27. The method according to claims 1-26, wherein said correction comprises a modified structure number.

28. The method according to claims 1-27, wherein said correction comprises modification to a toll status of a road.

29. The method according to claims 1-28, wherein said correction comprises a modified sign post.

30. The method according to claim 29, wherein said step of receiving input further comprises the step of placing a graphical representation of a sign icon on said map.

31. The method according to claim 30, wherein said step of placing further comprises the steps of clicking and dragging said icon.

32. The method according to claims 1-31, wherein said correction comprises a modification to a motorway exit number.

33. The method according to claims 1-32, wherein said correction comprises a modification to a postcode associated with a location.

34. The method according to claims 1-33, wherein said correction comprises a modification to a vehicle height, weight or width restriction on a particular road.

35. The method according to claims 1-34, further comprising the steps of compressing said correction for over the air distribution.

36. The method according to claims 1-35, further comprising the step of securely encoding said correction.

37. The method according to claims 1-36, wherein said correction does not permanently affect the map data stored on the device.

38. The method according to claims 1-37, further comprising the step of automatically removing a correction if newly released map data affects a fix related to said correction.

39. The method according to claims 1-38, further comprising the step of affecting manual selection of inclusion of a correction in route planning.

40. The method according to claims 1-39, further comprising the step of configuring said device to manually affect automatic inclusion of private or public corrections from one or more sources during route calculation.

41. The method according to claim 40, further comprising the step of notifying a device user when corrections are used.

42. The method according to claims 1-41, further comprising the step of suggesting a correction to a device user.

43. The method according to claim 42, wherein said suggestion is made when a user deviates from a route in accordance with said correction.

44. The method according to claims 1-43, further comprising the step of categorizing said corrections according to at least one of community, sharing status, validity and language.