A method for constructing a field acquisition system based on parameterized constraint data model

Abstract

The invention discloses a method for constructing a field collection system based on a parameterized constraint data model, which includes S1, constructing a framework model of a field collection data model based on a Sqlite database; S2, constructing a field collection data model based on the framework model of the field collection data model using a declarative data model definition tool; S3, compiling and generating a field collection system based on a unified field collection system framework and a field collection data model; S4, when the field collection system collects data, generating a data collection interactive interface according to a data model drive, and realizing the collection data entry, storage management and display. The invention facilitates professionals to quickly define the content of field collection data, and ensures the integrity, professionalism and flexibility of the content of the entity object survey.

Description

Technical Field

[0001] The present invention relates to the technical field of geological data acquisition, and in particular to a method for constructing a field acquisition system based on a parameterized constraint data model. Background Art

[0002] Geological survey is a basic, public welfare and strategic work. It collects and updates basic geological data to provide basic support for economic and social development. As a major responsibility of geological survey, geological survey widely adopts new earth exploration technology and data collection technology to obtain geological information from all directions and angles, conduct regional geological, geophysical, geochemical, remote sensing geological, environmental geological and marine geological surveys, continuously improve the level of basic geological work in my country, and fill in and update basic geological maps.

[0003] Digital field data collection technology is a technology that uses geographic information systems, global satellite positioning systems, remote sensing technologies, etc. to digitally collect and store various geological information obtained from field geological surveys through mobile collection terminals. It has been widely used in geological surveys, changing the traditional field paper records and data storage methods, and improving the efficiency of field data collection.

[0004] With the expansion of the scope of geological survey business work, the traditional way of developing field collection systems by computer personnel is to define field collection data models based on database standards and specifications, and to recode and generate various corresponding data collection interfaces according to the data models. This leads to inconsistent design ideas for field collection systems and field collection data models for different professions, repeated development of basic universal functions between systems, and the need to redevelop data collection interfaces for different entities, resulting in a long development cycle. Especially when the data collection standards and specifications for new business areas have not yet been established, and when the collection content changes with the degree of research, R&D personnel need to readjust the data collection interactive interface. The overall system R&D efficiency is low, and it is unable to support the needs of the collection system in new business areas to quickly respond to changes in business data models. Summary of the invention

[0005] In view of the problem that the traditional field collection system development model mentioned above cannot quickly support the expansion of business field investigation needs, especially when standard specifications, investigation content, and data models have not yet been established, and the field collection system cannot adapt to the data models collected at different stages, the present invention proposes a method for constructing a field collection system based on a parameterized constraint data model.

[0006] To achieve the above object, the present invention provides the following technical solutions:

[0007] The present invention provides a method for constructing a field acquisition system based on a parameterized constraint data model, comprising the following steps:

[0008] S1. A framework model for building a field collection data model based on the Sqlite database;

[0009] S2. Based on the framework model of the field collection data model, the field collection data model is constructed using a declarative data model definition tool;

[0010] S3, compile and generate a field collection system based on a unified field collection system framework and a field collection data model;

[0011] S4. When the field collection system collects data, it generates a data collection interactive interface based on the data model driver, and implements the collection data entry, storage management and display.

[0012] Furthermore, the specific process of step S1 is: facing the field geological survey data collection object, combining the characteristics of geological survey data collection, abstracting the real-world geological survey objects on a two-dimensional plane into three types of element entities: points, lines or surfaces, and summarizing the survey information of a field survey object into element entity information, rendering information, object description information of different specializations and attachment information, and recording each collection object in the geological survey with 1 element entity: 1 seed type: N object information description.

[0013] Furthermore, the framework model includes the MainTable feature class collection table, the TableSet object class collection table, the RelationTable relationship table, the user-defined feature class data table and the corresponding feature class field constraint parameter table, the user-defined object class data table and the corresponding object class field constraint parameter table, the multimedia video table and the multimedia photo table.

