JPH0259969A - Multimedia data management system - Google Patents

Abstract

PURPOSE:To easily and unitarily manage shape and spatial information and attribute information related to one thing by managing the shape and spatial information by a buffer chain having a fixed length and giving attributes for respective units of things to a relation data base. CONSTITUTION:Thing information is stored in a graphic master file 1 expressed with vectors using coordinate values and a picture data file 3 expressed with dots and managed by the buffer chain having the fixed length. Further, the attribute information is expressed with codes and character data and stored in an attribute data file 2 tupling an object and attributing the classifications of the attributes. These three types of data are linked by an identifier to identify the thing, and the relations between the things are expressed with a data structure having the pointering format of a fixed-length buffer with the identifier as its object. Thus, graphic data, picture data, and attribute data can be easily unitarily managed, and data management and data access can be executed unitedly.

Description

[Detailed Description of the Invention] [Industrial Application Field] This invention relates to graphical data and image data representing the shape and spatial information of objects included in drawings such as maps, and attribute information representing the nature of the meaning, content, etc. It is related to the method of managing.

[Prior art] Conventionally, graphical data is represented by vectors using coordinate values,
Attribute data expressed as code or character data and image data expressed as dots each have separate files as shown in Figure 5 due to differences in internal data structure, and the user can define these independently as data files. A method of access was adopted. For this reason, each user program had to create its own data access method, and since the program itself interpreted the data type, the program had to be rewritten for each purpose.

In particular, the relationships between graphic data and attribute data are linked by graphic identifiers as shown in Figure 6, but the relationships between graphic data and image data, and image data and attribute data are organized as neatly as shown in Figure 6. Can not.

[Problem to be solved by the invention] As mentioned above, this type of conventional data management method has the following problems:
Geometric data consisting of two lines and their meanings.

Attribute data representing properties such as content are related by graphic identifiers as shown in Figure 6, but graphic data and image data, and image data and attribute data are not related as shown in Figure 6, so they are each independent. There are problems, such as the fact that a multimedia data structure consisting of three types of data becomes increasingly complex.

This invention was made in order to solve the above-mentioned problems, and provides a multimedia data management system that facilitates the unified management of graphic data, image data, and attribute data, and that enables unified data management and access. The purpose is to obtain.

[Means for Solving the Problem] The multimedia data management system according to the present invention expresses object information on a drawing such as a map using graphic data expressed as a vector using coordinate values and image data expressed as a dot. In addition to managing it with a fixed-length buffer chain, the attribute information is expressed as code or character data and stored in a relational database in which the object is a tuple and the attribute type is a 71 attribute, and these three types are This system connects data and expresses the relationship between objects using a data structure in the form of a fixed-length buffer pointing to an identifier.

[Effect] In this invention, a shape on a drawing such as a map.

By managing spatial information with a fixed-length buffer chain, it is possible to flexibly deal with the diverse shapes and spatial information contents of objects, and by providing attributes for each object in a relational database, it is possible to handle them in mutually independent formats. , it becomes easy to centrally manage shape, spatial information, and attribute information regarding one thing. Furthermore, since a pointer structure is used for identifying the relationship between objects, which is independent of shape, spatial information, and attribute information, logical relationships between objects can be handled in a free format.

[Example] An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing the file system of this method. In the figure, 1 is a graphic master file that stores graphic data expressed as a vector using coordinate values, that is, vector data as a set of coordinate values indicating position data that is shape information of objects on a map, and 2 is a code; An attribute data file 3 stores attribute information expressed in character data, an image data file 3 stores image data in dot representation representing spatial information, and a management file 4 manages and represents relationships between objects.

FIG. 2 is a diagram showing the logical structure of the graphic mask file 1 shown in FIG. 1 above. In the figure, numeral 11 represents an identifier unique to an object, and numeral 12 represents identification of vector data and image data associated with the object and associated attributes. 13.
Coordinate information 14 is a coordinate string of vector data possessed by an object, and is managed in a chain structure. Reference numeral 15 denotes image information, which consists of a data string indicating a pointer to image data when an object has spatial information, and information indicating the structure of the image.

