JPH09305625A - Map display device - Google Patents

Abstract

(57) [Abstract] [Problem] To increase the rationalization and versatility in searching for a corresponding map element from the attribute of the map element. SOLUTION: When the map data 30 of an external storage medium such as a CDROM is set in the data reading device 6, the map data reading processing unit 14 sorts out the contents (map elements) in the map data, and the map element data is stored. The information in the code information table 11 is used as a guide and stored in the management tables 40 to 51 in accordance with the hierarchical search procedure. Search item list, search information Yes set in the management table 12, read to check whether or not the processing unit 14 the contents of the corresponding to the map data is present up to look like or upper-lower in advance, it In the search item list. According to the record, the search items that can be actually searched are highlighted on the display device 2.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a map display device for displaying map data on a screen.

[0002]

2. Description of the Related Art A map display device gives geographical information to a user by displaying map data (image) through a screen such as a CRT or liquid crystal according to a user's request.
For example, this device is a GPS (Global Positioning
When applied to car navigation in combination with a system (satellite navigation system), the user can know the current position of the vehicle on the map and know the geographical information of the surrounding area.

A map is composed of several elements, that is, buildings such as public facilities and houses, roads and bridges, or elements such as mountains, rivers and parks, which are basic units constituting the map. Each map element consists of shape data and attribute data. The shape data is coordinate information necessary for drawing various map elements existing on the map, and the attribute data is digitalized and managed attribute information associated with each map element. Take, for example, the library, which is an element of the map. The library has shape data representing the building of the library, and the library name, address, telephone number, staff,
There is attribute data such as the number of books and opening hours.

It is considered that the map display device will be utilized in various fields in the future and will be used properly according to the purpose. Therefore, the attribute data added to the map element also varies depending on the purpose of use.

The following display methods are available.

For example, in the geographical search device disclosed in Japanese Patent Laid-Open No. 63-298572, an ID number is set in a map element,
After the map element within the search range is fixed, a means for searching and displaying the attribute information based on the ID number of the fixed map element has been developed. Further, in the map display system of Japanese Patent Laid-Open No. 3-233680, when a position on the map is designated, an invention for displaying the attribute information of the position is described.

However, both inventions describe the means for identifying one map element and displaying the attribute information thereof, and conversely, present the requested attribute information from the user side to the map display device. Then, the map display device side cannot be expected to find and display a map element that satisfies the condition. There is also a request for emphasizing or selectively displaying map elements from such presentation of attribute information. On the other hand, there are requests such as displaying only natural elements of the map such as mountains, rivers, and green areas, and not displaying roads and houses, and extracting only map elements that match the attribute value conditions. In some cases, there may be a request such as wanting to emphasize and display.

If the map display device has a function of responding to such a request, by inputting a search condition (attribute condition), the user can select from the specified map range or the currently displayed map range. The user can instantly find out the map element to be searched for and display it on the map to notify the user. The following devices have already been proposed as devices that satisfy such requirements.

For example, in Japanese Patent Laid-Open No. 4-24873, various attribute items (for example, 1; water pipe, 2; water supply device, 3; fire hydrant, 4; sluice valve) of facilities (for example, water distribution system) which are map elements. 5: Pressure reducing valve) is displayed as an attribute file list on the screen by icon operation, and when the desired item is selected, the selected file (for example, water pipe) is displayed on the screen. Enter the attribute item you want to search (for example, pipe diameter, pipe type, NO, facility year) in the search input item shown in, and the map element (water pipe) corresponding to the attribute item will be extracted on the map on the screen. The technology to be displayed is proposed.

[0010]

As described above, it is already known that the user presents the search condition (attribute) and the corresponding map element is displayed on the screen. Conventional devices of this type can be used only for specific map data, and search conditions (search items) are fixed, and the type of map data (purpose, purpose, format, etc.) is different. Couldn't accommodate. Also,
When inputting the search condition, the user includes a process of writing the search condition in the item column on the screen through a keyboard or the like.

The present invention has been made in view of the above points, and an object thereof is to make it possible to hierarchically retrieve a corresponding map element from the attributes of the map element, and also to make the retrieval convenient and rational. To provide a map display device.

[0012] Specifically, firstly, even if the corresponding map elements can be searched by a unified search means for various map data, and even if various map data are connected (set), they match each map data. The searchable items (search menu) are displayed on the screen so that the user can be notified and the search is rationalized. As described above, various attribute information can be added to the elements on the map, and the attribute items (search items), the types of map elements, and the like are changed depending on the purpose of use and the time of use. Therefore, it is necessary to display the search item in which the currently connected map data is reflected to inform the user what the search is possible.

Secondly, in addition to the first object, the versatility of the map display device is improved.

Thirdly, it is intended to realize a device capable of flexibly picking up a map element to be searched from an attribute according to upper to lower hierarchical levels.

Fourth, it is to enable the user to easily set search conditions even when inputting hierarchical search conditions.

[0016]

A first aspect of the present invention is a map display device for setting an external storage medium storing map data in a map data reading device, reading the requested map data, and displaying it through a screen. , The map data search item list is prepared on the main body of the map display device, and this search item list is created based on the attributes of the map element so that the corresponding map element can be searched hierarchically from the attribute. Is managed by a search information management table having search fields of different layers and a flag column attached to the search items, and the contents corresponding to the search items, that is, the corresponding items, in the map data read from the external storage medium. A map data reading processing unit that investigates whether there is a map element and records the result of the investigation in the flag field of the search item list, and a map data reading processing unit. When there is a request to display a search menu with respect to, the search item list stored in the search information table is referred to, and hierarchically displayed on the screen in an expression format that notifies the user of search items having contents. When there is a request for disclosure of desired search items through, a map data display processing unit that searches for map elements that match the search conditions from the read map data and selects or highlights them on the map displayed on the screen. It is characterized by comprising.

According to the present invention, various search items from upper to lower created based on the attributes of map elements are hierarchically displayed as a menu on the screen, and the user can narrow down desired search items according to the hierarchy. If one of the search items is selected and the disclosure request is made, the map element to be searched is displayed on the map so that it can be seen at a glance. For example, when searching mountains at an altitude of 1,000 m or more from the map data, one of the higher-level search items (attributes) is provided with a “background” item and one of the middle search items is set. If one item is "mountain" and one of the subordinate search items is "elevation 1,000 meters or more", the user can display the map from the concept with the large attribute to the subordinate concept through the screen. Withdrawing while interacting with the device, selecting the search item of the desired hierarchy level, searching for the corresponding map element (in this example, a mountain with a specific name of 1,000 meters or more) and selecting it on the map or Highlight.