[0014] Furthermore, the MainTable feature class collection table defines different types of feature classes, each of which is defined using a feature class data table and a feature class field constraint parameter table; the TableSet object class collection table defines different object classes, each of which is defined using an object class data table and an object class field constraint parameter table; the RelationTable relationship table defines an object class collection corresponding to the feature class subtype in the MainTable table.

[0015] Furthermore, the feature class field constraint parameter table and the object class field constraint parameter table include field names, field Chinese names, field data types, special field types, associated control types and associated control data contents.

[0016] Furthermore, in step S2, the step of constructing a field collection data model includes:

[0017] S21. Create a data model file with parameterized constraints to form a data model framework;

[0018] S22. Create feature classes, and define the Chinese name, English name, status, type, feature class fields and constraint parameters of each feature class;

[0019] S23, creating object classes, and defining the name, alias, type, object class fields and constraint parameters of each object class;

[0020] S24. Define the object class set corresponding to the feature class subtype in the RelationTable relationship table, including the name of the feature class, the name of the subtype, the feature class storage subtype field and the ID set of the management object class.

[0021] Furthermore, in step S3, the field collection system framework includes a task creation and management module, a task data map browsing module, a survey object data collection module, and a general auxiliary tool module.

[0022] Furthermore, step S4 specifically includes:

[0023] S41, using the field collection data model file as a template, creating a field survey task and adding it to the task management list, generating a field collection data model file identical to the collection data model in the created task folder, and naming it with the task name;

[0024] S42. Click the field survey task in the task management list, create a display layer of the feature class with the same name as the feature class in the map view based on the feature class and the feature class constraint parameters defined in the MainTable in the data model, determine the type of the feature class display layer according to the defined type constraint parameters of the feature class, read the feature data one by one from the corresponding feature class data table according to the feature class name, create a feature display entity according to the feature class type and the coordinate information in the feature data, add it to the display layer, render it according to the feature rendering parameters defined in the feature class data table, and then control whether the corresponding display layer is displayed according to the display status of the feature class;

[0025] S43. On the basis of opening the task, click the feature entity add button to add the corresponding feature entity on the map and obtain the entity coordinate information. Then, use the technical method of data model driven information collection interactive interface generation to generate a data collection interactive interface based on the task data model, complete data collection, and save the collected data to the corresponding feature data table.

[0026] Furthermore, in step S43, the process of generating the data collection interactive interface includes:

[0027] S431, adding a feature object defined by the currently edited feature class to the map;

[0028] S432, after the element drawing is completed, a feature data collection interactive interface is generated based on the feature class field constraint parameter table;

[0029] S433, input feature class attribute information, select the subtype to which the current feature belongs, and save the collected data into the feature data table;

[0030] S434, generating a feature object class association interaction interface based on the subtype to which the selected feature belongs and the object class set associated with the feature class subtype defined in the RelationTable;

[0031] S435, selecting the name of the object class to be entered in the feature object class association interaction interface;

[0032] S436, generating an object class data collection interactive interface based on the selected object class and the field constraint parameter table corresponding to the object class;

[0033] S437, the object class data collection is completed, click Save to save the object class collection data to the corresponding object class data table, and return to the feature object class association interaction interface;

[0034] S438. Repeat the above steps to complete the collection and storage of multiple survey objects in the field.

[0035] Based on the above technical solution, the embodiments of the present invention can at least produce the following technical effects:

[0036] The method for constructing a field collection system based on a parameterized constraint data model provided by the present invention proposes a parameterized constraint data model framework model for field surveys, describes entities with parameterized constraints in the manner of 1 entity: 1 subtype: N object classes, and uses a Sqlite lightweight database to realize unified storage and management of field collection data models and constraint parameters, so as to facilitate professionals to quickly define the content of field collection data, and ensure the integrity, professionalism and flexibility of the entity object survey content. At the same time, the system generates a data collection interactive interface based on the data model drive, and can quickly respond to changes in the data collection model without programming to modify the system, greatly shortening the system development cycle, improving research and development efficiency, and meeting the needs of the system changing rapidly with changes in the data collection model. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying creative work.

