JP2012168169A - Vehicle navigation device and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a vehicle navigation device and method which can perform a route search and route guidance in consideration of passing lanes.SOLUTION: A vehicle navigation device (1) comprises a map data base (3) storing map data and a processing unit (2). The map data base (3) includes first attributes indicating presence of passing lanes and second attributes assigned to lanes to indicate which lanes of road segments are passing lanes. The processing unit (2) is linked to the map data base (3) and is configured to perform a route search based on at least the first attributes and to control output of route guidance information via a user interface (4) based on at least the second attributes.

Description

(Technical field)
The present invention relates to a vehicle navigation device including a map database for storing map data, a method for generating a map database, and a method for processing data stored in the map database. The invention particularly relates to such devices and methods in which a map database may include attributes.

(background)
Navigation devices are known to determine a route from a starting point to a destination using map data. In general, these navigation devices may search for routes that minimize the cost function. The cost function may represent travel time, distance or fuel cost associated with the route, or any other suitable amount to be minimized. The route that is the optimization may depend on the activation of the preferred option or the avoidance option. Preferred options and avoidance options for highways, ferries or tunnels may be provided.

  In addition to route determination, the navigation device may also provide route guidance functionality via the user interface. Providing guidance information may include generating optical or audio output that provides the driver with information about a portion of the road network surrounding the vehicle that can be combined with optical or audio instructions.

  Providing and using a map database that allows data to be used effectively for route search and route guidance can represent a significant challenge. Illustratively, for route search, information regarding the fine structure of the road network is usually not required for locations away from both the starting point and the destination. However, information regarding at least some types of roads (eg, highways) at locations away from both the starting point and the destination is required for route search. In contrast, the guidance function may require information only in the area surrounding the vehicle, not at a greater level of detail.

  Many road networks include so-called overtaking lanes. Such overtaking lanes can often be found in urban areas and their suburbs. In general, an overtaking lane is understood herein as a lane having access to a lane that is managed by limiting the number of entry and exit points to the facility. That is, not all access or exit points in a normal lane become overtake lane access or exit points. The overtaking lane can be physically separated from the universal acceptance capability provided in the main roadway or can be fenced. Alternatively, the overtaking lane can be separated from general acceptance capacity by road marking. The overtaking lane can be operated as a two-way facility or a two-way facility.

  Therefore, there is a need to provide a vehicle navigation device and method that can take overtaking lanes into account in route search and route guidance.

(Overview)
This need is addressed by the devices and methods described in the independent claims. The dependent claims define embodiments.

  In accordance with an aspect, a vehicle navigation device is provided that includes a map database and a processing unit. The map database stores map data including links and attributes. A link represents a road segment. The first attribute is assigned to each subset of links and indicates that the links included in the subset have at least one overtaking lane. The second attribute is assigned to at least some lanes of links included in each subset, and indicates which lane of each road segment is an overtaking lane. The processing unit is coupled to the map database and performs route search based on at least a first attribute and controls output of route guidance information based on at least a second attribute via a user interface. It is configured as follows.

  In the navigation device, first and second attributes indicating an overtaking lane are used. This allows the overtaking lane to be taken into account in both route search and route guidance. The first and second attributes may be stored in separate parts of the map database. This is because the processing unit performs a route search taking into account the overtaking lane by accessing the part where the first attribute is stored, and by accessing the part where the second attribute is stored, Enables route guidance taking into account overtaking lanes.

  The map database may include a data structure for each link. The data structure has a fixed number of data fields. A value is set for each data field. The first attribute and the second attribute may be stored separately from the data structure for the link. The map database is then required to include first and second attributes only for links that include at least one overtaking lane. Thereby, storage space requirements may be reduced.

  The first attribute may have a Boolean parameter. The processing unit may be configured to perform a route search based on both the first attribute and the Boolean parameter for the link. Boolean parameters allow avoidance and preference options to be implemented for overtaking lanes.

  In the map database, each first attribute with a Boolean parameter set to a first value can be assigned to a link that is entirely composed of an overtaking lane. Each first attribute having a Boolean parameter set to a second value different from the first value may each be assigned to a link that includes at least one non-overtaking lane. This allows avoidance and preference options to be implemented for the overtaking lane.

  The first attribute may have a parameter, in particular an integer parameter type parameter. The parameter may indicate the number of lanes. The processing unit may be configured to perform a route search based on both the first attribute and the parameter for the link.

  The map database can include a first portion and a second portion. The first attribute is stored in the first part, and the second attribute is stored in the second part. The processing unit may be configured to control the output of the route guidance information based on the data retrieved from the second part and independent of the data stored in the first part. Alternatively or additionally, the processing unit may be configured to perform a route search based on data retrieved from the first part and independent of the data stored in the second part. With such a map database, information can be efficiently retrieved from the map database for route search or route guidance. When performing a route search, if an avoidance or preference option is selected for the overtaking lane, the processing unit may be configured to adjust the cost of the link in the cost model based on the first attribute.

  The first part and the second part can be separate tables. The first part may represent the root layer of the map database. The second part may represent the guidance layer of the map database. The first part and the second part need not be stored in separate tables, but can be stored in parts of a logically different file.

  A vehicle navigation device may use tiling to organize or process data in a map database. Such tiling and corresponding organization rules for data in the map database facilitate local updates. Changes in map data resulting from local changes in the road network can be accommodated without requiring the exchange of the entire map database. The map database may include a first attribute for links placed on tiling tiles only if at least one of the links has at least one overtaking lane. By omitting the first attribute for tiles that have no links with at least one overtaking lane, storage space requirements may be reduced.

  The vehicle navigation device may use additional tiling for the guidance function. The further tiling can be the same as or different from the tiling used for the root function. The map database may include a second attribute for a road segment lane that is placed in a further tiling tile only if at least one of the road segments placed in the tile has at least one overtaking lane. . By omitting the second attribute for tiles that have no links with at least one overtaking lane, storage space requirements can be reduced.

  The map database can be a map database according to the Navigation Data Standard (NDS).

  According to another aspect, a method for generating a map database is provided. Data including information about road segments and information about lanes of each road segment is retrieved. For a plurality of road segments, it is determined whether the road segment has at least one overtaking lane. The first attribute is selectively assigned to a link representing a road segment when at least one lane of the road segment is an overtaking lane. The second attribute is selectively assigned to the lane of the link representing the road segment. The second attribute is selectively assigned based on which lane of the road segment is the overtaking lane. The first attribute and the second attribute are stored in the map database.

  Such a method allows a map database to be generated for use in a vehicle navigation device. The map database includes first and second attributes each indicating an overtaking lane. The first and second attributes may be used for route search and route guidance, respectively, when the map database is deployed in a vehicle navigation device.

  Assigning the first attribute selectively may include setting a parameter of the first attribute based on whether all lanes of the road segment are overtaking lanes. The parameters can be stored in a map database. The parameters allow avoidance and preference options to be implemented for the overtaking lane.

  The first attribute may be stored in a first part of the map database and the second attribute may be stored in a second part of the map database. The first part may represent data for route search, and the second part may represent data for outputting route guidance information. With such a map database, information can be efficiently retrieved from the map database for route search or route guidance.

  The first part can be a first table and the second part can be formed as a second table separate from the first table. The first and second tables may be SQL database tables, for example.

  A tiling that includes a plurality of tiles and that includes a road segment may be defined. The map database may be generated by storing data in the map database so that data associated with road segments located on any given tile of tiling can be identified in the map database.

  For each tile in the tiling, the first attribute may be stored in the map database only if at least one road segment included in each tile in the tiling includes at least one overtaking lane. By omitting the first attribute for tiles that have no links with at least one overtaking lane, storage space requirements can be reduced.

  Similarly, further tiling can be defined to organize data associated with route guidance. The further tiling can be the same as the tiling. For each tile of further tiling, the second attribute can be stored in the map database only if at least one road segment included in each tile of further tiling includes at least one overtaking lane. By omitting the second attribute for tiles that have no links with at least one overtaking lane, storage space requirements can be reduced.

  In accordance with another aspect, a method for processing data stored in a map database is provided. The map database includes a link representing a road segment and first and second attributes. The first attribute is assigned to a subset of links and the second attribute is assigned to at least some lanes of the link subset. In the method, a route search is performed. Activation of preference or avoidance options for overtaking lanes is monitored. The cost of the route is selectively adjusted based on the first attribute assigned to the link when a preference or avoidance option is activated. In the method, route guidance information is output. The route guidance information is output based on the second attribute.

  Performing a route search includes identifying a link to which the first attribute is assigned and selectively increasing or decreasing the cost in the cost model for the link when a preference or avoidance option is invoked. obtain.

  Outputting route guidance information includes identifying a lane in the surrounding environment of a vehicle that is an overtaking lane based on the second attribute and modifying audio or optical output based on the identified lane. obtain.

  The route search can be performed independently of the second attribute. Alternatively or additionally, outputting the route guidance information can be performed independently of the first attribute.

  The map database may be a map database generated by a method for generating map data according to any one aspect or embodiment.

  In accordance with another aspect, a data carrier is provided that stores a map database that includes links and attributes. The links represent road segments, and the first attributes are each assigned to a subset of links, indicating that the links included in the subset have at least one overtaking lane. Each second attribute is assigned to at least some lanes of the links included in the subset and indicates which lane of each road segment is an overtaking lane. The second attribute is different from the first attribute.

  According to yet another aspect, a data carrier is provided that stores a map database configured in accordance with a navigation data standard (NDS) and includes at least one attribute indicative of an overtaking lane.

  It is to be understood that the features mentioned above and described below can be used not only in the respective combinations shown, but also in other combinations or alone.

