Patent Application
20130002658
This patent application claims priority from EP Application No. 11 172 364.9 filed Jul. 1, 2011, which is hereby incorporated by reference.
The invention relates to a vehicle navigation device comprising a database storing object data units and to a method of processing data stored in a map database.
Navigation devices are known which determine a route from a starting point to a destination using map data. Generally, these navigation devices may perform a search for a route which minimizes a cost function. The cost function may represent travel time, distance or fuel costs associated with the route, or any other suitable quantity to be minimized. The route which is optimum may depend on the activation of prefer or avoid options. Prefer and avoid options for highways, ferries or tunnels may be provided.
In addition to route determination, navigation devices may also provide route guidance functions via a user interface. The provision of guidance information may involve the generation of optical or audio output which provides information on a portion of a road network surrounding the vehicle, possibly combined with optical or audio directions to a driver.
The provision and use of a map database that allow data to be used efficiently for route search and route guidance may represent a considerable challenge. For illustration, for route search, information on the fine scale structure of the road network is usually not required for locations remote from both the starting point and destination. However, information on at least certain types of roads, such as highways, at locations remote from both the starting point and destination will be required for a route search. By contrast, guidance functions may require information only in an area surrounding the vehicle, but to a greater level of detail.
For the generation of optical output, for example on a display screen of the navigation device, for providing the above-mentioned route guidance functions in modern navigation devices at least in some modes a surrounding of the navigation device is displayed in a perspective view, i.e. a 3D-view. With such three-dimensional views, care has to be taken to display objects like buildings on the correct height level, for example such that the object does not float above the ground or look like it is sunk into the ground, for all levels of detail which are desired.
Accordingly, there is a need to provide vehicle navigation devices and methods which assist in displaying objects correctly.
A vehicle navigation device comprises a database, the database comprising object data units comprising information for a perspective display of associated respective objects, wherein at least one of the object data units comprises an adjustable height parameter for adjusting a height of the respective object. The vehicle navigation device furthermore comprises a processing unit configured to cause an output interface like a display to display an object based on a corresponding one of the object data units and the adjustable height parameter.
The processing device may be configured to adjust the adjustable height parameter of an object data unit based on a height of a ground level at a location where the object is to be displayed. The ground level may depend on a level of detail to be displayed. The database may be a map database comprising a plurality of logical layers, the object data units being associated with one of the layers, for example a guidance layer.
According to another aspect, a method is provided, comprising providing a database, the database comprising object data units comprising information for perspective displaying of associated objects, at least some of the object data units comprising an adjustable height parameter for adjusting a height of the respective object, identifying at least one object to be displayed, and displaying the object based on the associated object data unit.
The method may further comprise determining a position, and identifying the object to be displayed depending on the position.
The method may further comprise adjusting the adjustable height parameter of an object data unit of an object data unit of said object data units associated with said object to be displayed.
These and other objects, features and advantages of the present invention will become apparent in light of the detailed description of the best mode embodiment thereof, as illustrated in the accompanying drawings. In the figures, like reference numerals designate corresponding parts.
The foregoing and other features of embodiments will become more apparent from the following detailed description of embodiments when read in conjunction with the accompanying drawings.
The navigation device may include additional components, such as a position sensor and/or a wireless receiver and/or a vehicle interface. The position sensor may be adapted to determine the current position of the vehicle in which the navigation device 1 is installed. The position sensor may comprise a GPS (Global Positioning System) sensor, a Galileo sensor, a position sensor based on mobile telecommunication networks and the like. The wireless receiver may be configured to receive information for updating the map database stored in the memory 3. The vehicle 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 for example comprise CAN (controller area network) or MOST (Media Oriented devices Transport) interfaces.
The memory 3 stores a map database comprising map data. The map database includes information on links representing road segments and attributes. In the map database, also object data units as explained below may be stored. In other embodiments, object data units may be stored in a separate database in the memory 3.
The processor 2 may use the information stored in the map database for performing a route search when a user sets, for example, via the input interface 5, a destination to be reached. The processor 2 may perform the route search independently of the second attributes assigned to lanes. The processor 2 may control the outputting of route guidance information.
Generally, various attributes may be assigned to links and stored in the map database. The attributes may include information on starting and end points of links or other information related to map topology. Such attributes may be stored in a data structure having a pre-defined number of data fields that is respectively provided for each link or other map feature stored in the map database. In addition, attributes may be selectively assigned to links, or other features, only when present on the respective link.
The map database stored in the memory 3 may include different logical layers. Additionally, the map database may be split into different blocks that are associated with different update regions or tiles of a tiling. Such a structure facilitates performing updates. This is particularly desirable for performing updates of the map database to adjust the map database to local changes in a road network. Such updates may then be performed for example by updating only the update regions or tiles affected by changes in the road network. This allows the updates to be more readily performed in a more time-efficient manner or as over-the-air updates.
As mentioned above, the map database or, in some embodiments, a separate database may store various object data units comprising information, e.g., data, usable for a perspective displaying of objects associated with the respective object data units, for example buildings. With a perspective displaying of objects, a three-dimensional impression may be generated. As will be explained in further detail in the following, at least some of the object data units comprise an adjustable height parameter for adjusting a height of the respective object.
The map database 10 includes a plurality of layers, which include a routing layer 11 and a guidance layer 14. The routing layer 11 includes the information required for performing route searches. This information may include information on the topology of the road network, such as starting points and end points of links. The information in the routing layer 11 may further include costs associated with links for various cost models. The information in the routing layer 11 may also include attributes which allow the costs of links to be adjusted in a route search based on prefer or avoid options.
In the routing layer 11, there may be different levels 12, 13 which include for example data representing the road network to different levels of details. For illustration, while all road segments of the road network may be present at the level 13, some of the road segments may be omitted at a higher level 12.
The guidance layer 14 includes data required for route guidance. The guidance layer 14 may in particular include data required for optical and/or audio output of guidance information. For example, guidance 14 may comprise the above-mentioned object data units or references thereto. The guidance layer may also include a level structure, with the data in the different levels representing the road network and/or road surroundings to different levels of details.
The routing layer 11 and the guidance layer 14 may be configured, for example in one embodiment, as separate tables stored in a memory. For illustration rather than limitation, the routing layer 11 may be a table in a SQL database, and the guidance layer 14 may be another table in the SQL database.
The map database 10 may include additional layers 15-17. A name layer 15 includes references to road names, house numbers or similar. A truck layer 16 may include specific attributes for trucks or lorries. An Advanced Driver Assistance System (ADAS) layer 17 may include data for Advanced Driver Assistance. Additional or alternative layers may be provided, such as a layer for points of interest, a layer for phonetic representations, or a layer for basic map display.
In one embodiment, the map database 10 may have a structure as defined by the Navigation Data Standard (NDS).
The use of object data units with adjustable height parameters will now be described.
In
As mentioned, object data units like the object data unit 20 of
The object data unit 20 as already mentioned above comprises a height adjustment parameter 21 with which the height of the associated object when displaying the object can be adjusted. This will now be explained with reference to
In
An adjustment of the height parameter and therefore of the height of the building 31 may in particular be done depending on a level of detail of the ground 30. In navigation devices, various levels of details of a representation may be used, for example based on a scale of the displayed landscape or based on a user selection. Depending on the level of detail, the exact height level of the ground 30 may vary. For example, when going to a lower level of detail certain vertices used for forming an elevation on the ground 30 may be omitted, which generally lowers the height level of the ground 30. In such a case, the height parameter of the data object unit of the building 31 may be adjusted such that the building 31 is still displayed as standing on the ground regardless of the level of detail used.
In
At step 50 in
At step 51, objects to be displayed are identified, for example based on a current position of a navigation device and a direction in which the navigation device is moving, such that the surroundings of the navigation device in the direction the navigation device (and therefore for example a car implementing the navigation device) is moving may be shown.
At step 52, a level of detail for displaying a landscape, comprising the objects identified at step 51 is determined. As explained with reference to
At step 53, the height parameter of one or more objects to be displayed is adjusted depending on the determined level of detail to ensure that the objects are correctly placed with respect to the ground, for example buildings being placed on the ground at the corresponding location of the building. It should be noted that in other embodiments the level of detail may be fixed, and the height parameter may be adjusted depending on the (fixed) ground level at a certain position.
At step 54, the objects are displayed corresponding to the information found in the associated object data units, for example the adjusted height parameters.
It should be noted that an adjustable height parameter like the height parameter 21 (
Although the present invention has been illustrated and described with respect to several preferred embodiments thereof, various changes, omissions and additions to the form and detail thereof, may be made therein, without departing from the spirit and scope of the invention.
| Number | Date | Country | Kind |
|---|---|---|---|
| 11 172 364.9 | Jul 2011 | EP | regional |