By preparing the search item list in the search information management table on the main body of the map display device, various map data can be obtained without being restricted by the contents of the map data in the external storage medium to be connected. A wide search item list can be created in advance from the attributes of the map elements.
Therefore, search items that can widely cover various map data can be prepared in advance.

With the above configuration, the search item list also includes search items applicable to map elements other than the contents (map elements) of the map data currently connected to the map display device (ie, , The search item list and the search items that can be searched by each map data do not necessarily all match). Therefore, if all the search item lists are displayed on the screen, actually, search items that are not needed for the currently connected map data will also be displayed on the screen as a search menu. I feel inconvenience and complexity in selecting items.

Therefore, in the present invention, a search item that can be actually searched in the currently connected map data (corresponding to the search item in the connected map data is used by utilizing the flag field of the above-mentioned search item list). If the map element exists, the search item) is notified to the user through the screen, so that the user can select the search item without waste.

A second aspect of the present invention is a map display device in which an external storage medium storing map data is set in a map data reading device to read requested map data and display it on a screen. A list is prepared on the main body of the map display device, and this search item list is a search item of the hierarchy created based on the attribute of the map element so that the corresponding map element can be searched hierarchically from the attribute. A management table group of a hierarchical structure that is managed by a search information management table with a flag column attached to the search item and that stores the data necessary for searching the map data and the map element data to be searched A map data table for constructing a unique map data storage format independent of the map data storage format of the external storage medium, And code information table having information to guide the creation of the management table group Tateburu,
In the map data read from the external storage medium, the contents corresponding to the search item, that is, whether or not there is a corresponding map element is investigated, and the survey result is recorded in the flag column of the search item list, A map data read processing unit for organizing map elements of the read map data and storing them in a predetermined management table while creating the management table group by using the information in the code information table as a guide, and searching for map data. When there is a request to display the menu, the search item list stored in the search information table is referred to, the search items having contents are hierarchically displayed on the screen in an expression format that notifies the user, and the desired items are displayed through this search menu. When there is a request for disclosure of a search item, the map element that matches the search condition is obtained from the information in the management table group of the map data table. A map data display processing unit that selects or highlights on the map appearing on the screen was taken out, characterized in that it comprises an.

According to the second invention, in addition to the same operation as the first invention, the following operation can be expected.

That is, according to the present invention, the contents of map data (map element data) read from the external storage medium are stored in the management table group of the map data table in a unique format that does not depend on the map data storage format of the external storage medium. By doing so (this management table group also stores the data related to the search procedure reflecting the hierarchical search items in a hierarchically organized manner), the map data table does not depend on the format of various map data. Gives gender (unity). In order to read the map data in various formats and store them in the map data table in this way, it is necessary to prepare the map data reading processing unit corresponding to the formats of various map data. In the present invention, the map data reading processing unit reads the connected map data to create the management table group (map data table). Code information relating to the procedure for creating the management table group is referenced from the code information table. By doing so, it is possible to read the map data of the external storage medium having a different data storage format and construct an original map data table (management table group) by using the above-mentioned preparation procedure as a guide.

According to a third aspect of the present invention, an external storage medium storing map data is set in a map data reading device, the requested map data is read, and the map data is displayed on a screen. Upper-lower hierarchical search items are created in advance based on the attributes of map elements, and the upper-lower search item data can be sequentially and hierarchically displayed on the screen by an input operation of a search menu display request. The map element data according to the hierarchy level is stored in the management table group in association with the search items of all the hierarchies. It is characterized in that a map element corresponding to the hierarchical level is searched for even if the above is performed, and is selected or highlighted on the map displayed on the screen.

According to the present invention, a menu of search items (attribute items) is hierarchically displayed on the screen, and no matter which hierarchy level the search item is requested to be disclosed, a map element corresponding to the hierarchy level is searched for, The map element is finally displayed on the screen.

According to a fourth aspect of the present invention, an external storage medium storing map data is set in a map data reading device to read the requested map data and display the map data on a screen, which constitutes the map data. Create a hierarchical search item to search the corresponding map element from the attribute based on the attribute of the map element.
All the item names are set to be displayed as a menu on the pen touch screen, and the search condition input section for pen touch is configured by the search item names in the hierarchy displayed on this menu. By consistently selecting the search item names across all layers via the pen, the user can set the search conditions without the need to create characters. With this configuration, the upper to lower search items can be performed only by a click operation with a pen touch, and other search condition input operations are unnecessary.

[0027]

FIG. 1 is a block diagram showing an example of an embodiment of a map display device of the present invention.

The map display device includes an input device 1, a display device 2, and a CPU for processing information according to a predetermined procedure.
3, a main storage device 5, and a data reading device 6 for reading map data from an external storage medium, and these device units are connected by a system bus 20.

The input device 1 includes a pen touch, a keyboard,
At least one method such as a mouse is adopted. The display device 2 is a display such as a liquid crystal display or a CRT. The map data (external storage medium) 30 is detachably connected (set) to the data reading device 6. The map data 30 is, for example, commercially available road map data or residential map data, and is stored in an external storage medium such as a CD-ROM or a floppy disk.

In the main memory 5, in addition to the operating system 9 that controls the basic operations of various device units connected by the system bus 20, a map data table 10 and a code information table 1 which are means for implementing the present invention.
1, a search information management table 12, a map data read processing unit 14 in which a processing procedure is programmed, a map data display processing unit 16, and an interface processing unit 15 are resident. Various data tables 10-12, processing units 14-16
The operating system 9 is connected by a connection line 21 representing an interface and can mutually exchange data and issue processing instructions. Hereinafter, description will be made sequentially.

In FIG. 1, the operating system 9 reads the map data from the data reading device 6 via the system bus 20 in response to a request from the map data reading processing unit 14, and the map data display processing unit 1
6 executes a process of drawing a map image on the display device 2 in response to a request from 6, and a process of drawing various information related to a search item in response to a request from the interface processing unit 15,
Further, it receives the event of the display area update request or various requests related to the search operation input by the user through the input device 1 and sends the event to the interface processing unit 15. This type of operating system includes, for example, Microsoft Windows 95 (Windows95
Is a registered trademark of Microsoft Corporation).

Now, the map data table 10 will be described.

The map data table 10 is a unique management table group having a hierarchical structure for storing data necessary for map data search and map element data to be searched, and does not depend on the map data storage format of the external storage medium 30. Build a map data storage format for. This management table group is created by the map data reading processing unit 14 using the information in the code information table 11 as a guide (the creation of these management tables is described later using the flowchart of FIG. 6), and the map data is created. It has a hierarchical structure that reflects the search procedure of.

