WO2013111440A1 - 地図データ構造、地図データ作成方法、および車載情報端末装置 - Google Patents
地図データ構造、地図データ作成方法、および車載情報端末装置 Download PDFInfo
- Publication number
- WO2013111440A1 WO2013111440A1 PCT/JP2012/080596 JP2012080596W WO2013111440A1 WO 2013111440 A1 WO2013111440 A1 WO 2013111440A1 JP 2012080596 W JP2012080596 W JP 2012080596W WO 2013111440 A1 WO2013111440 A1 WO 2013111440A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- map data
- mesh
- map
- hierarchy
- Prior art date
Links
Images
Classifications
-
- 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/3804—Creation or updating of map data
- G01C21/3807—Creation or updating of map data characterised by the type of data
- G01C21/3811—Point data, e.g. Point of Interest [POI]
-
- 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
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/29—Geographical information databases
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09B—EDUCATIONAL OR DEMONSTRATION APPLIANCES; APPLIANCES FOR TEACHING, OR COMMUNICATING WITH, THE BLIND, DEAF OR MUTE; MODELS; PLANETARIA; GLOBES; MAPS; DIAGRAMS
- G09B29/00—Maps; Plans; Charts; Diagrams, e.g. route diagram
- G09B29/003—Maps
Definitions
- the present invention relates to a map data structure, a map data creation method for creating map data having the map data structure, and an in-vehicle information terminal device using the map data created by the map data creation method.
- the name data that is common between meshes and layers of the name data included in the map data is collected as common name data, The data amount of the entire data is reduced (see, for example, Patent Document 1).
- the KIWI format is known as a format of map data used in the in-vehicle information terminal device (for example, see Non-Patent Document 1).
- map data has a large amount of data
- a space where map data including backgrounds and roads exists is divided to manage certain spatial data.
- a region obtained by dividing the space into tiles within a predetermined range is also referred to as a mesh.
- thinning map data according to the scale is also referred to as hierarchization.
- map data including backgrounds and roads are divided into meshes and managed in layers.
- Patent Document 1 name information for the same road data included in each of a plurality of meshes and layers is integrated without duplication, and the integrated name data is used as common name data to reduce the amount of data.
- the data structure of the common name data is not shown in Patent Document 1 and a spatial management form is not adopted, there is a problem in accessibility to desired data. That is, for example, in the case of obtaining desired plural name data, there is a possibility that the desired data may be scattered without being managed collectively in the common name data. If it is stored on the disk, disk access) may occur randomly, which may degrade the data access performance.
- Non-Patent Document 1 data is managed from a spatial point of view such as a hierarchy and a mesh, so that access to desired data is high, but the same data is redundantly managed in multiple hierarchies. There is a problem with the problem of reducing the amount of data.
- the processing capacity of a CPU central processing unit
- the storage capacity of a storage device such as a magnetic disk for storing data are limited. Reduction of volume is a challenge.
- the present invention has been made to solve these problems, and provides a map data structure, a map data creation method, and an in-vehicle information terminal device capable of improving the efficiency of data access and reducing the amount of data. Objective.
- the map data structure according to the present invention is a structure of map data included in each mesh of a plurality of layers, the map data in a mesh of a predetermined layer, and a lower level than the predetermined layer Among the map data in the mesh corresponding to the mesh of the predetermined hierarchy, the map data which is the predetermined map data and common to both is duplicated in the mesh of the predetermined hierarchy and the mesh of the lower hierarchy It is included in the mesh of a predetermined hierarchy so that it may not, and the common map data in each mesh of each several hierarchy is managed as one data set, It is characterized by the above-mentioned.
- map data included in each mesh of a plurality of layers there is a structure of map data included in each mesh of a plurality of layers, the map data in a mesh of a predetermined layer, and a mesh lower than the predetermined layer and in the mesh of the predetermined layer Among the map data in the corresponding mesh, the map data that is the predetermined map data and common to both is included in the mesh of the predetermined hierarchy so as not to overlap between the mesh of the predetermined hierarchy and the mesh of the lower hierarchy, Since common map data in each mesh of each of the plurality of hierarchies is managed as one data set, it is possible to improve data access efficiency and reduce the amount of data.
- Embodiment 1 of this invention shows the map data structure of the lowest layer in the map data structure shown in FIG. 7 by Embodiment 1 of this invention.
- FIG. 7 shows an example of a structure of the map data creation apparatus by Embodiment 1 of this invention.
- It is a flowchart which shows the preparation process of the map data which has the map data structure by Embodiment 1 of this invention.
- FIG. 1 is a diagram showing an example of the configuration of the map database 8 according to Embodiment 1 of the present invention.
- the map database 8 includes point (point) data that represents representative points of city names, place names, and polyline (line) data that represents lines such as rivers, bus routes, and contour lines.
- the map database 8 includes nodes and links used for route search, such as a road network connecting intersections (nodes) and roads (links), and a railway network connecting stations (nodes) and routes (links).
- the phase data 82 is provided.
- the map database 8 includes name data 83 indicating the name of a place such as an administrative name (A city) and a road name (ABC street) in the geometric data 81 that is the background of the map, a restaurant, a convenience store, and a station.
- name data 83 indicating the name of a place such as an administrative name (A city) and a road name (ABC street) in the geometric data 81 that is the background of the map, a restaurant, a convenience store, and a station.
- POI Point Of Interest
- the map database 8 includes voice data for voice guidance of route search results, VICS (registered trademark) (Vehicle Information and Communication) indicating traffic conditions such as traffic congestion and road construction, and TMC (Traffic). It has traffic information data such as Message Channel.
- the map database 8 including map data including the geometric data 81, the phase data 82, the name data 83, and the POI data 84 is stored in a storage device such as a hard disk drive (HDD: Hard Disk Drive) having a magnetic disk.
- a hard disk drive HDD: Hard Disk Drive
- FIG. 2 is a diagram showing an example of display of map data as shown in FIG.
- geometric data 81, name data 83, POI data 84, and the like are mapped in association with position information such as latitude and longitude in a plane space (on a map shown in a plane).
- the map database 8 shown in FIG. 1 is managed by dividing the map data for each mesh 9 obtained by dividing the plane space into tiles.
- FIG. 3 is a diagram showing a three-dimensional example of the hierarchical structure and the mesh structure of the map data. In addition, in FIG. 3, it has shown about the map data of 3 layers.
- a mesh 10 indicated by a solid line is used when a map is enlarged (large scale) and displayed. Further, the mesh 11 indicated by a broken line is used when displaying at a smaller scale than the mesh 10. Further, the mesh 12 indicated by a double line is used when displaying at a smaller scale than the mesh 11.
- the hierarchical number corresponding to the mesh 10 is level 1
- the hierarchical number corresponding to the mesh 11 is level 2
- the hierarchical number corresponding to the mesh 12 is level 3.
- Numbers 1 to 16 assigned to each mesh indicate that there are 16 level 1 meshes.
- the mesh 11 is composed of level 1 mesh numbers 1 to 4 (four meshes 10) as one unit.
- the mesh 12 is composed of four meshes of level 2 as one unit. That is, the one higher hierarchy (hierarchy with a small one-stage scale) is configured by combining four meshes in one hierarchy lower than the hierarchy (a hierarchy with a large one-step scale). Therefore, for example, the mesh 12 is composed of 16 level 1 meshes (mesh numbers 1 to 16) including the mesh 10 and manages these areas (the management will be described later). ).
- FIG. 4 is a plan view showing an example of the hierarchical structure and mesh structure of the map data shown in FIG.
- the mesh 10 indicated by a solid line is indicated as a level 1 mesh
- the mesh 11 indicated by a broken line is indicated as a level 2 mesh
- the mesh 12 indicated by a double line is indicated by a level Shown as 3 meshes.
- the level 2 mesh 11 is configured by combining the four level 1 meshes (mesh numbers 1 to 4). Further, the level 3 mesh 12 is composed of an area composed of four level 2 meshes, and is also composed of an area composed of 16 level 1 meshes (mesh numbers 1 to 16). .
- the map data has been described as having three layers.
- the above rule is applied even when there are more than three layers.
- the level 4 mesh is configured by an area obtained by combining four level 3 meshes.
- FIG. 5 is a diagram showing an example of the configuration of map data according to the first embodiment.
- the name data 83 and the POI data 84 that basically have no data thinning out between layers are targeted.
- the other geometric data 81 and phase data 82 are designed to speed up map display and route search processing by thinning out data between layers.
- a polyline indicating a road line when the map is large scale (at a large scale), for example, when the scale is such that the shape of the house can be identified, coordinate points indicating changes in the data shape are finely managed, A narrow area is displayed by expressing the actual road shape in detail.
- the map when the map is in a small scale (when the scale is small), for example, if it is a scale that displays the entire prefecture, it is only necessary to know the approximate shape of the road. Is unnecessary. Since map data in a wide area is required at a small scale, it is necessary to secure display performance by reducing the data amount of the map data. Therefore, the road shape obtained by thinning out the road shape at the time of large scale is separately managed.
- network information consisting of nodes and links is closely managed at a large scale, whereas at a small scale, the network information is thinned out to manage the route information.
- Network information processing such as search can be executed at high speed.
- the target name data 83 and the POI data 84 are point data consisting of a single point, and thus are basically used in a plurality of layers without thinning out the position information.
- the name and POI display may overlap at a small scale, it is necessary to shift the display position of the name and POI. In such a case, it is possible to manage the display position according to the scale by separately using attribute information or the like.
- a mesh 10 indicated by a solid line is indicated as a level 1 mesh
- a mesh 11 indicated by a broken line is indicated as a level 2 mesh
- a mesh 12 indicated by a double line is a level 3 mesh.
- the level 3 mesh 12 includes four level 2 meshes
- the level 2 mesh 11 includes four level 1 meshes. Includes mesh.
- map data is managed in 4 meshes for each level (each layer).
- four meshes at level 1 are managed in level 2 and four meshes at level 2 are managed in level 3 at level 3, respectively.
- the mesh order is usually arranged in ascending order of mesh number.
- the mesh number is assigned in a zigzag manner such as the lower left (1), the lower right (2), the upper left (3), and the upper right (4) as in the alphabet “Z”. is there.
- the ID for identifying each mesh is indicated by “level number ⁇ mesh number”.
- the ID of mesh number 1 of level 1 as the lowest layer is indicated by “mesh 1-1”.
- Data in each mesh of each layer is stored as data used in a layer to which the mesh storing the data belongs (hereinafter also referred to as a target layer), and is temporarily managed in a layer higher than the layer. When data is used, it is collected and used. By doing so, it is possible to eliminate duplication of data between hierarchies and reduce the amount of map data. That is, for example, the mesh data 16 with the mesh ID “mesh 2-1” is data that is not used at the upper layer level (for example, level 3). Also, for example, when there is data that is shared between level 1 and level 2, the data is stored as level 2 mesh data 16 on the upper layer side, and the data is used at level 1. Can acquire and use data corresponding to the level 1 mesh at level 2 from the level 2 mesh data 16. In FIG. 5, level 1 mesh data as the lowest layer is indicated by mesh data 17, and level 3 mesh data is indicated by mesh data 15.
- FIG. 6 is a diagram showing a map data structure in the mesh according to the first embodiment.
- the map data according to the first embodiment includes a header part 21 and an actual data part 22.
- the target hierarchy since data used in common in the target hierarchy and lower hierarchy is managed on the upper hierarchy side (that is, the target hierarchy), information on the lower hierarchy that uses the data is managed in the target hierarchy. There is a need.
- the header section 21 includes a lower layer number 23 indicating the number of layers lower than the target layer (including the target layer) and a lower layer number array 24 for managing the layer numbers of the lower layers.
- the header unit 21 includes N layer data information 30 for each lower layer, and the N layer data information 30 includes a lower layer mesh number 25 indicating the number of meshes included in each layer, and a mesh included in each layer.
- a lower layer mesh ID array 26 for arranging several IDs and a lower layer mesh offset array 27 indicating the position of the actual data in the actual data portion 22 corresponding to the mesh ID of the lower layer mesh ID array 26 are provided.
- the header section 21 includes a current layer mesh ID 28 indicating the ID of the target layer mesh and a current layer number 29 indicating the layer number of the target layer.
- the actual data part 22 stores various data.
- the name data includes a display position, a character string, a name type (for example, whether the name indicates a road or an administrative name), and the like.
- FIG. 7 is a diagram showing details of the map data structure shown in FIG.
- the N layer data information 30 corresponds to the lower layer numbers 31 and 32 stored in the lower layer number array 24. That is, the N layer data information 30 of the number designated by the lower layer number 23 exists in the map data structure. For example, when the map data has a structure as shown in FIG. 5 and the current layer number 29 is “3” and the current layer mesh ID 28 is “3-1”, the actual data of level 3 that is the target layer is displayed. In the case of use at lower levels 2 and 1, the lower layer number 23 is “3” including level 3 as the target layer, and level 3, level 2 and level 1 are stored in the lower layer number array 24 as lower layer numbers. . For example, level 3 is stored in the lower layer number 31 and level 2 is stored in the lower layer number 32.
- the number of N layer meshes 25 is “1”
- the mesh ID 33 of the lower layer mesh ID array 26 is “3-1”
- the offset 35 of the lower layer mesh offset array 27 is actual.
- An index of mesh ID 33 in the actual data of the data part 22 is stored.
- the number of meshes that share the actual data of level 3 also in level 2 (if the map data and the hierarchical structure of the map data are as shown in FIGS. Is stored in the N-layer mesh number 25, and each mesh ID is stored in the lower-layer mesh ID array 26.
- an index indicating the storage position of the actual data 22 included in the mesh ID is stored in the offset (for example, the offset 35 of the mesh ID 33).
- the map data structure according to the first embodiment is a structure of map data included in each mesh of a plurality of hierarchies, and the map data in a mesh of a predetermined hierarchy (target hierarchy) and lower than the predetermined hierarchy Among the map data in the mesh corresponding to the mesh of the predetermined hierarchy, the map data that is predetermined map data (for example, name data, POI data) and common to both is the mesh of the predetermined hierarchy It is included in a mesh of a predetermined hierarchy so as not to overlap with a mesh of a lower hierarchy, and common map data in each mesh of each of the plurality of hierarchies is managed as one data set.
- the mesh of a predetermined hierarchy (target hierarchy) has information (offset) indicating a data range corresponding to a mesh of a lower hierarchy with respect to common map data included in the mesh.
- FIG. 7 shows an example of the map data structure, and information (for example, the number of actual data) for efficiently accessing the actual data may be provided in addition to the illustrated information.
- FIG. 8 is a diagram showing a lowermost map data structure in the map data structure shown in FIG.
- FIG. 9 is a block diagram showing an example of the configuration of the map data creation device 50 according to the first embodiment.
- the map data input means 51 is a means for inputting original data which is the map data that is the basis for creating the above-described map data structure.
- the map data dividing means 52 is means for dividing the map data input by the map data input means 51 into meshes (see, for example, FIG. 4).
- the map data hierarchizing means 53 is means for hierarchizing the map data input by the map data input means 51 (see, for example, FIG. 3).
- the designated data extracting means 54 extracts predetermined designated data from the original data input by the map data input means 51 and assigns it to each layer hierarchized by the map data hierarchizing means 53.
- the designated data extraction unit 54 may refer to a rule as to which hierarchy data is allocated for each type of original data.
- the output data creation means 55 is means for creating the data of each hierarchy extracted and allocated by the designated data extraction means 54 in accordance with the map data structure described above.
- the map data output means 56 is means for outputting the map data created by the output data creation means 55 to an external storage device such as a magnetic disk.
- FIG. 10 is a flowchart showing a process for creating map data having a map data structure according to the first embodiment.
- step S1 the original data, which is the original map data (not shown) managed by an external storage device or the like for creating the map database 8 as shown in FIG. Read (input).
- step S2 it is determined whether or not the input map data is to be hierarchized.
- the process proceeds to step S3, and when not hierarchizing (NO in step S2), the process proceeds to step S4.
- step S3 the map data layering means 53 performs layering as shown in FIG.
- step S4 the map data dividing means 52 divides the input original data into meshes as shown in FIG.
- step S5 the designated data extraction means 54 extracts data designated from the original data input in step S1, for example, name data or POI data that is the target data of the first embodiment. I do.
- the extraction target data to be extracted may be specified by a separate definition file (not shown) or the like, and the specified data extracting unit 54 may refer to the definition file.
- FIG. 17 is a diagram showing an image of data extraction processing by the designated data extraction means 54.
- the original data included in the mesh is an image in which only necessary data in each layer is left and other data is screened down to the lower layer (data is filtered in each layer). Create data for each mesh.
- step S6 the output data creation means 55 performs processing for creating map data to be output according to the map data structure shown in FIG. 7 using the data specified and extracted in step S5.
- step S7 the map data output means 56 performs processing for outputting the output data (map data) created in step S6 to an external storage device such as a magnetic disk.
- step S8 it is determined whether or not map data has been created for all levels. If it is determined that map data has been created for all levels (YES in step S8), map data is determined. When it is determined that the map data has not been created for all layers (NO in step S8), the process returns to step S3 and the process is performed again.
- the map data creation method is a map data creation method for creating map data having the above-described map data structure (for example, see FIG. 7), and (a) a step of inputting map data (B) hierarchizing the map data input in step (a) and dividing it into a plurality of meshes; (c) after step (b), a map in a mesh of a predetermined hierarchy (target hierarchy) Map that is predetermined map data (for example, name data, POI data) and common to both of the data and map data in a mesh that is lower than the predetermined hierarchy and corresponds to the mesh of the predetermined hierarchy (D)
- the common map data for the common map data extracted in step (c) And a step of creating new map data by including it in a mesh of a predetermined layer so as not to overlap with a mesh of a lower layer, and in each of the new map data created in step (d), a plurality of The common data in each mesh of the hierarchy of is
- FIG. 11 is a diagram illustrating an example of a hardware configuration of the information processing apparatus included in the in-vehicle information terminal device according to the first embodiment.
- Examples of the information processing device provided in the in-vehicle information terminal device according to the first embodiment include an in-vehicle information terminal such as a car navigation device, a mobile phone, or a PDA (Personal Digital Assistant).
- the external storage device 7 stores a data access program, an application program, data used in application processing, and the like.
- the external storage device 7 can read and write data via a hard disk device (HDD) mounted on the information processing device, an external storage medium such as a CD or DVD that can be played back by a drive device, or a predetermined input / output interface.
- HDMI hard disk device
- USB Universal Serial Bus
- the application program is a program for realizing various functions executed by the in-vehicle information terminal device according to the first embodiment.
- the application program has a route guidance function, a map display function, or a route search function in the car navigation device. It is a program to realize.
- the data access program is a program for acquiring data necessary for executing the application program from a data set stored in the external storage device 7.
- the calculation result by the CPU 5 is output to the display device 3 via the bus and displayed on the screen.
- the display device 3 is a device that displays, for example, a map used for route guidance, and is realized by a liquid crystal display, a plasma display, or the like.
- the communication device 4 is a device that communicates with an external device (not shown).
- the information processing device according to the first embodiment is a car navigation device
- the communication device 4 receives a GPS signal or FM radio wave transmitted from a GPS (Global Positioning System) satellite and detects position information. It also functions as a position detection unit.
- GPS Global Positioning System
- the input device 2 is a device that accepts an operation input from the outside, and is realized by a keyboard, operation switches, a touch panel combined with the display device 3, or the like.
- a route search condition or the like is input using the input device 2.
- FIG. 12 is a block diagram showing a configuration of the in-vehicle information terminal device 1 according to the first embodiment.
- the in-vehicle information terminal device 1 includes an input device 2, a position detection unit 61 that detects position information related to the vehicle position, and a navigation function execution unit that executes functions related to navigation such as map display and route search. 63 and a data access unit 62 that performs data access to the map database 8 using a data access program.
- the input device 2 corresponds to the input device 2 in FIG.
- the position detecting device 61 has a function of detecting position information by receiving GPS signals and FM radio waves transmitted from GPS satellites, and corresponds to the communication device 4 of FIG.
- the navigation function execution unit 63 executes various functions in the navigation process based on the map data acquired from the map database 8 and the current position detected by the position detection unit 61.
- the data access unit 62 accesses the map database 8 with reference to related information of data corresponding to the function executed by the navigation function execution unit 63, and acquires desired map data.
- the CPU 5 of the information processing apparatus in FIG. 11 operates as the data access unit 62 by executing the data access program.
- the in-vehicle information terminal device 1 is an in-vehicle information terminal device that executes a predetermined function using map data having the above-described map data structure (see, for example, FIG. 7), such as navigation.
- a navigation function execution unit 63 that executes a predetermined function; a data access unit 62 that accesses the map database 8 that stores map data to acquire predetermined map data used by the navigation function execution unit 63; It is characterized by having.
- a data range corresponding to a mesh in a lower hierarchy is included with respect to common map data (for example, name data, POI data) included in the mesh included in the mesh of a predetermined hierarchy (target hierarchy) of the map data.
- the map data in the desired mesh in the lower hierarchy is directly accessed.
- FIG. 13 is a flowchart showing an operation in which the data access unit 62 of the in-vehicle information terminal device 1 according to the first embodiment acquires desired map data from the map database 8.
- the data access unit 62 acquires desired data from the map database 8 using a data access program.
- step S11 a data range required by the in-vehicle information terminal device 1 is set.
- the data range set at this time is acquired on the display screen based on the screen resolution and display scale of the display device 3 by acquiring the current location by the position detection unit 51. It is calculated by calculating the area required for The calculated data range is set in the data access unit 62.
- step S12 the data hierarchy (level) required by the in-vehicle information terminal device 1 is set (that is, the hierarchy number of the lower layer number array 24 in FIG. 7 is set).
- the data hierarchy set at this time is calculated based on a display scale necessary for the navigation function execution unit 63 to display a map, for example, and the calculated data hierarchy is set in the data access unit 62.
- step S13 a mesh ID in which necessary data is stored is calculated based on the data range set in step S11 and the data hierarchy set in step S12. As described above, the mesh is obtained by dividing the map data and is managed for each hierarchy. As a result, it is possible to uniquely identify the mesh corresponding to the target data range by giving the coordinate values of the data range, for example, the southeast coordinates (latitude, longitude) and the northeast coordinates (latitude, longitude). It becomes.
- step S14 data corresponding to the target mesh is acquired from the map database 8 based on the mesh ID calculated in step S13. Specifically, in the map data structure shown in FIG. 7, the current layer mesh ID 28 is compared with the mesh ID calculated in step S13, and if the mesh IDs are the same, the target mesh data 18 is acquired. If there are a plurality of meshes in step S13, the processes after step S14 are executed for the number of meshes.
- step S15 actual data 22 is acquired from the mesh data 15 acquired in step S14.
- the data (map data) of the target hierarchy can be acquired.
- step S16 it is determined whether or not data (upper layer data) is acquired from the upper layer (upper layer) of the target layer.
- the determination may be made separately using definition data.
- the definition data shows the data distribution for each layer for each data type, and the data access unit 62 compares the data types of the data to be acquired while referring to the definition data, It may be determined whether or not to acquire data from. If it is determined in step S16 that upper layer data is acquired (YES in step S16), the process proceeds to step S17. If it is determined that upper layer data is not acquired (NO in step S16), the data acquisition process ends.
- step S17 an upper layer mesh ID is calculated based on the mesh ID that is the target of data acquisition in step S14 and the hierarchy set in step S12. As described above, in the map database 8, since the mesh ID is uniquely determined based on the data range and the hierarchy, the upper layer mesh ID can be calculated similarly.
- step S18 data corresponding to the upper layer mesh ID is acquired from the map database 8 based on the upper layer mesh ID calculated in step S17.
- the acquisition method as in step S14, in the map data structure shown in FIG. 7, the present layer mesh ID 28 is compared with the upper layer mesh ID calculated in step S18.
- the mesh data 18 is acquired.
- step S19 the Nth lower layer data information (N layer data information 30) is specified based on the hierarchy number set in step S12, and the step is performed from the lower layer mesh ID array 26 of the specified N layer data information 30.
- a mesh ID corresponding to the mesh ID calculated in S ⁇ b> 14 is found, and an offset indicating a data range corresponding to the found mesh ID is acquired from the lower layer mesh offset array 27.
- step S20 based on the offset acquired in step S19, mesh ID data corresponding to the mesh ID found in step S19 is acquired from the actual data.
- step S21 it is determined whether or not all upper layer data has been acquired. If it is determined that the data has been acquired (YES in step S21), the data acquisition process is terminated and it is determined that the data has not been acquired. In the case (NO in step S21), the process returns to step S17 to acquire the upper layer data again.
- data common to each layer is managed in the upper layer, so that duplication of map data can be eliminated and the amount of data can be reduced.
- map data management becomes easy, and desired data can be accessed at high speed, thereby improving data access efficiency.
- the in-vehicle information terminal device by using the map data having the map data structure according to the first embodiment, processing in the in-vehicle information terminal device such as navigation, route search, or map display is performed. It can be executed at high speed. Moreover, the data amount of the map data which occupies storage devices, such as HDD which stores the map database with which a vehicle-mounted information terminal device is equipped, can be made small.
- FIGS. 6 and 7 the mesh data range corresponding to each lower layer (lower layer) than a certain layer is indicated by an offset.
- FIGS. 4 when actual data is created in the lowest layer and the actual data is used in an upper layer (upper layer), the mesh ID data 39 and a use layer indicating a layer using the actual data 40 may be managed as a set.
- the lower layer number 23, the lower layer number array 24, and the N layer data information 30 as shown in FIG. 7 of the first embodiment are not necessary, and the data in the header section 21 is reduced. As a result, the effect of reducing the amount of data can be obtained.
- the lowermost layer has a header part for managing data related to the lower layer, but the lowermost layer does not require an offset, and the hierarchical numbers are all the same.
- a hierarchy change flag 41 as shown in FIG. 16 may be provided, and the hierarchy number 29 may be set only when the hierarchy change flag 41 changes.
- the data in the header part is reduced and the data amount is reduced.
- 1 in-vehicle information terminal device 2 input device, 3 display device, 4 communication device, 5 CPU, 6 memory, 7 external storage device, 8 map database, 9 mesh, 10 mesh, 11 mesh, 12 mesh, 15 mesh data, 16 Mesh data, 17 mesh data, 18 mesh data, 21 header part, 22 actual data part, 23 lower layer number, 24 lower layer number array, 25 lower layer mesh number, 26 lower layer mesh ID array, 27 lower layer mesh offset array, 28 current layer mesh ID, 29 Current layer number, 30 N layer data information, 31 Lower layer number, 32 Lower layer number, 33 Mesh ID, 34 Mesh ID, 35 Offset, 36 Offset, 37 Mesh ID data, 38 Mesh ID data, 39 ID data, 40 usage hierarchy, 41 hierarchy change flag, 50 map data creation device, 51 map data input means, 52 map data division means, 53 map data hierarchy means, 54 specified data extraction means, 55 output data creation means, 56 Map data output means, 61 position detection unit, 62 data access unit, 63 navigation function execution unit, 81 geometric data, 82 phase data, 83 name data, 84
Landscapes
- Engineering & Computer Science (AREA)
- Remote Sensing (AREA)
- Radar, Positioning & Navigation (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Automation & Control Theory (AREA)
- Theoretical Computer Science (AREA)
- Mathematical Physics (AREA)
- Business, Economics & Management (AREA)
- Educational Administration (AREA)
- Educational Technology (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Navigation (AREA)
- Instructional Devices (AREA)
- Processing Or Creating Images (AREA)
- Traffic Control Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
図1は、本発明の実施の形態1による地図データベース8の構成の一例を示す図である。図1に示すように、地図データベース8は、市区町村名や地名の代表点などを表現するポイント(点)データや、川、バス路線、等高線などの線を表現するポリライン(線)データや、家形図、公園、湖沼などの閉空間を表現するポリゴン(面)データなど、地図の背景となる幾何データ81を備えている。
実施の形態1では、図6,7に示すように、ある階層より下位の階層(下層)ごとに対応するメッシュのデータ範囲をオフセットで示したが、本実施の形態2では、図14,15に示すように、最下層で実データを作成しておき、当該実データを上位の階層(上層)でも利用する場合は、当メッシュIDデータ39と、当該実データを利用する階層を示す利用階層40とをセットで管理するようにしてもよい。
実施の形態1では、図8に示すように、最下層において下層に関するデータを管理するヘッダ部を有していたが、最下層ではオフセットなどが不要であり、また階層番号は全て同じであるため、図16に示すような階層変化フラグ41を設け、当該階層変化フラグ41が変化したときのみ当階層番号29を設定するようにしてもよい。
Claims (9)
- 複数の階層の各メッシュに含まれる地図データの構造であって、
所定の階層のメッシュにおける地図データと、当該所定の階層より下位の階層であって前記所定の階層のメッシュに対応するメッシュにおける地図データのうち、所定の地図データであって両者に共通の地図データは、前記所定の階層のメッシュと前記下位の階層のメッシュとで重複しないように前記所定の階層のメッシュに含まれ、
各前記複数の階層の各メッシュにおける前記共通の地図データは、一のデータ集合として管理されることを特徴とする、地図データ構造。 - 前記所定の階層のメッシュは、当該メッシュに含まれる前記共通の地図データに対して、前記下位の階層のメッシュに対応するデータ範囲を示す情報を有することを特徴とする、請求項1に記載の地図データ構造。
- 前記所定の地図データは、地図上の場所の名称を示す名称データや、地点を示すPOIデータであることを特徴とする、請求項1または2に記載の地図データ構造。
- 請求項1に記載の地図データ構造を有する地図データを作成する地図データ作成方法であって、
(a)地図データを入力する工程と、
(b)前記工程(a)で入力された前記地図データを階層化するとともに複数のメッシュに分割する工程と、
(c)前記工程(b)の後、所定の階層のメッシュにおける地図データと、当該所定の階層より下位の階層であって前記所定の階層のメッシュに対応するメッシュにおける地図データのうち、所定の地図データであって両者に共通の地図データを抽出する工程と、
(d)前記工程(c)にて抽出された前記共通の地図データについて、前記地図データ構造に基づいて前記共通の地図データを前記所定の階層のメッシュと前記下位の階層のメッシュとで重複しないように前記所定の階層のメッシュに含めることにより新たな地図データを作成する工程と、
を備え、
前記工程(d)にて作成された前記新たな地図データにおいて、各前記複数の階層の各メッシュにおける前記共通の地図データは、一のデータ集合として管理されることを特徴とする、地図データ作成方法。 - 前記工程(d)にて作成された前記新たな地図データの所定の階層のメッシュは、当該メッシュに含まれる前記共通の地図データに対して、前記下位の階層のメッシュに対応するデータ範囲を示す情報を有することを特徴とする、請求項4に記載の地図データ作成方法。
- 前記所定の地図データは、地図上の場所の名称を示す名称データや、地点を示すPOIデータであることを特徴とする、請求項4または5に記載の地図データ作成方法。
- 請求項1に記載の地図データ構造を有する地図データを用いて所定の機能を実行する車載情報端末装置(1)であって、
ナビゲーションなど前記所定の機能を実行するナビ機能実行部(63)と、
前記地図データを格納する地図データベース(8)に対して、前記ナビ機能実行部(63)にて用いられる所定の前記地図データを取得するためにアクセスするデータアクセス部(62)と、
を備える、車載情報端末装置。 - 前記地図データの所定の階層のメッシュが有する、当該メッシュに含まれる前記共通の地図データに対して、前記下位の階層のメッシュに対応するデータ範囲を示す情報を用いることで、前記下位の階層の所望のメッシュにおける地図データに対して直接アクセスすることを特徴とする、請求項7に記載の車載情報端末装置。
- 前記共通の地図データは、地図上の場所の名称を示す名称データや、地点を示すPOIデータであることを特徴とする、請求項7または8に記載の車載情報端末装置。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE112012005733.3T DE112012005733B4 (de) | 2012-01-23 | 2012-11-27 | Kartendatenstruktur, Kartendatenerstellungsverfahren und Bordinformationsterminal |
CN201280067810.8A CN104067331B (zh) | 2012-01-23 | 2012-11-27 | 地图数据构造、地图数据制作方法、以及车载信息终端装置 |
JP2013555138A JP5714137B2 (ja) | 2012-01-23 | 2012-11-27 | 地図データ構造、地図データ作成方法、および車載情報端末装置 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012-010707 | 2012-01-23 | ||
JP2012010707 | 2012-01-23 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013111440A1 true WO2013111440A1 (ja) | 2013-08-01 |
Family
ID=48873181
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2012/080596 WO2013111440A1 (ja) | 2012-01-23 | 2012-11-27 | 地図データ構造、地図データ作成方法、および車載情報端末装置 |
Country Status (4)
Country | Link |
---|---|
JP (1) | JP5714137B2 (ja) |
CN (1) | CN104067331B (ja) |
DE (1) | DE112012005733B4 (ja) |
WO (1) | WO2013111440A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106446223A (zh) * | 2016-09-30 | 2017-02-22 | 北京百度网讯科技有限公司 | 地图数据的处理方法和装置 |
JP2021165857A (ja) * | 2020-09-02 | 2021-10-14 | ベイジン バイドゥ ネットコム サイエンス アンド テクノロジー カンパニー リミテッド | 地図情報ポイントの表示方法、装置、機器及び読み取り可能な記憶媒体 |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105574194B (zh) * | 2015-12-28 | 2018-12-04 | 江苏鸿信系统集成有限公司 | 一种用于电子地图界面的坐标点处理方法及装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH1124554A (ja) * | 1997-07-04 | 1999-01-29 | Toyota Motor Corp | 地図表示装置、地図データ記憶装置および地図データ記憶媒体 |
JP2004126036A (ja) * | 2002-09-30 | 2004-04-22 | Xanavi Informatics Corp | 配信地図データ構造、配信地図データ作成方法、配信地図データ作成装置、および端末装置 |
JP2010122128A (ja) * | 2008-11-21 | 2010-06-03 | Xanavi Informatics Corp | ナビゲーション装置、および、ナビゲーション装置における道路検索方法 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
BRPI0812782B1 (pt) * | 2007-05-31 | 2019-01-22 | Panasonic Corp | aparelho de captura de imagem, aparelho de provisão de informação adicional e método para uso em um aparelho de provisão de informação adicional |
CN101719160A (zh) * | 2009-12-16 | 2010-06-02 | 中国科学院对地观测与数字地球科学中心 | 基于集群系统的gis并行化系统 |
JP5440477B2 (ja) | 2010-01-29 | 2014-03-12 | 株式会社デンソー | 電子機器 |
JP5440220B2 (ja) | 2010-01-29 | 2014-03-12 | 株式会社デンソー | ナビゲーション装置 |
CN101996258B (zh) * | 2010-11-30 | 2012-11-14 | 重庆大学 | 一种便于快速查询的电子地图信息栅格化处理及查询方法 |
-
2012
- 2012-11-27 DE DE112012005733.3T patent/DE112012005733B4/de active Active
- 2012-11-27 WO PCT/JP2012/080596 patent/WO2013111440A1/ja active Application Filing
- 2012-11-27 CN CN201280067810.8A patent/CN104067331B/zh active Active
- 2012-11-27 JP JP2013555138A patent/JP5714137B2/ja active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH1124554A (ja) * | 1997-07-04 | 1999-01-29 | Toyota Motor Corp | 地図表示装置、地図データ記憶装置および地図データ記憶媒体 |
JP2004126036A (ja) * | 2002-09-30 | 2004-04-22 | Xanavi Informatics Corp | 配信地図データ構造、配信地図データ作成方法、配信地図データ作成装置、および端末装置 |
JP2010122128A (ja) * | 2008-11-21 | 2010-06-03 | Xanavi Informatics Corp | ナビゲーション装置、および、ナビゲーション装置における道路検索方法 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106446223A (zh) * | 2016-09-30 | 2017-02-22 | 北京百度网讯科技有限公司 | 地图数据的处理方法和装置 |
CN106446223B (zh) * | 2016-09-30 | 2020-04-07 | 北京百度网讯科技有限公司 | 地图数据的处理方法和装置 |
JP2021165857A (ja) * | 2020-09-02 | 2021-10-14 | ベイジン バイドゥ ネットコム サイエンス アンド テクノロジー カンパニー リミテッド | 地図情報ポイントの表示方法、装置、機器及び読み取り可能な記憶媒体 |
US11587533B2 (en) | 2020-09-02 | 2023-02-21 | Beijng Baidu Netcom Science And Technology Co., Ltd. | Method for displaying point of information of map, device, and readable storage medium |
Also Published As
Publication number | Publication date |
---|---|
JP5714137B2 (ja) | 2015-05-07 |
JPWO2013111440A1 (ja) | 2015-05-11 |
DE112012005733B4 (de) | 2022-12-22 |
DE112012005733T5 (de) | 2014-11-20 |
CN104067331A (zh) | 2014-09-24 |
CN104067331B (zh) | 2016-08-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7953548B2 (en) | Location-based information determination | |
Shen et al. | Discovering spatial and temporal patterns from taxi-based Floating Car Data: A case study from Nanjing | |
US20200090503A1 (en) | Method, apparatus, and system for real-time detection of road closures | |
KR20120017405A (ko) | 관심 지점을 디스플레이하는 방법 및 시스템 | |
JP5561915B2 (ja) | 地図描画装置及びプログラム | |
US11257200B1 (en) | Computationally efficient distance-based score approximations | |
JP5714137B2 (ja) | 地図データ構造、地図データ作成方法、および車載情報端末装置 | |
US10409842B2 (en) | Storage medium, map information processing apparatus, and data generation method | |
US8341192B2 (en) | Navigation system and methods regarding disputed territories | |
US10809072B1 (en) | Computationally efficient distance-based score approximations | |
US8996307B2 (en) | Navigation system and methods regarding disputed territories | |
JP6312493B2 (ja) | 差分地図データ作成装置、差分地図データ作成方法および差分地図データ配信システム | |
CN112084273A (zh) | 一种地图显示方法、装置、系统及计算机可读存储介质 | |
US20220092970A1 (en) | Method and apparatus for traffic report certainty estimation | |
JP5019129B2 (ja) | ナビゲーション装置及びナビゲーションプログラム | |
JP5225380B2 (ja) | 地図データ更新装置、更新地図データ作成装置、地図データ更新方法、更新地図データ作成方法、地図データ更新プログラム、更新地図データ作成プログラム、および記録媒体 | |
Sigala et al. | Measuring the quality of street surfaces in smart cities through smartphone crowdsensing | |
US11428534B2 (en) | Method, apparatus, and computer program product for map matching location data to a map | |
CN102679986A (zh) | 车辆导航装置和方法 | |
JP2013003107A (ja) | ナビゲーション装置およびその検索対象施設の提示方法 | |
US9933267B2 (en) | Navigation device and navigation method | |
JP7142054B2 (ja) | 情報処理装置、経路案内装置、プログラム、及び、情報処理方法 | |
US20230030245A1 (en) | Systems and methods for generating location-based information | |
JP7162028B2 (ja) | 情報処理装置、経路案内装置、プログラム、及び、情報処理方法 | |
JP6448241B2 (ja) | 地図情報表示装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12866940 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2013555138 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 112012005733 Country of ref document: DE Ref document number: 1120120057333 Country of ref document: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12866940 Country of ref document: EP Kind code of ref document: A1 |