Patent Grant
8224795
The present invention relates to a map data product, a map data processing program product, a map data processing method and a map data processing apparatus.
Map data of road maps and the like used in navigation systems are provided in a recording medium such as a CD ROM, a DVD-ROM or the like in the related art. In addition, map data are provided through communication to a navigation system installed in a vehicle.
However, a system that updates with a high degree of efficiency part of the map data with a large volume provided in a recording medium or the like and allows new and old map data to be used efficiently and with consistency is not provided in the related art.
The present invention provides a map data product, a map data processing program product, a map data processing method and a map data processing apparatus that make it possible to update part of map data with a large volume provided in a recording medium or the like with a high degree of efficiency and allow the new and old map data to be used with efficiency and consistency.
A first data product according to the present invention that can be read into a computer or a map data processing apparatus, contains therein map data having map-related information of a map. The map data comprises: a structure having the map-related information divided into units of a plurality of divisions into which the map is divided; and a structure having management information for the map-related information divided into units of the divisions, and: the map-related information obtained by the computer or the map data processing apparatus can be updated in units of the individual divisions by using the management information.
In this first data product, it is preferred that: the map is divided into a plurality of first division units, the first division units are each divided into a plurality of second division units, a number of the second division units is equal among the individual first division units, and the divisions into which the map is divided each corresponding to one of the second division units; and the management information contains a set of management information related to the plurality of second division units, provided in correspondence to each of the first division units. In this case, it is preferred that the management information further contains management information related to the plurality of first division units.
Also, in the first data product, it is preferred that: a plurality of levels are defined, each in correspondence to one of a plurality of different scaling factors at which the map is rendered; the map is divided into a plurality of first division units at each level, the first division units are each divided into a plurality of second division units, the number of second division units is equal among the individual first division units, and the divisions into which the map is divided each corresponding to one of the second division units; a plurality of sets of the map-related information are provided in correspondence to the plurality of levels; and the management information contains a set of management information related to the plurality of first division units provided in correspondence to each of levels, and also contains a set of management information related to the plurality of second division units provided in correspondence to each of the first division units.
Also, in the first data product, it is preferred that the map-related information which is provided in units of the individual divisions is separated into different types of map-related information to be individually managed.
Also, in the first data product, it is preferred that: a plurality of levels are defined, each in correspondence to one of a plurality of different scaling factors at which the map is rendered; a plurality of sets of the map-related information are provided in correspondence to the plurality of levels; and as the map-related information provided in units of the individual divisions, at least one type of map-related information available at all levels and another type of map-related information available at, at least, one level are provided separately from each other. In this case, it is preferred that: the one type of map-related information is used to display the map at a display device; and the other type of map-related information contains information used in route search.
Also, in the first data product, it is preferred that: a connecting point at which the map-related information corresponding to one of two divisions is correlated to the map-related information corresponding to the other division is present at a geographically matching position within the two divisions; and sets of information related to the connecting point contain common two-dimensional coordinate values indicating the position of the connecting point within the map in the map-related information corresponding to the two divisions. In this case, it is preferred that the two-dimensional coordinate values are values corresponding to latitudinal and longitudinal values. Furthermore, it is preferred that the information related to the connecting point contains a parameter other than the two-dimensional coordinate values of the connecting point in addition to the two-dimensional coordinate values. In this case, it is preferred that the parameter contains height information indicating a height of the connecting point. Furthermore, it is preferred that the parameter contains time information related to generation and update of the map-related information provided in units of the individual divisions. Yet furthermore, it is preferred that: a plurality of levels are defined, each in correspondence to one of a plurality of different scaling factors at which the map is rendered; a plurality of sets of the map-related information are provided in correspondence to the plurality of levels; the map is divided into a plurality of divisions at each level, and each of the plurality of sets of map-related information, corresponding to a given level, is divided in units of the individual divisions into which the map is divided; the two divisions belong to levels different from each other, and two-dimensional coordinate values of the connecting point at a level at which the map is rendered in greater detail are attached to the two-dimensional coordinate values of the connecting point at a given level.
Also, in the first data product, it is preferred that: the map-related information provided in units of individual divisions is separated into different types of map-related information to be individually managed; and map-related information having the highest priority among the different types of map-related information is managed by setting a predetermined upper limit to the size thereof. In this case, it is preferred that: if the size of the map-related information having the highest priority exceeds the predetermined upper limit after update, at least map-related information corresponding to an excess beyond the predetermined upper limit to the size, which results from the update, is managed as map-related information with lower priority relative to the highest priority. Furthermore, it is preferred that the map-related information with the highest priority includes at least information used to display the map at a display device. Also, it is preferred that: the map-related information with the highest priority includes at least information used to display the map at a display device; and the map-related information with the lower priority relative to the highest priority includes information that enables display of a more detailed map at the display device, compared to the map displayed by using the map-related information with the highest priority.
It is preferred that the above data products are each embodied as a recording medium having the map data recorded therein.
A map data processing apparatus according to the present invention, comprises: a recording medium drive unit at which a data product is loaded; an update data acquisition unit that obtains update data for the map-related information provided in units of the individual divisions; and a processing unit that processes the map data based upon the map data recorded in the recording medium and the update data obtained by the update data acquisition unit.
In this map data processing apparatus, it is preferred that: the map data are map display data; and the processing unit displays a map at a display unit by connecting the map data recorded in the recording medium with the update data obtained by the update data acquisition unit.
Also, it is preferred that: the map data are route search data; and the processing unit executes route search processing by connecting the map data recorded in the recording medium with the update data obtained by the update data acquisition unit.
A method for processing map data in a map data processing apparatus, according to the present invention, comprises steps for: reading map data management information indicating specific positions in a recording medium, at which map data divided into a plurality of divisions are stored, from the recording medium having stored therein the plurality of map data divisions and the management information into a nonvolatile memory within a map data processing apparatus; altering part of the management information in the nonvolatile memory corresponding to update data so as to indicate a position at which the update data are stored, when the update data for partially updating the map data in units of the individual divisions are obtained; and accessing the map data based upon the management information in the nonvolatile memory.
A program product that can be read into a computer or a map data processing apparatus, according to the present invention, contains a map data processing program executed to process map data. The map data processing program comprises: an instruction code for reading map data management information indicating specific positions in a recording medium, at which map data divided into a plurality of divisions are stored, from the recording medium having stored therein the plurality of map data divisions and the management information into a nonvolatile memory within a map data processing apparatus; an instruction code for altering part of the management information in the nonvolatile memory corresponding to update data so as to indicate a position at which the update data are stored, when the update data for partially updating the map data in units of the individual divisions are obtained; and an instruction code for accessing the map data based upon the management information in the nonvolatile memory.
A map data processing apparatus according to the present invention that processes map data, comprises: a recording medium drive unit at which a recording medium is loaded having stored therein the map data divided into a plurality of divisions and map data management information indicating specific storage positions of the plurality of map data divisions in the recording medium; a nonvolatile memory into which the management information read from the recording medium is stored; an update data acquisition unit that obtains update data to be used to update part of the map data in units of the individual divisions; and a control unit that alters part of the management information in the nonvolatile memory corresponding to the updated data so as to indicate a storage position of the update data when the update data acquisition unit obtains the update data, and accesses the map data based upon the management information in the nonvolatile memory.
Another method for processing map data in a map data processing apparatus, according to the present invention, comprises steps for: confirming that a recording medium is loaded at the map data processing apparatus, the recording medium having stored therein the map data divided into a plurality of divisions and map data management information indicating specific storage positions of the plurality of map data divisions in the recording medium; storing identification information, which bears an initial value indicating that the map data management information used in the map data processing apparatus is stored in the recording medium, into a first nonvolatile memory; storing update data obtained to update part of the map data in units of individual divisions into a second nonvolatile memory, obtaining the map data management information from the recording medium, altering part of the management information corresponding to the update data so as to indicate a storage position of the update data in the second nonvolatile memory, storing the management information into a third nonvolatile memory, and altering the identification information stored in the first nonvolatile memory to identification information indicating that the map data management information is stored in the third nonvolatile memory; obtaining the identification information to ascertain whether the map data management information is stored in the recording medium or in the third nonvolatile memory by accessing the first nonvolatile memory when accessing the map data; obtaining the map data management information from the recording medium if the map data management information is determined to be stored in the recording medium; obtaining the map data management information from the third nonvolatile memory if the map data management information is determined to be stored in the third nonvolatile memory; and accessing the map data based upon the obtained map data management information.
Another program product according to the present invention that can be read into a computer or a map data processing apparatus, contains a map data processing program executed to process map data. The map data processing program comprises: an instruction code for confirming that a recording medium is loaded at the map data processing apparatus, the recording medium having stored therein the map data divided into a plurality of divisions and map data management information indicating specific storage positions of the plurality of map data divisions in the recording medium; an instruction code for storing identification information, which bears an initial value indicating that the map data management information used in the map data processing apparatus is stored in the recording medium, into a first nonvolatile memory; an instruction code for storing update data obtained to update part of the map data in units of individual divisions into a second nonvolatile memory, obtaining the map data management information from the recording medium, altering part of the management information corresponding to the update data so as to indicate a storage position of the update data in the second nonvolatile memory, storing the management information into a third nonvolatile memory, and altering the identification information stored in the first nonvolatile memory to identification information indicating that the map data management information is stored in the third nonvolatile memory; an instruction code for obtaining the identification information to ascertain whether the map data management information is stored in the recording medium or in the third nonvolatile memory by accessing the first nonvolatile memory when accessing the map data; an instruction code for obtaining the map data management information from the recording medium if the map data management information is determined to be stored in the recording medium; an instruction code for obtaining the map data management information from the third nonvolatile memory if the map data management information is determined to be stored in the third nonvolatile memory; and an instruction code for accessing the map data based upon the obtained map data management information.
Another map data processing apparatus according to the present invention that processes map data, comprises: a recording medium drive unit at which a recording medium having stored therein the map data divided into a plurality of divisions and map data management information indicating specific storage positions of the plurality of map data divisions in the recording medium is loaded; a first nonvolatile memory in which identification information bearing an initial value indicating that map data management information used in the map data processing apparatus is stored in the recording medium is stored when the recording medium is loaded into the recording medium drive unit; an update data acquisition unit that obtains update data to be used to update part of the map data in units of the individual divisions; a second nonvolatile memory in which the update data obtained by the update data acquisition unit are stored; a control unit that obtains the map data management information from the recording medium when the update data acquisition unit obtains the update data, alters part of the management information corresponding to the update data so as to indicate a storage position of the update data in the second nonvolatile memory and alters the identification information stored in the first nonvolatile memory to identification information indicating that the map data management information is stored in a third nonvolatile memory; and the third nonvolatile memory in which the map data management information having been altered by the control unit is stored, wherein: the control unit obtains the identification information by accessing the first nonvolatile memory to ascertain whether the map data management information is stored in the recording medium or in the third nonvolatile memory when accessing the map data, obtains the map data management information from the recording medium if the map data management information is determined to be stored in the recording medium, obtains the map data management information from the third nonvolatile memory if the map data management information is determined to be stored in the third nonvolatile memory, and accesses the map data based upon the obtained map data management information.
Another method for processing map data in a map data processing apparatus, according to the present invention, comprises steps for; confirming that a recording medium is loaded at the map data processing apparatus, the recording medium having stored therein the map data divided into a plurality of divisions and map data management information indicating specific storage positions of the plurality of map data divisions in the recording medium; storing identification information, which bears an initial value indicating that the map data management information used in the map data processing apparatus is stored in the recording medium, into a first nonvolatile memory; confirming a connection with a second nonvolatile memory in which update data used to update part of the map data in units of the individual divisions are written; obtaining the map data management information from the recording medium when the connection with the second nonvolatile memory is confirmed, altering part of the management information corresponding to the update data so as to indicate a storage position of the update data in the second nonvolatile memory, storing the management information into a third nonvolatile memory and altering the identification information stored in the first nonvolatile memory to identification information indicating that the map data management information is stored in the third nonvolatile memory; obtaining the identification information to ascertain whether the map data management information is stored in the recording medium or in the third nonvolatile memory by accessing the first nonvolatile memory when accessing the map data; obtaining the map data management information from the recording medium if the map data management information is determined to be stored in the recording medium; obtaining the map data management from the third nonvolatile memory if the map data management information is determined to be stored in the third nonvolatile memory; and accessing the map data based upon the obtained map data management information.
Another program product according to the present invention that can be read into a computer or a map data processing apparatus, contains a map data processing program executed to process map data. The map data processing program comprises: an instruction code for confirming that a recording medium is loaded at the map data processing apparatus, the recording medium having stored therein the map data divided into a plurality of divisions and map data management information indicating specific storage positions of the plurality of map data divisions in the recording medium; an instruction code for storing identification information, which bears an initial value indicating that the map data management information used in the map data processing apparatus is stored in the recording medium, into a first nonvolatile memory; an instruction code for confirming a connection with a second nonvolatile memory in which update data used to update part of the map data in units of the individual divisions are written; an instruction code for obtaining the map data management information from the recording medium when the connection with the second nonvolatile memory is confirmed, altering part of the management information corresponding to the update data so as to indicate a storage position of the update data in the second nonvolatile memory, storing the management information into a third nonvolatile memory and altering the identification information stored in the first nonvolatile memory to identification information indicating that the map data management information is stored in the third nonvolatile memory; an instruction code for obtaining the identification information to ascertain whether the map data management information is stored in the recording medium or in the third nonvolatile memory by accessing the first nonvolatile memory when accessing the map data; an instruction code for obtaining the map data management information from the recording medium if the map data management information is determined to be stored in the recording medium; an instruction code for obtaining the map data management from the third nonvolatile memory if the map data management information is determined to be stored in the third nonvolatile memory; and an instruction code for accessing the map data based upon the obtained map data management information.
Another map data processing apparatus, according to the present invention, that processes map data, comprises: a recording medium drive unit at which a recording medium having stored therein the map data divided into a plurality of divisions and map data management information indicating specific storage positions of the plurality of map data divisions in the recording medium is loaded; a first nonvolatile memory in which identification information bearing an initial value indicating that map data management information used in the map data processing apparatus is stored in the recording medium is stored when the recording medium is loaded into the recording medium drive unit; a memory connection unit that enables a connection with a second nonvolatile memory in which update data used to update part of the map data in units of the individual divisions are written; a control unit that obtains the map data management information from the recording medium when a connection of the second nonvolatile memory with the memory connection unit is confirmed, alters part of the management information corresponding to the update data so as to indicate a storage position of the update data in the second nonvolatile memory and alters the identification information stored in the first nonvolatile memory to identification information indicating that the map data management information is stored in a third nonvolatile memory; and the third nonvolatile memory in which the map data management information having been altered by the control unit is stored, and: the control unit obtains the identification information by accessing the first nonvolatile memory to ascertain whether the map data management information is stored in the recording medium or in the third nonvolatile memory when accessing the map data, obtains the map data management information from the recording medium if the map data management information is determined to be stored in the recording medium, obtains the map data management information from the third nonvolatile memory if the map data management information is determined to be stored in the third nonvolatile memory, and accesses the map data based upon the obtained map data management information.
It is preferred that the above program products are each embodied as a recording medium having recorded therein the map data processing program.
In addition, the navigation system 1 can be connected to a communication device 4 such as a portable telephone. The navigation system 1 can be connected to the Internet 5 via the communication device 4 and can be further connected with a map server 6 via the Internet 5. At the map server 6, map data from old versions up to and including the latest version of map data, are held at a map database 7, and guidance search data from old versions up to and including the most recent guidance search data, are held at a guidance search database 8. Thus, the map server 6 is capable of providing update data to be used to update part of the map data to the navigation system 1 via the Internet 5. It is to be noted that the guidance search data contain position information indicating the positions of POIs and the like and attribute information indicating the specific types, the names and the like of the POIs and the like.
The navigation system 1 includes a control device 11 and a nonvolatile memory 12. The control device 11 is constituted with a microprocessor and its peripheral circuits. The nonvolatile memory 12 is a nonvolatile memory such as a hard disk or a flash memory installed inside the navigation system 1. The nonvolatile memory 12 may be any type of storage device as long as data written therein are retained even when the power to the navigation system 1 is turned off.
Once the recording medium 2 is loaded into the navigation system 1, it remains loaded in the navigation system 1 until it is replaced with a new recording medium 2. Accordingly, it may be referred to as a fixed medium as opposed to the removable memory 3. The map database 7 and the guidance search database 8, which hold all the versions of map data and guidance search data, from the oldest to the most recent, are databases holding mother data. Using the data at the map database 7 and the guidance search database 8, the map server 6 can prepare a recording medium 2 having recorded therein initial (pre-update) map data or a removable memory 3 having stored therein update data to be used for data update.
The current position detection device 13, which detects the current position of the vehicle, may be constituted with, for instance, an azimuth sensor that detects the advancing azimuth of the vehicle, a vehicle speed sensor that detects the vehicle speed, a GPS sensor that detects a GPS signal transmitted from a GPS (global positioning system) satellite and the like. The DVD drive device 14 reads map data and the like in the recording medium 2 loaded therein. In the embodiment, the recording medium 2 is a DVD ROM. However, the recording medium 2 may be a CD ROM or another type of recording medium.
The memory 15 is used to store the vehicle position information detected with the current position detection device 13 and the like and also to store node information, link information and the like of the nodes and the links on a recommended route calculated by the control device 11. In addition, full mesh management information which is to be detailed later is stored in the memory 15. The memory 15 constitutes a working area of the control device 11. The communication interface 16 is used to achieve a connection with the communication device 4. The use of a portable telephone and an Internet connection are enabled via the communication interface 16. Data in the removable memory 3 can be read with the removable memory read device 17 at which the removable memory 3 is loaded.
The monitor 18 is a display device at which a map, a recommended route and various types of information are displayed. The monitor 18 may be provided as an integrated part of the navigation system main unit or it may be provided as a separate casing. In addition, the monitor 18 disposed at an isolated position may be connected to the navigation system main unit through a cable or the like. Through the input device 19, the destination for the vehicle and the like are entered when conducting a route search. It may be constituted as a remote-control unit or it may be constituted as a touch panel disposed on the screen at the monitor 18. The control device 11 executes various types of navigation processing such as road map display, route search and route guidance by using the current vehicle position information detected with the current position detection device 13, the map data stored in the recording medium 2 or the nonvolatile memory 12. It is to be noted that a program of the various types of processing executed by the control device 11 is installed in a ROM (not shown) provided inside the control device 11.
-Map Data Structure-
The data structure adopted in the map data mentioned above is now explained in further detail. The map data are information related to maps and include background (for map display) data, locator data, network (for route search) data and guidance data (information indicating intersecting point names, node names, directional terms, directional guidance facility information and the like). The background data are used to display a background of a road or a background in a road map. The locator data are used to specify the current vehicle position for map matching and the like. The network data, which are route search data constituted with branching information and the like not directly relevant to the specific road shapes, are mainly used when calculating a recommended route (when executing a route search). The guidance data include the names of intersecting point and the like, and are used to provide guidance for the driver or the like along the recommended route based upon the calculated recommended route.
The map data are managed based upon a concept that they are provided at different levels in blocks and meshes in the embodiment. In the embodiment, the map data are divided into seven different levels of data, with each level corresponding to a specific scaling factor. Level 0 corresponds to the scaling factor at which the map is provided with the most detail, and at level 6, the map is provided as the widest-area map. While the different levels of map data are provided at varying scaling factors, a common area is covered by the various levels of map data. Namely, supposing that the subject area is the entire nation of Japan, map data of the entire nation of Japan are provided at each level with a scaling factor different from the scaling factors corresponding to the other levels. For instance, at level 0, map data of the entire nation of Japan are provided at a scaling factor of 1/6250, at level 3, map data of the entire nation of Japan are provided at a scaling factor of 1/400,000, at level 4, map data of the entire nation of Japan are provided at a scaling factor of 1/1,600,000, and at level 6, map data of the entire nation of Japan are provided at a scaling factor of 1/128,000,000. In other words, seven sets of map data are provided in correspondence to levels 0 to 6.
At level 4, the area 101 is managed with a plurality of blocks 104, i.e., 2×2=4 blocks. Each block 104 is divided into a plurality of meshes 105 and is managed with the meshes. In the embodiment, the data in the block are managed as p×q sets of mesh data. The blocks 104 of map data at the same level are each divided into p×q meshes.
At levels 3 and 4, the area 101 is divided into different numbers of blocks and the individual blocks are divided into different numbers of meshes, since different volumes of data are handled at level 4 with a smaller scaling factor (a larger denominator) providing a wider area map and at level 3 with a larger scaling factor (a smaller denominator) providing a more detailed map compared to level 4. Namely, the map data are divided as appropriate in correspondence to the volume of data handled at each level. However, at a given level, the size of the individual blocks and the size of the individual meshes remain constant. It is to be noted that the numbers of blocks that the area 101 is divided into at the two levels in
The terms “blocks” and “meshes” in this context are used for convenience in the explanation of the embodiment, and other terms may be used as well. Meshes may instead be referred to as parcels, or blocks may be referred to as first division units and meshes may be referred to as second division units. In addition, the blocks and meshes may be considered to be units obtained by geographically dividing the data.
A total mesh number 183 in the full mesh management information 181 in
Each set of mesh data 182 is constituted with mesh internal management information 111, background (for map display) data 112, locator data 113, network (for route calculation) data 114 and guidance data 115. The mesh internal management information 111 and the background (for map display) data 112 constitute basic data, whereas the locator data 113, the network data 114 and the guidance data 115 constitute extension data. The basic data are included at all the levels of data. The mesh data at a given level contain specific extension data inherent to the level. For instance, the network data are contained in the data at levels 1, 2, 3 and 4, whereas the locator data and the guidance data are provided in the data at level 0. It is to be noted that address calculation data, image data, VICS data, building attribute data, peripheral area search data and the like may also be provided as extension data.
It is to be noted that the data are managed by setting an upper limit to the data size of the basic data in the embodiment. The data size upper limit may be set to, for instance, 32 KB. If the basic data size exceeds the upper limit value after updating map data, the excess data are managed as extension data. Let us consider a case in which a set of mesh data 182 initially contains 20 KB of basic data and 10 KB of extension data, the basic data alone are updated and the data size of the basic data increases to 40 KB as a result. The updated basic data are edited so as to keep the basic data size equal to or under 32 KB, and the excess 8 KB of basic data is managed as extension data. As a result, the size of the extension data increases to 18 KB, and the size of the overall mesh data 182 increases from 30 KB to 50 KB. If, on the other hand, the mesh data 182 initially contains 20 KB of basic data and 10 KB of extension data and the basic data alone are updated to increase the basic data size to 30 KB, the basic data size still does not exceed the upper limit 32 KB, and the additional 10 KB of basic data is held as part of the basic data. Thus, the size of the basic data after the update increases to 30 KB, the size of the extension data remains at 10 KB, and the size of the overall mesh data 182 increases from 30 KB to 40 KB. The upper limit is set for the data size of the basic data as described above for the following reason.
The navigation system 1 may be used for a number of years without installing additional memory under normal circumstances. For this reason, it is desirable to use a fixed size of map data, which matches the performance level of the navigation system 1 that is likely to be used for years. However, the volume of the map data is likely to increase over time as building shape data become more accurate, more detailed topographical data become available, and land development and rezoning take place. Accordingly, the map data adopt a structure which allows the map data to be updated in units of individual meshes in the embodiment.
When a new model navigation system comes onto the market, it usually has a greater memory capacity, a higher processing capability and the like. As a result, the volume of data that can be handled by the program increases, new functions are added or more detailed display becomes possible under normal circumstances. In this situation, the updated map data need to have a structure that allows the updated map data to be utilized commonly in the old navigation system and the new navigation system.
To satisfy the needs described above, the basic data are edited to maintain the data size which allows the basic data to be handled in the old navigation system as well as the new navigation system and the excess data are stored as extension data. In addition, data that are only needed in conjunction with a new function that cannot be used in the old type of navigation system, too, are stored as extension data.
The concept explained above by using the expression “old and new types of navigation systems” also applies to “general-purpose and high-performance” navigation systems or “portable and on-vehicle navigation systems” as well as “old and new” navigation systems. In other words, the structure of the map data achieved in the embodiment allows the map data to be utilized commonly in a system with a low processing capability and in a system with a high processing capability. The type of map data which is invariably utilized regardless of the level of the processing capability of the system is referred to as basic data. The upper limit to the size of the basic data is set in conformance to the memory size or the like of a system with the lowest processing capability. Since this makes it possible to commonly utilize the map data in the embodiment in systems with varying levels of processing capability, a higher degree of efficiency in map data management and a cost-reduction are achieved.
It is to be noted that the initial basic data, which are commonly used at varying levels of processing capability, may be regarded as high-priority data. The additional basic data resulting from an update, on the other hand, are background data to be used to display a more detailed map than the map displayed by using the initial basic data or nonessential, low priority background data that do not need to be displayed in the old model. It goes without saying that as long as the additional basic data can be managed as part of the basic data, the size of which is kept equal to or less than the upper limit, the additional basic data can be regarded as data with the same priority as the initial basic data.
No specific upper limit is set for the data size of the mesh data 182 in the explanation given above. However, an upper limit to the data size of the mesh data 182 may be set in correspondence to the capacity of the memory within the navigation system 1. For instance, the upper limit to the size of the mesh data 182 may be set to 128 KB. It is to be noted that values other than 32 KB and 128 KB may be set for the upper limits to the data sizes of the basic data and the mesh data 182, as well. The upper limits should be set to appropriate values by taking into consideration the initial performance level of the navigation system when the map data are originally defined, a subsequent improvement in the performance that is anticipated for the future and the like.
-Map Data Management in the Navigation System-
A navigation system in the related art reads data from a recording medium such as a CD ROM or a DVD-ROM alone. The navigation system achieved in the embodiment, on the other hand, uses the map data in the recording medium 2 and updated map data in combination. For this reason, it includes the nonvolatile memory 12 which is a read/write medium. The nonvolatile memory 12 is constituted of a hard disk or a flash memory, and data held in the nonvolatile memory 12 are retained even when the power to the navigation system is turned off. The nonvolatile memory 12 may be referred to as a cache medium 12 as well.
Block management information 124 is held at the nonvolatile memory 12. The block management information 124 includes identification information used to check whether the full mesh management information corresponding to the subject block is available in the recording medium 2 or in the nonvolatile memory 12. The initial value is set so as to indicate that all the full mesh management information corresponding to the individual blocks is available in the recording medium 2. As map data are updated in units of meshes, full mesh management information 125 corresponding to the block containing an updated mesh is prepared in the nonvolatile memory 12, and a value indicating that the full mesh management information for the block is available in the nonvolatile memory 12 is set in the block management information 124. The program is enabled to judge whether the full mesh management information is available in the recording medium 2 or in the nonvolatile memory 12 by first referencing the block management information 124.
Reference numeral 126 indicates a memory area where the full mesh management information is stored within the memory 15 of the navigation system. This memory area is hereafter referred to as the memory 126. After judging whether the full mesh management information is available in the recording medium 2 or in the nonvolatile memory 12, the program reads out the full mesh management information from the appropriate medium and stores the full mesh management information thus readout into the memory 126. The full mesh management information 127 read into the memory 126 includes mesh management information corresponding to meshes 1 through n. The mesh management information 128 contains position information 129, storage location data 130, offset data 131 and size data 132. The position information 129 indicates the position of the subject mesh represented by the latitude/longitude or the like of the mesh, whereas the storage location data 130 indicate whether the data are available in the recording medium 2 or in the nonvolatile memory 12. The offset data 131 indicate the position of the data in the medium (the recording medium 2 or the nonvolatile memory 12) and the size data 132 indicate the size of the map data.
After the map data in a given mesh are individually updated with the removable memory 3, the map data in the mesh are read into the nonvolatile memory 12 and are stored as map data 133. Thus, based upon the contents of the storage location data 130, the non-updated map data can be accessed at the recording medium 2 and the updated data can be accessed at the nonvolatile memory 12.
-Structure of Data in the Recording Medium-
Next, the data in the recording medium 2 are explained. A main data file is held in the recording medium 2.
The overall management information 151 includes information related to the overall data, such as information on format version revisions, information on data version revisions, medium identification information, information on the data generation dates, information on the data generating parties and information on the areas covered by the data. The stored data information 152 indicates that types and the storage location of the data stored in the recording medium 2. The level management information 153 includes information on the hierarchical layer structure (the level structure) of the map data stored in the recording medium 2, information on the types of extension data attached to the data at the individual levels and information indicating the storage positions of the block management information. When map data are updated, the level management information 153 is copied into the non-volatile memory 12 and is used to change the storage location (the recording medium 2 or the non-volatile memory 12) of the block management information.
The block management information 154 includes management information used to manage the full mesh management information, such as assignment information indicating the assignment of the full mesh management information at the individual levels, information on the storage locations of the full mesh management information and information indicating the storage positions of the full mesh management information. When the recording medium 2 is loaded into the DVD drive device 14, the block management information 154 is copied into and is used in the nonvolatile memory 12. The initial value is set for the full mesh management information storage location so as to indicate that the full mesh management information is all stored in the recording medium 2. The number of sets of block management information 154 corresponds to the number of different levels of map data that are available.
The full mesh management information 155 is stored in units of individual blocks at each level. For instance, the map data at level 0 are divided into m blocks and thus, there are m sets of full mesh management information 155 in correspondence in the example presented in
The map data 156 are equivalent to data provided in units of individual meshes. The map data 156 are stored in the number of sets matching the sum of the numbers of all the meshes in all the blocks at all the levels of map data stored in the recording medium 2. The structure of the map data in each mesh is as shown in
-Structure of Data in the Nonvolatile Memory-
As shown in
-Main Management File-
In the main management file (not shown), stored data information and level management information copied from the recording medium 2 are stored. The stored data information is created by copying the stored data information in the main data file in the recording medium 2 when data (e.g., guidance search data) other than the data provided in units of meshes in the recording medium 2 are updated and the updated data are stored into the nonvolatile memory 12. Each time data other than the data provided in units of individual meshes are updated and the updated data are stored into the nonvolatile memory 12, the storage location of the corresponding management information is switched from the recording medium 2 to the nonvolatile memory 12.
In addition, medium identification information is contained in the stored data information so as to indicate the recording medium 2 which is the source of the particular piece of cache information. As long as this information and the medium identification information in the recording medium 2 match when they are compared with each other at startup, no problem arises. However, if they do not match (if a different recording medium is loaded), the storage location, the positions and the sizes which are managed with the individual sets of information in the nonvolatile memory 12 are inconsistent with those in the other recording medium 2 and thus, the updated data in the nonvolatile memory 12 can no longer be used. If this occurs, the navigation is executed by using the data in the recording medium 2 alone.
The level management information is created by copying the level management information in the recording medium 2 when any set of mesh data in the map data stored in the recording medium 2 is updated and the updated mesh data are stored into the nonvolatile memory 12. Each time map data are stored into the nonvolatile memory 12, the storage location of the block management information at the corresponding level is switched from the recording medium 2 to the nonvolatile memory 12. At this time, the information indicating the position and the size of the block management information, too, is updated so as to indicate the values in the nonvolatile memory 12.
-Block Management Files-
Block management files are created by copying the block management information 154 at the individual levels in the recording medium 2 into the nonvolatile memory 12 when the recording medium 2 is loaded into the DVD drive device 14. The initial values of the storage locations of the full mesh management information corresponding to the various blocks are invariably set to indicate the recording medium 2. When map data are updated and stored into the nonvolatile memory 12, the block management information at the level corresponding to the map data being updated, too, is updated. The storage location of the full mesh management information of the map data being updated is switched from the recording medium 2 to the nonvolatile memory 12. At this time, the information indicating the position and the size, too, is changed to indicate the values within the nonvolatile memory 12. The block management files are each created in correspondence to one of the different levels of map data. The file name assigned to a block management file is created by using the corresponding level as a key. Since this eliminates the need to write a block management file name, the level management information size does not become unnecessarily large.
-Full Mesh Management Information Files-
A full mesh management information file is created when map data in a mesh inside a given block are updated for the first time and the updated map data are stored into the nonvolatile memory 12, by copying the full mesh management information for the block corresponding to the map data in the recording medium 2. The storage location of the map data is switched from the recording medium 2 to the nonvolatile memory 12. At this time, the information indicating the position and the size of the map data, too, is updated to indicate the values within the nonvolatile memory 12. Subsequently, if mesh data within the same block are updated, the full mesh management information file for the block which is already in the nonvolatile memory 12 is updated. Full mesh management information files are created each in correspondence to one of the blocks. The file name assigned to a full mesh management information file is created by using the corresponding level and block management information as keys. Since this eliminates the need to write a full mesh management file name, the block management information size does not become unnecessarily large.
-Map Data Files-
A map data file is created when map data are updated and the updated map data are stored into the nonvolatile memory 12. Map data files are each created in correspondence to a specific mesh. Full mesh management information corresponding to the updated map data is created by copying the full mesh management information in the recording medium 2, and the storage location, the storage position and the size of the actually updated basic/extension data alone are updated to the values within the nonvolatile memory 12. Data in the recording medium 2 are referenced when non-updated basic/extension data are needed. Map data files are created each in correspondence to a specific mesh. The file name assigned to a map data file is created by using the corresponding level, block management information and full mesh management information as keys. Since this eliminates the need to write a map data file name, the map management information size and the block management information size do not become unnecessarily large.
-Basic/Extension Data in the Map Data-
As shown in
-Mesh Internal Management Information-
Each set of mesh internal management information 111 includes information inherent to the map data contained in the corresponding mesh and information indicating the storage locations, the positions, the sizes and the like of the stored background and extension data.
As the mesh information 161, basic information such as the size of the mesh internal management information, the actual size of the corresponding mesh taken along the vertical and horizontal directions and the like is stored. The background management information 162 contains management information related to the background data (map display data) in the mesh. More specifically, history information, information indicating the storage location, information indicating the storage position, offset information and information indicating the size are stored as the background management information. As the history information, the management number assigned to updated information, for instance, is stored, and the management number bears a larger value to indicate a more recent data version. As the storage location information, an identification flag indicating whether the data are stored in the recording medium 2 or the nonvolatile memory 12 is stored. The storage position at which the background data are stored is written as the storage position information. If the background data are stored in the recording medium 2, the storage position is indicated as the offset from the beginning of the main data file, whereas the storage position is indicated as the offset from the beginning of the corresponding map data file itself if the background data are stored in the nonvolatile memory 12. The actual size of the background data is stored as the size information.
The background data are managed by further dividing the area contained in each mesh into n×m portions. Thus, there are n×m sets of background management information in correspondence to a given mesh. The background data are updated individually in units of the partitioned mesh portions (n×m mesh portions).
As explained earlier, a given level of map data does not necessarily include all the types of extension data. In addition, even when a given type of information can be added on, it may not always be contained in all the meshes. For instance, the network data are not contained in a mesh holding data constituted entirely of a body of water. For this reason, the types of extension data that can be added onto the corresponding mesh and the presence/absence of the individual types of extension data are written as the extension data identification information 163. The sets of extension data management information 164, the number of which matches the number of different types of extension data that can be added onto the mesh data, are provided in the order specified in the information.
Each set of extension data management information 164 contains management information for the corresponding type of extension data. The various types of extension data are each managed as are the background data. History information of the extension data is managed in correspondence to a specific type of extension data.
-Background Data-
While the background data (map display data) 112 may be managed in units of individual meshes, they are managed by further dividing the area contained in each mesh into n×m portions in the embodiment, so as to allow the data to be handled at a small screen with small memory, as in a portable telephone. The background data 112 are updated in units of single divided portions (in units of single mesh portions). The standardized size of the background data is set to 256×256 (a coordinate value assumes a value between 0 and 256) per mesh portion. A given mesh may contain, for instance, 4×4 mesh portions. In this case, the standardized size of the background data corresponding to one mesh is 1021×1021, since the coordinate value 255 in a given mesh portion equals the coordinate value 0 in the adjacent mesh portion and thus, the number of coordinate points is calculated to be 1021 by subtracting 3 from 256×4.
While the standardized size is smaller than the size of other map data, this does not pose any problem in actual use since the background data contained in only up to a single mesh portion can be displayed over a range containing approximately 320×260 points. In addition, since the number of bits used in correspondence to a single coordinate point can be reduced, the size of the overall data can be reduced as well.
Various background shapes are managed over up to 256 layers and are each drawn with the drawing attribute corresponding to a specific layer. While the background data in the existing navigation data are divided into approximately 16 different classes and the different classes of background data are each assigned with specific drawing attributes, there are not enough classes to indicate various types of background objects in a map of an urban area or the like with distinguishable colors. For this reason, the number of layers that are equivalent to the classes in the related art is increased to 256. The background objects are drawn in the order in which the corresponding background data were stored. In the case of the existing navigation data, data indicating the shapes of objects in a given type are all stored continuously. Thus, the shapes of objects of the same type that need to be drawn in a different order, e.g., a road running under an elevated express highway and a road running astride an express highway) cannot be displayed correctly, or an extra class needs to be created unnecessarily. By drawing various shapes of background objects in the order matching the order with which the corresponding data were stored, it is ensured that the number of layers does not need to increase.
In some existing navigation data, a single type of road shape data is used for both display and for map matching networking, so as to reduce the data volume by using the same road shape data for the display and the search. In the embodiment, the storage of road shape data used as the background data is switched for each level of data. An advantage of storing road shape data as background data lies in that when drawing a map, the map can be drawn through a single access without having to perform a plurality of accesses to acquire different types of data such as background data, road data and text data. In addition, since the road shapes only need to be indicated as background, their shapes and connections can be drastically simplified or exaggerated to make it possible to reduce the volume of the display data and improve the display speed.
-Locator Data-
The locator data express roads with links, nodes and link strings. A node may be an intersecting point or a special point specified on a road. A link is equivalent to a road connecting nodes, whereas a link string is a string of a plurality of links representing a single road. The locator road data, which are provided in the road map data at the lowermost level 0, are used when verifying the position of the subject vehicle, obtaining the route coordinates resulting from a route search, conducting a narrow urban street search and the like. The road data used as locator data hold information similar to the types of information held in the navigation data in the related art. Namely, roads sharing a common attribute are managed as a collection of road data which are managed in the form of link strings. The road attributes are divided into two primary groups, i.e., road attributes assigned to individual link strings and road attributes assigned to individual links or individual nodes.
The attributes assigned to individual link strings include road types, toll/toll-free designation, infrastructure object attributes and route calculation target flags and the like. The attributes assigned to links or nodes include link types, widths, intersecting link information, regulation information and interpolation point coordinate information. The number of standardized coordinate points in the locator data is 2048×2048. The standardized size of the locator data differs from that of the background data (1021×1021) since the locator data need to assure a higher degree of coordinate accuracy.
An explanation is now given on how the connections with the roads in an adjacent mesh are achieved when the locator data in a given mesh have been updated.
Link string data corresponding to a given link string in the locator data are constituted of a string of sets of data related to nodes present in the link string. The data related to each node include data indicating the positional coordinates of the node, the link number assigned to a link connecting with the node and the like. The standardized coordinate values are used to indicate the positional coordinates of the node.
The data related to each node contains the positional coordinates of the node and the link number assigned to the link connecting with the node along one direction. For instance, the positional coordinates of the node 174 and the link number of the link 175 connecting with the node 174 to the right are stored for the node 174. The positional coordinates of the node 176 and the link number of the link 173 connecting with the node 176 to the left are stored for the node 176.
If the mesh 171 and the mesh 172 contain data sharing the same history, the points at which they should be connected with each other can be specified by checking the link numbers assigned to the connecting links. However, the link number assigned to the link 175 may change due to an update of the data in the mesh 172. In such a case, the connecting points at the mesh boundary can no longer be identified with the link numbers.
In the embodiment, the connecting points are identified by conducting a search to ascertain whether or not a connecting point with the same positional coordinates is present at the adjacent mesh if data have been updated. Namely, meshes are connected by using standardized coordinate values of the connecting points. An adjacent mesh itself is identified by using the mesh position information or the like as in the related art.
It is to be noted that if the data in a mesh are updated without updating the data in an adjacent mesh following the construction of a new road, a road to connect to the new road may not be found in the data in the non-updated mesh. In such a case, the road is processed as a dead end in the data even when the road actually continues on into the non-updated mesh. Under these circumstances, it is more desirable to update the locator data for the adjacent mesh as well. Accordingly, an update request that the map data in the adjacent mesh be updated may be automatically transmitted if the map server 6 can be accessed via the Internet. Alternatively, a display or the like may be brought up so as to prompt the user to transmit a map data update request.
-Network (route calculation) Data-
The lowest level of data that contain the network data as extension data is level 1 (scaling factor 1/25,000), and is used for reference. The network data are also stored as extension data of data at a plurality of higher levels. As are the locator data, the network data, too, are prepared based upon the concept of links, nodes and link strings. The network data contain connection information indicating how nodes representing intersecting points connect with other nodes. Each node holds subject node information and adjacent node information on each adjacent node with which the subject node connects. As the subject node information, the positional coordinates of the subject node are stored, whereas information related to all the nodes that connect with the subject node is stored as the adjacent node information. As the node information of a connecting node, the node number assigned to the node and the link number assigned to a link connecting to the node are stored.
The range within which a single set of network data are contained as the same as the range containing the corresponding map data, and the standardized size of each mesh is 2048×2048.
The structure of the network data which greatly differs from that of the existing navigation data is the correlation of nodes and links in adjacent meshes and also among different levels. In the case of the existing navigation data, a node in a given mesh or at a given level is made to correlate to the same node in an adjacent mesh or at a different level by directly referencing the index number or the offset information. In contrast, data are updated in units of individual meshes and new and old data are utilized in combination in the embodiment. For this reason, the node/link correlation cannot be directly referenced by checking the index numbers or the offset information, unlike in the related art.
As long as history information for the network data in a mesh matches history information for the network data in an adjacent mesh or as long as history information for the network data in a higher-order mesh matches history information for the network data in a lower-order mesh, the node/link correlation can be referenced by using the index number or the like as in the related art. However, if the sets of history information do not match, the correlation cannot be referenced by using index numbers or the like. Accordingly, the coordinate values of the connecting points at the mesh boundaries are used as keys in the embodiment, as is done with the locator data. As a connecting point used to correlate different levels to each other, a node present both in a higher-order level mesh and in a lower-order level mesh, which is not necessarily on the mesh boundary, is selected.
When searching for a matching node in an adjacent mesh simply by using the coordinate values as a key, the set of coordinate values and the node will achieve a one-to-one match at the lowest-order (most detailed) level unless there are roads intersecting each other on the mesh boundary, since node coordinates are defined at the resolution of the standardized coordinates at the lowermost order level. For this reason, the matching node can always be searched even though it takes a considerable length of search time. However, the matching node cannot be accurately searched in higher-order level network data simply by using coordinate values as a key, since there is a possibility that a plurality of different nodes may exist at the same coordinates. Namely, when two nodes present in close proximity to each other, they are defined with different coordinate values at a lower-order level. However, the coordinate values may be rounded and, as a result, the two nodes may be indicated with the same coordinate values at a higher-order level. In such a case, the two nodes cannot be distinguished from each other and thus, an accurate search cannot be conducted.
For this reason, the coordinate values at the lowermost layer level, too, are used as a key, as well as the coordinate keys in the embodiment. As a result, even when there are a plurality of nodes with the same coordinate values at a higher level, the coordinate keys of the same nodes, which are used as sub keys, at the lowermost level are different and the matching node can be searched with accuracy. In addition, since there may be a plurality of nodes with the same coordinate values even at the lowermost level, a 4-bit extension coordinate value (within a range of 0 through 15) is attached to the coordinate values of each node at the lowermost layer.
With (Xh, Yh) representing the standardized coordinates of a node at a higher-order level, (X1, Y1) representing the standardized coordinates of the node at the lower-order level and α representing the extension coordinate value, the standardized coordinates of the node at a given higher-order level can be defined by the combination of (Xh, Yh), (X1, Y1) and (α).
Through the measures described above, data at different levels can be connected with a high degree of reliability as well as data in adjacent meshes, even when newer versions of data are used together with the original version of data. It is to be noted that corresponding meshes at different levels are identified by using level correspondence tables provided each in correspondence to a given level of data. In a level correspondence table, information that indicates a specific node at a lower-order level that corresponds to a node at the subject level also indicates the mesh containing the corresponding node. Thus, by using the level correspondence table and the definition of the standardized coordinates explained above, connecting points at different levels can be accurately matched. Even when the data in a given mesh at a lower-order level alone have been updated, the use of the level correspondence tables and the standardized coordinates allow any road that remains unchanged after the update to maintain the connection with the non-updated higher-order level data. In addition, while a newly added road or a road having undergone a change in shape in an updated mesh cannot connect with the non-updated higher-order level data, an erroneous connection of such a road, at least, can be averted.
The position of a mesh is normally indicated by the latitude and the longitude of the lower left corner of the mesh. Namely, each set of position information 129 in the full mesh management information holds position information corresponding to the latitude and longitude of the lower left corner of the subject mesh. In addition, the standardized coordinates in the mesh are indicated by setting the lower left corner of the mesh as the origin point. Accordingly, the standardized coordinates explained earlier indicate various positions in the map as two-dimensional coordinate values corresponding to specific latitudinal and longitudinal values based upon the mesh position information indicating the mesh position by its latitude and longitude. Such two-dimensional coordinate values, which correspond to latitudinal and longitudinal values, may be considered to be universal values that remain unaffected by differences among various navigation systems and standards. In other words, adjacent meshes and meshes at higher and lower levels are connected by using universal keys.
It is to be noted that the standardized coordinates of the node at a higher-order level may be instead defined so as to be indicated with the combination of (Xh, Yh) and (X1, Y1) or the combination of (Xh, Yh) and (α).
In addition, the standardized node coordinates (X1, Y1) at the lower-order level do not need to be the coordinates at the lowermost level. The coordinates at any appropriate lower level may be used as such. The extension coordinate α is a parameter other than the standardized coordinates and may be, for instance, height data indicating the height of the node. Alternatively, it may be time data (information) related to the data generation/update. Moreover, the extension coordinate a may be set by combining the height data and the time data. The data size of a may be greater than four bits, as well.
The standardized coordinates described above are defined by using a parameter such as the coordinates (X1, Y1) at another level or the height data (α), in addition to the two-dimensional coordinates (Xh, Yh) at the subject level. Since this parameter is used to attach PS information to the two-dimensional coordinates so as to indicate the connecting state between different levels in the embodiment, it is referred to as a level correspondence key in the description of the embodiment. It may be otherwise referred to as a 2.5 dimensional space key.
In the embodiment, the correspondence between nodes at different levels is indicated in the level correspondence tables each provided in correspondence to a given level. For this reason, the level correspondence keys of the various levels do not need to hold the standardized coordinates at all the lower levels. For instance, they may hold the standardized coordinates at the lowermost level alone. When the standardized node coordinates at level 0 are (X0, Y0), the standardized node coordinates at level 1 are (X1, Y1), the standardized node coordinates at level 2 are (X2, Y2) and the standardized node coordinates at level 3 are (X3, Y3), the level correspondence keys for the node at the individual levels are defined as follows. The level correspondence key at level 0 is defined as (X0, Y0), the level correspondence key at level 1 is defined by the combination of (X1, Y1) and (X0, Y0), the level correspondence key at level 2 is defined by the combination of (X2, Y2) and (X0, Y0) and the level correspondence key at level 3 is defined by the combination of (X3, Y3) and (X0, Y0).
-Guidance Data-
The guidance data that are included in the map data at the lowermost layer level 0 only are used when providing route guidance along the route resulting from a route search. As the guidance data, information indicating intersecting point names, information indicating road names, information indicating directional terms, directional guidance information, spot guidance information, information on landmarks in surrounding areas, information on road construction and the like is stored.
-Data Update with the Removable Memory-
As the power to the navigation system 1 is turned on, the program that executes the processing as shown in the flowchart presented in
In step S2, the update data in the removable medium 3 are referenced, the full mesh management information corresponding to the data in the recording medium 2 that need to be updated is read out from the recording medium 2 and the full mesh management information thus read out is written into the nonvolatile memory 12. In step S3, the full mesh management information recorded in the nonvolatile memory 12 is rewritten in conformance to the update data. In step S4, data of an area around the destination are readout based upon the full mesh management information recorded in the nonvolatile memory 12. In the previous explanation, the update data are written in the nonvolatile memory 12. However, in this example, the update data are simply read from the removable memory 3 by directly loading the removable memory 3. Non-updated map data are read from the recording medium 2.
If, on the other hand, it is decided in step S1 that there are no update data, the operation proceeds to step S5. In step S5, a decision is made as to whether or not there is a history of an update. The decision as to whether or not there is an update history is made by accessing the block management information 124 in the nonvolatile memory 12. If it is decided in step S5 that there is an update history, the operation proceeds to step S6. In step S6, the full mesh management information that has been sequentially rewritten to the current version is readout from the nonvolatile memory 12 by referencing the block management information 124. In step S7, the full mesh management information that is not stored in the nonvolatile memory 12 is read out from the recording medium 2 by referencing the block management information 124. In step S8, data of an area around the destination are read out as in step S4, based upon the full mesh management information read out from the nonvolatile memory 12 and the recording medium 2.
If it is decided in step S5 that there is no update history, the operation proceeds to step S9. In step S9, the full mesh management information is read out from the recording medium 2. Next, in step S10, data of an area around the destination are readout from the recording medium 2 based upon the full mesh management information read out from the recording medium 2.
In step S11, a route search is executed by using the map data that have been read. While only the data of an area around the destination are read in the flowchart presented in
-Data Update Through Communication with the Map Server-
As the power to the navigation system 1 is turned on, the program that executes the processing as shown in the flowchart presented in
In step S101 in
If, on the other hand, it is decided in step S101 that there is no update history, the operation proceeds to step S105. In step S105, the full mesh management information is read out from the recording medium 2. Next, in step S106, data of an area around the current position are read out from the recording medium 2 based upon the full mesh management information read out from the recording medium 2. Next, the operation proceeds to step S22 in
The data of the area around the destination are read in step S22 and subsequent steps in
If, on the other hand, it is decided in step S111 that the data of the area around the destination have never been updated, the operation proceeds to step S113. In step S113, the update data having been transmitted from the map server 6 are referenced, the full mesh management information corresponding to the data in the recording medium 2 that need to be updated is read out from the recording medium 2 and the full mesh management information thus read out is written into the nonvolatile memory 12. In step S114, the full mesh management information recorded in the nonvolatile memory 12 is rewritten in conformance to the update data. Subsequently, the operation proceeds to step S115.
In step S115, the full mesh management information that has been rewritten is read from the nonvolatile memory 12 into the memory 126. In step S116, the data of the area around the destination are read out based upon the full mesh management information read out from the nonvolatile memory 12. Then, the operation proceeds to step S26 in
If it is decided in step S23 in
-Route Search Executed by Using Level Correspondence Keys-
The network data at the lowermost layer level (with the most detail) are normally used in the vicinity of the current position and the destination in the route search. Accordingly, if the current position and the destination are close to each other, only the network data at the lowermost layer level are utilized. However, if the current position and the destination are set apart from each other, the network data at a higher layer level (on the wider range side) are used for the search of the intermediate route in order to reduce the length of time required for the route search. Accordingly, the network data at the lowermost layer level are used for the areas around the current position and the destination and the network data at the higher layer level are used to search for the intermediate route. Namely, the two layer route search processing or the three layer route search processing is executed.
If it is decided in step S33 that the one layer route search processing is to be executed, the operation proceeds to step S34. If it is decided that the two layer route search processing is to be executed, the operation proceeds to step S35. If it is decided that the three layer route search processing is to be executed, the operation proceeds to step S36.
In step S203, a decision is made as to whether or not the subject node is a connecting point. Adjacent meshes connect at a connecting point, and a point positioned at the mesh boundary is set as a connecting point in the one layer route search. The operation proceeds to step S207 if it is decided that the subject node is not a connecting point, whereas the operation proceeds to step S204 if the subject node is judged to be a connecting point and the adjacent node, too, is judged to be a connecting point. If the subject node is not a connecting point, all the adjacent nodes connecting with the subject node are contained within the same mesh. When the subject node is a connecting point, the adjacent node in the adjacent mesh, too, is a connecting point.
In step S204, the level correspondence keys of the subject node and the adjacent node are referenced. In step S205, a decision is made as to whether or not the level correspondence keys of the subject node and the adjacent node match. The operation proceeds to step S208 if they are judged to match, whereas the operation proceeds to step S206 if it is decided that they do not match. If the level correspondence keys of the subject node and the adjacent nodes match, it is assumed that the correct adjacent node has been identified, and accordingly, the subject node is connected with the node with the identical level correspondence key in the adjacent mesh.
In step S206, the subject node is processed as a dead-end point. Namely, if an adjacent node with a matching level correspondence key has not been found, it is concluded that the route is cut off at that point. It is to be noted that the processing in step S204 and step S205 has been explained by assuming that one connecting point is present at each adjacent mesh. However, there may be a plurality of connecting points on the mesh boundary. In such a case, it is necessary to determine through a search the exact connecting point in the adjacent mesh with which the subject node connects. Accordingly, the processing in steps S204 and S205 needs to be repeatedly executed for the plurality of connecting points in the adjacent mesh until the correct adjacent node is identified.
If it is decided in step S203 that the subject node is not a connecting point, the operation proceeds to step S207 to identify the adjacent node by referencing the standard pointer index, since the subject node and the adjacent node are both contained in the data corresponding to the same mesh. It is to be noted that processing for identifying the adjacent node by referencing the pointer index is simpler and can be executed faster than the processing for identifying the adjacent node by referencing the level correspondence keys.
In step S208, Dijkstra route search processing is executed by using the node information corresponding to the identified node, and then the operation proceeds to step S209. In step S209, a decision is made as to whether or not the entire route search processing has been completed, and if it is judged that the route search processing has not been completed yet, the operation returns to step S201. If it is judged that the route search processing has been completed, the one layer route search processing ends.
In step S221 in
In step S223, the level correspondence key of the node at the lower layer level in the level correspondence table is referenced. In step S224, a decision is made as to whether or not the level correspondence key of the node at the lower layer level in the level correspondence table matches the level correspondence key of the node in the lower layer mesh obtained through the search. The operation proceeds to step S227 if they are determined to match, whereas the operation proceeds to step S225 if it is decided that they do not match. In step S225, the subject node at the lower layer level is processed as a dead-end point.
If, on the other hand, it is decided in step S222 that the corresponding meshes at the higher layer level and the lower layer level share identical history information, the operation proceeds to step S226. In step S226, the higher layer level node is identified by referencing the node ID number (by executing standard processing). In step S228, the higher layer node corresponding to the lower layer node, which has been identified, is saved as a candidate. In step S228, a decision is made as to whether or not the processing has been completed, and if it is decided that the processing is to be executed continuously, the operation returns to step S221 to repeatedly execute the processing. If, on the other hand, it is judged that the processing is to end, the processing for connecting the nodes at the lower layer level and the higher layer level shown in
In step S213, route search processing is executed by using meshes at the higher layer level. Since the processing executed in step S213 is identical to the one layer route search processing in
As explained above, the following advantages are achieved by adopting the map data structure and the map data processing method achieved in the embodiment.
While an explanation is given above in reference to the embodiment on an example in which the control program executed by the control device 11 of the navigation system is stored in a ROM, the present invention is not limited to this example. The control program and an installation program used to install the control program may be provided in a recording medium such as a DVD. It is to be noted that the recording medium does not need to be a DVD, and instead, it may be any of various types of recording media including a CD ROM and magnetic tape.
In addition, these programs may be provided via a transmission medium such as a communication line, a typical example of which is the Internet. Namely, the programs may be converted to signals on a carrier wave through which a transmission medium is carried. When providing the programs in a recording medium or via the Internet, they can be provided to the navigation system in a configuration identical to that shown in
Furthermore, a car navigation system may be achieved by executing the control program described above on a personal computer. In such a case, the current position detection device 13, the input device 19 and the like should be connected to specific I/O ports or the like of the personal computer.
While an explanation is given above in reference to the embodiment on an example in which update data are provided from the removable memory 3, the present invention is not limited to this example. Instead, update data may be written into a CD ROM or a DVD ROM and then be provided by temporarily replacing the recording medium 2 with the CD ROM or the DVD ROM.
While an explanation is given above in reference to the embodiment on an example in which the initial map data are read from the recording medium 2, the present invention is not limited to this example. The initial map data may be received via the Internet 5, stored into the non-volatile memory 12 and then used and managed as update data by adopting the method described earlier. In addition, map data may be received via the Internet as they become needed, the received map data may be stored into the non-volatile memory 12 each time, and they may be updated and managed through the method described earlier whenever it becomes necessary to update them.
While an explanation is given above in reference to the embodiment on an example in which the route search is executed in the navigation processing, the present invention is not limited to this example. Any of various other types of navigation processing including map display and route guidance can be executed by using the map data described above.
While an explanation is given above in reference to the embodiment on an example in which the nonvolatile memory 12 is installed inside the navigation system 1, the present invention is not limited to this example and the nonvolatile memory 12 may instead be an external storage device which is connected through a cable or the like.
While an explanation is given above in reference to the embodiment on an example in which the background (for map display) data constitute basic data and the network data constitute extension data, the present invention is not limited to this example. For instance, the network data may instead be designated as basic data if map data (the network data and the like) are utilized in an application in which no map is displayed. More specifically, the network data may be used as basic data in an application in which a route search is executed and guidance for the vehicle is provided along the advancing direction with an arrow or the like alone, since no background data for map display) are required in such a navigation system. In this case, the network data are the data with the highest priority, and the network data alone may be updated in units of individual meshes. Namely, the map data with the highest priority that are commonly used in a plurality of specific model types should be used as the basic data in a given application.
While the invention has been particularly shown and described with respect to a preferred embodiment thereof by referring to the attached drawings, the present invention is not limited to these examples and it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit, scope and teaching of the invention.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2002-143111 | May 2002 | JP | national |
| 2002-143112 | May 2002 | JP | national |
This application is a division of U.S. application Ser. No. 10/514,423, filed May 16, 2003, which is a national stage application of PCT/JP03/06115, filed May 16, 2003, which claims priority under 35 U.S.C. §119 to Japanese Patent Application Nos. 2002-143111, filed May 17, 2002 and Japanese Patent Application No. 2002-143112, filed May 17, 2002, the entire disclosures of which are herein expressly incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6184823 | Smith et al. | Feb 2001 | B1 |
| 6650998 | Rutledge et al. | Nov 2003 | B1 |
| 6732124 | Koseki et al. | May 2004 | B1 |
| 6985929 | Wilson et al. | Jan 2006 | B1 |
| 20020007367 | Narahara | Jan 2002 | A1 |
| 20020059024 | Ogaki | May 2002 | A1 |
| 20020070981 | Kida | Jun 2002 | A1 |
| 20020091485 | Mikuriya et al. | Jul 2002 | A1 |
| 20020191867 | Le et al. | Dec 2002 | A1 |
| Number | Date | Country |
|---|---|---|
| 1 134 674 | Sep 2001 | EP |
| 1134674 | Sep 2001 | EP |
| 11-312295 | Nov 1999 | JP |
| 2001-056823 | Feb 2001 | JP |
| 2001-082965 | Mar 2001 | JP |
| 2001-110000 | Apr 2001 | JP |
| WO 0113069 | Feb 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20110307648 A1 | Dec 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10514423 | US | |
| Child | 13198753 | US |