[0038] Figure 1 It is a data model framework model diagram of the present invention;

[0039] Figure 2 It is a frame diagram of the data collection and storage of the survey object of the present invention;

[0040] Figure 3 It is a relationship diagram between the data table of the object class of the present invention and the constraint parameter table;

[0041] Figure 4 It is a data model definition flow chart of the present invention;

[0042] Figure 5 It is a database model framework diagram of an embodiment of the present invention;

[0043] Figure 6 It is a field structure diagram of an element data table according to an embodiment of the present invention;

[0044] Figure 7 It is a data diagram of a feature class field constraint parameter table according to an embodiment of the present invention;

[0045] Figure 8 It is the overall framework diagram of the field collection system of the present invention;

[0046] Fig. 9 It is a constraint relationship diagram of the feature class and constraint parameter definitions in task loading and display of the present invention;

[0047] Fig.10 It is a flow chart of the present invention for generating data collection interaction based on the task data model. DETAILED DESCRIPTION

[0048] The technical solutions in the embodiments of the present invention will be described clearly and completely below. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in this field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0049] This embodiment provides a method for constructing a field acquisition system based on a parameterized constraint data model. Figure 1-10 Describe them together.

[0050] 1. Construct a parameterized constraint data model framework model for field surveys, and use a unified data model framework model to define the field collection data model.

[0051] Aiming at the field geological survey data collection objects, combined with the characteristics of geological survey data collection, the real-world geological survey objects are abstracted into three types of element entities: points, lines or surfaces on a two-dimensional plane. The survey information of a field survey object is summarized as element entity information, rendering information, object description information of different specializations and attachment information. Each collection object in the geological survey is recorded as "1 element entity: 1 seed type: N object information descriptions", which ensures the integrity, professionalism and flexibility of the survey content of the survey object. Based on the above principles, the data model framework model is defined as follows: Figure 1 shown.

[0052] The data model framework model mainly includes the MainTable feature class collection table, the TableSet object class collection table, the RelationTable relationship table, various user-defined feature class data tables and corresponding feature class field constraint parameter tables, various user-defined object class data tables and corresponding object class field constraint parameter tables, multimedia video tables and multimedia photo tables.

[0053] The MainTable feature class collection table defines feature classes of different types (points, lines, and surfaces). Each record in the table corresponds to a feature class, which corresponds to a type of field survey object in the real world, such as geological survey points (point feature classes), field observation routes (line feature classes), etc. For each feature class, in addition to recording the Chinese name and English name of the feature class, the feature class type and feature class status constraint parameters are also defined. The feature class type constrains the rendering method of the feature, and the feature class status constrains the display and editing status of the feature. In the Sqlite database, each feature class is defined using a feature class data table and a feature class field constraint parameter table. The feature class data table name is defined by the feature class English name, and the feature class field constraint parameter table name is defined by the feature class English name + STRU. The feature class data table and the feature class field constraint parameter table appear in pairs. Each field of the feature class data table corresponds to a data record in the feature class field constraint parameter table, such as the feature class A data table and the feature class A field constraint parameter table in the framework model diagram of the data model. The feature class data table is used to store the survey object feature collection and rendering information. The feature class field constraint parameter table is used to store the constraint parameters of each field in the corresponding feature data table, including field name (FldName), field Chinese name (FldCnName), field data type (ValueType), special field type (ItemType), associated control type (BtnType) and associated control data content (BtnValue). Once the data model definition is completed, the data items in the feature class field constraint parameter table will no longer change, and are used to generate the corresponding feature class data collection interactive interface based on the constraint parameters of each feature class field.

