WO2004008073A1 - ナビゲーション方法、ナビゲーションシステムのための処理方法、地図データ管理装置、地図データ管理プログラム、及びコンピュータプログラム - Google Patents
ナビゲーション方法、ナビゲーションシステムのための処理方法、地図データ管理装置、地図データ管理プログラム、及びコンピュータプログラム Download PDFInfo
- Publication number
- WO2004008073A1 WO2004008073A1 PCT/JP2003/009088 JP0309088W WO2004008073A1 WO 2004008073 A1 WO2004008073 A1 WO 2004008073A1 JP 0309088 W JP0309088 W JP 0309088W WO 2004008073 A1 WO2004008073 A1 WO 2004008073A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- map
- update
- map data
- updated
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
- G08G1/0969—Systems involving transmission of navigation instructions to the vehicle having a display in the form of a map
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3885—Transmission of map data to client devices; Reception of map data by client devices
- G01C21/3896—Transmission of map data from central databases
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3804—Creation or updating of map data
- G01C21/3807—Creation or updating of map data characterised by the type of data
- G01C21/3815—Road data
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3863—Structures of map data
- G01C21/387—Organisation of map data, e.g. version management or database structures
- G01C21/3878—Hierarchical structures, e.g. layering
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3863—Structures of map data
- G01C21/387—Organisation of map data, e.g. version management or database structures
- G01C21/3881—Tile-based structures
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3885—Transmission of map data to client devices; Reception of map data by client devices
- G01C21/3889—Transmission of selected map data, e.g. depending on route
Definitions
- Map data overnight management device Map data management program
- Japanese patent application 2000 No. 1 4 3 1 11 1 (filed on May 17, 2000) Japanese patent application No. 2 2002 No. 1 4 3 1 1 2 (20 (Filed on May 17, 2012) Patent application in Japan No. 2008, No. 20887 (filed on July 17, 2002)
- the present invention relates to a navigation method, a processing method for a navigation system, a map data management device, a map data management program, and a computer program.
- map data such as a road map used in a navigation device has been provided on a recording medium such as a CD-ROM or a DVD-ROM. Also, map data is provided to a vehicle-mounted napige equipment using communication. Disclosure of the invention
- the present invention provides a navigation method for efficiently updating a part of large-capacity map data provided on a recording medium, a processing method for a navigation system, a map data overnight management device, and the like.
- the navigation method using the map data of the present invention is a method of updating the map data.
- the menu for narrowing down the area to be updated on the map is displayed, and this menu contains items for narrowing down based on the map and items for narrowing down based on the route.
- the update data based on the route is fetched, and processing is performed reflecting the fetched update data.
- Another navigation device that includes an output device including an input device and a display device, a processing device, and a recording medium, stores storage data including map data in a storage medium, and performs navigation using the storage data.
- the processing method for the system is as follows. To narrow down the map data to be updated, multiple items including roads are displayed, and when a road is selected from the displayed items, multiple roads are displayed, and from the displayed road When a specific road is selected, updated data related to the selected road is imported, and processing is performed reflecting the imported data.
- the present invention further includes an output device including an input device and a display device, a processing device, and a recording medium, stores storage data including map data in a storage medium, and uses the storage data to move from a current position to a destination.
- the processing method for the navigation system that displays the route information to reach is that a plurality of items including roads are displayed to narrow down the map data to be updated, and when a road is selected from the displayed items, A plurality of related roads are displayed. When a specific road is selected from the displayed roads, the update data relating to the selected road is fetched, and processing is performed reflecting the fetched data.
- the present invention further includes an output device including an input device and a display device, a processing device, and a recording medium, stores storage data including a map data in a storage medium, and uses the storage data to store a current position.
- the processing method for the navigation system that displays the route information from the route to the destination is as follows: multiple items including roads are displayed in order to narrow down the map data to be updated, and when a road is selected from the displayed items, , The number of roads related to the route and the presence / absence of data to be updated are displayed. Select a specific road from the displayed roads. Then, the update data related to the selected road is fetched, and processing is performed reflecting the fetched data.
- Another navigation method using map data is to display a menu for narrowing down an area to be updated in order to update the map data.
- update data is captured based on the specified genre, and the captured update data is inverted. Process it.
- the map data management device in which a navigation system that uses map data stored on a fixed recording medium and updated map data obtained by download mixedly is connected via a communication network, has a large memory capacity.
- a map data management means that manages a mesh that has history information that is the key to discriminating between new and old data in units of individual data as map data management units, and a navigation system
- the map data management program used in the navigation system that uses the map data stored on the fixed recording medium of the present invention and the updated map data obtained by downloading from the map data management device in a mixed manner is prepared in advance.
- a map data management program used in a navigation system that uses a mixture of map data stored in another fixed recording medium of the present invention and updated map data downloaded from a map data management device includes: A step of performing a route search and displaying the route information from the current position or the departure point to the destination on a map, and at least one of the updated genre menus prepared in advance after the route information is determined. Prompts you to make a selection, and based on the selection, the route displayed on the map Reflecting the updated map data in the information.
- a navigation system that uses a mixture of the map data stored in another fixed recording medium of the present invention and the updated map data obtained by downloading is connected to a map data management device connected via a communication network.
- the map data management program used is managed by fixing it to the minimum size allowed by the memory capacity, and handles the reference mesh that has history information that is the key to discriminating between old and new in individual data units as the map data management unit. And a step of searching for an area to which the corresponding map data belongs in reference mesh units based on a data update request obtained from the navigation system, and providing updated data along with history information.
- a region and a road are displayed as items, and a region is selected. If a road is selected, a prefecture or city for narrowing down the area is displayed, and further selecting from the displayed contents to narrow down the area to be updated is displayed. If a road is selected, a plurality of roads are displayed and displayed. It further comprises a step of narrowing down the area to be updated by further narrowing down the roads that have been narrowed down, and a step of taking in updated data relating to the narrowed down area and reflecting the updated data in the processing.
- a computer program used in a navigation system using other map data of the present invention includes a step of displaying route information from a current position to a destination; a step of displaying presence / absence of update information related to the route information. And a step of performing processing based on the data fetched based on the update instruction.
- the computer program used in the navigation system using other map data according to the present invention includes a step of displaying route information from the current position to the destination, and a step of displaying the presence or absence of update information related to the route information on a mesh basis. And a step for performing processing based on the data taken in based on the update instruction.
- FIG. 1 is a diagram for explaining transmission and reception of map data having a structure of map data according to the present invention.
- FIG. 2 is a block diagram of an in-vehicle navigation device.
- Figure 3 is a conceptual diagram illustrating the relationship between map data levels, blocks, and meshes.
- FIG. 4 is a diagram showing a data structure of one mesh of FIG.
- FIG. 5 is a diagram for explaining how map data is managed in the navigation device.
- FIG. 6 is a diagram for explaining the configuration of a main data file.
- FIG. 7 is a diagram showing a configuration of the management information in the mesh.
- FIG. 8 is a diagram illustrating a case where one road exists over an adjacent mesh.
- FIG. 9 is a flowchart for updating the map data in the removable memory, reading data near the destination, and performing a route search.
- FIG. 10 is a flowchart for reading and updating data near the destination from the map server via the Internet, reading data near the current location and near the destination, and performing a route search.
- FIG. 11 is a flowchart of the initialization process in step S21 of FIG.
- FIG. 12 is a flowchart of the update process in step S24 of FIG.
- FIG. 13 is a block diagram showing the internal configuration of the navigation device by developing its functions.
- FIG. 14 is a block diagram showing the internal configuration of the map server in terms of functions.
- FIG. 15 is a flowchart for explaining the operation of the present embodiment.
- FIG. 16 is a flowchart illustrating the operation of the present embodiment.
- FIG. 17 is a flowchart illustrating the operation of the present embodiment.
- FIG. 18 is a screen transition diagram for explaining the operation of the present embodiment.
- FIG. 19 is a screen transition diagram for explaining the operation of the present embodiment (select update data from a display map).
- FIG. 20 is a screen transition diagram for explaining the operation of the present embodiment (select update data—evening from area).
- FIG. 21 is a screen transition diagram for explaining the operation of the present embodiment (select update data from around the route).
- FIG. 22 is a screen transition diagram for explaining the operation of the present embodiment (selecting update data from around the search route).
- FIG. 23 is a screen transition diagram for explaining the operation of the present embodiment (select update data from guidance search information).
- FIG. 24 is a screen transition diagram for explaining the operation of the present embodiment (select update data from genre).
- FIG. 1 is a diagram for explaining transmission and reception of map data having a map data structure according to the present embodiment.
- the in-vehicle navigation device 1 reads map data, management information, guidance search data, and the like from a recording medium 2 such as a CD-ROM or a DVD-ROM.
- Update data such as map data is provided from the removable memory 3.
- the removable memory 3 is a replaceable recording medium on which update data and the like are recorded for updating a part of the map data.
- the navigation device 1 can also be connected to a communication device 4 such as a mobile phone.
- the navigation device 1 can be connected to the Internet 5 via the communication device 4, and can be connected to the map server 6 via the Internet 5.
- the map server 6 retains from the old map data to the latest map data in the map database 7, and also retains from the old guide search data to the latest guide search data in the guide search database 8. Therefore, the map server 6 can provide the navigation device 1 with the update data for updating a part of the map data via the Internet 5.
- the guidance search data is data that stores attribute information such as position information such as POI, type, and name.
- the navigation device 1 has a control device 11 and a nonvolatile memory 12.
- the control device 11 includes a microprocessor and its peripheral circuits.
- the non-volatile memory 12 is a non-volatile memory such as a hard disk and a flash memory provided inside the navigation device 1.
- the nonvolatile memory 12 may be any storage device as long as the written data is not erased even when the navigation device 1 is turned off.
- the removable memory 3 may be referred to as a fixed medium. Since the map database 7 and the guidance search database 8 have both new and old map data and guidance search data, they are based on mother data.
- the map server 6 uses the map data overnight base 7 and the guidance search database 8 to store the initial (pre-update) map data—a recording medium 2 containing evenings, etc., and a removable memory 3 containing update data. Can be prepared.
- FIG. 2 is a block diagram of the in-vehicle navigation device 1.
- the navigation device 1 includes a control device 11, a non-volatile memory 12, a current location detection device 13, a DVD drive device 14, a memory 15, a communication interface 16, and a removable memory reading device. It has a device 17, a monitor 18, and an input device 19.
- the current position detection device 13 is a current position detection device that detects the current position of the vehicle, such as a direction sensor that detects the direction of travel of the vehicle, a vehicle speed sensor that detects the vehicle speed, and a GPS signal from a GPS (G1 obal Positioning System) satellite. It consists of a GPS sensor.
- the DVD drive device 14 is a device that mounts the recording medium 2 and reads map data and the like. In the present embodiment, the recording medium 2 is DVD_ROM. Note that a CD-ROM or another recording medium may be used.
- the memory 15 is a memory that stores vehicle position information and the like detected by the current position detection device 13 and stores node information and link information on the recommended route calculated by the control device 11. Further, it stores all mesh management information described later.
- the memory 15 is a working area of the control device 11.
- the communication interface 16 is an interface for connecting the communication device 4. Use of a mobile phone and connection to the Internet are possible via the communication interface 16.
- the removable memory reading device 17 is a device capable of loading the removable bubble memory 3 and reading data from the removable bubble memory 3.
- the monitor 18 is a display device that displays a map, a recommended route, and various information.
- the monitor 18 may be provided integrally as a part of the navigation device main body, or may be provided separately as a housing. Furthermore, only monitor 18 is used for the navigation device body. It may be connected with a cable or the like and provided at a separate location.
- the input device 19 is an input device for inputting a destination or the like of the vehicle when searching for a route. It may be a remote control, or may be composed of a touch panel provided on the monitor 18 screen.
- the control device 11 uses the current position information of the vehicle detected by the current position detection device 13 and the map data stored in the recording medium 2 or the non-volatile memory 12 to display a road map, search for a route, Various navigation processes such as guidance are performed.
- Various processing programs executed by the control device 11 are incorporated in a ROM (not shown) provided inside the control device 11.
- Map data Evening is information about the map, including background (for map display), data for night and location, data for network (for route search), guidance data (intersection name ⁇ road name ⁇ direction name ⁇ direction guide) Facility information).
- Background data is data for displaying the background of roads and road maps.
- the locator data is used for identifying the current location of the vehicle and for map matching.
- Network data is route search data that includes branch information that is not directly related to the road shape, and is mainly used when calculating recommended routes (route search).
- the guidance route is a schedule consisting of intersection names and the like, and is used to guide a driver or the like to a recommended route based on the calculated recommended route.
- the map data of the present embodiment is managed based on the concept of level, block, and mesh.
- map data is divided into seven levels having different scales, the level of the most detailed scale is set to level 0, and the level of the widest area map is set to level 6.
- Each level contains map data with different scales, but the target area is the same for each level. In other words, if the whole of Japan is the target, the map data for all levels of Japan is different for each level.
- the scale is 1,620,0, at level 3, the scale is 1,400,000, at level 4, the scale is 1,600,000, at level 6, the scale is 1/1. It has a map data of 280,000,000 throughout Japan. That is, there are seven sets of map data corresponding to levels 0-6.
- FIG. 3 is a conceptual diagram illustrating the relationship between map data levels, blocks, and meshes. Representatively, levels 3 and 4 are shown.
- Reference numeral 101 denotes an area to be covered by the map. Assuming that map data for the whole of Japan is handled, area 101 is a range that includes the whole of Japan. Both Level 3 and Level 4 cover the same area.
- One block 102 is divided into a plurality of meshes 103 and managed. In the present embodiment, management is performed using m ⁇ n meshes. The number of divided meshes between the blocks 102 is the same number m X n at the same level.
- One block 104 is divided into a plurality of meshes 105 and managed.
- pXQ meshes are managed.
- the number of divided meshes between each block 104 is the same number p X q at the same level.
- Level 4 which handles a wide area map with a smaller scale (larger denominator value) and Level 3 which handles a more detailed map with a larger scale (lower denominator value) compared to Level 4.
- Level 4 which handles a wide area map with a smaller scale (larger denominator value)
- Level 3 which handles a more detailed map with a larger scale (lower denominator value) compared to Level 4.
- the data amount is different. That is, appropriate division is performed according to the data amount handled at each level.
- the size of one block and the size of one message are the same. Note that the number of divided blocks at each level in FIG. 3 is one example, and is not necessarily limited to this number.
- a mesh may be called a parcel
- a block may be called a first division unit
- a mesh may be called a second division unit.
- These blocks and meshes can be called geographically divided units.
- FIG. 4 is a diagram showing the configuration of all mesh management information 18 1 and mesh data 18 2 for managing all meshes in a block.
- the mesh data 182 is map data provided corresponding to the mesh 103 or the mesh 105 described above.
- All mesh management information 1 8 1 is the management information of all mesh data contained in the block. Information and is provided for each block.
- the total number of meshes 18 3 of the total mesh management information 18 1 in FIG. 4 is the total number of meshes included in the block.
- the lower left reference position code 1884 contains position information on the latitude and longitude of the lower left position of the block.
- the number of meshes in the longitudinal direction 1 85 is the number of meshes arranged in the east-west longitude direction. In the example of level 3 in Fig. 3, m is entered.
- the number of meshes in the latitudinal direction 1 86 is the number of meshes arranged in the north-south latitude direction. In the example of level 3 in Fig. 3, n is entered.
- Each mesh management information 187 is information for managing each mesh data 182, and is provided for the number of meshes in the block.
- Each mesh data 18 2 contains the management information in the mesh 11 1, background (for map display) data 1 1 2, location data 1 1 3, network (for route calculation) data 1 It consists of 14 and guidance data 1 15.
- Management information in mesh 1 1 1 and background (for map display) Data 1 1 and 2 are used as basic data, locator data 1 1 3, network data 1 1 4 and guidance data 1 1 5 are extended data. I do.
- Basic data is data that exists at all levels.
- Extended data is data that exists at a unique level. For example, network data exists at levels 1, 2, 3, and 4, and voice data and guided data exist at level 0.
- address calculation data, image data, VICS data, building attribute data, peripheral search data, and the like may be further provided as extension data.
- the data size of the basic data is managed by setting an upper limit. For example, assume that the upper limit data size is 32 KB. If the basic data exceeds the upper limit due to the update of map data, the excess data is managed as extended data. For example, suppose that the initial basic data is 20 KB, the extended data is 10 KB, and the mesh data is 18 2, and only the basic data is updated to 40 KB. As the updated data, the basic data is edited to fit within 32 KB, and the basic data of 8 KB exceeding 32 KB is managed as extended data. Therefore, the size of the extended data is 18 KB, and the size of the mesh data 182 is 30 KB to 50 KB.
- the upper limit of the basic data 32 K Since it does not exceed B, the increasing basic data of 10 KB is added as it is as the basic data. As a result, the updated basic data is 30 KB, the extended data is 10 KB, and the size of the mesh data 18 2 is reduced from 30 KB to 40 KB.
- the upper limit is set for the data size of basic data for the following reasons. Normally, the navigation device 1 may be used for many years without adding memory or the like. For this reason, it is desirable that the map data is also fixed in size according to the performance of the navigation device 1 used for many years. However, it is likely that the amount of map data will increase due to the progress of building shape data maintenance, the advancement of detailed topographical data, and the development of actual residential land. Therefore, the map data structure of the present embodiment enables updating of map data in units of meshes.
- the updated map data needs to have a structure that can be commonly used by both the old navigation device and the new navigation device.
- the basic data size is edited so that the data size that can be handled by the old navigation device is maintained, and data exceeding the basic data size is recorded in the extended data. Also, data for new functions that are not used in the old model should be recorded in the extension data.
- the map data structure of the present embodiment can be used in common for devices with low processing capability to devices with high processing capability.
- the basic data is the map data that is used in common by devices with low processing capability and devices with high processing capability.
- the upper limit size of this basic data is set to a data size that matches the memory size of the device with the lowest processing capacity.
- the map data of the present embodiment can be used in common for a device having a low processing capability to a device having a high processing capability. As a result, management of map data can be made more efficient and cost can be reduced.
- the basic data prepared from the beginning can be processed from devices with low processing capacity. Since it is commonly used for high-power devices, it can be said that it is a type of data with high priority.
- the basic data that is updated and increased includes background data that displays a map that is more detailed than the basic data prepared from the beginning, and low-priority background data that does not hinder display on older models. I can say.
- the basic data is updated and increased, it can be said that if the basic data can be managed within the upper limit described above, it has the same priority as the basic data prepared from the beginning. .
- the upper limit of the data size of the mesh data 182 is not specified.
- the upper limit of the data size may be specified for the mesh data 18 due to the memory in the navigation device 1.
- the upper limit of Meshudde 18 2 is 128 KB.
- the upper limit value of 32 KB of the above basic data and the upper limit value of 128 KB of the mesh data may be other values.
- An appropriate value may be determined in consideration of the performance of the navigation device when initially defining the map data and the expected performance improvement in the future.
- FIG. 5 is a diagram for explaining how the navigation device 1 manages map data.
- the navigation device 1 reads all the mesh management information and map data from the recording medium 2 and reads updated map data from the map server 6 via the removable memory 3 or the Internet 5 to read the latest map data. Data can be used.
- the data was read only from a recording medium such as CD-ROM or DV-ROM.
- the navigation device of the present embodiment uses the map data in the recording medium 2 and the updated map data in a mixed manner. Therefore, the navigation device has the nonvolatile memory 12 which is a readable / writable medium.
- the nonvolatile memory 12 is composed of a nonvolatile memory such as a hard disk or a flash memory, and retains data even when the power of the navigation device is turned off.
- the non-volatile memory 12 may be called a cache medium 12.
- the nonvolatile memory 12 has block management information 124.
- the block management information 124 has identification information indicating whether all the mesh management information of the block is on the recording medium 2 or the non-volatile memory 12.
- the initial value is All the mesh management information is set as being on the recording medium 2.
- all the mesh management information 1 25 of the block having the updated mesh is created in the non-volatile memory 12, and the corresponding block is It sets that all the mesh management information is on the nonvolatile memory 12.
- the program can determine whether all the mesh management information is on the recording medium 2 or the non-volatile memory 12 by first referring to the block management information 124.
- Reference numeral 126 denotes a memory in the memory 15 of the navigation device, which is an area for storing all mesh management information. Hereinafter, it is referred to as memory 1 26.
- the program After determining whether all the mesh management information is on the recording medium 2 or the non-volatile memory 12, the program reads all the mesh management information from the relevant medium and stores it in the memory 126.
- the entire mesh management information 127 read into the memory 126 has mesh management information from mesh 1 to mesh n.
- the mesh management information 128 has data of location information 129, storage location 130, offset 131, and size 1332.
- the position information 129 is position information expressed by the latitude and longitude of the mesh
- the storage location 130 is data indicating whether the data is in the recording medium 2 or the nonvolatile memory 12.
- the offset 13 1 is data indicating a position on the medium (the recording medium 2 or the nonvolatile memory 12)
- the size 13 2 is data indicating the size of the map data.
- the map data in mesh units is updated in the removable memory 3
- the map data of the corresponding mesh is read into the non-volatile memory 12 and stored as the map data 13. Therefore, based on the contents of the storage location 130, the map data that has not been updated can access the recording medium 2, and the updated map data can access the nonvolatile memory 12.
- FIG. 6 is a diagram illustrating the configuration of the main data file.
- the main data file contains all management information 151, stored data information 152, level management information 153, block management information 1554, and all mesh management information 1555. Map data 1 5 And 6.
- All management information 15 1 has information on the entire data such as format version 'revision, data version * revision, media identification information, creation date, creator, cover area, etc. .
- the storage data information 152 describes the type and storage location of the data stored in the recording medium 2.
- the level management information 153 includes information on the hierarchical structure (level structure) of the map data stored in the recording medium 2, the type of extension data assigned to each level, and the storage position of the block management information. Having. When the map data is updated, the level management information 15 3 is copied to the non-volatile memory 12 to change the storage location (the recording medium 2 or the non-volatile memory 12) of the pro- cess management information. To use.
- the block management information 154 has management information of all mesh management information, such as division information of all mesh management information at each level, a storage location and a storage location of all mesh management information, and the like.
- the recording medium 2 is mounted on the DVD drive 14, it is copied to the nonvolatile memory 12 and used.
- the storage locations of all the mesh management information are all set in the recording medium 2 as initial values.
- Block management information 154 is created for each level.
- the entire mesh management information 155 is stored for each level block unit. For example, in FIG. 6, at level 0, there are m blocks, and there are m pieces of all mesh management information 155. The same applies to level 1 to level 6.
- the all-mesh management information 155 includes the storage location, location, size, and history information of all the meshes existing in one block.
- the map data 156 is equivalent to one night in mesh units.
- the map data 156 is stored for the total number of meshes of all blocks and all blocks stored in the recording medium 2.
- the structure of map data in mesh units is as shown in Fig.4. Since the update cycle is different for map data in mesh units, management information and updated data are managed in the nonvolatile memory 12, and data on the recording medium 2 is used for data that has not been updated. For example, background data is frequently updated with shapes, characters, etc., but updates of other extended data are not so frequently. Therefore, storing the updated data in the nonvolatile memory 12 has the capacity of the nonvolatile memory 12 better. Can be used for effect. Since the basic and extended data on the map data are managed individually, the management information section in the mesh manages the history information, storage location, storage location, and size of each data.
- the non-volatile memory 12 has block management information 124, all mesh management information 125, and map data 133, and further stores stored data (not shown). ) And level management information (not shown). Data is stored in a file format, and the stored data information and level management information are stored as a main management file (not shown).
- the block management information 124 is stored as a block management file, the entire mesh management information 125 is stored as an all mesh management information file, and the map data 133 is stored as a map data file.
- the main management file (not shown) stores the storage data information copied from the recording medium 2 and the level management information.
- the stored data information is stored in the non-volatile memory 12 when data other than the data in mesh units (for example, guidance search data) in the storage medium 2 is updated and stored in the nonvolatile memory 12. Created by copying the stored data information in the main data file. Each time update data of data other than mesh unit data is stored in the nonvolatile memory 12, the storage location of the corresponding management information is changed from the recording medium 2 to the nonvolatile memory 12.
- the stored data information holds the media identification information, and the correspondence with the recording medium 2 on which the cache information is based is aimed. At the time of startup, this information is compared with the media identification information in the recording medium 2, and if they match, there is no problem. However, if this information is different (another recording medium is inserted), the storage location, position, and size managed by each information on the non-volatile memory 12 will be inconsistent with the recording medium 2. Therefore, the update data on the nonvolatile memory 1 2 cannot be used. When such a situation occurs, navigation is performed using only the data in the recording medium 2.
- the level management information is copied from the level management information in the recording medium 2.
- Created. Store map data in nonvolatile memory 1 2
- the storage location of the block management information of the corresponding level is changed from the recording medium 2 to the non-volatile memory 12 every time. At this time, the position information and size of the block management information are also updated to the values in the nonvolatile memory 12.
- the block management file is created by copying the block management information 154 of each level in the recording medium 2 to the non-volatile memory 12 when the recording medium 2 is mounted on the DVD drive device 14.
- the storage location of all the mesh management information of each block is set as recording medium 2 as an initial value.
- the map data is updated and stored in the non-volatile memory 12
- the block management information at the level corresponding to the updated map data is updated.
- the storage location of all the mesh management information corresponding to the map data to be updated is changed from the recording medium 2 to the nonvolatile memory 12.
- the position information and the size are also changed to the values in the nonvolatile memory 12.
- the block management file is created for each level.
- the file name at this time shall be created using the level as a key. As a result, it is not necessary to describe the block management file name, and the size of the level management information can be reduced.
- the all-mesh management information file stores all the mesh management information of the block corresponding to the map data in the recording medium 2. Created by copying. The storage location of the map data is changed from the recording medium 2 to the nonvolatile memory 12. At this time, the position information and size of the map data are also updated to the values in the nonvolatile memory 12. Thereafter, when the mesh in the block is further updated, all the mesh management information files of the corresponding block already in the nonvolatile memory 12 are updated. All mesh management information files are created in block units. The file name at this time shall be created using the level and block management information as a key. As a result, it is not necessary to describe all the mesh management information file names, and the size of the block management information can be reduced.
- the map data file updates the map data and stores it in the nonvolatile memory 12 Create at the time.
- the unit of creation is the mesh unit. All map mesh management information corresponding to the updated map data is created by copying the data in recording medium 2 and only the storage location, storage location, and size of the actually updated basic / extended data are stored in nonvolatile memory 1 2 Update to the value in. For basic / extended data that has not been updated, refer to the data in recording medium 2.
- Map data files are created in mesh units. The file name at this time shall be created using the level, block management information, and all figure mesh management information as one key. This eliminates the need to describe the file name of the map data and saves the figure management information and block management information size.
- the mesh data is management information in the mesh 1 1 1, background (for map display) data 1 1 2, locator data 1 1 3, network (for route calculation) data 1 1 4, guidance data 1 1 5 Consists of The in-mesh management information 1 1 1 and the background (for map display) data 1 1 2 are used as basic data, and the locator data 1 1 3, network data 1 1 4, and guidance data 1 1 5 are used as extension data.
- Basic data is data that exists at all levels.
- Extended data is data that exists only at a specific level. For example, network data exists only at levels 1, 2, 3, and 4, while location data and guidance data only exist at level 0.
- address calculation data, field image data, VICS data, building attribute data, peripheral search data, and the like may be provided.
- the map data consists of the management information in the mesh 1 1 1 and the basic data of the background 1 (for map display) 1 1 2 —Consists of multiple extended data of 1 1 4 and 1 1 5
- the individual data (frames) that make up the map data are described below.
- the in-mesh management information 1 1 1 describes information unique to the map data divided by the mesh, and information such as the stored background, storage location of extended data, position, and size.
- FIG. 7 is a diagram showing the configuration of the management information 1 11 in the mesh.
- In-mesh management information 1 1 1 is mesh information 1 61, background management information 1 62, extended data identification information Information 16 3 and extended data management information 16 4.
- the mesh information 161 stores basic information such as the size of the management information in the mesh and the actual size information in the vertical and horizontal directions of the mesh.
- Background management information 16 2 stores management information on the background data (map display data) of this mesh. Specifically, history information, storage location, storage location, offset, and size are stored.
- the history information stores, for example, the management number of the update information, and the larger the value, the more recent the data.
- the storage location stores an identification flag indicating which of the recording medium 2 and the non-volatile memory 12 stores data.
- the storage location describes the storage location of the background data. In the case of the recording medium 2, the offset is from the beginning of the main data file, and in the case of the nonvolatile memory 12, the offset is from the beginning of the map data file.
- the size stores the actual size of the background data.
- the background data is managed by further dividing the area of one mesh into n ⁇ m. Therefore, there are n ⁇ m pieces of the background management information. Updating of the background data is performed in units of the mesh divided into n ⁇ m.
- the extended data identification information 163 describes the type of extended data that can be assigned to the mesh and the state of the assignment.
- the extended data management information 164 is arranged in the order specified by this information for the number of extension data that can be added.
- the extended data management information 164 stores management information of each extended data.
- the content of the management is the same as that of the background.
- the history information of the extended data is managed in units of extended data.
- the background data (map display data) 1 1 and 2 may be managed in units of meshes, but in the present embodiment, the area of one mesh is further managed by being divided into n ⁇ m. This is because data can be handled on a small screen or memory like a mobile phone.
- the background data is updated for each unit (divided mesh).
- the normalized size of the background is 2 5 6 x 2 per mesh 5 6 (coordinate values are 0 to 255).
- the normalized size is smaller than other map data, if the background is assumed to be drawn, there is no practical problem because only a maximum of one divided mesh is displayed in an area of about 320 ⁇ 260. In addition, since the number of bits used for one coordinate can be reduced, the size of the entire data can be reduced.
- the background shape is managed with a maximum of 256 layers, and is drawn with the drawing attribute for each layer.
- the background data is divided into about 16 classes, and the drawing attributes are assigned.However, if there are many types of backgrounds such as city maps, the classes are insufficient, and the colors cannot be classified properly. . For this reason, the number of layers corresponding to the existing classes will be increased to 256.
- the drawing order is the data storage order. In existing navigation data, all shapes of the same type are stored consecutively. For this reason, shapes of the same type in different drawing order (such as a road under a highway and a road that crosses a highway) cannot be displayed correctly, or unnecessary classes are generated. By setting the shape drawing order to the data storage order, it is possible to suppress an increase in layers.
- some of the data share the road shape for display and the road shape for map matching networks. This is because the amount of data can be reduced by using road shapes for display and search.
- storage of the road shape as background data is switched for each level.
- the merit of storing the road shape as the background shape is that the map can be drawn with one access without accessing multiple data groups such as background, road, and characters when drawing the map. Also, since the road can be used as the background, drastic deformation and connection are possible, so that the amount of display data can be reduced and the display speed can be improved.
- roads are represented by the concept of links, nodes, and link strings.
- a node refers to an intersection or a specially designated point on a road.
- a link corresponds to a road between nodes, and a link string represents one road by a plurality of links.
- Locator way The road data exists at the lowest level 0 of the road map, and is used for confirming the position of the vehicle, acquiring the route coordinates of the search result, and searching for narrow streets.
- the structure of the road data as the location for location overnight stores the same information as the existing navigation data.
- roads with the same attribute are managed as a set of road data managed in the form of link strings.
- Road attributes can be broadly classified into those that are assigned to link strings and those that are assigned to links or nodes.
- Attributes to be assigned to the link string include road type, toll / free classification, infrastructure target attribute, route calculation target flag, and the like. Attributes assigned to a link or node include link type, width, cross link information, regulation information, and interpolated coordinate information.
- the normalized coordinates of the locator data are assumed to be 2048 x 2048. Location-Since the evening image requires coordinate accuracy, it should be a normalized image with a different normalized size from the background image (10 2 1 X 10 2 1).
- This section describes how to connect roads to adjacent meshes when locator data is updated on a mesh basis.
- the link sequence data of the location location data is a data sequence of the nodes existing in the link sequence.
- data such as the position coordinates of the node and the link number connected to the node are entered.
- the position coordinates of the node use normalized coordinate values.
- FIG. 8 is a diagram illustrating a case where one road exists over an adjacent mesh.
- Mesh 17 1 and mesh 17 2 are adjacent, and one road represented by link 17 3 and link 17 5 exists across mesh 17 1 and mesh 17 2.
- a connection point is set on the road located at the boundary of the mesh, and it is used as a node.
- a node 174 is provided as a node of the connection point
- a node 176 is provided as a node of the connection point.
- the node data stores the position number of the node and the link number connected in one direction.
- the node 174 stores the position coordinates of the node 174 and the link number of the link 175 connected rightward.
- the node 176 stores the position coordinates of the node 176 and the link number of the link 173 connected to the left. If mesh 1 7 1 and mesh 1 7 2 have the same history, connect The connection destination can be specified by the link number. However, the data of the mesh 17 2 is updated, and the link number of the link 1 75 may change. In such a case, the connection destination at the mesh boundary cannot be specified by the link number.
- connection destination when the data is updated, the connection destination is specified by searching whether or not there is a connection point having the same position coordinate in an adjacent mesh. That is, connection between meshes is performed using the normalized coordinate values of the connection points.
- the adjacent mesh itself is specified using the mesh position information and the like as before.
- Network data is stored as extension data at a plurality of higher levels, with level 1 (scale factor 1 250 000) serving as a reference as the lowest layer.
- Network data is represented using the concept of links, nodes, and link strings, similar to location data.
- Network data, c each node is representative of the connection information of the nodes representing intersection has a neighbor node information connected to the own node information.
- the own node information stores the position coordinates of the own node, and the adjacent node information stores information of all nodes connected to the own node.
- the node information of the connected node stores the node number of the node and the link number connected to the node.
- the area of one network data is the same as the area of the corresponding map data, and the normalized size of one mesh is 24048 x 248.
- the major difference between the existing network structure and the existing navigation data is the association of nodes and links between adjacent meshes and levels.
- the association of the same node between adjacent levels is Direct reference is made using index numbers or offsets.
- data is updated on a mesh basis, and old and new data are mixed and used. For this reason, direct reference by the conventional index number or offset is not possible.
- connection points for associating the levels are not necessarily at the mesh boundary, but nodes that exist at both the upper level and the lower level are selected.
- the coordinate value of the lowest level is also set to be the same, so that even if the node is a duplicate node at a higher level, the maximum value of the secondary key is not obtained. Since the coordinate keys at the lower level are different, it is possible to search for the other party correctly, and at the lowest level, duplicate nodes can be generated. 4 bits in (Range 0-1 5) adding extensions coordinates.
- the normalized upper-level node normalized coordinates are (X h, Y h)
- the lower-level node normalized coordinates are (XI, Y 1)
- the extended coordinates are ⁇
- the coordinates can be defined as a combination of (Xh, Yh), (XI, Y1) and ( ⁇ ).
- the corresponding mesh between levels is specified by providing an interlevel correspondence table for each level.
- the interlevel correspondence table contains information on which node of the lower level corresponds to which node of the lower level mesh.
- connection points between the levels are associated using the inter-level correspondence table and the definition of the normalized coordinates described above.
- this inter-level correspondence table and the above-described normalized coordinates even if only a part of the lower level meshes are updated, the roads that have not changed even after the update are not updated with the upper level data that has not been updated. Connection can be maintained. In addition, new roads and roads whose shape has changed in the updated mesh cannot be connected to unupdated upper-level data, but incorrect connection can be avoided.
- the position of a mesh is represented by the latitude and longitude of the lower left corner of the mesh. That is, the position information corresponding to the latitude and longitude of the lower left corner of the mesh is stored in the position information 127 of the all mesh management information.
- the origin of the normalized coordinates of the mesh is the lower left corner of the mesh. Therefore, in the above-described normalized target, the position in the map is represented by two-dimensional coordinate values corresponding to the latitude and longitude in consideration of the position information of the mesh based on the latitude. Since these two-dimensional coordinate values correspond to latitude and longitude, they can be said to be universal values that are not affected by different navigation devices or different standards. In other words, connections between adjacent meshes and upper and lower meshes are made using universal keys.
- the normalized coordinates of the upper-level node are not limited to the above definition, but may be a combination of (X h, Y h) and (X l, Y 1), or a combination of (X h, Y h) and ( ⁇ ). It may be defined to be represented by a combination.
- the extended coordinates ⁇ are parameters other than the normalized coordinates, for example, the height data of the node. Also, it may be used as time data (information) on data generation and updating. Furthermore, both height data and time data may be used. The size of ⁇ data may be 4 bits or more.
- the definition of the normalized coordinates described above uses parameters such as coordinates (XI, Y1) or height data ( ⁇ ) of other levels in addition to the two-dimensional coordinates (Xh, Yh) at the corresponding level. are doing. Since this parameter is a method of describing the connection status between levels by adding additional information to the two-dimensional coordinates, it is referred to as an inter-level correspondence key in the present embodiment. It may also be called a 2.5-dimensional space key.
- an inter-level correspondence table is provided for each level, and the correspondence between the levels is performed. Therefore, the inter-level correspondence key of each level does not necessarily need to include all the lower level normalized coordinates. For example, only the lowest level normalized coordinates need to be included.
- Level 0 node normalized coordinates ( ⁇ 0, ⁇ 0)
- level 1 node normalized coordinates (XI, ⁇ 1)
- level 2 node normalized coordinates ( ⁇ 2, ⁇ 2)
- level 3 Assuming that the node normalized coordinates are ( ⁇ 3, ⁇ 3), the inter-level correspondence key of each level node is expressed as follows.
- the level 0 key is (X 0, ⁇ 0)
- the level 1 key is (XI, ⁇ ⁇ 1) and (0, ⁇ 0)
- the level 2 key is The combination of ( ⁇ 2, ⁇ 2) and ( ⁇ 0, ⁇ 0)
- the key corresponding to level 3 is ( ⁇ 3, ⁇ 3) & ( ⁇ 0, ⁇ 0).
- the guidance data exists only in the map data at the lowest level 0, and is used when guiding the route of the route search result.
- the guidance data includes information on intersection names, information on road names, information on direction names, information on direction guides, information on spot guides, information on nearby landmarks, information on road buildings, and the like.
- FIG. 9 is a flowchart for updating map data in the removable memory 3, reading data near the destination, and searching for a route. Update data is provided in removable memory3. The control of the flowchart in FIG. 9 is executed by the control device 11.
- step S1 it is determined whether or not there is update data. Judgment of the presence or absence of the update data means that the removable memory 3 storing the update data is installed. To determine if they have been If it is determined that there is updated data, the process proceeds to step S2.
- step S2 by referring to the update data in the removable medium 3, all the mesh management information of the data that needs to be updated with respect to the data in the recording medium 2 is read from the recording medium 2 and written into the nonvolatile memory 12 .
- step S3 all the mesh management information recorded in the nonvolatile memory 12 is rewritten according to the update data.
- step S4 the data near the destination is read out based on all the mesh management information recorded in the nonvolatile memory 12.
- the update data is written to the nonvolatile memory 12.
- the removable memory 3 is mounted as it is, and the update data is read from the removable memory 3.
- the map data that has not been updated is read from the recording medium 2.
- step S5 it is determined whether there is an update history. Whether or not there is an update history is determined by accessing the block management information 124 of the nonvolatile memory 12. If it is determined in step S5 that there is an update history, the process proceeds to step S6. In step S6, referring to the block management information 124, all the mesh management information that has been sequentially rewritten so far is read from the nonvolatile memory 12. In step S7, referring to the block management information 124, all other mesh management information not present in the non-volatile memory 12 is read from the recording medium 2. In step S8, data near the destination is read out in the same manner as in step S4, based on all the mesh management information read from the nonvolatile memory 12 and the recording medium 2.
- step S5 If it is determined in step S5 that there is no update history, the process proceeds to step S9.
- step S9 all the mesh management information is read from the recording medium 2.
- step S10 data near the destination is read from the recording medium 2 based on all the mesh management information read from the recording medium 2.
- step S11 a route search is performed based on the read map data.
- route search is performed by sequentially reading data near the current location.
- FIG. 10 is a flowchart for reading and updating data near the destination from the map server 6 via the Internet 5, reading data near the current location and near the destination, and performing a route search.
- the updated data is provided from the removable memory 3 and the map server 6.
- the control in the flowchart of FIG. 10 is executed by the control device 11.
- step S21 initialization processing such as reading of all mesh management information is performed.
- FIG. 11 is a flowchart of the initialization process.
- step S101 of FIG. 11 it is determined whether or not there is an update history. Whether or not there is an update history is determined by accessing the block management information 124 of the nonvolatile memory 12. If it is determined in step S101 that there is an update history, the process proceeds to step S102. In step S102, referring to the block management information 124, all the mesh management information that has been sequentially rewritten so far is read from the nonvolatile memory 12. In step S103, referring to the block management information 124, all other mesh management information not present in the non-volatile memory 12 is read from the recording medium 2. In step S104, the data near the current location is read based on all the mesh management information read from the nonvolatile memory 12 and the recording medium 2. Next, the process proceeds to step S22 in FIG.
- step S101 determines whether there is no update history. If it is determined in step S101 that there is no update history, the process proceeds to step S105.
- step S105 all the mesh management information is read from the recording medium 2.
- step S106 data near the current location is read from the recording medium 2 based on the all mesh management information read from the recording medium 2.
- step S22 new data is requested from the map server 6, and if new data exists, the updated data is transmitted by communication. (Near the destination).
- step S23 it is determined whether or not there is update data. What is the determination of the presence or absence of update data? It is determined whether or not update data has been sent from the map server 6. If it is determined that there is update data, the flow advances to step S24 to perform update processing.
- FIG. 12 is a front chart of the updating process.
- step S111 of FIG. 12 it is determined whether there is a data update history near the destination, that is, whether there has been any data update near the destination. If it is determined that there is an update, the process proceeds to step S112.
- step S112 all the mesh management information already existing in the non-volatile memory 12 is rewritten according to the update data transmitted from the map server 6. Then, go to step S115.
- step S113 the control unit refers to the update data transmitted from the map server 6, reads out all the mesh management information of the data that needs to be updated for the data on the recording medium 2 from the recording medium 2, and reads the non-volatile data. Write to memory 1 and 2.
- step S114 all the mesh management information recorded in the nonvolatile memory 12 is rewritten according to the update data. Then, the process proceeds to step S115.
- step S115 the rewritten all mesh management information is read from the nonvolatile memory 12 to the memory 126.
- step S116 data near the destination is read based on all the mesh management information read from the nonvolatile memory 12. Next, the process proceeds to step S26 in FIG.
- step S25 data near the destination is read from the existing data. That is, the data is read from the recording medium 2 or, in the case of previously updated data, from the nonvolatile memory 12.
- step S26 a route search is performed based on the read map data.
- FIG. 20 is a block diagram showing the functions of the control device 11 of the navigation device 1 in an expanded manner.
- the control device 11 reads out and executes a program recorded in ROM (not shown) to realize the function of the block.
- the control device 11 includes a GUI (Graphics-User-Interface) control unit 12, a map data management unit 13, and a route information display unit 14.
- GUI Graphics-User-Interface
- the GUI control unit 22 is selected from the map data update menu prepared in advance. It has a function that prompts you to make a selection, captures the selection input, and narrows down and displays the area you want to update.
- the map data overnight management unit 23 prompts at least one selection input from among the prepared update genre menus, and based on the selection input, stores the updated map data in the narrowed-down area. Has a function to reflect the evening.
- the map data management unit 23 also prompts the user to select at least one of the updated genre menus prepared in advance and, based on the selected input, displays on the map. It also has a function to reflect the updated map data on the displayed route information.
- the “update genre menu” refers to any one of the elements constituting the map data, such as background, road, network, guidance, and guidance search, or a combination thereof.
- the map data management section 23 includes a highlighting section 2 31, a map data update section 2 32, and an information transfer control section 2 33.
- the highlighting section 2 3 1 has a function of displaying the area to which the updated map data belongs in the area map displayed by the GUI control section 2 2 based on the selected updated genre menu.
- the map data updating unit 232 displays the update status of the updated map data, prompts the user to indicate whether or not to update the map data, and incorporates the display to update the map update data.
- the information transfer control unit 233 requests the route search from the map server 6, which is a map data management device, to obtain the route information and the update history information. It has a function to fetch map data including the latest route information from the map server 6 in comparison with the update history information of the data, and reflect it in the route information.
- the route information display unit 24 has a function of performing a route search and displaying the route information from the current position or the departure point to the destination on a map.
- FIG. 21 is a block diagram showing the function of the internal configuration of the map data management device of the present embodiment, specifically, the internal configuration of the map server 6 shown in FIG.
- a CPU (not shown) of the map server 6 reads out and executes a program recorded in a memory (not shown), thereby realizing the function of the block.
- Map server 6 is a communication interface It comprises an ace section 61, a map data management section 62, and an update data providing section 63.
- the map data management unit 62 has a function of managing map data in units of meshes, and the update data providing unit 63 has a function of updating the area to which the corresponding map data belongs based on a data update request obtained from the navigation device 1. It has a function to search by and provide updated data along with history information.
- FIG. 22 and FIG. 23 are flowcharts showing the operation of the navigation device 1 side.
- FIG. 24 is a flowchart showing the operation of the map server 6 side.
- FIGS. 18 to 24 are diagrams showing surface transitions in the use state of the navigation device 1.
- the data stored in the navigation device 1 may be replaced with new information.
- the new data may be retained, and the navigation device may operate by using the new information when performing the processing operation.
- the intended purpose of updating data can be achieved as a navigation system.
- FIG. 18 shows a summary of screen transition of the navigation system in the present embodiment.
- FIG. 18 (a) shows a map display screen displayed on the display monitor 18.
- the screen shown in Fig. 18 (b) is displayed, and the "Update data" menu is selected by default.
- a menu indicating the updating method is displayed on the display monitor 18.
- Figure 18 (b) shows how the update method appears as a menu in a pull-down method. If "From Map" is selected and clicked from the pull-down menu (Fig. 18 (c)), the process moves to the process shown in Fig. 19 (select update data from the display map).
- the processing shifts to the processing shown in FIG. 24 (select update data from genre).
- the update method is displayed, so that even those who do not know the technical contents can use it without difficulty.
- it since several update methods are prepared, it can be updated according to the situation and is easy to use.
- Figure 19 shows the screen transition when selecting update data from the display map
- Figure 15 shows the processing procedure of the map management program installed in the napigege device 1 for that purpose. Have been.
- the user is prompted to make a selection from a plurality of menus for updating map data prepared in advance, capture the selection input, narrow down the area to be updated, and display it on the display monitor 18. Is performed by the GU I control unit 12.
- the screen changes to the screen shown in Fig. 19 (c).
- a menu for selecting an update item of the map for example, an update genre displayed on the right side of the screen is displayed by, for example, a pull-down method (S805).
- the updated genre for example, five types of background, road, network, guidance, and guidance search are prepared (S806).
- the OK button is clicked, the screen changes to a screen shown in FIG. 19 (d).
- control is transferred to the map data management unit 13, and the map data management unit 13 obtains background update data when the background is selected (S 807), and when the road is selected, the road is updated.
- Update data is obtained (S808), and if a network is selected, network update data is obtained (S809).
- the guidance update data is obtained, and when the guidance search is selected, the guidance search update data is obtained.
- the source of these update data is not limited to the navigation system itself or the type of map data management device, but here, the latest data transferred from the map server 6, which is the map data management device, is used. The following describes the map data as an acquisition source.
- the screen transitions to the screen shown in FIG. 19 (d), and a map display reflecting the update state of the data as a result of the search performed by the map server 6 in mesh units is performed (S810). ).
- the area where the new data exists is displayed in a visually different manner from the others by the highlighting section 131, for example, in a different color display. Or by blinking.
- a grid line indicating the mesh unit is also displayed.
- data capacity and transfer time for updating are also displayed, providing convenience when the user performs a confirmation operation (S811: whether to update data or not). In addition to these displays, the user will be prompted with an operation button to update the map.
- the screen shown in Fig. 19 (d) shows the area where the map has been changed (the updated data exists) in mesh units.
- This embodiment shows that six of the displayed meshes can be updated. It is possible to select whether to update all of them or only the selected mesh among them. For example, if it takes a long time to update, select the required mesh from the 6 It is also possible to update only this selected mesh.
- the display format of the selected mesh changes to a visually different display, and the display contents of data capacity / update time also change.
- the user selects the update mesh and selects the operation button "Yes" as the update instruction the selected mesh is updated.
- Fig. 20 shows the screen transition when "Region” is selected from the pull-down menu, and shows a method in which the map is narrowed down from the viewpoint of items related to the region, for example, prefectures, municipalities, and sightseeing spots.
- the operation item relating to the region for example, the item of "Prefecture, city” or the item of "sightseeing spot” , Etc. are output.
- items such as "prefecture, city” and “sightseeing spot” are output in the form of display.
- prefecture name which is the data under this item, is output as shown in Fig. 20 (c).
- the data may be output in order from the north or the south.However, if the data is output from the current location and the name of the prefecture nearby, or from the destination and the name of the prefecture nearby, in most cases, the destination area will be output sooner. There is a merit power that can be selected.
- the lower layer data of the selected prefecture "Kanagawa prefecture”, for example, "city” is output as shown in Fig. 20 (d).
- the output “city”, for example, “Yokohama” is selected, the area including the facility related to the selected “city” can be specified. Then, a list of update target items is output to the map data relating to the specified area, and by selecting this, the update of the specified target item is promoted.
- “genre” is output as an item to be updated.
- the “Janur” includes, for example, “background”, “road”, “network”, “guidance”, and “guidance search”.
- the update target data when the genre item “background” is selected is data for displaying roads, rivers, railways, place names, and the like.
- the background for roads is the data necessary to display roads, and does not include data used for route calculation. This data corresponds to a case where a route search is not performed but a road map is to be displayed.
- the update target data when the genre item “road” is selected is road information for map matching and route calculation.
- the navigation device If the navigation device is set not to have the map matching function or if an area for which map matching is not possible is specified, the navigation device will not automatically select the genre item "road". It is possible. In this case, the device is easy to use for those who are not familiar with navigation-related technologies.
- the data to be updated becomes node information and information on the connection relationship between nodes and can be used for route search.
- the update target data when the genre item “guidance” is selected is display information for guiding the car along the route, that is, information output to the driver to assist driving. For example, landmarks when turning right at an intersection, and indications of buildings and structures as landmarks.
- the update target information is information on facilities, such as restaurants, department stores, shops, various other events, and information on schools.
- FIG. 20 (f) is displayed to indicate whether or not to update the data on the genre as described above.
- the selected area "Yokohama I” and an operation screen for instructing the update data capacity, update time, and whether or not to update are displayed. “Yes” on the operation screen indicates an instruction to update, and “No” indicates an instruction not to update.
- a message indicating that the update operation is in progress and the progress of the update operation is displayed as shown in Fig. 20 (g), and an operation The screen "Cancel” is displayed.
- Specifying “prefectures” or “municipalities” as described above means specifying administrative districts. Administrative divisions vary from country to country, but it is only necessary to be able to specify administrative divisions according to each country.
- Fig. 21 shows the screen transitions related to the operation when "From route” is selected from the pull-down menu shown in Fig. 18 (b).
- the main road names related to this map are output based on the map that is already selected and displayed, as shown in Figure 21 (b). From the output road name list shown in Fig. 21 (b), select the road you want to update. Outputs the data items used to display the selected road.
- data items are displayed by genre, for example, "background”, “road”, “network”, “guidance”, and “guidance search” (Fig. 21 (c)).
- genre items are items related to roads.
- users may be confused if various items are changed.
- the items of the genre are the same as the contents of FIG. 20 (e) described above. The detailed description of these genre items is the same as described above, and will not be repeated.
- an operation screen for updating data capacity, update time, and whether to perform update is displayed as shown in Fig. 21 (d).
- “Yes” is an operation screen for an instruction to perform an update, that is, an operation button display
- “No” is an operation screen for instructing not to perform an update, that is, an operation button display.
- the display of the road name shown in Fig. 21 (b) is, for example, a method of visually distinguishing between a road with new data to be updated and a road that has been updated or has no data to be updated. Is easy to use. Therefore, these may be visually distinguished and displayed. Also, only roads that have new data to be updated may be output. good.
- the operation of FIG. 18 is again shifted from the operation of FIG. 18 to the operation of FIG. 21 in order to confirm the completion of the update.
- Road name is not displayed.
- the road name is displayed, it is displayed in such a manner that it can be visually determined that there is no updated data without updated data, that is, in a display format different from the previous time. If there is no road to be updated, there is a risk of misunderstanding that the road name is not displayed at all, and "No road to be updated" may be displayed.
- Figure 22 shows how the screen transitions when selecting update data from the results of a route search.
- Figures 16 and 17 show the processing procedure of the map management program for that purpose.
- FIG. 16 is a diagram showing the operation of the navigation device 1 side
- FIG. 17 is a diagram showing the operation of the map server 6 side.
- the operation of the route search differs between the case where the navigation device 1 performs the search and the case where the map server 6 performs the route search (S 902). That is, when the map server 6 performs the search, the route information search result output by the map server 6 based on the route search request requested by the navigation device 1 is used to maintain the latest maintained map data. Although reception is sufficient (S914), when the navigation device 1 performs a route search, it is necessary to check the history information of the map data possessed by the navigation device 1.
- the navigation device 1 receives the route information and the history information from the map server 6 (S903), and updates the version of the map data held by the navigation device 1. Is checked (S904).
- S904 As a result of checking the version of the navigation device 1 with ⁇ as the history of the map data and ⁇ as the history of the received route information, it was found that it was not the latest one ( ⁇ ⁇ / 3). Then, it is necessary to download and receive the latest version of the surrounding map related to the route information from the map server 6 (S905).
- the display that new data exists that is, the existence of new purge data
- a display on the right side of FIG. 22 (e) for inputting whether to update is displayed.
- the screen transits to the screen shown in FIG. 22 (c) and the result of the route search is displayed, and the operation moves to the step of specifying the route to be updated over time. If the displayed route is acceptable, select an operation that indicates the route, for example, “Yes” in the displayed content. When “Yes” is selected, the screen transitions to the screen shown in Fig. 22 (d), and the search result to be updated is determined.
- the data is updated along the specified route.
- the renewable area along the route may be displayed, an instruction to update the area may be made, and the updating may be performed.
- the operation is simple and the burden on the user is small.
- a menu for genre selection is displayed (S9 0 7).
- Fig. 19 (c) Fig. 20 (e), and Fig. 21 (c)
- one or more genres of the data to be updated are selected and the OK button is clicked.
- the screen transits to the screen shown in () (S908).
- background update data is obtained (S909)
- road update data is obtained (S910)
- network update data is obtained (S911).
- the map mesh with the data to be updated may be displayed in Fig. 22 (d), and the genre may be selected while viewing the mesh. In this case, it can be determined whether the mesh is important for the user.
- an update target mesh related to the selected genre is displayed on the screen.
- a road map display that reflects the update status of the data, which is the result of a search performed on a mesh basis, is performed.
- the route information and the update history information are obtained by requesting the map server 6 to perform a route search, and the latest route information from the map server 6 is compared with the update history information of the map data of the navigation device 1.
- the information transfer control unit 233 carries out the import of the map data and the reflected route information.
- the highlighting section 2 3 1 displays the area where new data (road) exists in consideration of the map displayed as a result of the route search and the selected update genre. Highlighting is performed using a different color display or blinking. It also displays the data capacity and transfer time for updating, etc., and provides convenience when the user performs a confirmation operation (S912: whether or not to update data). In addition to these displays, an operation button is displayed to the user as to whether to update the map.
- the screen changes to a screen shown in FIG. 22 (f), and the progress of the data update is displayed.
- the icon is displayed in real time by the icon, and the actual map data is updated by the map update unit 13 (S913).
- FIG. 17 shows the processing procedure of the map data management program installed on the map server 6.
- the map server 6 when the map server 6 receives a data update request from the navigation device 1 by clicking the OK button (S101), the map server 6 further checks the update genre menu selected and designated (S102). In the case of the background, the updated data relating to the background is searched for in mesh units with reference to the map data DB 7 (S103). In the case of the road, the road update data is searched in mesh units (S103). 10 4), Net In the case of a network, network update data is searched for in units of meshes (S105), and each is transferred via the update data providing unit 63 (S106).
- update data related to guidance retrieval is searched for in mesh units with reference to guidance retrieval data DB8 and transferred via the update data providing unit 63.
- the map data management unit 62 manages the map data in units of meshes, and based on the update request from the navigation device 1 via the update data providing unit 63, the map data The area is searched in units of mesh, and the update information is provided together with the history information.
- Fig. 23 shows the screen transition when "Guidance search information" is selected from the pull-down menu.
- the list of guidance search information items (golf Sites, leisure lands, restaurants, hotels, etc.) are displayed as shown in Figure 23 (b). If you select, for example, “Restran” from the guide list item, the screen changes to the screen in Fig. 23 (c).
- the guide list item "Restorn” is highlighted, and a menu showing the same update method (update area) as in Fig. 18 is displayed on the right side of the screen.
- Figure 24 shows the screen transition when "From genre” is selected from the pull-down menu.
- "From genre” is selected in Fig. 24 (a)
- a list of genres is displayed as shown in Fig. 24 (b).
- the screen moves to the screen shown in Fig. 24 (c).
- Fig. 24 (c) as in Fig. 18, the area is narrowed down from the map or from the area (Fig. 24 (c)).
- the narrowing down method is performed in the same way as in Figs.
- Figure 24 (d) it is displayed whether there is new data in the selected area in the selected genre.
- the update screen may be displayed only when there is a new data in the area selected by the selected genre.
- map data can be updated in units of meshes, when updating only part of the map data, it is necessary to update the entire recording medium such as a DVD-ROM that stores the map data. Absent.
- the minimum update unit can be the mesh unit, that is, the basic / extended data unit, and the communication amount (cost) required for unnecessary data update can be reduced. In addition, it is possible to make the update cycle of each basic and extension data different.
- the mesh data is separated into basic data and extended data, even if there are navigation devices that only require map display or navigation devices that perform route search and guidance processing, a common map It is possible to use the data.
- extended data is also separated according to the type of data. As a result, even if some extended data is required but other extended data is not required, the same mechanism can be used to provide updated data.
- background data and other location data and network data are managed separately. Therefore, when drawing a map, a map can be drawn with a single access without accessing multiple data groups such as backgrounds, roads, and characters. In addition, the road as the background is good, so drastic deformation It is possible to reduce the amount of display data and improve the display speed.
- the same map database can be used for simple devices such as mobile phones and high-end devices such as in-vehicle navigation devices. Offer can be made. For example, for map display and navigation on mobile phones, only basic data is provided. Basic data and extended data are provided to the on-board navigation device.
- Two-dimensional coordinate values corresponding to latitude and longitude are used for the connection between adjacent meshes and the connection between upper and lower levels, so the data update method depends on the model or standard. Can be prevented.
- the two-dimensional coordinates corresponding to latitude and longitude can be said to be universal data, and by using these data, the data update method can be standardized.
- the two-dimensional coordinate value plus alpha parameters are used, identification between nodes can be performed reliably. For example, if the height data is a parameter of plus alpha, it is possible to reliably distinguish even connection points where roads are elevated and intersect. If the lower-level coordinate value is a parameter of plus alpha, nodes and the like can be specified at the lower-level resolution. In other words, it is possible to reliably connect data between upper and lower levels with different scales.
- map data is managed while all the mesh management information is stored in the non-volatile memory, management of update data can be performed easily and reliably. This makes it easier to develop programs for navigation devices.
- the extended coordinate ⁇ is provided as a part of the inter-level correspondence key, and this parameter is used for, for example, the height data of the node and the generation / update of the data. He explained that it may be time (overnight).
- Such an extended coordinate ⁇ need not be provided to all boundary nodes on the mesh boundary, but may be provided only to some special nodes. For example, only the boundary nodes that intersect on the mesh boundary and have the same coordinates may be provided. As a result, an increase in the amount of data and a decrease in the data processing speed can be minimized.
- the mesh to be updated can be specified by specifying the administrative division name of, for example, a prefecture or city.
- the map data of a desired area can be easily updated at a low cost.
- the mesh to be updated can be specified by specifying the route name or the road name, this is convenient when the route name or the road name to be updated is known.
- the line names and road names in the displayed map not only the line names and road names in the displayed map, but also the line names and road names nationwide may be used.
- a highway genre may be selected, a list of expressways nationwide may be displayed, and the Tomei Expressway may be selected to update all meshes passing by the Tomei Expressway.
- Route names and road names are not limited to official names such as National Highway No. 1 and may be other names.
- the name of the highway such as the Ome highway may be used.
- the route from the starting point (current location) to the destination can be specified, and the map data of the mesh related to the route can be updated.
- map display and guidance can be performed with the latest map data.
- the route search can be performed with the latest map data.
- control program executed by the control device 11 of the navigation device has been described as an example in which the control program is stored in R ⁇ M.
- the control program and its installation program may be provided on a recording medium such as a DVD.
- the recording medium need not be limited to DVD, but CD-R DM, a magnetic tape, or any other recording medium may be used.
- those programs can be provided via a transmission medium such as a communication line typified by the Internet Network. That is, it is also possible to convert the program into a signal on a carrier wave that carries the transmission medium and transmit the signal.
- the program may be provided in the same configuration as in FIG.
- the recording medium 2 may be a recording medium provided with a program
- the map server 6 may be a server providing an application program. In this way, the program can be supplied as a computer program product readable in various forms such as a recording medium and a carrier wave.
- control program is executed on a personal computer to execute car navigation equipment. May be realized.
- the current position detection device 13 and the input device 19 may be connected to a predetermined IZO port of a personal computer.
- update data may be written in CD-ROM or DV-ROM, and the recording medium 2 may be temporarily replaced to be provided.
- the initial map data may be received via the Internet 5 and stored in the non-volatile memory 12, and then updated and managed by the method described above.
- the necessary map data may be received via the Internet 5 each time, and may be stored in the non-volatile memory 12 each time, and when there is an update thereafter, the update may be managed by the above-described method.
- the example of the route search has been described as the navigation process.
- the present invention is not limited to this.
- Various navigation processes such as map display and route guidance can be performed using the above map data.
- the present invention is not limited to this. It may be an external storage device connected by a cable or the like.
- network data may be used as basic data.
- map data network data, etc.
- it is used for an application that searches for a route and guides the traveling direction of a vehicle only with arrows or the like. This is because such a navigation device does not require background (for map display) data.
- the network data becomes the highest priority data, and only the network data may be updated in mesh units.
- the basic data may be, for example, map data of the highest priority type commonly used by a plurality of predetermined models in each application.
Landscapes
- Engineering & Computer Science (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Databases & Information Systems (AREA)
- Navigation (AREA)
- Traffic Control Systems (AREA)
- Instructional Devices (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/521,327 US7584049B2 (en) | 2002-07-17 | 2003-07-17 | Navigation method, processing method for navigation system, map data management device, map data management program, and computer program |
EP03741460A EP1562021B1 (en) | 2002-07-17 | 2003-07-17 | Navigation method and computer program |
CN038170035A CN1668893B (zh) | 2002-07-17 | 2003-07-17 | 导航方法、用于导航系统的处理方法、地图数据管理装置、地图数据管理程序、以及计算机程序 |
KR1020057000653A KR100707568B1 (ko) | 2002-07-17 | 2003-07-17 | 네비게이션 방법, 네비게이션 시스템을 위한 처리 방법,지도 데이터 관리 장치, 지도 데이터 관리 프로그램, 및컴퓨터 프로그램 |
JP2004521226A JP4409431B2 (ja) | 2002-07-17 | 2003-07-17 | ナビゲーション方法、ナビゲーション装置、及びコンピュータプログラム |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2002208763 | 2002-07-17 | ||
JP2002-208763 | 2002-07-17 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004008073A1 true WO2004008073A1 (ja) | 2004-01-22 |
Family
ID=30112856
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2003/009088 WO2004008073A1 (ja) | 2002-07-17 | 2003-07-17 | ナビゲーション方法、ナビゲーションシステムのための処理方法、地図データ管理装置、地図データ管理プログラム、及びコンピュータプログラム |
Country Status (6)
Country | Link |
---|---|
US (1) | US7584049B2 (ja) |
EP (1) | EP1562021B1 (ja) |
JP (1) | JP4409431B2 (ja) |
KR (1) | KR100707568B1 (ja) |
CN (1) | CN1668893B (ja) |
WO (1) | WO2004008073A1 (ja) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005274740A (ja) * | 2004-03-23 | 2005-10-06 | Mitsubishi Electric Corp | 案内情報検索装置およびこれを用いた案内情報検索システム |
JP2007139968A (ja) * | 2005-11-16 | 2007-06-07 | Nissan Motor Co Ltd | 地図データ更新システム、地図データ配信装置、地図データ更新装置、および地図データ更新方法 |
JPWO2005101350A1 (ja) * | 2004-04-13 | 2008-03-06 | パイオニア株式会社 | 地図描画装置、ナビゲーション装置、ファイル更新方法及びファイル更新プログラム並びにこのファイル更新プログラムを記録した情報記録媒体 |
WO2008044373A1 (fr) * | 2006-10-10 | 2008-04-17 | Mitsubishi Electric Corporation | Dispositif terminal d'informations embarqué dans une automobile, dispositif de fourniture d'informations cartographiques et système d'utilisation |
JP2008216285A (ja) * | 2007-02-28 | 2008-09-18 | Aisin Aw Co Ltd | ナビゲーション装置及びデータ更新システム |
JP2009236692A (ja) * | 2008-03-27 | 2009-10-15 | Xanavi Informatics Corp | ナビゲーション装置 |
JP2011149786A (ja) * | 2010-01-21 | 2011-08-04 | Honda Motor Co Ltd | ナビゲーション装置 |
JP2012189448A (ja) * | 2011-03-10 | 2012-10-04 | Clarion Co Ltd | カーナビゲーションシステム |
DE102005055125B4 (de) * | 2004-11-18 | 2013-09-26 | Xanavi Informatics Corp. | Kartenaktualisierungssystem, Navigationsvorrichtung und Bereitstellungsvorrichtung |
WO2015008465A1 (ja) * | 2013-07-15 | 2015-01-22 | 株式会社デンソー | ナビゲーション装置 |
JP2015179285A (ja) * | 2015-06-05 | 2015-10-08 | クラリオン株式会社 | カーナビゲーションシステム |
WO2019188165A1 (ja) * | 2018-03-28 | 2019-10-03 | 日立オートモティブシステムズ株式会社 | 地図提供装置 |
CN112307025A (zh) * | 2020-10-29 | 2021-02-02 | 杭州海康威视数字技术股份有限公司 | 一种分布式索引的构建方法及装置 |
JP2022100357A (ja) * | 2018-10-01 | 2022-07-05 | 日産自動車株式会社 | 情報処理システム、情報処理装置、及び情報処理方法 |
Families Citing this family (92)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4162959B2 (ja) * | 2002-09-27 | 2008-10-08 | 株式会社ザナヴィ・インフォマティクス | 地図データ処理装置 |
JP2004198321A (ja) * | 2002-12-19 | 2004-07-15 | Pioneer Electronic Corp | ナビゲーション用の差分更新データ作成装置及び方法、ナビゲーション装置及び方法、ナビゲーション用の差分更新データセット並びにコンピュータプログラム |
JP2004309705A (ja) * | 2003-04-04 | 2004-11-04 | Pioneer Electronic Corp | 地図情報処理装置、そのシステム、その方法、そのプログラム、および、そのプログラムを記録した記録媒体 |
JP4543637B2 (ja) * | 2003-08-26 | 2010-09-15 | 三菱電機株式会社 | 地図情報処理装置 |
KR100754168B1 (ko) * | 2004-11-12 | 2007-09-03 | 삼성전자주식회사 | 지도 데이터 업데이트 방법 및 장치와, 그 방법을수행하기 위한 프로그램이 저장된 기록 매체 |
JP4533201B2 (ja) * | 2005-03-22 | 2010-09-01 | 日立オートモティブシステムズ株式会社 | ナビゲーション装置、ナビゲーション方法、ナビゲーションプログラム、サーバ装置およびナビゲーション情報配信システム |
US7552009B2 (en) * | 2005-07-14 | 2009-06-23 | Honda Motor Co., Ltd. | System and method for synchronizing data for use in a navigation system |
JP5002140B2 (ja) * | 2005-08-24 | 2012-08-15 | クラリオン株式会社 | ナビゲーション装置およびナビゲーション処理方法 |
JP4839765B2 (ja) * | 2005-10-04 | 2011-12-21 | 株式会社デンソー | 電子機器、路線地図データ更新システム、及び、路線地図データ管理装置 |
US7742857B2 (en) * | 2005-12-07 | 2010-06-22 | Mazda Motor Corporation | Automotive information display system |
US7603621B2 (en) * | 2006-01-25 | 2009-10-13 | Microsoft Corporation | Computer interface for illiterate and near-illiterate users |
JP5116236B2 (ja) * | 2006-01-30 | 2013-01-09 | アルパイン株式会社 | 地図データ作成方法及び地図データ作成装置 |
US20070266239A1 (en) * | 2006-03-08 | 2007-11-15 | David Vismans | Method for providing a cryptographically signed command |
ATE409307T1 (de) * | 2006-03-31 | 2008-10-15 | Research In Motion Ltd | Benutzerschnittstellenverfahren und vorrichtung zur steuerung der visuellen anzeige von karten mit auswählbaren kartenelementen bei mobilen kommunikationsvorrichtungen |
US7720893B2 (en) | 2006-03-31 | 2010-05-18 | Research In Motion Limited | Methods and apparatus for providing map locations in user applications using URL strings |
US7913192B2 (en) * | 2006-03-31 | 2011-03-22 | Research In Motion Limited | Methods and apparatus for retrieving and displaying map-related data for visually displayed maps of mobile communication devices |
US8014796B2 (en) * | 2006-03-31 | 2011-09-06 | Research In Motion Limited | Map version control methods and apparatus for updating the use of network-maintained map data sets for mobile communication devices |
TWI311294B (en) * | 2006-06-15 | 2009-06-21 | Olemap Inc | Method for modifying the electric map |
JP4995499B2 (ja) * | 2006-06-23 | 2012-08-08 | アイシン・エィ・ダブリュ株式会社 | 地図情報配信システム |
US7646296B2 (en) * | 2006-08-11 | 2010-01-12 | Honda Motor Co., Ltd. | Method and system for receiving and sending navigational data via a wireless messaging service on a navigation system |
US8102281B2 (en) * | 2006-08-11 | 2012-01-24 | Honda Motor Co., Ltd. | Method and system for receiving and sending navigational data via a wireless messaging service on a navigation system |
US8134481B2 (en) * | 2006-08-11 | 2012-03-13 | Honda Motor Co., Ltd. | Method and system for receiving and sending navigational data via a wireless messaging service on a navigation system |
GB2440958A (en) * | 2006-08-15 | 2008-02-20 | Tomtom Bv | Method of correcting map data for use in navigation systems |
JP4694443B2 (ja) * | 2006-08-17 | 2011-06-08 | 本田技研工業株式会社 | ナビサーバ、ナビ装置およびナビシステム |
DE102006039377A1 (de) * | 2006-08-22 | 2008-03-13 | Bayerische Motoren Werke Ag | Verfahren und Einrichtung zur Aktualisierung einer elektronischen Straßenkarte |
DE102007001852A1 (de) * | 2007-01-12 | 2008-07-17 | Robert Bosch Gmbh | Verfahren zum Aktualisieren von geographischen Daten |
WO2008084553A1 (ja) * | 2007-01-12 | 2008-07-17 | Pioneer Corporation | 情報処理装置、情報処理方法、情報処理プログラムおよびコンピュータに読み取り可能な記録媒体 |
CN101636720A (zh) * | 2007-03-20 | 2010-01-27 | 株式会社爱可信 | 具备应用程序更新管理功能的终端、应用程序更新管理程序以及系统 |
KR100852617B1 (ko) | 2007-03-20 | 2008-08-18 | 팅크웨어(주) | 지도 책 보기 표시장치 및 그 방법 |
JP4466675B2 (ja) * | 2007-03-30 | 2010-05-26 | アイシン・エィ・ダブリュ株式会社 | ナビゲーション装置 |
US20080270576A1 (en) * | 2007-04-09 | 2008-10-30 | Ian Cummings | Apparatus and methods for reducing data transmission in wireless client-server navigation systems |
JP5361148B2 (ja) * | 2007-06-26 | 2013-12-04 | アルパイン株式会社 | 配信地図作成装置及び差分データ作成装置 |
US20090027418A1 (en) * | 2007-07-24 | 2009-01-29 | Maru Nimit H | Map-based interfaces for storing and locating information about geographical areas |
DE102008011290A1 (de) * | 2008-02-27 | 2009-09-03 | Continental Teves Ag & Co. Ohg | Vorrichtung und Verfahren zur Aktualisierung von digitalen Karten |
US8554469B2 (en) | 2007-08-25 | 2013-10-08 | Continental Teves Ag & Co. Ohg | Apparatus and method for updating digital maps |
DE102007048264A1 (de) * | 2007-10-08 | 2009-04-09 | Robert Bosch Gmbh | Verfahren zum Betrieb eines Navigationssystems |
WO2009080069A1 (en) * | 2007-12-20 | 2009-07-02 | Tomtom International B.V. | Method and apparatus for updating a digital map |
JP5034931B2 (ja) | 2007-12-26 | 2012-09-26 | ソニー株式会社 | 表示装置、プログラム、及び記録媒体 |
JP5339731B2 (ja) * | 2008-01-22 | 2013-11-13 | 日立オートモティブシステムズ株式会社 | 更新情報提供サーバ、更新情報提供システム、およびナビゲーション装置 |
CN102016501A (zh) * | 2008-04-30 | 2011-04-13 | 歌乐株式会社 | 地图显示装置 |
CN101294819B (zh) * | 2008-06-05 | 2010-11-03 | 凯立德欣技术(深圳)有限公司 | 导航系统的客户端、服务端、及地图数据提供、响应方法 |
KR101495166B1 (ko) * | 2008-07-01 | 2015-02-24 | 엘지전자 주식회사 | 차량 항법 방법 및 그 장치 |
US8341267B2 (en) * | 2008-09-19 | 2012-12-25 | Core Wireless Licensing S.A.R.L. | Memory allocation to store broadcast information |
JP5057246B2 (ja) * | 2008-10-16 | 2012-10-24 | アイシン・エィ・ダブリュ株式会社 | ナビゲーション装置およびプログラム |
US20100198503A1 (en) * | 2009-01-30 | 2010-08-05 | Navteq North America, Llc | Method and System for Assessing Quality of Location Content |
US8775074B2 (en) * | 2009-01-30 | 2014-07-08 | Navteq B.V. | Method and system for refreshing location code data |
US8554871B2 (en) | 2009-01-30 | 2013-10-08 | Navteq B.V. | Method and system for exchanging location content data in different data formats |
US8271195B2 (en) | 2009-01-30 | 2012-09-18 | Navteq B.V. | Method for representing linear features in a location content management system |
JP4905483B2 (ja) * | 2009-03-05 | 2012-03-28 | 株式会社デンソー | 地図データ更新装置および地図データ更新用プログラム |
CN101846523A (zh) * | 2009-03-27 | 2010-09-29 | 佛山市顺德区顺达电脑厂有限公司 | 电子地图的更新系统及其方法 |
US8260550B2 (en) * | 2009-06-19 | 2012-09-04 | GM Global Technology Operations LLC | Presentation of navigation instructions using variable levels of detail |
US9298345B2 (en) | 2009-06-23 | 2016-03-29 | Microsoft Technology Licensing, Llc | Block view for geographic navigation |
JP5054734B2 (ja) * | 2009-06-26 | 2012-10-24 | クラリオン株式会社 | カーナビゲーション装置、プログラムおよび地図データ更新方法 |
US8306729B2 (en) | 2009-10-13 | 2012-11-06 | Telenav, Inc. | Navigation system with user generated content mechanism and method of operation thereof |
US20120130944A1 (en) * | 2009-10-21 | 2012-05-24 | Hisanobu Masuda | Map information processing device |
US9417691B2 (en) * | 2010-03-26 | 2016-08-16 | Nokia Technologies Oy | Method and apparatus for ad-hoc peer-to-peer augmented reality environment |
US9541402B2 (en) | 2010-03-31 | 2017-01-10 | Telenav, Inc. | Hybrid navigation system with location based services and method of operation thereof |
US9182498B2 (en) * | 2010-03-31 | 2015-11-10 | Telenav Inc. | Hybrid navigation system with non-network update and method of operation thereof |
SE1100538A1 (sv) | 2011-07-15 | 2013-01-16 | Scania Cv Ab | Grafiskt användargränssnitt |
JP5729236B2 (ja) | 2011-09-26 | 2015-06-03 | 株式会社デンソー | ナビゲーションシステム、ナビゲーション装置及びセンタ |
KR20130141872A (ko) * | 2012-06-18 | 2013-12-27 | 현대엠엔소프트 주식회사 | 카테고리별 객체단위의 업데이트를 위한 내비게이션 및 업데이트 방법 |
US8813061B2 (en) * | 2012-10-17 | 2014-08-19 | Movimento Group | Module updating device |
CN102944243B (zh) * | 2012-11-16 | 2016-12-21 | 沈阳美行科技有限公司 | 一种地图数据可以增量更新的方法 |
KR101556618B1 (ko) * | 2013-10-16 | 2015-10-01 | 팅크웨어(주) | 다양한 사용자 네트워크 환경 지원 및 자유로운 데이터 권역 설정을 위한 지도 데이터 제공 장치 및 방법과 그 시스템 |
EP3135526B1 (en) * | 2014-04-24 | 2023-03-01 | Hyundai Motor Company | Display system |
DE102014217654A1 (de) * | 2014-09-04 | 2016-03-10 | Bayerische Motoren Werke Aktiengesellschaft | Verfahren zum Verarbeiten von Messdaten eines Fahrzeuges zur Bestimmungdes Beginns eines Parksuchverkehrs und Computerprogrammprodukt |
JP6459442B2 (ja) * | 2014-11-28 | 2019-01-30 | アイシン・エィ・ダブリュ株式会社 | 案内情報表示システム、案内情報表示方法、及び案内情報表示プログラム |
CN104359486A (zh) | 2014-11-28 | 2015-02-18 | 百度在线网络技术(北京)有限公司 | 更新车载导航地图的方法、车载导航设备及系统 |
US9593959B2 (en) * | 2015-03-31 | 2017-03-14 | International Business Machines Corporation | Linear projection-based navigation |
US9874451B2 (en) * | 2015-04-21 | 2018-01-23 | Here Global B.V. | Fresh hybrid routing independent of map version and provider |
KR20180037234A (ko) * | 2015-09-04 | 2018-04-11 | 가부시끼가이샤 잇츠 엠엠씨 | 경로 선택 지원 장치, 경로 선택 지원 방법 및 컴퓨터 프로그램을 기록한 컴퓨터 판독가능 기록매체 |
KR101768137B1 (ko) * | 2015-10-12 | 2017-08-30 | 현대자동차주식회사 | 자동차용 지도 정보 표시 장치 및 그 제어방법 |
JP6650242B2 (ja) * | 2015-10-16 | 2020-02-19 | 日立オートモティブシステムズ株式会社 | 自動運転システム、自動運転制御方法、データecuおよび自動運転ecu |
US10935390B2 (en) | 2016-03-28 | 2021-03-02 | Aisin Aw Co., Ltd. | Communication terminal, server device, movement guidance system, and computer program |
JP6718715B2 (ja) * | 2016-03-28 | 2020-07-08 | アイシン・エィ・ダブリュ株式会社 | 通信端末、サーバ装置、移動案内システム及びコンピュータプログラム |
US11422672B2 (en) | 2016-04-11 | 2022-08-23 | Samsung Electronics Co., Ltd. | Managing updates in a computing system using multiple access methods |
US11092446B2 (en) | 2016-06-14 | 2021-08-17 | Motional Ad Llc | Route planning for an autonomous vehicle |
US10126136B2 (en) | 2016-06-14 | 2018-11-13 | nuTonomy Inc. | Route planning for an autonomous vehicle |
US10309792B2 (en) | 2016-06-14 | 2019-06-04 | nuTonomy Inc. | Route planning for an autonomous vehicle |
US10829116B2 (en) | 2016-07-01 | 2020-11-10 | nuTonomy Inc. | Affecting functions of a vehicle based on function-related information about its environment |
US10857994B2 (en) | 2016-10-20 | 2020-12-08 | Motional Ad Llc | Identifying a stopping place for an autonomous vehicle |
US10681513B2 (en) | 2016-10-20 | 2020-06-09 | nuTonomy Inc. | Identifying a stopping place for an autonomous vehicle |
US10331129B2 (en) | 2016-10-20 | 2019-06-25 | nuTonomy Inc. | Identifying a stopping place for an autonomous vehicle |
US10473470B2 (en) | 2016-10-20 | 2019-11-12 | nuTonomy Inc. | Identifying a stopping place for an autonomous vehicle |
JP6813347B2 (ja) | 2016-12-12 | 2021-01-13 | アイシン・エィ・ダブリュ株式会社 | 通信端末、移動案内システム及びコンピュータプログラム |
US10677599B2 (en) * | 2017-05-22 | 2020-06-09 | At&T Intellectual Property I, L.P. | Systems and methods for providing improved navigation through interactive suggestion of improved solutions along a path of waypoints |
US11747168B2 (en) | 2018-10-01 | 2023-09-05 | Nissan Motor Co., Ltd. | Information processing systems, information processing apparatus, and information processing methods |
WO2021108905A1 (en) * | 2019-12-02 | 2021-06-10 | Wsp Global Inc. | Railway management system with brake calculation and related method |
JP7341176B2 (ja) * | 2021-01-12 | 2023-09-08 | 本田技研工業株式会社 | 地図データの更新方法及び地図情報システム |
US11543264B1 (en) * | 2022-02-23 | 2023-01-03 | Plusai, Inc. | Methods and apparatus for navigating an autonomous vehicle based on a map updated in regions |
CN114879818A (zh) * | 2022-05-11 | 2022-08-09 | 江苏晶众信息科技有限公司 | 一种基于智能网联平台及mec的数字地图管理方法及装置 |
WO2024064945A1 (en) * | 2022-09-24 | 2024-03-28 | Apple Inc. | Offline maps |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000036097A (ja) | 1998-07-17 | 2000-02-02 | Aisin Aw Co Ltd | 地図情報管理システム |
JP2001229369A (ja) * | 2000-02-18 | 2001-08-24 | Sumitomo Electric Ind Ltd | 地図データ記憶装置 |
JP2002048574A (ja) * | 2000-07-31 | 2002-02-15 | Fujitsu Ten Ltd | 地図情報配信方法及び地図情報配信システム |
JP2002107169A (ja) * | 2000-10-03 | 2002-04-10 | Hitachi Ltd | 通信型ナビゲーション装置、および情報センター |
JP2002188927A (ja) * | 2000-12-22 | 2002-07-05 | Matsushita Electric Ind Co Ltd | 地図情報更新装置および地図情報更新システム |
EP1221587A1 (de) | 2001-01-03 | 2002-07-10 | Robert Bosch Gmbh | System und Verfahren zum Erstellen eines Navigationsdatenträgers |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3391171B2 (ja) * | 1995-11-21 | 2003-03-31 | 松下電器産業株式会社 | 地図編集表示装置 |
US5951620A (en) * | 1996-01-26 | 1999-09-14 | Navigation Technologies Corporation | System and method for distributing information for storage media |
US6304885B1 (en) * | 1996-05-01 | 2001-10-16 | The United States Of America As Represented By The Secretary Of The Navy | Digital data retrieving, organizing and display system |
JPH1165436A (ja) * | 1997-08-21 | 1999-03-05 | Toyota Motor Corp | 地図データ選択支援装置、その支援装置を含む地図データ処理システムおよび処理装置 |
JP3500928B2 (ja) * | 1997-09-17 | 2004-02-23 | トヨタ自動車株式会社 | 地図データ処理装置、地図データ処理方法および地図データ処理システム |
JPH11257975A (ja) * | 1998-03-11 | 1999-09-24 | Alpine Electronics Inc | ナビゲーション装置のデータ転送方法 |
JP2001012957A (ja) * | 1999-06-29 | 2001-01-19 | Mitsubishi Electric Corp | カーナビゲーション用地図更新システムおよびカーナビゲーション端末 |
JP2001075967A (ja) * | 1999-08-31 | 2001-03-23 | Denso Corp | 地図データの更新用情報作成方法及び地図データの差分更新システム |
JP2002055601A (ja) * | 2000-08-08 | 2002-02-20 | Dream Technologies Kk | 地図表示システム及び方法 |
JP4302872B2 (ja) * | 2000-12-12 | 2009-07-29 | パナソニック株式会社 | ランドマーク更新システムおよびナビゲーション装置 |
JP2003075174A (ja) * | 2001-08-31 | 2003-03-12 | Pioneer Electronic Corp | 通信型ナビゲーション装置およびサーバ装置 |
-
2003
- 2003-07-17 KR KR1020057000653A patent/KR100707568B1/ko not_active IP Right Cessation
- 2003-07-17 WO PCT/JP2003/009088 patent/WO2004008073A1/ja active Application Filing
- 2003-07-17 JP JP2004521226A patent/JP4409431B2/ja not_active Expired - Fee Related
- 2003-07-17 US US10/521,327 patent/US7584049B2/en active Active
- 2003-07-17 EP EP03741460A patent/EP1562021B1/en not_active Expired - Lifetime
- 2003-07-17 CN CN038170035A patent/CN1668893B/zh not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000036097A (ja) | 1998-07-17 | 2000-02-02 | Aisin Aw Co Ltd | 地図情報管理システム |
JP2001229369A (ja) * | 2000-02-18 | 2001-08-24 | Sumitomo Electric Ind Ltd | 地図データ記憶装置 |
JP2002048574A (ja) * | 2000-07-31 | 2002-02-15 | Fujitsu Ten Ltd | 地図情報配信方法及び地図情報配信システム |
JP2002107169A (ja) * | 2000-10-03 | 2002-04-10 | Hitachi Ltd | 通信型ナビゲーション装置、および情報センター |
JP2002188927A (ja) * | 2000-12-22 | 2002-07-05 | Matsushita Electric Ind Co Ltd | 地図情報更新装置および地図情報更新システム |
EP1221587A1 (de) | 2001-01-03 | 2002-07-10 | Robert Bosch Gmbh | System und Verfahren zum Erstellen eines Navigationsdatenträgers |
Non-Patent Citations (1)
Title |
---|
See also references of EP1562021A4 |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005274740A (ja) * | 2004-03-23 | 2005-10-06 | Mitsubishi Electric Corp | 案内情報検索装置およびこれを用いた案内情報検索システム |
JP4684565B2 (ja) * | 2004-03-23 | 2011-05-18 | 三菱電機株式会社 | 案内情報検索装置およびこれを用いた案内情報検索システム |
JPWO2005101350A1 (ja) * | 2004-04-13 | 2008-03-06 | パイオニア株式会社 | 地図描画装置、ナビゲーション装置、ファイル更新方法及びファイル更新プログラム並びにこのファイル更新プログラムを記録した情報記録媒体 |
DE102005055125B4 (de) * | 2004-11-18 | 2013-09-26 | Xanavi Informatics Corp. | Kartenaktualisierungssystem, Navigationsvorrichtung und Bereitstellungsvorrichtung |
JP2007139968A (ja) * | 2005-11-16 | 2007-06-07 | Nissan Motor Co Ltd | 地図データ更新システム、地図データ配信装置、地図データ更新装置、および地図データ更新方法 |
JP4622822B2 (ja) * | 2005-11-16 | 2011-02-02 | 日産自動車株式会社 | 地図データ更新システム、および地図データ更新方法 |
WO2008044373A1 (fr) * | 2006-10-10 | 2008-04-17 | Mitsubishi Electric Corporation | Dispositif terminal d'informations embarqué dans une automobile, dispositif de fourniture d'informations cartographiques et système d'utilisation |
JP2009008682A (ja) * | 2006-10-10 | 2009-01-15 | Mitsubishi Electric Corp | 車載情報端末 |
US7890251B2 (en) | 2006-10-10 | 2011-02-15 | Mitsubishi Electric Corporation | Onboard information terminal and map information providing apparatus and map information providing system using them |
US8510042B2 (en) | 2007-02-28 | 2013-08-13 | Aisin Aw Co., Ltd. | Navigation device and data update system |
JP2008216285A (ja) * | 2007-02-28 | 2008-09-18 | Aisin Aw Co Ltd | ナビゲーション装置及びデータ更新システム |
JP2009236692A (ja) * | 2008-03-27 | 2009-10-15 | Xanavi Informatics Corp | ナビゲーション装置 |
JP2011149786A (ja) * | 2010-01-21 | 2011-08-04 | Honda Motor Co Ltd | ナビゲーション装置 |
JP2012189448A (ja) * | 2011-03-10 | 2012-10-04 | Clarion Co Ltd | カーナビゲーションシステム |
WO2015008465A1 (ja) * | 2013-07-15 | 2015-01-22 | 株式会社デンソー | ナビゲーション装置 |
JP2015179285A (ja) * | 2015-06-05 | 2015-10-08 | クラリオン株式会社 | カーナビゲーションシステム |
WO2019188165A1 (ja) * | 2018-03-28 | 2019-10-03 | 日立オートモティブシステムズ株式会社 | 地図提供装置 |
JPWO2019188165A1 (ja) * | 2018-03-28 | 2021-05-20 | 日立Astemo株式会社 | 地図提供装置 |
JP7026208B2 (ja) | 2018-03-28 | 2022-02-25 | 日立Astemo株式会社 | 地図提供装置 |
US11692846B2 (en) | 2018-03-28 | 2023-07-04 | Hitachi Astemo, Ltd. | Map presentation device |
JP2022100357A (ja) * | 2018-10-01 | 2022-07-05 | 日産自動車株式会社 | 情報処理システム、情報処理装置、及び情報処理方法 |
JP7218464B2 (ja) | 2018-10-01 | 2023-02-06 | 日産自動車株式会社 | 情報処理システム、情報処理装置、及び情報処理方法 |
CN112307025A (zh) * | 2020-10-29 | 2021-02-02 | 杭州海康威视数字技术股份有限公司 | 一种分布式索引的构建方法及装置 |
CN112307025B (zh) * | 2020-10-29 | 2024-06-04 | 杭州海康威视数字技术股份有限公司 | 一种分布式索引的构建方法及装置 |
Also Published As
Publication number | Publication date |
---|---|
US7584049B2 (en) | 2009-09-01 |
JP4409431B2 (ja) | 2010-02-03 |
EP1562021A4 (en) | 2007-06-20 |
EP1562021A1 (en) | 2005-08-10 |
US20060173614A1 (en) | 2006-08-03 |
CN1668893A (zh) | 2005-09-14 |
KR20050014922A (ko) | 2005-02-07 |
CN1668893B (zh) | 2012-03-21 |
JPWO2004008073A1 (ja) | 2005-11-10 |
EP1562021B1 (en) | 2011-12-14 |
KR100707568B1 (ko) | 2007-04-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4409431B2 (ja) | ナビゲーション方法、ナビゲーション装置、及びコンピュータプログラム | |
EP0772173B1 (en) | Information guidance system based on structure configuration map | |
EP0766216B1 (en) | Navigation system | |
KR100735441B1 (ko) | 지도 구조를 가진 데이터를 기록한 기억매체, 지도 데이터 처리 프로그램을 기록한 기억매체, 지도 데이터 처리 방법 및 지도 데이터 처리 장치 | |
JP3842799B2 (ja) | 地図データ提供装置 | |
JP3944671B2 (ja) | ナビゲーション装置 | |
JP2004178248A (ja) | 地図情報提供装置および地図情報提供プログラム | |
JP4226491B2 (ja) | 検索データの更新システムおよびナビゲーション装置 | |
JP4112274B2 (ja) | 地図データ処理方法および地図データ処理プログラム | |
JP4951614B2 (ja) | ナビゲーション装置および地図データ更新方法 | |
JP4083694B2 (ja) | ナビゲーション装置 | |
JP4138637B2 (ja) | ナビゲーション装置、更新データ提供装置、更新データ提供方法 | |
JP2005338687A (ja) | 地図データ更新システム | |
JP2004177245A (ja) | 地図情報処理装置および地図情報処理プログラム | |
JP4080308B2 (ja) | 地図情報処理装置および地図情報処理プログラム | |
JP4037167B2 (ja) | 地図データ処理装置 | |
JP2849577B2 (ja) | 家形の情報の出力装置、家形の情報の出力方法、地図表示装置、地図表示方法、ナビゲーション装置及びナビゲーション方法 | |
JP2010107468A (ja) | 車載ナビゲーションの目的地検索装置及び車載ナビゲーションの目的地検索方法 | |
JP2001116562A (ja) | ナビゲーション装置 | |
JP2010282526A (ja) | 地点検索装置、地点検索方法及びプログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CN JP KR US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2004521226 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020057000653 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20038170035 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 1020057000653 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003741460 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2003741460 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2006173614 Country of ref document: US Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10521327 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 10521327 Country of ref document: US |