JP4063342B2 - Map information storage system - Google Patents

Description

[0001]
[Industrial application fields]
In the present invention, there is map data in which symbolized data representing the shape of an object on the map, coordinate sequence data representing the position of the object, and the like, and data representing the material of the object on the map are present. The present invention relates to a map information storage system having attribute data.
[0002]
[Prior art]
FIG. 5 is a diagram showing a conventional map information management method disclosed in, for example, “Map data attribute data unified management method” of Japanese Patent Laid-Open No. 2-85963.
In the figure, (a) is an example of storing attribute data 51 in a tabular database, and (b) is an example of storing map data 52 in a tabular database.
In the attribute data 51, the ID 53 is an identifier uniquely assigned to each thing on the map. The attribute 54 corresponds to an item of attribute data, and indicates information such as the height of an object on the map, the construction year, and the contractor.
On the other hand, in the map data 52, the ID 55 corresponds to the ID 53 of the attribute data 51, and the sub-ID 56 indicates the order relationship of records when the information of a certain ID 55 is divided so that it can be stored in a fixed-length record. It represents.
The graphic data 57 corresponds to the ID 53 of the attribute data 51. The symbol data 61 represents the type of each object as a graphic, the coordinate string data 62 indicates the position by coordinates, and the text indicates the location, etc. It consists of data 63. The graphic data 57 is a fixed-length storage area and stores the symbol data, coordinate string data, and text data described above in a record for each data.
[0003]
Next, details will be described.
In the map data 52, the graphic data 57 relating to ID = 1 stores the sub ID 56 in a fixed length in the order of 1, 2, and 3. The number of records 58 indicates how many records the graphic data 57 in one ID is composed of, so that it is possible to know what the final number of the sub ID 56 is for one ID 55. it can.
That is, for example, since the number of records 58 is 3 for the thing of ID = 1, it can be seen that the information of the graphic data 57 is stored in total of 3 records.
Further, in the map data 52, the graphic data 57 has a fixed storage area and the record to be stored differs depending on the type of data. Therefore, when the information actually stored is shorter than the record length of the graphic data 57, As shown in the figure, an empty space 59 is created at the end of the information.
Thereby, it turns out that the full length of figure data changes for every thing.
An example will be described with reference to FIG.
FIG. 6 is a diagram showing an example of graphic data storage in a conventional map information management method.
For example, the total length of the graphic data of the thing with ID = 1 is 190 bytes. Here, symbol data, coordinate string data, and text data exist without a break. For example, when this is stored in a record having a fixed length of 80 bytes, the symbol data, the coordinate sequence data, and the text data are stored in separate records, respectively, so that the stored data has a record length of 80 If it is less than a byte, there will be a free space after the record.
[0004]
[Problems to be solved by the invention]
In a conventional map information storage system, graphic data having different lengths for each thing is stored as fixed-length records in map data, and graphic data for one ID is managed as a collection of a plurality of records.
In particular, when storing a plurality of coordinate sequence data for one thing, or storing a plurality of types of information such as coordinate sequence data, symbol data, and text data as graphic data corresponding to one ID, a plurality of records Need. For this reason, it is necessary to control the order relationship of a plurality of graphic data records in the same ID based on the map data sub-ID and the number of records. In addition, search, addition, change, and deletion of records are complicated, and it is difficult to manage the map data flexibly.
[0005]
The present invention has been made to solve the above-described problems, and an object of the present invention is to centrally manage a plurality of pieces of information representing one thing on a map in a map information storage system.
[0006]
[Means for Solving the Problems]
Map information storage system according to the present invention, the table and the map data representing the things on the map, the map information storage system that stores the attribute data representing the things of the attributes on the map, and the map data and the attribute data In addition to storing in the format database, the area for storing the map data is a variable length area,
If the same kind of a plurality of objects in one plane positions exist, the tabular database, as part of the map data, ID uniquely identifying as one thing on the map a plurality of objects, the A graphic data representing the type and number of the object as the object is stored in association with the ID, and each of the plurality of objects is used as one attribute data of the object to identify the ID and the object. The ID and the height at which the object exists corresponding to the ID and the sub-ID are stored as a part of the attribute data .
[0011]
[Action]
The map information storage system according to the present invention includes a sub-ID that associates one piece of information corresponding to a plurality of things on the map in the attribute data, thereby storing the attributes of the plurality of things in the attribute data. Information on things can be stored in one record in map data .
[0014]
【Example】
Example 1.
An embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing attribute data and map data in one embodiment of the present invention.
In FIG. 1, (a) is an example of storing attribute data 11 in a tabular database, and (b) is an example of storing map data 12 in a tabular database.
In the attribute data 11, ID 13 is an identifier uniquely assigned to each thing on the map. The attribute 14 corresponds to an item of attribute data, and indicates information such as the height of an object on the map, a construction year, and a contractor.
On the other hand, in the map data 12, ID 15 corresponds to ID 13 of the attribute data 11. The graphic data 17 is a variable-length storage area that stores the type, position, location, and the like of each thing as symbol data, coordinate string data, and text data. As shown in the figure, the data length information of the symbol data, the coordinate string data, and the text data is stored in the graphic data corresponding to each data.
[0015]
In the conventional example, since the graphic data 12 is a fixed length area, the symbol data, the coordinate string data, and the text data are stored in separate records. However, in the present invention, since the graphic data 12 is a variable-length area, symbol data, coordinate string data, and text data corresponding to one thing can be stored in one record.
[0016]
A method for accessing the map data 12 will be described.
The map data 12 is accessed by searching one record of graphic data of one thing using ID15 as a key. In the map data 12, the data length of each record is managed for the variable length area of the graphic data 17, and the record can be searched by the set of the data length and the data portion.
Furthermore, addition, change, and deletion of the map data 12 can be flexibly handled in units of records in the tabular database.
[0017]
Example 2
In the above embodiment, a case where a plurality of graphic data (symbol data, coordinate string data, text data) are stored together in one record of a variable length area has been shown. An example in which a plurality of records of graphic data for one thing is stored with an ID added will be shown below.
FIG. 2 is a diagram of attribute data and map data to which a sub ID is added according to another embodiment of the present invention.
2A shows an example of storing attribute data 21 in a tabular database. ID23 is an identifier uniquely assigned to each thing on the map. The attribute 24 corresponds to an item of attribute data, and indicates information such as the height of an object on the map, a construction year, and a contractor.
(B) is a storage example of the map data 22 in the same table format database. The ID 25 corresponds to ID 23 of the attribute data 21, and the graphic data 27 stores information such as coordinate string data, symbol data, and text data corresponding to one thing. The graphic data area of each record has a variable length. The data length information is assumed to be stored in the same manner as in FIG. 1, but is omitted from the drawings in the following embodiments.
The sub ID 26 is assigned to make each record of a plurality of graphic data for one thing on the map unique. As shown in FIG. 2, the sub-ID 26 does not indicate the record storage order relationship as in the prior art. Therefore, the sub ID 26 does not have to be a serial number. As a result, the control of the sub ID 26 itself is not complicated.
For example, in FIG. 2, the thing with ID = 1 corresponds to two records with sub ID = 1 and sub ID = 10 in the map data 22.
[0018]
The map data 22 can be searched for a plurality of graphic data 27 (multiple records) using ID25 as a key, and only one graphic data 22 (one record) is searched using ID25 + sub-ID26 as a key. It is also possible.
Furthermore, addition, change, and deletion of records in the map data 22 can be flexibly handled in units of records in the tabular database by using ID25 or ID25 + sub-ID26 as a key.
[0019]
A usage example of the sub ID 26 will be described.
For example, it is assumed that the name of the person in charge of investigating a matter is stored as information in the graphic data record of sub ID = 10. However, it is assumed that this information is eventually unnecessary (for example, when the system is completed). In that case, the sub ID of the record in which the name of the person in charge of the investigation is stored determines the ID number as “10” for any record of the matter, and when the system is completed, ID + sub ID “10” is set. As a key, it is possible to delete records in a batch. Further, depending on how the database index is held, a method of deleting all at once using only the sub ID “10” as a key is also possible.
[0020]
In addition, it is effective when batch processing is performed, for example, a comment that is not necessary for actual processing is attached with a sub-ID to be an independent record.
Furthermore, in any of the symbol data, coordinate data, and text data, it is possible to attach a sub ID as one record and store it in the map data as a plurality of records for one thing.
[0021]
Example 3
Another embodiment of the present invention will be described below with reference to the drawings.
FIG. 3 is a diagram of a map example showing things related to other things in another embodiment and map data having related data.
In FIG. 3, (a) is a map example, and each figure of ID = 1 to ID = 6 represents an object on the map. (B) is a storage example of the map data 32 in a tabular database.
(A) In the map example, each figure has an ID, which is an identifier uniquely assigned to each thing on the map, and has a relationship with a plurality of things. On the other hand, in the map data 32, ID 35 corresponds to the ID of a thing in the map example of (a). The graphic data 37 stores symbol data corresponding to one thing, and the area of the graphic data 37 of each record has a variable length.
Related data 1 and 38 and related data 2 and 39 show identifiers of other things related to one thing.
[0022]
(A) In a map example, when figures are grouped (like figures with IDs of 5 and 6), the thing has the ID of the parent in the group and is stored in the related data 1 and 38. The If it is a parent graphic (such as a graphic with IDs 1 and 2), its own ID is stored as related data 1.38. In addition, when the figure is adjacent to two figures or straddles two figures (such as a figure with IDs 3 and 4), both figures of the figure (ID is 1). 2) is stored in the related data 1.38 and the related data 2.39.
[0023]
In the present embodiment, it is possible to know the IDs of the figures in the group having the same parent only by searching the contents of the related data 1 • 38 or the related data 2 • 39 in the map data 32. In addition, when searching the graphic data 37 of the map data 32, it is possible to easily add, update, and delete records of the graphic data 37 without being aware of the presence or absence of other graphics in the same group.
[0024]
Example 4
Another embodiment of the present invention will be described below with reference to the drawings.
FIG. 4 is a diagram showing attribute data having a sub ID and map data in another embodiment.
4A is a storage example of the attribute data 41 in the tabular database, and FIG. 4B is a storage example of the map data 42 in the same tabular database.
In the attribute data 41, ID 43 is an identifier uniquely assigned to each thing on the map. The attribute 48 corresponds to an item of attribute data, and indicates information such as the height of an object on the map, a construction year, and a contractor. Furthermore, when one thing on a map represents a some attribute, it identifies with sub ID44.
On the other hand, in the map data 42, ID 45 corresponds to ID 43 of the attribute data 41. The graphic data 47 stores a plurality of types of information such as coordinate string data, symbol data, and text data corresponding to one thing, and is a variable-length storage area.
[0025]
In the present embodiment, a plurality of records for things having a plurality of information can be stored as attribute data.
In the attribute data 41, it is possible to search a plurality of records for one thing using the ID 45 of the map data 42 as a key, and obtain a plurality of attributes of the thing.
In addition, addition, update, and deletion of records in the attribute data 41 can be flexibly handled using ID 43 + sub ID 44 as a key.
[0026]
An example in which the attribute data 41 has a plurality of records corresponding to one thing will be described.
For example, when multiple transformers are attached to one utility pole, as the attribute data indicates as information on each transformer, the height at which the transformer is installed, the construction year, and the contractor are different. Information. Therefore, there are a plurality of records indicating attributes.
However, in the graphic data, since there is only one symbol data that expresses the transformer in a graphic form, as shown in the map data, the content of the record with ID = 2 is “two transformers are attached to the power pole. ", And it will be summarized in one record.
[0027]
As described above, even if the attribute data 41 includes a plurality of records, the record of the graphic data 47 of the map data 42 corresponds to one thing and does not become a plurality. Therefore, in this case, duplication of records having the same contents for one thing in the map data can be avoided.
[0028]
Example 5 FIG.
In the first embodiment, the case where the information stored in the graphic data which is the variable-length area is in the order of the symbol data, the coordinate string data, and the text data is shown, but the order of storing may be other order.
In addition, although three types of information, symbol data, coordinate string data, and text data, have been described, other types of information may be stored.
[0029]
Example 6
In the first embodiment, the height, the construction year, and the contractor are listed as the attribute items of the attribute data. However, other items may be used as the attributes.
[0030]
Example 7
In the second embodiment, an example of a record that stores a person-in-charge name as one of a plurality of records when the graphic data is a plurality of records has been described, but the content stored in the plurality of records is not particularly limited to this.
[0032]
【The invention's effect】
Since the map information storage system according to the present invention includes association data in attribute data, information on a plurality of things can be collected in one record in the map data. Attribute data can be assigned, and unified management of attribute data and map data becomes possible .
[Brief description of the drawings]
FIG. 1 is a diagram showing attribute data and map data in an embodiment of the present invention.
FIG. 2 is a diagram of attribute data and map data to which a sub ID is added in another embodiment of the present invention.
FIG. 3 is a diagram of a map example showing things related to other things in another embodiment and map data having related data.
FIG. 4 is a diagram showing attribute data having a sub ID and map data in another embodiment.
FIG. 5 is a diagram showing a conventional map information management method;
FIG. 6 is a diagram showing an example of graphic data storage in a conventional map information management method;
[Explanation of symbols]
11 attribute data, 12 map data, 13 ID, 14 attributes, 15 ID, 17 graphic data (variable length area).

Claims (1)

A map data representing the things on the map, the map information storage system that stores the attribute data representing the things of the attributes on the map, and the map data and the attribute data stores in a table format database, the map data The area for storing
If the same kind of a plurality of objects in one plane positions exist, the tabular database, as part of the map data, ID uniquely identifying as one thing on the map a plurality of objects, the A graphic data representing the type and number of the object as the object is stored in association with the ID, and each of the plurality of objects is used as one attribute data of the object to identify the ID and the object. map information storage system ID and, wherein memorize to Rukoto a height above ID and is allowed to the object corresponding to the sub-ID is present as part of the attribute data.

Images