[0054] Different object classes are defined in the TableSet object class collection table, and each record in the table corresponds to an object class. Each object class in the Sqlite database is defined using an object class data table and an object class field constraint parameter table. The object class data table name is defined using the object class English name, and the object class field constraint parameter table name is defined using the object class English name + UI. The object class data table and the object class field constraint parameter table appear in pairs. Each field in the object class data table corresponds to a data record in the object class field constraint parameter table, such as the object class A data table and the object class A field constraint parameter table in the framework model diagram of the data model.

[0055] The object class data table is used to store the corresponding object class survey information collected in the field of the survey object entity, and the object class field constraint parameter table is used to store the constraint parameters of each field in the corresponding object information table, including field name (FldName), field Chinese name (FldCnName), field data type (ValueType), special field type (ItemType), associated control type (BtnType) and associated control data content (BtnValue). Once the data model definition is completed, the data items in the object class field constraint parameter table will no longer change, and are used to generate the corresponding object class data collection interactive interface based on the constraint parameters of each object class field.

[0056] The RelationTable relationship table defines the object class set corresponding to a certain feature class subtype in the MainTable table. A feature class can contain multiple subtypes, each subtype can correspond to multiple object classes, and an object class can be assigned to different subtypes. For example, the hydrological survey point feature class can be divided into multiple subtypes such as geological and geomorphological survey points, hydrogeological survey points, dynamic observation record points, and environmental geological survey points. The geological and geomorphological survey point subtype is associated with geomorphological point survey forms, geological structure point survey forms, joint and fissure survey forms, and karst geomorphological point survey forms.

[0057] The MediaVedio multimedia video data table and the MediaPhoto multimedia photo data table store the photo and video multimedia information associated with each element.

[0058] Based on the above framework, the collection data storage of a survey object can be expressed as follows: Figure 2 shown.

[0059] Taking the object class as an example, the relationship between the data table and the constraint parameter table is as follows: Figure 3 shown.

[0060] 2. Based on the parameterized constraint data model framework model, use the declarative data model definition tool to create and define the field collection data model.

[0061] In the face of standards, specifications, survey content, and data models that have not yet been established, the field collection data model will change with the depth of research, and it is difficult for computer personnel to define a data model that meets the needs of field professional surveys. The present invention is based on a parameterized constraint data model framework model, using a declarative data model definition tool, and is created and defined by geological professionals. The generated field collection data model is stored and managed using a Sqlite database. The specific steps include the creation of a parameterized constraint data model framework, the creation of feature classes, the definition of feature class fields and constraint parameters, the creation of object classes, the definition of object class fields and constraint parameters, and the definition of object class collections corresponding to feature class subtypes. The specific process is as follows: Figure 4 As shown;

[0062] (1) Create a parameterized constrained data model file. Create a framework model Sqlite database file. The system automatically creates the MainTable feature class collection table, TableSet object class collection table, RelationTable relationship table, MediaVedio multimedia video data table and MediaPhoto multimedia photo data table and corresponding standardized attribute fields to form a data model framework.

[0063] (2) Feature class creation. Define the feature class Chinese name (layer Chinese name), English name (layer English name), feature class status (layer status) and feature class type (layer type). The feature class status includes four types: closed, open, edited and currently edited, which constrain whether the corresponding feature class entity is displayed on the map, whether it can be edited, and whether it can be added. The feature class types include point, line and surface, which constrain the feature class to be rendered and displayed with point symbols, line symbols or surface graphics. The Chinese name of the feature class constrains the display name of the corresponding layer in the layer list. The English name constrains the name of the feature class data table and the name of the feature class field constraint parameter table.