The management table reflects the search items hierarchically created based on the attributes of various map elements. Here, the upper (hereinafter, referred to as layer), the middle (hereinafter, referred to as type), The map data is managed in the lower three layers (hereinafter referred to as elements), and the user is made to search the map data in this procedure.

That is, the map display device first presents a searchable layer name in response to a search item display request, and prompts the user to select an item to be searched from the layer names. Next, the type names that can be searched are presented from the types handled by the selected layer, and the user is made to select the item to be searched from among them.
Finally, the map display device presents to the user the searchable attribute items owned by the selected element.

As described above, by managing the map data in a hierarchical structure in consideration of the search procedure, the user can sequentially determine the search items while interacting with the map and efficiently perform the search setting operation. it can. For the above reason, the map data table 10 in FIG. 1 has the layer management table 40 as the highest level and the type management tables 41 to 4
3. The element management tables 45 to 47 have three types of management tables in a hierarchical form, and the shape data table 50 and the attribute data table 51 are placed at the lowest level.

The contents of the map data 30 to be connected are not always organized for the convenience of retrieval.
Therefore, by setting the unique map data table 10 in the map display device, after reading the contents of the map data 30 to be connected, the map data 30 can be conveniently searched without depending on the data format. Organize, manage and search. The map data table 10 is a unique data storage system that does not depend on individual map data, and therefore can handle a plurality of map data. further,
The operability for the user is also unified.

In the map data table 10, there is only one layer management table 40, for example, as shown in FIG.
The data storage format is as follows. That is, the layer code 2 indicating the kind of map data layer that is actually handled.
01, the type management table top address 202 indicating the location of the type management tables 41 to 43 arranged one for each layer, and the size 203 of the type management table are recorded.

Here, "map data actually handled"
This map data table 10 is a type for organizing map data according to search items, and the map data is not arranged in the management table from the beginning, and the map data is actually read. This is because the map data read by connecting (setting) to the device 6 is targeted.

The map data required out of the map data in the external storage medium 30 is the map data reading processing unit 1.
4 is read out via the data reading device 6 at any time.

The data that can be handled by the map data table 10 and the data that actually exist in the map data 30 do not always match. For example, even though the map data table 10 is ready for acceptance, the actual map data Thirty
In some cases, the corresponding data (map element data) may not exist. As a result, the item column of the management table may be blank. In this case, the type management table start address 202 is -1 and the type management table size 20 is 20.
3 is set to 0. In the present embodiment, for example, the layer code indicating the layer type of the map data is defined by a 4-byte unsigned integer, and there are a background, a transportation facility, and a public facility, and are defined by codes of 0001, 0002, and 0003, respectively. ing. In the example of FIG. 2A, each type management table exists for the layer codes 0001 to 0003.

The type management tables 41 to 43 exist as many as the number of layers handled, and are connected via the type management table top address (address indicating the location of the type management table) 202 of the layer management table 40 ( Connection lines 60-61 shown in FIG. 1 represent this connection). Therefore, it is possible to refer to the applicable type management table from the layer management table 40 using the layer code as a key.

The type management tables 41 to 43 have a data storage format as shown in FIG. 2B, for example. That is, the type management table has a type code 21 indicating the type of type.
1. An element management table start address 212 indicating the location of each element management table 45 to 47 arranged for each type, and an element management table size 213. Only the number is set. The type code 211, the element management table start address 212, and the element management table size 213 are each 4 bytes of data, and 12 per record.
Space for bytes is required. What kind of type is set for each layer is defined in the code information table 11.

The element management table corresponding to each type of code may not be present due to the range of data handled by the map data 30 as in the case described above. In this case, -1 is set to the element management table top address (indicating the location of the element management table) of the type management table, and 0 is set to the table size. Type management table 41
The number of types to be managed differs depending on each layer, and the table sizes are different.

The type code indicating the type of type is defined for each layer and is represented by a 4-byte unsigned integer. As a result, for example, the type code 000 belonging to the background layer
1 and the type code 0001 belonging to the transportation layer have different meanings. As will be described later in detail, in the present embodiment, the type code connected to the background layer includes items indicating the types such as sea, mountain, and green space, and the type code connected to the transportation layer includes road, JR line, There is an item that indicates the type of station, bus stop, etc., and the type codes that connect to public facilities include city hall, hospital, school, hotel, and the like.

FIG. 2B shows an example of the type management table managed in a certain layer. From the type management table of FIG. 2B, there are three types (three type codes) in this layer, and each type (type code) indicates the location of the element management table connected to the lower level of each type. An address (element management table top address) 212 and data regarding the size 213 of the element management table are stored.

In FIG. 1, there are as many element management tables 45 to 47 as the number of types to be handled, and the map element data actually read by the map data reading processing unit 14 is managed. In the present embodiment, a map element is the smallest unit that constitutes a map, for example, a XX mountain or XX
It has a unique shape such as a station, prefectural road □□ line, △△ bridge, etc., and is grouped by type. One piece of map element data is composed of a shape data table storing shape data and an attribute data table storing attribute data, as described later.

As described above, the element management tables 45 to 47 have their location (element management start address) and table size shown in the type management tables 41 to 43. The connection lines 62 to 64 in FIG. As shown by, the corresponding element management table can be referenced from the type management tables 41 to 43 using the type code as a key.

The element management tables 45 to 47 have a data storage format as shown in FIG. 2C, for example. That is, the element management table includes a shape data table top address 222 and a shape data table size 223 indicating the location of the shape data table corresponding to the map element, and an attribute data table start address 224 and attribute indicating the location of the attribute data table. The data table size 225 is composed of a set of records, and this record is set by the number of existing map elements. The shape data table start address 222, the shape data table size 223, the attribute data table start address 225, and the attribute data table size 226 are each 4 bytes of data, and an area of 16 bytes is required for each record.

In FIG. 1, the shape data table 50 exists as many as the number of map elements in the range actually read by the map data reading processing unit 14, and the coordinate information necessary for drawing the shape of the map element is stored. .

The shape data table is individually shown in each record (item) of the element management table in which the location and the table size correspond, and as shown by connection lines 65 to 66 in FIG. Can refer to the shape data table.

The shape data table 50 is, for example, as shown in FIG.
The data storage format is as shown in (d). That is,
The shape data table 50 has a coordinate value 231 of the drawing start point,
The total number of drawing points 232, 0 if the drawn shape is a line, 1 if the shape is a surface / line flag 233, and the offset value from the drawing start point coordinate value is X. A set of coordinates and Y coordinates is stored as many as the (total number -1) of drawing points.