For example, the present invention provides the following items.
(Item 1)
A vehicle navigation device,
The vehicle navigation device is
A map database (10), wherein the map database (10) stores map data, the map data including links and attributes (63, 64, 83, 86, 93, 98), , Representing road segments (51-59), and the first attributes (63, 64, 83, 86) are each assigned to a subset of the links so that the links included in the subset have at least one overtaking lane And the second attribute (93, 98) is assigned to at least a part of the lanes of the links included in the subset, so that which lane of the respective road segment (51-53) Indicates the overtaking lane and the second attribute (93, 98) is different from the first attribute (63, 64, 83, 86) A map database (10),
A processing unit (2) that is coupled to the map database (10) and performs a route search based at least on the first attribute (63, 64, 83, 86) And a processing unit (2) configured to control the output of route guidance information based on at least the second attribute (93, 98) via the user interface (4); Including vehicle navigation devices.
(Item 2)
The map database (10) includes a data structure (62, 82, 85, 88, 90, 92, 97, 101, 103) for each link, and the data structure (62, 82, 85, 88, 90). , 92, 97, 101, 103) have a fixed number of data fields for the link, and a value is set for each data field,
The first attribute (63, 64, 83, 86) and the second attribute (93, 98) are obtained from the data structure (62, 82, 85, 88, 90, 92, 97, 101, 103). A vehicle navigation device according to any of the preceding items, stored separately.
(Item 3)
The first attribute (63, 64, 83, 86) has a Boolean parameter,
The processing unit (2) is configured to perform a route search for a link based on both the first attribute (63, 64, 83, 86) and the Boolean parameter. Vehicle navigation device as described in Crab.
(Item 4)
In the map database (10), the first attribute (63, 83) in which the Boolean parameter is set to a first value is assigned to the link (51, 52), respectively, and the link (51, 52). ) Is composed entirely of overtaking lanes, and the first attribute (64, 86) in which the Boolean parameter is set to a second value different from the first value is to the link (53), respectively. The vehicle navigation device according to any of the preceding items, wherein the allocated link (53) includes at least one overtaking lane and at least one non-overtaking lane.
(Item 5)
The map database (10) includes a first part (11) and a second part (14), and the first attribute (63, 64, 83, 86) includes the first part (11). And the second attribute (93, 98) is stored in the second part (14),
The processing unit (2) outputs the route guidance information based on data retrieved from the second part (14) and independent of the data stored in the first part (11). A vehicle navigation device according to any of the preceding items configured to control.
(Item 6)
Any of the above items, wherein the first part (11) is a first table and the second part (14) is a second table different from the first table (11). Vehicle navigation device as described in.
(Item 7)
Each road segment (51-59) is located on at least one tile (50, 71-74) of tiling,
The map database (10) is placed on the tile (50, 71-74) of the tiling only if at least one of the road segments (51-53) represented by links has at least one overtaking lane The vehicle navigation device according to any of the preceding items, comprising the first attribute (63, 64, 83, 86) for the generated link (51-53).
(Item 8)
Each link is located on at least one tile (71-74) of further tiling,
The map database (10) can be used for the further tiling only if at least one of the road segments (51-59) located on the further tiling tiles (71-74) has at least one overtaking lane. 79. A vehicle navigation device according to any of the preceding items, comprising the second attribute (93, 98) for the lane of the road segment (51-59) located on the tile (71-74).
(Item 9)
A method for generating a map database (10) comprising:
The method
Searching for data including information on road segments (51-59) and information on lanes of each road segment;
For multiple road segments (51-59)
Determining whether the road segment (51-59) has at least one overtaking lane;
If at least one lane of the road segment (51-59) is an overtaking lane, the first attribute (63, 64, 83, 86) is selectively assigned to the link representing the road segment (51-59). And
Selectively assigning a second attribute (93, 98) to the lane of the road segment (51-59), wherein the second attribute (93, 98) is the road segment (51-59). ) To be selectively assigned based on which lane is the overtaking lane,
Storing the first attribute (63, 64, 83, 86) and the second attribute (93, 98) in the map database (10).
(Item 10)
Selectively assigning the first attribute (63, 64, 83, 86) assigns the parameter of the first attribute (63, 64, 83, 86) to all of the road segments (51-59). A method according to any of the preceding items, comprising setting based on whether the lane is an overtaking lane, wherein the parameters are stored in the map database (10).
(Item 11)
The first attribute (63, 64, 83, 86) is stored in the first part (11) of the map database (10), and the second attribute (93, 98) is stored in the map database (10). 10) is stored in the second part (14), the first part (11) represents data for route search, and the second part (14) is for outputting route guidance information The method according to any of the preceding items, wherein the data is represented.
(Item 12)
A tiling is defined that includes a plurality of tiles (50, 71-74) and covers the road segments (51-59),
For each tile (50, 71-74) of the tiling, a first attribute (63, 64, 83, 86) is included in the respective tile (50, 71-74) of the tiling. Method according to any of the preceding items, wherein the method is stored in the map database (10) only if at least one road segment (51-59) contains at least one overtaking lane.
(Item 13)
A further tiling is defined that includes a plurality of tiles (71-74) and covers the road segments (51-59);
For each tile (71-74) of the further tiling (93, 98), a second attribute (93, 98) includes at least one road segment included in the respective tile of the further tiling (71-74) ( A method according to any of the preceding items, wherein 51-59) is stored in the map database (10) only if it contains at least one overtaking lane.
(Item 14)
A method of processing data stored in a map database (10), wherein the map database (10) includes links representing road segments (51 to 59) and first attributes (63, 64, 83, 86). ) And a second attribute (93, 98), the first attribute (63, 64, 83, 86) is assigned to a subset of links (51-53), the second attribute (93, 98) are assigned to at least some lanes of the subset of the links (51-53), the method comprising:
Performing a route search, and performing the route search,
Monitoring activation of a preference or avoidance option for an overtaking lane and, if the preference or avoidance option is activated, based on the first attribute (63, 64, 83, 86) assigned to the link Selectively adjusting the cost of the route, and
Outputting route guidance information based on the second attribute (93, 98).
(Item 15)
The route search is performed independently from the second attribute (93, 98), and the output of the route guidance information is performed independently from the first attribute (63, 64, 83, 86). The method according to any of the above items.