[0064] After the creation is completed, a corresponding feature class data record is added to the MainTable table, and the corresponding feature class data table and feature class field constraint parameter table are created. In the feature class data table, a unique identification code (UID), entity coordinate information (COORDINATES), feature class subtype field (TYPE), and corresponding rendering information related fields are automatically added according to the feature class type, such as the sub-map symbol number (SYMBOLOGY), color (COLOR), sub-map size (PIXELSIZE), transparency (TRANSPARENCY), etc. of the point type are added. The constraint parameter information of the above fields is added to the feature class field constraint parameter table.

[0065] (3) Definition of feature class fields and constraint parameters. For each field of the feature class, define the field English name, Chinese name, value type, special field type, plug-in button type and plug-in button attribute value definition and other constraint parameters.

[0066] Value type: includes four types: text, signed integer, unsigned integer, and floating point. The value type constrains the type of collected values ​​when inputting on the mobile terminal. For example, a field with an unsigned integer constraint can only input numbers, and a numeric keyboard will automatically pop up when inputting.

[0067] Control types: including custom attribute fields (common fields), X coordinates, Y coordinates, XY coordinates, longitude, latitude, latitude and longitude, elevation, line length, surface area, surface perimeter, creation time, scale, sheet number, unified number, route number, administrative division code and geographic location. For other control types except common fields, the system automatically enters attribute values ​​or associates them with specific data dictionaries. For example, if it is defined as a scale type, the system automatically pops up the scale dictionary selection dialog box when the edit box is clicked. If it is defined as an XY coordinate system, the XY coordinate values ​​of the added elements are automatically calculated and filled into the corresponding attribute value edit box. If it is defined as a geographic location, the system automatically calls the Tiandi Map LBS service to fill in the geographic location information.

[0068] Plug-in button types: including no dictionary, primary dictionary and secondary dictionary.

[0069] Plug-in button attribute value: When the plug-in button type is defined as a primary dictionary or a secondary dictionary, enter the dictionary file name. Click Edit Dictionary to directly enter the dictionary content value of the corresponding field.

[0070] The system provides add, delete, modify and query operations for each feature class field constraint parameter definition. When the feature class field is added, click Save to update the data values ​​in the feature class data table field and the feature class field constraint parameter table according to the field declaration definition.

[0071] (4) Object class creation. Define the object class name (table name), object category name (table alias) and table type. After creation, add a corresponding object class data record to the TableSet table, and create the corresponding object class data table and object class field constraint parameter table. The object class name constrains the name of the object class data table and the name of the object class field constraint parameter table, and the object class name constrains the corresponding object class display in the feature class subtype association object class interaction interface.

[0072] (5) Object class field and constraint parameter definition. For each field of the object class, define the field name, field alias, field type, control type, plug-in button type and other constraint parameters.

[0073] Numeric type: including text, signed integer, unsigned integer, floating point, etc.

[0074] Control type: including edit boxes and radio buttons,

[0075] External button types: including sub-table, multimedia photo, location map, unified number, time, date, date + time, electronic compass, primary dictionary, secondary dictionary, sketch, etc. For example, when defined as multimedia photo, add a photo button after the corresponding attribute value entry interface, click the button to pop up the camera interface, and save the photo name to the corresponding field attribute edit box after taking the photo. When defined as an electronic compass, add an electronic compass button after the corresponding attribute value entry interface, click the button to pop up the electronic compass measurement interface, and fill the measurement value into the corresponding field attribute edit box after the measurement is completed.

[0076] External button attribute value: When the external button type is defined as a primary dictionary or a secondary dictionary, the external button attribute value enters the dictionary file name, and clicks Edit Dictionary to directly enter the dictionary content value of the corresponding field. When the external button type is defined as an electronic compass, the external button attribute value defines the return value type, including five types: inclination, tilt, direction, pitch angle, and inclination\tilt\direction.

[0077] The system provides add, delete, modify and query operations for each object class field constraint parameter definition. When the object class field is added, click Save to update the data values ​​in the object class data table field and feature class field constraint parameter table according to the field declaration definition.