As shown in FIG. 2D, the shape data table is formed by one record consisting of information on drawing coordinate points, and the table size varies depending on the total number of drawing points. Also,
For a shape having a plurality of lines or surfaces, the pen-up operation is performed by setting the offset value to (-1, -1) to draw a plurality of shapes.

There are as many attribute data tables 51 as there are map elements in the range that are actually read by the map data reading processing section 14, and the attribute data of the map elements are stored.

The attribute data table 51 has an attribute data table start address 224 and an attribute data table size 225 indicating the location of the attribute data table 51 in the corresponding element management table.
The attribute data table can be referred to from the element management table as indicated by the connecting lines 65 to 66 in FIG.

As will be described later, with respect to the attributes owned by each map element, the attribute code and the possible value of the attribute value are defined in advance for each attribute type.

The attribute data table 51 is shown in FIG.
The data storage format is as shown in (e). That is,
The attribute data table stores an attribute code indicating an attribute type and an attribute value of the attribute included in the map element. The attribute code is an unsigned integer value consisting of 4 bytes, and the attribute value defines the data type of the attribute value set for each attribute code. The data in the attribute data table depends on how much each individual map element of the map data actually read by the map data reading processing unit 14 has the attribute data added thereto.

Next, the code information table 11 will be described. The code information table 11 has code information that defines a search item (hierarchical search item) created independently that does not depend on individual map data, and the map data reading processing unit 14 refers to this code information. A management table group of the map data table 10 is created. That is, the code information table 11 has information that serves as a guide for creating the management table groups 41 to 43 of the map data table. The creation of the map data table will be described later with reference to the flowchart of FIG.

A code is defined for each type in the hierarchical search items including layers, types, and attributes handled by the map display device. The code information table 11 is made up of several correspondence tables in which codes and their meanings are grouped in pairs of names. Here, for attributes, in addition to the attribute code defined for each type of attribute,
It defines the data type and range of attribute values that the attribute can have. As a result, when setting the search condition, the range of attribute values that the user can select can be clearly presented.

3 and 4 show an example of the code information table handled in this embodiment. The code information table is a layer code information table 301,
Type code information tables 311 to 311 corresponding to each layer
13, and attribute code information table 321 for each type
~ 326 is set.

The layer code information table 301 is shown in FIG.
As shown in (a), a layer code consisting of 4 bytes,
A character string of up to 10 characters (layer name) that describes the content of the code, the type code information table top address indicating the location of the type code information tables 311 to 313 that are summarized as lower-level search items for each layer, and the type code information table The size is stored as a set of records. In FIG. 3A, three layers of background, transportation, and public facilities are set, and data for three records are stored.

Next, the type code information tables 311 to 311
13 is created for each layer and can be referred to by the type code information table top address in the layer code information table 301.

Code information tables 311 to 313 for each type
Then, as shown in FIG. 3B, a type code consisting of 4 bytes, a character string (type name) of up to 10 characters for explaining the content of the code, an attribute code information start address indicating the location of the attribute code information table, In addition, the size of the attribute code information table is set as a set of records, and as many records as the number of types handled in each layer are provided.

In FIG. 3B, the type code information table 311 is for types that are grouped in the background layer, and type codes are defined for types such as mountains and rivers. Further, in the type code information table 312 collected in the transportation layer, type codes are defined for types such as roads and JR lines. In the type code information table 313 that is summarized for public facility layers, type codes are defined for types such as city hall and school, and the head address and the table size indicating the whereabouts of the attribute code information table corresponding to each type are recorded.

On the other hand, the attribute code information table is provided for each type. Attribute code information table 321 in FIG.
˜326 shows an example of each, and mountains, rivers, roads,
It corresponds to JR lines, city halls, and schools. In each attribute code information table, an attribute code consisting of 4 bytes,
A character string (attribute name) of up to 10 characters that describes the content of the code, a numerical value or a character symbol for which an attribute value can be set are stored as a set of records, and data exists as many as the number of attributes handled by that type. The attribute code information can be referred to by the attribute code information table start address in the corresponding type code information table.

Next, the search information management table 12 shown in FIG.
Will be described.

The search information management table 12 manages the search item list. The search item list has a form as shown in FIG. 5 (FIG. 5 will be described later), and a hierarchy created based on the attributes of the map element so that the corresponding map element can be searched hierarchically from the attribute. Of search items (layer code, type code, attribute code) and flag fields (type flag, attribute flag). The layer code, type code, and attribute code correspond to those defined in the code information table 11. The type flag and the attribute flag notify as search information whether or not the contents corresponding to those codes exist in the map data that is actually handled.

That is, in the search information management table 12, the map data 3 is processed by the map data reading processing unit 14.
When 0 is read into the map data table 10, it is checked whether or not there is applicable data (map element and its attribute) for each search item, and the result is recorded (when applicable data exists. , The flag is "1", and the flag is "0" when it does not exist). Then, in response to a request from the user to display a menu for search items in the interface processing unit 15, search items (search menu) for items currently searchable are displayed to the user through the screen of the display device 2.
Let us know as. In other words, the search menu hierarchically displayed on the display device 2 is created based on the search information management table.