FIG. 3 is a diagram showing the logical structure of the attribute data file 2 of FIG. 1. In the figure, 21 represents an identifier unique to an object, and 22 and 23 are attribute information representing the nature of the object.

FIG. 4 is a diagram showing the logical structure of the management file 4 of FIG. 1. In the figure, 41, 42, and 43 are identifiers unique to things, and logical relationships between things, such as inclusion, are managed in the form of pointers between buffers.

Next, the operation will be explained.

Shape and spatial information about certain objects on the map are stored in a graphic master file 1 and managed in a fixed length buffer chain format shown in FIG. At the beginning of the chain, an object identifier 11, identification of vector/image data as a means of expressing the object, and associated attributes 12 are set, and from there sequentially coordinate information 13, 14/image information 15
Pointing to. By setting the coordinate string using the fixed-length buffer pointer method, it is possible to flexibly deal with the relationship between the variable-length structure that is the coordinate string of position data and the spatial information related to this position data. It can be managed with a chain of fixed-length buffers, and it is possible to set as many chains as there are things.

On the other hand, as shown in FIG. 3, the attribute information of the thing adopts a table format in which each of the attribute items 22 and 23 is an attribute and the thing is a tuple, and has a data structure with the identifier 21 of the thing as a key. That is, a relational database is used for attribute information.

Furthermore, the relationship between objects is managed using a fixed-length buffer pointer structure as shown in FIG. Here, one fixed-length buffer is allocated according to the correspondence between the object identifiers 41, 42, and 43, and the logical relationship is managed using the pointer.

A plurality of pointer areas are prepared by using a predetermined position of a fixed length buffer as a pointer area, and the types of the pointers are provided. By defining relationships for each pointer in this way, you can manage various relationships with pointers. The above-mentioned series of structures for managing relationships between things are stored in the management file 4 shown in FIG.

As described above, for one object, vector data representing shape information, that is, figure data, is stored in the figure master file 1 in Figure 1, attribute information representing properties is stored in attribute data file 2, and image data representing spatial information is stored in the attribute data file 2. is stored in the image data file 3, and the relationship is stored in the management file 4.
The interface between each file is managed using a unique identifier.

In the above embodiment, an example of the relationship in multimedia data management was shown, but since the relationship between vector data representing conventional figures, attribute data consisting of characters and codes, and image data can be easily realized, It has the advantage that it can be used in drawing management and editing systems in which rask vector conversion to data is not possible.

[Effects of the Invention] As described above, according to the present invention, object information is expressed by vector representation graphic data using coordinate values and image data represented by dots, and is managed by a fixed length buffer chain. The attribute information is expressed in code or character data and stored in a relational database where objects are tuples and attribute types are attributes, and these three types of data are connected using identifiers that identify objects, and relationships between objects are established. Since identifiers are expressed using a fixed-length buffer pointer data structure, it is easier to centrally manage graphic data, image data, and attribute data, and data management and access can be performed in a unified manner. This has the effect of reducing input costs for systems that use drawings such as maps, making it possible to construct systems with better cost performance.

[Brief explanation of the drawing]

FIG. 1 is a diagram showing the file system of a multimedia data management system according to an embodiment of the present invention, FIG. 2 is a diagram showing the data storage structure of the graphic master file of FIG. 1, and FIG. Figure 4 is a diagram showing the data storage structure of the attribute data file. Figure 4 is a diagram showing the data storage structure of the management file in Figure 1. Figures 5 and 6 are the file system and the relationship between graphic data and attribute data in the prior art. FIG. 1 is the figure master file, 2 is the attribute data file, 3
is an image data file, and 4 is a management file. Agent Masuo Oiwa (2 idiots) Figure 3 Figure 4 True Figure 5

Claims (1)

[Claims] Object information is expressed as vector representation graphic data using coordinate values and image data expressed as dots, and is managed in a fixed-length buffer chain.At the same time, the attribute information is expressed as code or character data to create tuples, Store it in a relational database that uses the attribute type as an attribute,
Multimedia data management characterized by linking these three types of data using identifiers that identify objects, and expressing relationships between objects using a data structure in the form of fixed-length buffer pointing to identifiers. method.