[0078] (6) The corresponding setting of the association relationship between the feature class subtype and the object class. When the definition of the feature class and object class is completed, the object class set corresponding to a certain feature class subtype in the MainTable table is defined in the RelationTable relationship table, including the name of the feature class, the name of the subtype, the feature class storage subtype field and the ID set of the management object class.

[0079] Example: Using the surface matrix survey field collection data model, the SQLITE database model framework is as follows Figure 5 As shown, the feature classes defined in the feature class dataset MainTable are shown in the following table.

[0080]

[0081] Taking the DCDDDCX2 survey point feature class as an example, the DCDDDCX2 feature data table and the DCDDDCX2STRU feature class field constraint parameter table are defined as follows: Figure 6 and Figure 7 shown.

[0082] The table data of the object class data set TableSet is shown in the following table.

[0083]

[0084] Taking the soil survey table object class as an example, the DCDDTZD2 object class data table and the DCDDTZD2UI object class field constraint parameter table are defined.

[0085] The relationship between feature class subtypes and object classes in the RelationTable relationship table is shown in the following table:

[0086]

[0087] 3. Based on the unified field collection system framework and the field collection data model file compilation and packaging, a collection system with parameterized constraints of data models for field data collection in professional geological surveys is generated.

[0088] In the unified field collection system framework, the defined data model files are packaged as system template file resources to form field collection systems for different professions. The field collection system framework includes task creation and management modules, task data map browsing modules, survey object data collection modules, and general auxiliary tool modules. The overall framework of the system is as follows: Figure 8 shown.

[0089] When the field collection system based on the parametric constraints of the data model collects data, a field data collection task is created in the task creation and management module based on the data model as a template, and used as a task collection data storage and management database. After the system loads a single task, the system generates a data collection interactive interface based on the data model file in the task, and realizes the collection data entry, storage management and display. The specific process is as follows:

[0090] (1) Create a field survey task. In the task creation and management module, use the field collection data model file as a template to create a field survey task and add it to the task management list. Generate a field collection data model file that is the same as the field collection data model in the created task folder and name it with the task name.

[0091] (2) Loading and displaying field survey tasks. Click a field survey task in the task management list. Based on the feature class and feature class constraint parameters defined in the MainTable in the data model, a display layer of the feature class with the same name as the feature class is created in the map view. The type of the feature class display layer is determined according to the type constraint parameters of the defined feature class. The feature data is read one by one from the corresponding feature class data table according to the feature class name. Feature display entities (points, lines, or surfaces) are created according to the feature class type and the coordinate information in the feature data, added to the display layer, and rendered according to the feature rendering parameters defined in the feature class data table. Then, the corresponding display layer is controlled to be displayed according to the display status of the feature class. The constraints of the feature class constraint parameters on the loading and display of task data are as follows: Fig. 9 shown.

[0092] (3) Field data collection and storage. After opening the task, click the feature entity add button to add the corresponding feature entity on the map and obtain the entity coordinate information. Then, use the data model to drive the generation of the information collection interaction interface. Generate a data collection interaction interface based on the task data model, complete the data collection, and save the collected data to the corresponding feature data table. The process of generating data collection interaction based on the task data model is as follows: Fig.10 shown.

[0093] ①Depending on the type of feature class currently being edited, draw feature objects on the map by adding points, lines or surfaces.

[0094] ②When the drawing is completed, read each field and its constraint parameters one by one from the corresponding feature class field constraint parameter table, and display the field name and field attribute value edit box and associated buttons in a unified style in each row in the form of a vertical list page, and generate a data collection interactive interface based on the constraint parameters. For the defined X coordinate, Y coordinate, XY coordinate, longitude, latitude, longitude and latitude, elevation, line length, surface area, surface perimeter, creation time, scale, map sheet number, unified number, route number, administrative division code and geographical location, the system automatically obtains the corresponding attribute values ​​for filling. For the defined fields with dictionaries, add a dictionary association selection button in the interface.