(Summary)
The vehicle navigation device (1) includes a map database (3) for storing map data and a processing unit (2). The map database (3) includes a first attribute indicating the presence of an overtaking lane and a second attribute indicating which lane of the road segment is an overtaking lane by being assigned to the lane. The processing unit (2) is coupled to the map database (3) and performs route search based on at least the first attribute and outputs route guidance information via at least a second interface via the user interface (4). And controlling based on the attributes of the.

  The foregoing and other features of the embodiments will become more apparent from the following detailed description of the embodiments when read in conjunction with the accompanying drawings. In the drawings, like reference numerals refer to like elements.

FIG. 1 is a schematic block diagram of a navigation device according to an embodiment. FIG. 2 is a schematic display of the map database. FIG. 3 is a flowchart of a procedure for performing a route search in the method according to the embodiment. FIG. 4 is a flowchart illustrating the use of the overtaking lane attribute in the route search. FIG. 5 is a flowchart of a procedure for outputting route guidance information in the method according to the embodiment. FIG. 6 illustrates a portion of the road network. FIG. 7 is a schematic diagram illustrating the structure of the root layer of the map database. FIG. 8 illustrates a portion of the road network of FIG. 6 at another level. FIG. 9 is a schematic diagram illustrating the structure of the root layer of the map database at a level different from the level of FIG. FIG. 10 is a schematic diagram illustrating the structure of the guidance layer of the map database. FIG. 11 is a flowchart of a method for generating a map database.