FIG. 5 shows an example of the search information management table 12. The search information management table 12 in FIG. 5 includes a field 401 showing a layer code, a field 402 showing a type code collected for each layer, and data (map element) corresponding to the type code. A type flag column 403 indicating whether or not it exists in the map data 30, a column 404 indicating an attribute code corresponding to the type summarized in the type code column 402, and data corresponding to the attribute code (map element (Attribute data) is included in the map data 30 and a column 405 for writing an attribute flag indicating whether or not the map data 30 exists.

The examination result of the presence / absence of data regarding the map element is recorded in the type flag column 403 and the attribute flag column 405. Regarding the record of the investigation result, the map data reading processing unit 14 first sets all the type flags and the attribute flags to 0 (initialization), and then records 1 if the corresponding data exists. As a result, it is possible to know at high speed what items can be searched for in the map data 30.

In FIG. 1, the map data reading processing unit 14 accesses the data reading device 6 via the operating system 9 according to a command from the interface processing unit 15, and maps the map data according to the code information defined in the code information table 11. A management table group 40, 41 to 43, 45 to 47, 5 for reading out the data 30 and constructing an original map data storage method in the map data table 10.
Create 0 and 51.

Further, the map data reading processing unit 14
Checks the presence / absence of map element data for the currently connected map data 30 according to the items set in the code information table 11, and records it using the type flag and attribute flag in the search information management table 12. is there.

Here, the map data 30 has different data contents and storage formats (formats) depending on types such as a provider and a purpose of use. Therefore, the map data reading processing unit 1
4 depends on the data content and storage format of the map data 30, and when other map data is used,
The map data reading processing unit 14 corresponding to the format of the map data is required.

An example of the map data reading processing unit 14 will be described below.

Since the map data read processing unit 14 depends on the format of the map data 30 in the external storage medium, first, before explaining the operation of the map data read processing unit 14, the data structure of the map data 30 is described. An example will be described.

FIG. 9 shows an example of the map data 30.

The map data 30 is stored in the area management table 80.
1 and several data blocks 802 to 805, and an attribute information file 806. The map handled by the map data 30 is divided into some small areas, and data is divided into data blocks 802 to 8 for each of the divided areas.
It is summarized as 05.

The data blocks 802 to 805 are managed by the area management table 801. That is, the area management table 801 shows where the data divided for each area is stored, and the set of the left end longitude, the right end longitude, the upper end latitude, and the lower end latitude indicating the divided areas 8
11 and a data location 812 indicating the location of the corresponding data block. If a set 811 of leftmost longitude, rightmost longitude, uppermost latitude, and lowermost latitude and data location 812 is one recode, the area management table 801.
In this area, as many records as the number of divided areas and FFFF indicating the end of the area management table 801 are arranged. Also,
An offset value from the head of the area management table 801 is set in the data location 812.

One data block stores the shape data relating to the map element in the corresponding divided area and the location of the attribute data added to each element. Here, the map element is a basic unit forming a map, and is, for example, each mountain, river, road, building or the like.

Next, the data structure of the data blocks 802 to 805 will be described. Data block 802
805 all have the same configuration. For example, regarding an arbitrary data block i 804, the data block i
Reference numeral 804 denotes a type code 821 indicating the type of map element, a drawing start point 822 of shape data used for drawing, a total number 823 of drawing coordinate points, a surface / line flag 824 indicating whether the drawing point sequence is a line or a surface, and X. An offset coordinate sequence 825 that represents a sequence of each rendering coordinate point consisting of a set of coordinates and a Y coordinate as an offset from the rendering start point 822, and an attribute information start address 826 indicating a storage location of attribute data added to this map element. Consists of.

Type code 821, drawing start point 822, total number of points 823, face / line flag 824, offset coordinate sequence 8
25, and the attribute information start address 826 is one record, the data block i804 has a data block i8.
The number of records corresponding to the number of map elements in the area handled by 04 and the FFFF indicating the end of the data block i804 are arranged.

On the other hand, the attribute information file 806 stores the attribute data added to all the map elements handled by the map data 30. In the attribute information file 806, one attribute data corresponds to one map element, and the map element name 8
31, address 832, telephone number 833, attribute code 83
4 and an attribute value 835 corresponding to the attribute code 834. The address 832 and the telephone number 833 may be blank depending on the meaning of the map element.

FIG. 10A shows the types handled by the map data 30, and a code is defined for each type. Further, FIG. 10B shows the attributes added to the map elements handled by the map data 30, and the attribute code is defined for each type of attribute.

Next, the map data reading process in this embodiment will be described with reference to FIG. FIG. 6 is a flowchart illustrating the operation of the map data reading processing unit 14.

The map data reading processing unit 14 starts the processing in step 501 in response to a command from the interface processing unit 15. At this time, the interface management unit 15 passes the display management list indicating the read-out area of the map data in the data format as shown in FIG.

Next, at step 502, the map data reading processing unit 14 firstly makes the search information management table 12
Initialize. That is, the search information management table 12
All the type flags and attribute flags in the above are set to 0.

Next, the search layer number indicating the layer of current interest is set to 0001. Then, the layer information table in the code information table 11 is referred to check the number of defined layers, and this is set to the maximum number of layers. Here, since the layer code is set as a natural number in order from 0001, the final code value matches the number of layers. Next, a layer management table is created in the map data table 10. The layer management table 40 is
As described with reference to FIG. 2A, one record consists of 12 bytes, so the required area can be known by multiplying the maximum number of layers.

Then, the map data reading processing unit 14
After the determination process in step 503 repeats all the processes described below for the maximum number of layers,
In step 518, the interface processing unit 15 is notified that the processing is completed, and the operation ends.

During the repetitive processing, in step 504, the map data reading processing unit 14 sets the search type number indicating the type of current attention to 0001, and regarding the layer currently being searched, the type included in the layer. The maximum number of types is checked by the type information table defined in the code information table 11 and set to the maximum number of types. Here, like the layer code, since the types are set as natural numbers starting from 0001, the final code value matches the number of types of the layer. This maximum number of types is used in the determination processing in step 505, and
The processes from to 517 are repeated for the maximum number of types.

On the other hand, in the final processing of step 504, the map data reading processing section 14 creates a type management table in the map data table 10. In the type management tables 41 to 43, as described with reference to FIG. 2B, the required area can be known from the 24 bytes of one record by multiplying the maximum number of types.

If the search classification number has not reached the maximum classification number in the determination processing of step 505, the map data reading processing unit 14 is currently focused on in the map area specified by the display management list from the interface processing unit 15. It means that there is a type that has not been completely checked out of the existing layers, so the processing from step 508 to step 517 is performed.

First, in step 508, the map data read processing unit 14 creates an element management table in the map data table 10. At this point, the element management table is made large enough to store one record of data, and is incremented by one record each time a map element is found in step 510.

In step 509, in the map area designated by the display management list from the interface processing section 15, the data relating to the map element belonging to the search layer and the search type which is currently focused is the map data 30.
Check to see if it exists. For example, when the search layer number is 0002 and the search type number is 0001, the layer of current interest is transportation as shown in FIG. 3 (a), and the type code 0001 in transportation is road as shown in FIG. 3 (b). Therefore, the map data reading device 14 checks whether or not the map element data regarding the road exists in the map data 30 in the area designated by the display management list.

This operation depends on the data storage format of the map data 30. Here, the processing for the map data shown in FIG. 9 will be described.

That is, the map data reading processing unit 14
In FIG. 10A, since the classification code for the road in the map data 30 is 040, in FIG.
The location of the data block corresponding to the area specified by the display management list is found from the area management table 801, and the element data having the type code 821 of 040 is searched for in the data block.

If there is corresponding element data, the map data read processing unit 14 creates the shape data table 50 for storing the shape data in the map data table 10 in step 505, and stores the shape data of the map data 30. The data size and the location of the shape data table are read in the shape data table and recorded in the element management table.

Then, in step 511, 1 is set in the type flag corresponding to the type of the layer currently focused on in the search information management table 12, and the focused map element data exists in the map data 30. Is memorized.

Next, at step 512, the map data reading processing unit 14 creates the attribute data table 51 in the map data table 5. The format of the attribute data table 51 to be created can be easily determined by checking the format of the attribute table for each type, as shown in FIG. 4 and the like, from the currently-searched search layer number and search type number.

Next, in step 512, the map data 30 is accessed to read out the attribute data of the map element currently being noticed. For example, when the search layer number is 0002 and the search type number is 0001, the layer of current interest is transportation as shown in FIG. 3A, and the type code 0001 in transportation is road as shown in FIG. 3B. Therefore, when the map data 30 includes road map element data in the area specified by the display management list, the map data read processing unit 14 checks the attribute information added to this map element. Become. This operation depends on the data storage format of the map data 30. Here, processing for the map data described in FIG. 9 will be described. That is, the map data reading processing unit 14 is configured as shown in FIG.
In (a), since the type code for the road in the map data 30 is 040, the location of the data block corresponding to the area specified in the display management list is found from the area management table 801 in FIG. , Element data whose type code 821 is 040 is searched for. Next, according to the attribute information start address 826, the attribute data in the attribute information file 806 is drawn to check whether or not the attribute value defined in the attribute code information table 323 corresponding to the road in FIG. 4 is set.
That is, since the name and road type are defined in the attribute code information table 323, in the attribute file 806,
If there is name and road type attribute data, the data can be read and set.

That is, at step 512, the map data reading processing unit 14 creates an attribute data table for storing the attribute data in the map data table 10, reads the attribute data from the map data 30 into the attribute data table, and reads the data. Record the size and location of the attribute data table in the element management table. At this time, if there is no attribute data of the map element currently focused on in the map data 30 in step 512, the map data table 1
An attribute data table for storing the attribute data in 0 is created according to the code information, but -1 is set for the item of the attribute data that could not be read.

Then, in step 513, 1 is set to the attribute flag corresponding to the item for which the attribute data can be read in the search information management table 12. At this time, step 5
If there is no attribute data of the map element currently focused on in the map data 30 in 12, the search information management table 12
The attribute flag is set to 0 in the corresponding item. Next, in step 514, the area of the element management table is expanded by one record to store the next element data.

Now, returning to step 509, it is checked again whether or not the map element data in the map layer 30 which belongs to the search layer which is the search layer of interest at present is present. If there is no more map element data of interest in the map data 30, no more FFFF indicating the end of the table is stored at the end of the element management table in step 515. Next, in step 516, the type code (the same value as the search type number) of interest, the size and location of the element management table are registered in the type management table. In step 517, the search type number is incremented and the type of interest is updated.

When the processing in steps 508 to 517 is repeated for all the types belonging to the layer of interest in the search layer number by the determination in step 505, the layer management table is currently focused on in step 506. The layer code (the same value as the search layer number), the size and location of the type management table are registered in the layer management table, the search layer number is incremented in step 507, and the layer of interest is updated. Search layer number is step 50
It is checked whether the maximum number of layers is exceeded in 3,
If not exceeded, the same processing is performed after step 504. This process is repeated until the search and the reading of the map data are completed for all the layers.

In FIG. 1, the interface processing unit 15 receives a user's request event from the input device 1 via the operating system 9 to update the display map area and interactively display the searchable items. The interface processing unit 15 internally has a display management list 18 for storing the currently displayed map area,
It owns a search request list 19 in which search request contents determined by interactive selection of search items with the user are stored. The display management list 18 has, for example, a data storage format as shown in FIG. 11, and the left edge longitude 1001, right edge longitude 1002, and upper edge latitude 1 on the currently displayed map.
The values of 003 and bottom latitude 1004 are stored. On the other hand, the search request list 19 stores information about the search request selected by the user. The search request is composed of four pieces of information of layer, type, attribute, and attribute condition, and a value that meets the code value or attribute value condition described with reference to FIGS. 3 and 4 is set. The search request list 19 is shown in FIG.
Take the data storage format as shown in 2 and use layer code 1
101, a type code 1102, an attribute code 1103, and an attribute value 1104 are stored. Here, the search request list 1
The value 9 is filled in the order of the layer, the type, the attribute, and the attribute condition, but the search processing request may be issued before the setting is completed. At this time, -1 is set to the item whose value is not filled, and the item is not limited to any item.

From input device 1 to interface processing unit 15
The user request event sent to the map display device activation request, display area update request, search item display request,
There are four search processing requests. Interface processing unit 15
Issues an instruction to appropriate processing or each processing unit in response to these requests. Here, the request event has a data format as shown in FIG. 13, for example, and is defined for each of the map display device activation request, the display area update request, the search item display request, and the search processing request as shown in FIG. The event code and the event attribute value are stored in each item.

7 and 8 show the interface processing unit 15
The operation of is explained. Interface processing unit 1
There are some tools or library packs on the market for interactive processing with the user in 5, and the input device 1, that is, basic processing related to the graphical user interface (for example, application studio provided by Microsoft Corporation). Therefore, basic graphical user interface processing in the interface processing unit 15 and the input device 1 will be realized using these tools.

In the following, a search is performed while interacting with a map and a means (search information management table) for notifying the user what search items can be set for the currently connected map data 30. It is about means for setting items.

The interface processing unit 15 executes step 60.
1, the process is started by a request to activate the map display device sent from the input device 1 via the operating system 9.

The processing from step 602 to step 604 is for initializing the map display device.

First, in step 602, the interface processing unit 15 has its own display management list (table) 1
The initial display area is set to 8 and in step 603,
The data in the display management list 18 is passed to the map data reading processing unit 14 so that the map data of this area is read from the map data 30 into the map data table 10, and a read command is issued.

When the notification that this command is completed is received from the map data read processing unit 14, the interface processing unit 15 issues a map display command to the map data display processing unit 16 in step 604. When the notification that the display command is completed is received from the map data display processing unit 16, the initial setting of the map display device is completed, and the interface processing unit 15 waits for a request event from the input device 1 in step 605.

When the request event from the input device 1 is sent to the interface processing section 15, the interface processing section 15 analyzes the request event in steps 606 and 607.

If the request event is a display area update request, the interface processing unit 15 moves to the processing of step 608, and if it is a search item display request, it moves to step 610. If the request event is any other request event, the request event is ignored and the process returns to the step 605 waiting for the request event.

If the request event is a display area update request, the interface processing unit 15 adds the attribute value of the display area update request event, that is, the offset value corresponding to the upper, lower, left and right to the value in the display management list 18 in step 608. The display area data of the display management list 18 is updated.

The attribute value of the display area update request event is set by the input device 1 in a timely manner. Next, the data in the display management list 18 is passed to the interface processing unit 15 and the map data reading processing unit 14, and a read command is issued. As a result, the map data reading processing unit 14 reads the map data covering the new area from the map data 30 into the map data table 10 and updates the data in the map data table 10 and the search information management table 12.

By this operation, it is possible to deal with the case where the searchable item changes depending on the target map area. When the notification that the reading command is completed is received from the map data reading processing unit 14, the interface processing unit 15
Issues a map display command to the map data display processing unit 16. When the notification that the display command is completed is received from the map data display processing unit 16, the interface processing unit 15
Returns to the state waiting for the request event in step 605.

On the other hand, if the request event is a search item display request, the interface processing unit 15 proceeds to step 610.
5, all searchable layer codes registered in the layer code 401 shown in FIG. 5 are read by referring to the search information management table 12, and read from the correspondence table of the layer code information table 301 in the code information table 11. The name that the layer code means is read out, and this is displayed as a search menu on the display device 2 as a searchable layer name.

Next, since the searchable layer name is selected from the input device 1, the map data display processing section 16 reversely displays the corresponding searchable layer name, and the searchable layer selected by the user is displayed. Give your name clearly. Basic processing related to the graphic user interface is realized by utilizing some specialized tools already provided as described above. Next, the layer code value corresponding to the selected searchable layer name is set in the layer code area 1101 of the search request list 19 (see FIG. 12), and the user sent through the input device 1 by steps 611 and 613. Identify request events for.

If the request event is a search processing request, it is recognized in step 611, and the interface processing unit 15
Performs the processing of step 612.

At step 612, the search request list 19
The inside data is passed to the map data display processing unit 16 to specify a map element to be emphasized and displayed, and then a display command is issued to the map data display processing unit 16.

In this case, since only the selected layer code is stored in the search request list 19, the map data display processing unit 16 causes the map data display processing unit 16 to store all map elements (shape data and shape data) of all types included in the layer. Attribute data such as name)
Is taken out from the map data table 10 and highlighted.