[0095] ③ Enter the attribute information of the feature class. For the field defined as dictionary type, click the corresponding dictionary association selection button. According to the plug-in button attribute value in the constraint parameter, the corresponding dictionary file content is read from the system default dictionary file storage path and a dictionary dialog box pops up. Select the corresponding attribute value for attribute entry. For ordinary fields, click the corresponding type of data keyboard popped up according to the data type defined in the dictionary to complete the attribute data entry. According to the subtype of the feature class defined in the RelationTable, the feature class subtype selection dialog box pops up to complete the feature subtype selection.

[0096] ④According to the object class ID set associated with the subtype of the feature and the feature class subtype defined in the RelationTable, obtain the corresponding object class name from the TableSet object class collection table, and generate the feature object class association interaction interface in a grid layout.

[0097] ⑤ Select the name of the object class to be entered in the feature object class association interactive interface, and the system will obtain the corresponding object class name.

[0098] ⑥ Obtain the corresponding object class name to obtain the corresponding object class field constraint parameter table. Based on the selected object class and the field constraint parameter table corresponding to the object class, traverse and read each field and its constraint parameters in the object class field constraint parameter table. In the form of a vertical list page, each row displays the field name and field attribute value edit box and the unified style of the associated button, and generates the object class data collection interactive interface according to the constraint parameters. In the process of interface generation, the system automatically creates corresponding associated buttons for special fields defined as sub-tables, multimedia photos, location maps, unified numbers, time, date, date + time, electronic compass, primary dictionary, secondary dictionary, sketch, etc.

[0099] ⑦ Object class attribute information entry. During the collection process, for fields defined as dictionary types, click the corresponding dictionary association selection button. According to the plug-in button attribute value in the constraint parameter, the corresponding dictionary file content is read from the system default dictionary file storage path and a dictionary dialog box pops up. Select the corresponding attribute value to enter the attribute. For ordinary fields, click the data type defined in the dictionary to pop up the corresponding type of data keyboard to complete the attribute data entry. For fields defined as subtables, multimedia photos, location maps, unified numbers, time, date, date + time, and electronic compasses, click the association button to automatically pop up the corresponding information collection interface. After the collection is completed, return to the object class attribute collection interaction interface and save the collected information in the attribute editing box of the corresponding field. After all information is entered, click Save to save the object class collection data to the corresponding object class data table and return to the feature object class association interaction interface.

[0100] ⑧ Repeat steps ⑤-⑦ to complete the entry of multiple object class attribute information. After all the object class attribute information that needs to be collected for the feature is collected, click Save to return to the feature drawing and adding interface to complete the data collection of a single feature.

[0101] ⑨ Repeat steps ①-⑧ to complete the collection and storage of multiple survey objects in the field.

[0102] The above shows and describes the basic principles and main features of the present invention and the advantages of the present invention. It should be understood by those skilled in the art that the present invention is not limited to the above embodiments, and the above embodiments and descriptions are only for explaining the principles of the present invention. Without departing from the spirit and scope of the present invention, the present invention may have various changes and improvements, and these changes and improvements fall within the scope of the present invention to be protected. The scope of the present invention to be protected is defined by the attached claims and their equivalents.

Claims