(Detailed explanation)
FIG. 1 schematically illustrates a vehicle navigation device 1 according to an embodiment. The navigation device 1 includes a processing unit 2 that controls the operation of the navigation device 1 (eg, according to control instructions stored in a memory). The processing unit 2 may include, for example, a central processing unit in the form of one or more microprocessors, digital signal processors or application specific integrated circuits. The navigation device 1 further includes a map database stored in the memory 3. The memory 3 may include any one of various types of memory, such as random access memory, flash memory or hard drive, or any combination, but a compact disc (CD), DVD, memory card, etc. Removable memory such as The navigation device 1 also includes an output interface 4 that outputs guidance information to the user. The output interface 4 may include an optical output device, an audio output device, or a combination thereof. The navigation device 1 also includes an input interface 5 that allows the user to set options. In particular, the input interface 5 may allow the user to set preferred options or avoidance options for the route search.

  The navigation device may include additional components such as position sensors and / or wireless receivers and / or vehicle interfaces. The position sensor can be adapted to determine the current position of the vehicle on which the navigation device 1 is installed. The position sensor may include a GPS (Global Positioning System) sensor, a Galileo sensor, a position sensor based on a mobile communication network, and the like. The wireless receiver may be configured to receive information that updates a map database stored in the memory 3. The car interface may allow the processing unit 2 to obtain information from other vehicle systems or vehicle status information via the vehicle interface. The vehicle interface may include, for example, a CAN (Controller Area Network) or MOST (Media Oriented Device Transport) interface.

  The memory 3 stores a map database including map data. The map database includes information regarding links and attributes representing road segments. The map database specifically includes an attribute that indicates whether the road segment represented by the link includes an overtaking lane. Different first and second attributes are provided to inform the processor that the link includes at least one overtaking lane and / or to provide information about which lane of the road segment is an overtaking lane. obtain.

  The processor 2 may use the first attribute to perform a route search if the user sets a preferred option or avoidance option for the overtaking lane via the input interface 5. The processor 2 may perform a route search independent of the second attribute assigned to the lane. The processor 2 may use the second attribute for controlling the output of route guidance information via the output interface 5. The processor 2 may control the output of route guidance information independently of the first attribute. The map database may thus include different first and second attributes, each associated with an overtaking lane. The first attribute is used for route search, and the second attribute is used for route guidance.

  In general, various attributes can be assigned to links and stored in a map database. Attributes may include information about link start and end points or other information about map topology. Such attributes can be stored in a data structure having a predefined number of data fields. A predefined number of data fields are provided for each link or other map feature stored in the map database, respectively. Furthermore, attributes can be selectively assigned to links or other features only if present on each link. The map database stored in the memory 3 includes an attribute indicating an overtaking lane as a flexible attribute. The flexible attribute is selectively stored only for links that include at least one overtaking lane. The attribute indicating the overtaking lane may be stored separately from the fixed format data structure stored in the map database for each link.

  The map database stored in the memory 3 can include different logical layers. Furthermore, the map database may be divided into different blocks associated with different tiling update regions or tiles. Such a structure facilitates the execution of updates. This is particularly desirable for updating the map database to adjust the map database to local changes in the road network. Such an update can then be performed by updating only the update areas or tiles affected by the change in the road network. This allows updates to be made more easily as a more time efficient manner or as a wireless update.

  FIG. 2 is a schematic display of the map database 10. A map database 10 having the structure described below can be stored in the memory 3 of the vehicle navigation device 1.

  The map database 10 includes a plurality of layers 11 and 14. The plurality of layers 11 and 14 include a route layer 11 and a guidance layer 14. The route layer 11 includes information required for performing route search. This information may include information regarding the topology of the road network, such as link start and end points. Information in the route layer 11 may further include costs associated with links to various cost models. The information in the route layer 11 may further include attributes that allow the cost of the link to be adjusted based on the preferred or avoided options in the route search.

  There can be different levels 12, 13 in the root layer 11. Different levels 12, 13 contain data representing the road network with different levels of detail. Illustratively, all road segments of the road network may be present at level 13, but some road segments may be omitted at higher level 12.

  The guidance layer 14 includes data required for route guidance. The guidance layer 14 may specifically include data required for optical and / or audio output of guidance information. The guidance layer may also include a level structure. Data at different levels represents the road network with different levels of detail.

  The route layer 11 and the guidance layer 14 may be configured as separate tables stored in memory. By way of example rather than limitation, the root layer 11 may be a table in the SQL database and the guidance layer 14 may be another table in the SQL database. The root layer 11 and the guidance layer 14 can be stored in separate files. The root layer 11 and the guidance layer 14 can be logically different parts of a file.

  The map database 10 may include additional layers 15-17. The name layer 15 includes references to road names, house numbers, and the like. The track layer 16 may include specific attributes for the track or lorry. The advanced driver assistance system (ADAS) layer 17 may include data for advanced driver assistance. Additional or alternative layers may be provided, for example, a layer for points of interest, a layer for audio display or a layer for basic map display.

  The map database 10 may have a structure defined by the navigation data standard (NDS). NDS allows flexible attributes to be used. This allows the attribute indicating the overtaking lane to be defined and stored when the map database 10 is set according to NDS.

  The attribute indicating the overtaking lane is stored in the map database. Each of the first attributes may be used for data stored in the root layer 11. A first attribute may be assigned to each link, each link including at least one overtaking lane. This allows preferred options to be implemented for road segments that include at least one overtaking lane. The map database 10 may store the first attribute for both directional and non-directional links. If the map database 10 is structured so that different types of links are distinguished, the map database 10 may store a first attribute for all types of links. By way of example, if the map database 10 includes tiling tiles extending across tile boundaries and base links located across the root link, the map database 10 is allocated to both the base link and the root link. One attribute may be stored.

  The first attribute may have a parameter that may be a Boolean parameter. For any link (for this link, the first attribute is stored in the map database 10), if all lanes of the road segment are overtaking lanes, the parameter is a single value (e.g. , TRUE).

  If there is at least one lane that is not an overtaking lane, the parameter may have another value (eg, FALSE). Based on the first attribute and its parameters, the processor 2 may determine whether any road segment is entirely composed of overtaking lanes. In that case, if the avoidance option for the overtaking lane is selected, the cost increases in the route search. The processor 2 may also determine whether any road segment has at least one overtaking lane, in which case if the preferred option for the overtaking lane is selected, the cost will be the route Increase in search.

  The first attribute may be stored separately from the fixed format data structure. A fixed format data structure is stored in the map database 10 for all links or other map features. Thus, it is not required for each road segment to save storage space for a flag that must be set to indicate whether the road segment contains an overtaking lane. For each road segment, it is also not required to save storage space for a flag that must be set to indicate whether the road segment is entirely composed of overtaking lanes. Rather, such information is included as a flexible attribute. The first attribute may be omitted for update areas or tiles that do not have a link that includes at least one overtaking lane. The storage space requirement for storing information about the overtaking lane can thereby be reduced.

  When performing a route search, the processor 2 may take into account the avoidance or preference options for the overtaking lane based on the first attribute stored in the route layer 11 and its parameters. Such a procedure is described in more detail below with reference to FIGS. 3 and 4.

  A second attribute indicating an overtaking lane may be stored in the guidance layer 14. The second attribute may be selectively stored only for those road segments that include at least one overtaking lane. In some implementations, the second attribute may be selectively assigned to a road segment lane only if the road segment has at least one lane that is an overtaking lane and another lane that is not an overtaking lane. The second attribute may be stored in the guidance layer 14 to indicate to the processor 2 that each road segment includes at least one overtaking lane and may further provide information regarding which lane of the road segment is an overtaking lane. Further information may be selectively stored for the link in the map database 10 to assign the second attribute to the lane. The link includes at least one overtaking lane and indicates which lane of each road segment is an overtaking lane. This additional information can be stored in the form of a lane mask. The lane mask has one value (eg, “1”) for lanes that are overtaking lanes and another value (eg, “0”) for lanes that are not overtaking lanes. Such further information can be used to assign a second attribute to individual lanes.

  When the navigation device 1 provides route guidance, the processor 2 accesses the guidance layer 14 and retrieves data for route guidance. In general, only data relating to the area surrounding the vehicle must be retrieved for route guidance. When retrieving data for a road segment from the guidance layer 14, the processor 2 determines whether the second attribute is assigned to one lane or multiple lanes of each road segment. The processor 2 can summarize the second attribute into further information indicating which lane is the overtaking lane (eg, in the form of a lane mask) and determine which lane of the road segment is the overtaking lane. Alternatively, the second attribute can be stored separately for each lane.

  The processor 2 may control the route guidance based on which lane of the road segment is the overtaking lane. For example, the audio output with driving instructions can be controlled based on which lane of the road segment is an overtaking lane. Additionally or alternatively, the optical output with driving instructions can be controlled based on which lane of the road segment is the overtaking lane.

  The second attribute may be stored separately from the fixed format data structure. A fixed format data structure is stored in the map database 10 for all links or other map features. Thus, it is not required to save storage space for flags that must be set for each road segment that indicates which lane of the road segment is the overtaking lane. The second attribute may be omitted for update areas or tiles that do not have a road segment that includes at least one overtaking lane. The storage space requirement for storing information about the overtaking lane can thereby be reduced.

  When providing route guidance, the processor 2 may take into account which lane of the road segment is the overtaking lane based on the second attribute stored in the guidance layer 14. Such a procedure is described in more detail below with reference to FIG.

  The first and second attributes are stored separately in different layers of the map database 10, but the overhead storage space required to store this information associated with the overtaking lane information can be kept reasonably. . The map database 10 selectively includes first and second attributes only for those road segments that include at least one overtaking lane. Furthermore, by using separate first and second attributes in the different layers 11 and 14, access to the map database 10 can be efficiently performed in both route search and route guidance.

  With reference to FIGS. 3 to 5, the method that can be performed by the processor 2 of the vehicle navigation device 1 will be described in more detail. The processor 2 may perform the route search illustrated in FIGS. 3 and 4 and the route guidance illustrated in FIG.

  The method may be performed using a map database that stores information about links representing road segments and attributes indicating passing lanes. The map database may have a configuration described with reference to FIG. 2 or FIGS. By way of example, the first attribute is called “EXPRESS_ROAD” in FIGS. The parameter of the first attribute is called “Alllanes” and the second attribute is called “EXPRESS_LANE”.

  FIG. 3 is a flowchart of the procedure 20 for performing a route search. At 21, a route search is started. A route search may be initiated based on user input. Alternatively or additionally, a route search can also be automatically initiated when a predetermined event is detected (eg, when a user leaves a route previously found in the route search).

  At 22, it is determined whether an avoidance option or a preference option for a road having an overtaking lane has been selected. Selection of such avoidance or preference options for the road can be made via an input interface and stored in the vehicle navigation device.

  If it is determined that no avoidance or preference option has been selected for a road with an overtaking lane, at 23, a route search is performed based on data in the map database in a conventional manner. The first attribute EXPRESS_ROAD is ignored in this route search.

  If it is determined that an avoidance or preference option has been selected for a road with an overtaking lane, at 24, the route search considers the first attribute EXPRESS_ROAD assigned to some of the links. To be done. The first attribute EXPRESS_ROAD may be taken into account in various ways. By way of example, if the all avoidance option is set for a road with an overtaking lane, all links representing roads that make up all of the overtaking lane may be ignored. Alternatively or additionally, the cost of the link may be adjusted based on avoidance or preference options for the link assigned the first attribute EXPRESS_ROAD. Such adjustment of the cost can be achieved for various cost models such as fastest route (minimizing travel time), shortest route (minimizing travel distance) or least fuel consumption route (minimizing fuel consumption). It can be done for any one of them.

  FIG. 4 is a flowchart of a procedure 30 for adjusting the link cost in the route search based on the first attribute. Procedure 30 may be used to implement cost adjustment in route search performed at 24 in procedure 20 of FIG.