The highlighting can be performed by, for example, displaying the designated map element in a blinking manner or by emphasizing the color. When the interface processing unit 15 receives the instruction end notification from the map data processing unit 16, step 605
Then, the process returns to the state of waiting for the request event again.

If the request event is a search item display request, it is recognized in step 613, and the interface processing section 15 performs the processing of step 614. Step 61
In step 4, in the searchable layer name selected in step 610, the search information management table 12 finds a searchable type name among the types grouped in this layer.

That is, with the layer code in the search request list 19 as a key, the type name in which the type flag 403 is set to 1 in the type code 402 corresponding to the layer code 401 is displayed as a search menu. Notify users that they can search.

Next, since the searchable type name is selected from the input device 1, the map data display processing section 16 reversely displays the corresponding searchable type name, and the search selected by the user. Tell the name of the possible category.

As described above, some basic tools are provided for the basic processing related to the graphic user interface, and these tools are utilized to realize the basic processing.

Next, the type code value corresponding to the selected searchable type name is set to the type code area 1 of the search request list 19.
102, step 615 and step 617
Thus, after that, the user's request event sent through the input device 1 is identified.

If the request event is a search processing request, it is recognized in step 615 and the interface processing unit 15
Performs the processing of step 616. In step 616, the data in the search request list 19 is passed to the map data display processing unit 16 to specify the map elements to be emphasized and displayed, and then a display command is issued to the map data display processing unit 16.

