Method and system for providing a preview of a route calculated with a navigation system

• US 6,122,593 A
• Filed: 08/03/1999
• Issued: 09/19/2000
• Est. Priority Date: 08/03/1999
• Status: Expired due to Term

• Current Assignee: Navigon AG (Garmin Limited)
• Original Assignee: Navigation Technologies Corp. (Nokia Corporation)
• Inventors: McDonough, William, Friederich, Matthew, Ashby, Richard
• Primary Examiner(s): Cuchlinski, Jr., William A.
• Assistant Examiner(s): Beaulieu, Yonel
• Application Number:
  US09/368,283
• Time in Patent Office: 413 Days
• Field of Search: 701/200, 701/202, 701/208, 701/23, 701/25, 701/209, 707/1, 707/100, 707/102, 707/104, 340/995
• US Class Current: 701/202
• CPC Class Codes: G01C 21/3407 specially adapted for specific applications
• CPC Class Codes: G01C 21/3878 Hierarchical structures, e.g. layering
• CPC Class Codes: G01C 21/3881 Tile-based structures
• CPC Class Codes: G06Q 10/047 Optimisation of routes or paths, e.g. travelling salesman problem
• CPC Class Codes: G09B 29/007 using computer methods
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A navigation system uses a geographic database to determine a solution route to a destination and provides detailed maneuvering guidance for following the solution route. In addition, the navigation system includes a preview function that provides a summary of the solution route prior to providing the detailed maneuvering guidance for following the solution route. The preview function is included in the programming of the navigation system. The preview function uses a feature incorporated in the geographic database wherein the portion of the geographic database used by the navigation system when determining a solution route includes references to another portion of the database that includes the actual text of the names of the roads represented thereby. As the navigation system uses the data in the geographic database to determine the solution route, data representing the roads in the solution route are saved, including the references to the other portion of the geographic database that includes the actual text of the names of the roads. After the solution route is determined, the preview function evaluates the data representing the roads in the solution route and provides a list of route preview data structures. The list of route preview data structures includes the references to the portion of the geographic database that includes the actual text of the names of the roads. The list of route preview data structures is used to provide the user of the navigation system with a preview that contains a summary of the solution route. The preview provided to the user can include the names of the roads in the solution route. The names can be obtained from the geographic database using the references contained in the list of route preview data structures. When obtaining the names, the references can be reordered to facilitate accessing the text of the names quickly. By providing a preview of the calculated route, the user is familiarized with the route prior to being given detailed guidance for following the route.

Claims

1. A geographic database construction for representing navigable road segments located in a geographic region, comprising:

data entities of a first type; and

data entities of a second type,

wherein each navigable road segment is represented by at least one separate data entity of said first type,

wherein each data entity of said first type contains navigable attributes of the road segment represented thereby,

and further wherein each name by which a road segment represented by a data entity of said first type is represented by a data entity of said second type,

and wherein said data entities of said first type are located together in the geographic database separate from the data entities of said second type,

and further wherein each data entity of said first type include a reference to that data entity of said second type that contains the name by which the road segment represented by the data entity of said first type is known.

2. The invention of claim 1 wherein the data entity of said second type to which the reference in each data entity of said first type refers contains that name by which the road segment represented by the data entity of said first type is referred to by a road sign located along the road segment represented by said data entity of said first type.

3. The invention of claim 1 wherein said data entities of said first type are organized spatially in said geographic database.

4. The invention of claim 1 wherein said data entities of said second type are organized alphabetically in said geographic database.

5. The invention of claim 4 wherein said data entities of said first type are organized spatially in said geographic database.

6. The invention of claim 1 wherein said geographic database comprises data entities of a third type, wherein each navigable road segment is represented by at least one separate data entity of said third type, and

wherein each data entity of said third type contains explicatory attributes of the road segment represented thereby.

7. The invention of claim 1 wherein said database construction is stored on a computer-readable physical storage medium.

8. In a geographic database containing data that represent navigable road segments located in a geographic region, wherein said geographic database includes data entities of a first type and data entities of a second type, wherein each navigable road segment is represented by at least one separate data entity of said first type, wherein each data entity of said first type contains navigable attributes of the road segment represented thereby, and further wherein each name by which a road segment represented by a data entity of said first type is represented by a data entity of said second type, and wherein said data entities of said first type are located together in the geographic database separate from the data entities of said second type, wherein the improvement comprises:

in each data entity of said first type that represents a road segment known by a name, an indication contained in said data entity of said first type of the name by which the represented road segment is known.

9. The invention of claim 8 wherein said indication is a reference to one of said data entities of said second type.

10. The invention of claim 9 wherein the data record of said second type to which said reference in said data entity of said first type refers contains that name by which the road segment represented by the data entity of said first type is referred to by a road sign located along the road of which the represented road segment is a part.

11. The invention of claim 8 wherein said data entities of said second type are organized alphabetically in said geographic database.

12. The invention of claim 11 wherein said data entities of said first type are organized spatially in said geographic database.

13. The invention of claim 8 wherein said geographic database further comprises data entities of a third type, wherein each navigable road segment is represented by at least one separate data entity of said third type, and

wherein each data entity of said third type contains attributes used to provide maneuvering instructions relating to said represented road segment.

14. The invention of claim 8 wherein said database construction is stored on a computer-readable physical storage medium.

15. A geographic database construction for representing navigable road segments located in a geographic region and that facilitates a presentation of a preview of a calculated route, the geographic database construction comprising:

plural sets of data comprising;

routing data that include a first set of data entities representing the navigable road segments and containing data used for route calculation; and

name data that include a second set of data entities containing names of the navigable road segments,

wherein each of the data entities of the first set that represents a navigable road segment that is known by a name includes a reference to a data entity in the second set that contains the name.

16. The invention of claim 15 wherein each of the data entities of the first set that represents a navigable road segment that is known by plural names includes references to those data entities in the second set that contain the names.

17. The invention of claim 15 wherein the data entity in the second set that is referenced by the data entity in the first set contains the name by which the navigable road segment represented by the data entity in the first set is referred to by a road sign located along the navigable road segment represented by the data entity of the first set.

18. The invention of claim 15 wherein the routing data are organized spatially in the geographic database.

19. The invention of claim 15 wherein the name data are organized alphabetically in the geographic database.

20. The invention of claim 19 wherein the routing data are organized spatially in the geographic database.