At 31, the link is identified in the route search. The link may be identified, for example, in the search algorithm extension process. The links may be identified, for example, in the Dijkstra algorithm or the A ^* algorithm extension process. Alternatively, cost adjustments can be made prior to performing, for example, Dijkstra's algorithm or A ^* algorithm. In the latter case, all links with the EXPRESS_ROAD attribute can first be identified in order to adjust the cost of these links.

  At 32, it is determined whether the identified link has a first attribute EXPRESS_ROAD assigned to the identified link. This determination is made based on data retrieved from the map database. For a map database having a layered structure, a determination can be made based on the first attribute stored in the root layer 11.

  If it is determined that the identified link does not have the first attribute EXPRESS_ROAD assigned to the identified link, at 33 the cost of the link remains unadjusted. The route search may continue with a cost that represents the cost of the respective cost model.

  If it is determined that the identified link has the first attribute EXPRESS_ROAD assigned to the identified link, it is determined at 34 whether an avoidance option for the overtaking lane has been set.

  If it is determined that the avoidance option is not set, at 35, the cost of the link is reduced. Thereby, the preferred option for roads with overtaking lanes is taken into account by reducing the cost for the links. The first attribute EXPRESS_ROAD is assigned to the link. Reducing the cost of the link at 35 can be done in various ways. Illustratively, the cost of each cost model can be multiplied by a factor less than one. Alternatively, the value can be subtracted from the cost of the respective cost model. Decreasing the cost of the link at 35 can be done using a mathematical operation or a table lookup. Route search may continue with reduced cost for the link.

  If it is determined that the avoidance option has been set, it is determined at 36 whether the parameter Alllanes of the first attribute EXPRESS_ROAD is TRUE.

  If the parameter Alllanes of the first attribute EXPRESS_ROAD is not TRUE, at 38 the cost of the link remains unadjusted. The procedure may continue with a cost that represents the cost of each cost model. This reflects that the avoidance option does not require that a road with at least one lane that is not an overtaking lane be avoided.

  If it is determined that the parameter Alllanes of the first attribute EXPRESS_ROAD is not TRUE, at 37, the cost of the link is increased. Increasing the cost of the link at 37 can be done in various ways. Illustratively, the cost of each cost model can be multiplied by a factor greater than one. Alternatively, a value can be added to the cost of each cost model. Increasing the cost of the link at 37 can be done using a mathematical operation or a table lookup. Route search can continue with increased cost for the link.

  Although a route search that takes into account avoidance and preference options for overtaking lanes is illustrated in FIGS. 3 and 4, the route search may also include a variant of options where the use of overtaking lanes is completely prohibited. In such a case, each link may be released from consideration in the route search based on the first attribute EXPRESS_ROAD and its parameter Alllanes.

  FIG. 5 is a flowchart of a procedure 40 for controlling the output of route guidance information. At 41, a road segment in the local environment of the vehicle is identified. A road segment may be identified based on the current vehicle position. Road segments can be further identified based on the results of the route search. The road segments identified at 41 may include all road segments. Information about all road segments is required to output guidance information.

  At 42, it is determined whether any one lane of the identified road segment has a second attribute EXPRESS_LANE assigned to that lane. This determination is made based on data retrieved from the map database. For a map database having a layered structure, a determination may be made based on a second attribute stored in the guidance layer 14.

  If it is determined that the lane of the road segment does not have the second attribute EXPRESS_LANE assigned to the lane, guidance information is output at 45. In this case, the guidance information is not modified based on the second attribute EXPRESS_LANE.

  If it is determined that the lane of the road segment has a second attribute EXPRESS_LANE assigned to that lane, information regarding the number and type of lanes for each road segment is retrieved at 43. Information can be retrieved from a map database. Information can be retrieved from the guidance layer 14 if the map database, such as the map database 10, has a layered structure. The retrieved information may include information regarding the number of lanes in the road segment. The retrieved information may include information regarding which of the lanes are overtaking lanes.

  At 44, the output information is adjusted based on the information retrieved at 43. Adjusting the output information may include adjusting the speech output based on which lane of the road segment is the overtaking lane. Adjusting the output information may alternatively or additionally include adjusting the optical output based on which lane of the road segment is the overtaking lane. The optical output information may be adjusted using, for example, color markings indicating the overtaking lane or graphic icons indicating the overtaking lane.

  Next, at 45, guidance information is output. If the road segment that affects the guidance information output at 45 includes an overtaking lane, the guidance information is generated based on information about the overtaking lane provided by the second attribute EXPRESS_LANE.

  With reference to FIGS. 6 to 10, the definition of the first attribute and the second attribute indicating the overtaking lane and the structure of the map database will be described in more detail.

  FIG. 6 is a schematic diagram of a road network including road segments 51-55. Tiling including road network is defined. The tiling includes a tile 50.

  A plurality of road segments 51 to 55 are referred to in the map database by labels “RS1” and “RS5”. A portion of the road segment may include at least one overtaking lane. Illustratively, in the map database, road segments 51 and 52 labeled “RS1” and “RS2” may consist entirely of overtaking lanes. The road segment 53 labeled “RS3” in the map database may have at least one overtaking lane and at least one lane that is not an overtaking lane. Road segments 54 and 55 may not include any overtaking lanes.

  Road segments 51-55 are indicated in the map database by links. Both the data in the root layer and the data in the guidance layer can each be organized according to tiles. Each road segment is arranged in a tile. This allows local updates to be made easier.

  FIG. 7 is a schematic representation of section 12 of the root layer. Section 12 represents a level with coarse resolution, omitting less important road segments. The set of road segments still existing in the level can be selected based on, for example, functional road classification or other road segment characteristics.

  The root layer section 12 includes data 61 associated with the tile 50. Data 61 includes a data structure for each link representing road segments 51-55. This data structure is shown schematically at 62 for links representing road segments 51-55. The data structure includes a fixed number of data fields for each link. The data structure may have a predefined structure. A value must be set in each field.

  The map database further includes a first attribute assigned to the links, indicating that each link includes at least one overtaking lane. The first attribute may also be stored for tile 50 in data 61. In the tile 50, the respective road segments 51 to 55 are arranged.

  Data 61 for tile 50 includes a first attribute 63 and the boolean parameter is set to one value for the road segments labeled “RS1” and “RS2”. This indicates that the road segments labeled “RS1” and “RS2” are entirely composed of overtaking lanes. The road segment labeled “RS1” and “RS2” is assigned a first attribute 63 with a Boolean parameter set to one value.

  Data 61 for tile 50 includes a first attribute 64 and the Boolean parameter is set to a different value for the road segment labeled “RS3”. This indicates that the road segment labeled “RS3” has at least one overtaking lane, but is not entirely composed of overtaking lanes. The road segment labeled “RS3” is assigned a first attribute 64 with a Boolean parameter set to a different value.

  The first attributes 63 and 64 are not included in the data structure 62 predefined for the link. The first attributes 63 and 64 are flexible attributes. The first attribute may be included in the route layer data 61 representing a tile only if at least one road segment in each tile has at least one overtaking lane.

  In FIG. 7, the first attribute is indicated as attribute EXPRESS_ROAD, and the parameter of the first attribute is indicated as Alllanes.

  FIG. 8 is a schematic diagram of the road network of FIG. In FIG. 8, the road network is illustrated with a greater level of detail. 8 and 6 represent the same road network at different levels, but road segments 56-59 of the road network that exist at the level illustrated in FIG. 8 are omitted at the coarser level illustrated in FIG. .

  The road network includes road segments 51 to 55 and road segments 56 to 59. A tiling 70 including a road network is defined. The tiling includes tiles 71-74. At the resolution level illustrated in FIG. 8, the tile sizes of tiles 71-74 are selected to be smaller than at the coarser resolution level illustrated in FIG.

  The road network may include road segments disposed within the entire tile and road segments extending across the tile boundaries. Road segment 59 extends across the boundary between tile 73 and tile 74. In order to organize the data in the map database, the road segment 59 may be associated with one link that reflects the topology of the road segment 59. In addition, structures 75, 76 that reflect the geometry of the road segment 59 can be defined, each placed on only one tile. Structures 75, 76 may be referred to as geometry lines.

  At the level of resolution shown in FIG. 8 where fewer road segments are omitted or no road segments are omitted, data in the route layer and the guidance layer can also be organized in a tile-by-tile manner.

  FIG. 9 is a schematic representation of the root layer section 13. Section 13 represents a level that represents the road network with a greater level of detail than section 12 of FIG. By way of illustration, the level of detail represented by section 13 of the route layer may include all road segments.

  The root layer section 13 includes data 81 associated with the tile 71. Data 81 includes a data structure for each link representing road segments 51 and 52 disposed within tile 71. This data structure is schematically shown at 82 for links representing road segments 51 and 52. The data structure includes a fixed number of data fields for each link and has a predefined structure. A value must be set in each field.

  The map database further includes a first attribute assigned to the links, indicating that each link includes at least one overtaking lane. The first attribute may also be stored in the data 81 for the tile 71 where the respective road segments 51 and 52 are located.

  The data 81 for tile 71 includes a first attribute 83 and the boolean parameter is set to one value (eg, “TRUE”) for the road segments labeled “RS1” and “RS2”. . As explained above, this indicates that the road segments labeled “RS1” and “RS2” are composed entirely of overtaking lanes. A road segment labeled “RS1” and “RS2” is assigned a first attribute 83 with a Boolean parameter set to one value.

  Route layer section 13 includes data 84 associated with tile 72. Data 84 includes a data structure for each link representing road segments 53-55 disposed within tile 72. This data structure is shown schematically at 85 for links representing road segments 53-55. The data structure includes a fixed number of data fields for each link and has a predefined structure. A value must be set in each field.

  The map database further includes a first attribute assigned to the links, indicating that each link includes at least one overtaking lane. The first attribute may also be stored in the data 84 for the tile 72 where each road segment 53-55 is located. Data 84 for tile 72 includes a first attribute 86 and the Boolean parameter is set to another value (eg, “FALSE”) for the road segment labeled “RS3”. This indicates that the road segment labeled “RS3” has at least one overtaking lane, but does not consist entirely of overtaking lanes. The road segment labeled “RS3” is assigned a first attribute 86 with the Boolean parameter set to another value.

  The root layer section 13 includes data 87 associated with the tile 73 and data 89 associated with the tile 74. Data 87 includes a data structure for each link representing road segments 57, 58 disposed within tile 73 and a geometry line 76 representing a portion of road segment 59. The data structure shown schematically at 88 is composed of fixed attributes having a predefined number and type of fields. Data 89 includes a data structure for links representing road segments 56 disposed within tile 73 and geometry lines 75 representing portions of road segments 59. The data structure shown schematically at 90 is composed of fixed attributes having predefined data fields.

  If no road segment in tiles 73 and 74 has an overtaking lane, the first attribute is not stored in data 87 and 89 representing tiles 73 and 74. It is not required to store the first attribute in data associated with a tile that has no road segment with an overtaking lane. Thereby, storage space requirements for implementing excessive lane attributes may remain reasonable.

  In FIG. 9, the first attribute is indicated as attribute EXPRESS_ROAD, and the parameter of the first attribute is indicated as Alllanes.

  As can be seen from FIGS. 7 and 9, according to the embodiment, the first attribute for road segments 51-53 is represented at section 12 representing higher level road segments and at lower levels, representing more road segments. It can be stored both in the containing section 13.

  FIG. 10 is a schematic representation of a section of the guidance layer 14 again for the road network of FIG. The guidance layer 14 may also include multiple levels that represent the road network with different accuracies, but the second attribute assigned to the lane to indicate the overtaking lane need not be included in each level. If there are different levels, the second attribute can be stored, especially at the level with the fewest number of road segments omitted (i.e. the basic level where the road network is represented in the largest detail). Only such levels are schematically illustrated in FIG.

  The first attribute in the root layer may be present at each different level of the root layer, but if the guidance layer has multiple levels, the second attribute is included only in one of the levels of the guidance layer. It is enough.

  Guidance layer 14 includes data 91 associated with tile 71. Data 91 includes a data structure for each link representing road segments 51 and 52 disposed within tile 71. This data structure is shown schematically at 92 for links representing road segments 51 and 52. The data structure includes a fixed number of data fields for each link and has a predefined structure. A value must be set in each field.

  The map database further includes a second attribute assigned to the lane of the link, indicating that each lane is an overtaking lane. The second attribute may also be stored in the data 91 for the tile 71 where the respective road segments 51 and 52 are located.

  Data 91 for tile 71 includes a second attribute 93 for the road segments labeled “RS1” and “RS2”. Additional data structures 94 and 95 can be provided to assign the second attribute 93 to individual lanes of the road segments 51 and 52. Data structures 94 and 95 may represent a lane mask having a value such as “1” if each lane of the road segment is an overtaking lane, and “0” if each lane of the road segment is not an overtaking lane. May represent another value. The processor may organize the second attribute 93 into a data structure 94 representing the lane mask of the road segment 51 and identify the lane of the road segment 51 that is an overtaking lane. The processor may organize the second attribute 93 into a data structure 95 representing the lane mask for the road segment 52 and identify the lane of the road segment 52 that is an overtaking lane.

  The guidance layer includes data 96 associated with tile 72. Data 96 includes a data structure for each link representing road segments 53-55 disposed within tile 72. This data structure is shown schematically at 97 for links representing road segments 53-55. The data structure includes a fixed number of data fields for each link and has a predefined structure. A value must be set in each field.

  Data 96 for tile 98 includes a second attribute 98 for the road segment labeled “RS3”. A further data structure 99 may be provided to assign the second attribute 98 to individual lanes of the road segment 53. Data structure 99 may represent a lane mask. The processor may organize the second attribute 98 into a data structure 99 representing a lane mask for the road segment 53 and identify a lane of the road segment 53 that is an overtaking lane.

  The guidance layer 14 includes data 100 associated with the tile 73 and data 102 associated with the tile 74. Data 100 includes attributes 101 that are at least fixed for road segments in tile 73. Data 102 includes attributes 103 that are at least fixed for road segments in tile 74. Assuming that none of the road segments in tiles 73 and 74 have an overtaking lane, the second attribute is not stored in data 100 and 102 representing tiles 73 and 74. It is not required to store the second attribute in data associated with a tile that has no road segment with an overtaking lane. Thereby, storage space requirements for implementing excessive lane attributes may remain reasonable.

  In FIG. 10, the second attribute is indicated as an attribute EXPRESS_LANE.

  It will be appreciated that other map database structures may be used with the first and second attributes. Illustratively, the second attribute EXPRESS_LANE can be assigned directly to an individual lane, rather than assigned to an individual lane by the additional data structure illustrated at 94, 95 and 99 of FIG. Assigning the second attribute directly to individual lanes can be particularly useful when individual lanes are represented as individual map features in the map database.

  FIG. 11 is a flowchart of a method 110 for generating a map database, the map database including an attribute indicating an overtaking lane. The method may be performed by an electronic computer system. The method uses raw data including information about road segments of the road network and information about lanes of the road segments. Such data is provided by various suppliers and may have various formats such as Navtech or Teleatlas. Using the method, the raw data is processed to form a database containing attributes indicating the overtaking lanes.

  At 111, raw data is retrieved. The raw data may include information about the road segment and information about which lane of the road segment is an overtaking lane. Such raw data may have a format that is inappropriate for direct use in a vehicle navigation device, for example due to storage space limitations or due to inefficient access.

  At 112, road segment topology and geometry information is determined. The topology may include information regarding the start and end points of the road segment, information regarding connections to other map features, and the like. The geometry information may include information regarding the geometry of a portion of the road segment located on one of the road segments or tiles of the tiling. The topology information can be used to generate links in map data representing road segments.

  At 113, it is determined whether the road segment has at least one overtaking lane. If it is determined that the road segment does not have an overtaking lane, the attribute indicating the overtaking lane need not be stored for the road segment. The method may return to 111.

  If it is determined that the road segment has at least one overtaking lane, at 114 a first attribute EXPRESS_ROAD is assigned to the link. The first attribute may be registered for subsequent storage in the map data. The first attribute can be stored, but need not be stored immediately. Rather, the first attributes assigned to the different road segments arranged in the tile can be collected for subsequent storage.

  At 115, it is determined whether all lanes in the road segment are overtaking lanes. If it is determined that the road segment has at least one lane that is not an overtaking lane, at 116, the Boolean parameter Alllanes of the first attribute EXPRESS_ROAD is set to FALSE. If it is determined that all lanes of the road segment are overtaking lanes, at 117, the Boolean parameter Alllanes of the first attribute EXPRESS_ROAD is set to TRUE. The parameter can be registered for subsequent storage in the map data. Parameters can be stored, but need not be stored immediately. Rather, the first attribute can be collected for subsequent storage, with each set parameter assigned to a different road segment located in the tile.

  At 118, a second attribute EXPRESS_LANE is assigned to the lane of the road segment. The second attribute is selectively assigned based on which lane of the lane is the overtaking lane. In some embodiments, the attribute EXPRESS_LANE may be assigned only to lanes that are overtaking lanes. Assigning the second attribute EXPRESS_LANE to the road segment lane may include generating a data structure that associates the second attribute shown at 94, 95, and 99 of FIG. 10 with the individual lane. This data structure may have a lane mask format in which binary string numbers represent individual lanes of a road segment. Alternatively, the second attribute EXPRESS_LANE can be stored to be directly associated with the individual lanes of the road segment without requiring a lane mask.

  At 119, the first attribute EXPRESS_ROAD may be stored in the root layer of the map database. The second attribute EXPRESS_LANE may be stored in the guidance layer of the map database.

  For each road segment, it is not required to store the first and second attributes individually in the map database. Rather, tiling can be defined and steps 111-118 can be first repeated for all road segments included in the tile. Information about the link to which the first attribute is assigned and information about the lane to which the second attribute is assigned can be subsequently collected and stored after steps 111-118 have been performed for all road segments of the tile. . This process can be repeated iteratively for different tiles.

  In the method, if the tile does not have a road segment with at least one overtaking lane, it is not required to store the first attribute or the second attribute in the data representing the tile in the map database.

  Further, in some embodiments, if all lanes of a road segment are overtaking lanes, it may not be required to store the second attribute for the lane of the road segment. That is, the method can proceed directly from step 117 to step 119. Thus, in some embodiments, the map database may include a second attribute only for lanes of road segments that have at least one overtaking lane but are not entirely composed of overtaking lanes.

  The map database generated using the method of FIG. 11 can have a variety of formats. By way of example rather than limitation, the map database may be a map database configured according to NDS. The first attribute and the second attribute may be flexible attributes defined by NDS.

  The map database generated using the method of FIG. 11 may be used in a vehicle navigation device according to an embodiment.

  Although devices and methods according to embodiments have been described in detail, modifications may be implemented in other embodiments. By way of example, the map database used by the devices and methods of the embodiments is not required to store data organized according to tiling. If tiling is used to organize the map database, the tiling need not be square tiling, but can be any other tiling that includes a road network. Different tilings can be used for route and guidance functions. The tiling defined for the root layer may include tiles, which may be different from other tiles in another tiling defined in size and / or shape for the guidance layer.

  As a further illustration, the first attribute may have a Boolean parameter, but the first attribute may have a parameter of another parameter type. Illustratively, the first attribute may have an integer parameter type parameter. The parameter may indicate the number of lanes in each road segment.

  By way of further illustration, the map database of the embodiment may include a second attribute for any road segment that includes at least one overtaking lane, while in other embodiments the map database is entirely from the overtaking lane. The configured road segment lane may not have a second attribute. In this case, information regarding the lane that is the overtaking lane may be derived from the first attribute and its parameters.

  Embodiments of the invention may be used as a vehicle navigation device.