1. A method for constructing a field acquisition system based on a parameterized constraint data model, characterized in that: The following steps are involved: S1. A framework model for building a field collection data model based on the Sqlite database; The framework model includes MainTable feature class collection table, TableSet object class collection table, RelationTable relationship table, user-defined feature class data table and corresponding feature class field constraint parameter table, user-defined object class data table and corresponding object class field constraint parameter table, multimedia video table and multimedia photo table; S2. Based on the framework model of the field collection data model, the field collection data model is constructed using a declarative data model definition tool; The step of constructing a field collection data model includes: S21. Create a data model file with parameterized constraints to form a data model framework; S22. Create feature classes, and define the Chinese name, English name, status, type, feature class fields and constraint parameters of each feature class; S23, creating object classes, and defining the name, alias, type, object class fields and constraint parameters of each object class; S24. Define the object class set corresponding to the feature class subtype in the RelationTable relationship table, including the name of the feature class, the name of the subtype, the feature class storage subtype field and the ID set of the management object class; S3, compile and generate a field collection system based on a unified field collection system framework and a field collection data model; S4. When the field collection system collects data, it generates a data collection interactive interface based on the data model driver, and implements the collection data entry, storage management and display; S41, using the field collection data model file as a template, creating a field survey task and adding it to the task management list, generating a field collection data model file identical to the field collection data model in the created task folder, and naming it with the task name; S42. Click the field survey task in the task management list, create a display layer of the feature class with the same name as the feature class in the map view based on the feature class and feature class constraint parameters defined in the MainTable in the data model, determine the type of the feature class display layer according to the defined type constraint parameters of the feature class, read feature data one by one from the corresponding feature class data table according to the feature class name, create a feature display entity according to the feature class type and the coordinate information in the feature data, add it to the display layer, and render it according to the feature rendering parameters defined in the feature class data table, and then control whether the corresponding display layer is displayed according to the display status of the feature class; S43. On the basis of opening the task, click the feature entity add button to add the corresponding feature entity on the map and obtain the entity coordinate information. Then, use the technical method of data model driven information collection interactive interface generation to generate a data collection interactive interface based on the task data model, complete data collection, and save the collected data to the corresponding feature data table.

2. The method for constructing a field acquisition system based on a parameterized constraint data model according to claim 1, characterized in that: The specific process of step S1 is: facing the field geological survey data collection object, combining the characteristics of geological survey data collection, abstracting the geological survey objects in the real world into three types of element entities: points, lines or surfaces on a two-dimensional plane, and summarizing the survey information of a field survey object into element entity information, rendering information, object description information of different specializations and attachment information, and recording each collection object in the geological survey with 1 element entity: 1 seed type: N object information description.

3. The method for constructing a field acquisition system based on a parameterized constraint data model according to claim 1, characterized in that: The MainTable feature class collection table defines different types of feature classes, each of which is defined using a feature class data table and a feature class field constraint parameter table; the TableSet object class collection table defines different object classes, each of which is defined using an object class data table and an object class field constraint parameter table; the RelationTable relationship table defines the object class collection corresponding to the feature class subtype in the MainTable table.

4. The method for constructing a field acquisition system based on a parameterized constraint data model according to claim 3, characterized in that: The feature class field constraint parameter table and the object class field constraint parameter table include field name, field Chinese name, field data type, special field type, associated control type and associated control data content.

5. The method for constructing a field acquisition system based on a parameterized constraint data model according to claim 1, characterized in that: In step S3, the field collection system framework includes a task creation and management module, a task data map browsing module, a survey object data collection module, and a general auxiliary tool module.

6. The method for constructing a field acquisition system based on a parameterized constraint data model according to claim 1, characterized in that: In step S43, the process of generating the data collection interactive interface includes: S431, adding a feature object defined by the currently edited feature class to the map; S432, after the element drawing is completed, a feature data collection interactive interface is generated based on the feature class field constraint parameter table; S433, input feature class attribute information, select the subtype to which the current feature belongs, and save the feature class collection data into the feature data table; S434, generating a feature object class association interaction interface based on the subtype to which the selected feature belongs and the object class set associated with the feature class subtype defined in the RelationTable; S435, selecting the name of the object class to be entered in the feature object class association interaction interface; S436, generating an object class data collection interactive interface based on the selected object class and the field constraint parameter table corresponding to the object class; S437, the object class data collection is completed, click Save to save the object class collection data to the corresponding object class data table, and return to the feature object class association interaction interface; S438. Repeat the above steps to complete the collection and storage of multiple survey objects in the field.

Images