In this case, since the selected layer code and type code are stored in the search request list 19, the map data display device 2 stores all the map elements of the type in the layer in the map data table 10. Will be highlighted and highlighted. For highlighting, for example, a designated map element is displayed by blinking, or the color is emphasized. When the interface processing unit 15 receives the instruction end notification from the map data display processing unit 16, the interface processing unit 15 proceeds to step 605 and returns to the state of waiting for a request event.

If the request event is a search item display request, it is recognized in step 617, and the interface processing section 15 performs the processing of step 618. Step 61
In step 8, in the searchable type name selected in step 614, the search information management table 12 finds an attribute name for which conditions can be set among the attribute information associated with this type.

That is, using the layer code and the type code in the search request list 19 as a key, the layer code 401
And the corresponding attribute code 404 from the type code 402
Among them, the attribute name whose attribute flag is set to 1 is displayed to inform the user that these attribute items can be searched.

Next, since the searchable attribute name has been selected from the input device 1, the display processing unit 16 highlights the corresponding searchable attribute name and the user selects the searchable attribute name. Make a name. As mentioned above, some basic tools are provided for the basic processing of this graphic user interface.
Realize by utilizing these tools.

Next, the attribute value condition corresponding to the selected searchable attribute name is displayed, the settable attribute values are displayed, and the user is allowed to select the attribute value. The attribute code corresponding to the selected searchable attribute name is the attribute code area 110 in the search request list 19 and the attribute value is the value.
2 and the attribute value area 1103.

Thereafter, in step 619, a search processing request event is waited for, and when this event is input, step 6
At 20, the interface processing unit 15 passes the data in the search request list 19 to the map data display processing unit 16 and specifies the map element to be displayed in an emphasized manner. Then, this is taken out from the map data table 10 to display the map data. A display command is issued to the processing unit 16.

In this case, since the selected layer code, type code, and attribute code and their attribute values are stored in the search request list 19, the map data display processing unit 16 indicates the specified type in the specified layer. Of the map elements, only those map elements whose attribute values match will be highlighted. For highlighting, for example, a designated map element is displayed by blinking, or the color is emphasized. When the interface processing unit 15 receives a command end notification from the map data display device 15, the interface processing unit 15 proceeds to step 605 and returns to the state of waiting for a request event.

15 to 18 are examples of operations as seen from the user of the map display device. In FIG. 15, the map display device is implemented by a pen-touch type personal computer capable of pen input, and includes an input / output liquid crystal display 1401 and a pointing device 1402.

In FIG. 16, when the map displayed on the liquid crystal display is double-clicked by the pointing device, a menu 1403 showing the searchable layer names is displayed. The searchable layers include the background item 1404 and the transportation item 1405. , The user is notified that there is a public facility item 1406. Of these, public facility items 1406
When is clicked with the pointing device, the display is reversed and the public facility layer is selected. Further, when the public facility item 1406 is double-clicked with the pointing device, a menu 1410 of type names grouped in the public facility layer is displayed as shown in FIG. 17, and the searchable types are city hall 1421, school 1422, hotel 14
23, Park 1424 is announced.

Then, when the hotel 1423 is clicked with the pointing device, the display is reversed to notify that the hotel type has been selected. Furthermore, when the hotel item 1306 is double-clicked with the pointing device, a searchable attribute value menu 1331 associated with the hotel is displayed, showing that the attribute values that can be set as conditions include a charge 1432, half board 1433, and a parking lot 1434. There is.