Claims (15)

A vehicle navigation device,
The vehicle navigation device is
A map database (10), wherein the map database (10) stores map data, the map data including links and attributes (63, 64, 83, 86, 93, 98), , Representing road segments (51-59), and the first attributes (63, 64, 83, 86) are each assigned to a subset of the links so that the links included in the subset have at least one overtaking lane And the second attribute (93, 98) is assigned to at least a part of the lanes of the links included in the subset, so that which lane of the respective road segment (51-53) Indicates the overtaking lane and the second attribute (93, 98) is different from the first attribute (63, 64, 83, 86) A map database (10),
A processing unit (2) that is coupled to the map database (10) and performs a route search based at least on the first attribute (63, 64, 83, 86) And a processing unit (2) configured to control the output of route guidance information based on at least the second attribute (93, 98) via the user interface (4); Including vehicle navigation devices. The map database (10) includes a data structure (62, 82, 85, 88, 90, 92, 97, 101, 103) for each link, and the data structure (62, 82, 85, 88, 90). , 92, 97, 101, 103) have a fixed number of data fields for the link, and a value is set for each data field,
The first attribute (63, 64, 83, 86) and the second attribute (93, 98) are obtained from the data structure (62, 82, 85, 88, 90, 92, 97, 101, 103). The vehicle navigation device of claim 1, stored separately. The first attribute (63, 64, 83, 86) has a Boolean parameter;
The processing unit (2) is configured to perform a route search for a link based on both the first attribute (63, 64, 83, 86) and the Boolean parameter. The described vehicle navigation device.   In the map database (10), the first attributes (63, 83) in which the Boolean parameter is set to a first value are assigned to the links (51, 52), respectively, and the links (51, 52). ) Is composed entirely of overtaking lanes, and the first attribute (64, 86) in which the Boolean parameter is set to a second value different from the first value is to the link (53), respectively. 4. The vehicle navigation device of claim 3, wherein the allocated (53) includes at least one overtaking lane and at least one non-overtaking lane. The map database (10) includes a first part (11) and a second part (14), and the first attribute (63, 64, 83, 86) is the first part (11). And the second attribute (93, 98) is stored in the second part (14),
The processing unit (2) outputs the route guidance information based on data retrieved from the second part (14) and independent of the data stored in the first part (11). The vehicle navigation device of claim 1, wherein the vehicle navigation device is configured to control.   6. The first part (11) is a first table and the second part (14) is a second table different from the first table (11). Vehicle navigation device. Each road segment (51-59) is located on at least one tile (50, 71-74) of tiling,
The map database (10) is placed on the tiling tile (50, 71-74) only if at least one of the road segments (51-53) represented by links has at least one overtaking lane 7. A vehicle navigation device according to any one of the preceding claims, comprising the first attribute (63, 64, 83, 86) for said linked link (51-53). Each link is located on at least one tile (71-74) of further tiling,
The map database (10) can be used for the further tiling only if at least one of the road segments (51-59) located in the further tiling tile (71-74) has at least one overtaking lane. The vehicle navigation device of claim 7, comprising the second attribute (93, 98) for a lane of the road segment (51-59) located on the tile (71-74). A method for generating a map database (10) comprising:
The method
Searching for data including information on road segments (51-59) and information on lanes of each road segment;
For multiple road segments (51-59)
Determining whether the road segment (51-59) has at least one overtaking lane;
If at least one lane of the road segment (51-59) is an overtaking lane, the first attribute (63, 64, 83, 86) is selectively assigned to the link representing the road segment (51-59). And
Selectively assigning a second attribute (93, 98) to the lane of the road segment (51-59), wherein the second attribute (93, 98) is the road segment (51-59). ) To be selectively assigned based on which lane is the overtaking lane,
Storing the first attribute (63, 64, 83, 86) and the second attribute (93, 98) in the map database (10).   Selectively assigning the first attribute (63, 64, 83, 86) assigns the parameter of the first attribute (63, 64, 83, 86) to all of the road segments (51-59). 10. The method according to claim 9, comprising setting based on whether the lane is an overtaking lane, wherein the parameters are stored in the map database (10).   The first attribute (63, 64, 83, 86) is stored in a first part (11) of the map database (10), and the second attribute (93, 98) is stored in the map database (10). 10) is stored in the second part (14), the first part (11) represents data for route search, and the second part (14) is for outputting route guidance information The method of claim 9, wherein A tiling is defined that includes a plurality of tiles (50, 71-74) and covers the road segments (51-59),
For each tile (50, 71-74) of the tiling, a first attribute (63, 64, 83, 86) is included in the respective tile (50, 71-74) of the tiling. The method according to any one of claims 9 to 11, wherein the map database (10) is stored only if at least one road segment (51-59) comprises at least one overtaking lane. A further tiling comprising a plurality of tiles (71-74) and covering said road segment (51-59) is defined;
For each tile (71-74) of the further tiling (93, 98), a second attribute (93, 98) includes at least one road segment included in the respective tile of the further tiling (71-74) ( Method according to claim 12, wherein 51-59) is stored in the map database (10) only if it contains at least one overtaking lane. A method of processing data stored in a map database (10), wherein the map database (10) includes links representing road segments (51 to 59) and first attributes (63, 64, 83, 86). ) And a second attribute (93, 98), the first attribute (63, 64, 83, 86) is assigned to a subset of links (51-53), the second attribute (93, 98) are assigned to at least some lanes of the subset of the links (51-53), the method comprising:
Performing a route search, and performing the route search,
Monitoring activation of a preference or avoidance option for an overtaking lane and, if the preference or avoidance option is activated, based on the first attribute (63, 64, 83, 86) assigned to the link Selectively adjusting the cost of the route, and
Outputting route guidance information based on the second attribute (93, 98).   The route search is performed independently of the second attribute (93, 98), and the output of the route guidance information is performed independently of the first attribute (63, 64, 83, 86). The method according to claim 14.

Images