Then, when the charge 1432 is clicked, the attribute value setting condition menu 1341 is displayed and the charge is 700
It is shown that any one of 0, 8000 and 10000 can be set as the search condition. If you select 7000 with the pointing device, the charge attribute will be 7000.
Is set. Next, when the map displayed on the liquid crystal display is double-clicked by the pointing device, the search process is started, and the hotel with a charge of 7000 is searched, and the corresponding hotel 14 as shown in FIG. 18 is searched.
51 to 1453 are displayed in black.

[0140]

According to the first aspect of the present invention, even if various map data having different purposes of use or the map is divided into a plurality of pieces, each map data is connected to each piece of map data. The user can hierarchically display a menu of search items based on the attributes that match the contents (map elements) of the item, and the user can search for the corresponding map element from the attributes according to the search items. Therefore, the rationalization of search and versatility can be improved.

According to the second invention, in addition to the above effects,
The map data table on the side of the main body of the map display device can use a unified one that does not depend on the format of the map data in the external storage medium, so that the versatility of the map display device can be further enhanced.

According to the third aspect of the invention, the map element to be searched from the attribute can be flexibly picked up according to the upper to lower hierarchical levels, so that the search request range of the map element based on the attribute can be widened. .

According to the fourth invention, the user can easily set the search condition even when inputting the hierarchical search condition.

[Brief description of drawings]

FIG. 1 is an overall configuration diagram showing an example of an embodiment of the present invention.

FIG. 2 is a diagram illustrating a storage format example of various management tables and data tables created in the map data table in FIG.

FIG. 3 is a diagram illustrating various code information tables managed by the code information table in FIG.

FIG. 4 is a diagram illustrating various code information tables managed by the code information table as in FIG.

5 is a diagram illustrating a search information management table in FIG.

6 is a flowchart showing an operation of a map data reading processing unit in FIG.

7 is a flowchart showing the operation of an interface processing unit in FIG.

FIG. 8 is a view showing a continuation of the flowchart of FIG.

9 is a diagram illustrating an internal configuration of map data in FIG. 1. FIG.

10 is a diagram illustrating an internal configuration of map data in FIG.

11 is a diagram illustrating a format of a display management list in FIG.

12 is a diagram illustrating the format of a search request list in FIG.

FIG. 13 is a diagram illustrating a format of a request event.

FIG. 14 is a diagram illustrating code correspondence of a request event.

FIG. 15 is a diagram illustrating a usage example of the map display device.

FIG. 16 is a diagram illustrating an example of use of the map display device.

FIG. 17 is a diagram illustrating a usage example of the map display device.

FIG. 18 is a diagram illustrating an example of use of the map display device.

[Explanation of symbols]

1 ... Input device, 2 ... Display device, 5 ... Main memory device, 6 ... Data reading device, 10 ... Map data table, 11 ...
Code information table, 12 ... Search information table, 14 ...
Map data read processing unit, 15 ... Interface processing unit, 16 ... Map data display processing unit, 40 ... Layer management table, 41-43 ... Type management table, 45-47.
Element management table, 50 ... Shape data table, 51 ...
Attribute data table.

 ─────────────────────────────────────────────────── ─── Continued Front Page (72) Inventor Kozo Nakamura 7-1, 1-1 Omika-cho, Hitachi-shi, Ibaraki Hitachi Ltd. Hitachi Research Laboratory

Claims (4)

[Claims] 1. A map display device that sets an external storage medium storing map data in a map data reading device, reads the requested map data, and displays the map data on a screen. This search item list is prepared on the device side, and this search item list is attached to the search items and search items of the hierarchy created based on the attributes of the map element so that the corresponding map element can be searched hierarchically from the attribute. It is managed by the search information management table with the flag field described above, and whether or not the map data read from the external storage medium contains the content corresponding to the search item, that is, whether or not the corresponding map element exists. And the map data reading processing unit that records the survey result in the flag field of the search item list, and the display of the search menu for the map data. Upon request,
By referring to the search item list stored in the search information table, the search items having contents are hierarchically displayed on the screen in an expression format for notifying the user, and there is a request for disclosure of a desired search item through this search menu. And a map data display processing unit that searches for map elements that match the search conditions from the read map data and selects or highlights them on the map displayed on the screen. apparatus. 2. An external storage medium storing map data is set in a map data reading device, the requested map data is read and displayed on a screen, a map data search item list is displayed on the map display device. This search item list is prepared on the device side, and this search item list is attached to the search items and search items of the hierarchy created based on the attributes of the map element so that the corresponding map element can be searched hierarchically from the attribute. The external storage is managed by a search information management table including a flag field and a management table group having a hierarchical structure for storing the data necessary for searching the map data and the map element data to be searched. A map data table for constructing a unique map data storage format independent of the map data storage format of the medium, and the map data table Of a code information table having information to be used as a guide for creating a management table group for a file, and whether or not the map data read from the external storage medium contains the content corresponding to the search item, that is, whether the corresponding map element exists or not. Then, the survey result is recorded in the flag column of the search item list, and the management table group is created by using the information of the code information table as a guide, and the map elements of the read map data are arranged. When there is a request to display a search menu for map data and a map data read processing unit to be stored in a predetermined management table,
By referring to the search item list stored in the search information table, the search items having contents are hierarchically displayed on the screen in an expression format for notifying the user, and there is a request for disclosure of a desired search item through this search menu. And a map data display processing unit for extracting a map element that matches the search condition from the information in the management table group of the map data table and selecting or highlighting it on the map displayed on the screen. Map display device. 3. An attribute of a map element constituting map data in a map display device which sets an external storage medium storing map data in a map data reading device, reads the requested map data and displays it on a screen. Based on
The lower hierarchical search items are created in advance, and the upper and lower search item data are managed so that they can be sequentially and hierarchically displayed on the screen by the input operation of the search menu display request. In the search item of the hierarchy, the map element data according to the hierarchy level is associated and stored in the management table group, and no matter which search item of the hierarchy is input the disclosure request A map display device characterized in that map elements are searched and selected or highlighted on a map displayed on a screen. 4. An attribute of a map element constituting map data in a map display device which sets an external storage medium storing map data in a map data reading device, reads the requested map data and displays it on a screen. Create a hierarchical search item to search the corresponding map element from the attribute based on, and set all the search item hierarchically as the search menu on the pen-touch screen Then, the search item name of the hierarchy displayed in this menu constitutes the search condition input part of the pen touch, and by consistently selecting the search item name across all the layers through this search condition input part of the pen touch, A map display device, which allows a user to input search conditions that do not require character creation.