Ground monitoring data identification and association method, system and device and storage medium

Abstract

The invention discloses a ground monitoring data identification and association method, system and device, and a storage medium, and the key points of the technical scheme are that the method comprises the steps: receiving the current monitoring data of a current object and the identification data of a to-be-associated object; encoding the current object according to a preset encoding scheme and the current monitoring data to obtain an identifier of the current object; determining an identifier of the to-be-associated object according to the identification data of the to-be-associated object; and according to the identifier of the current object and the identifier of the to-be-associated object, establishing an association relationship between the current object and the to-be-associated object. Unification and association of the same objects in different monitoring tasks are ensured, and dynamic monitoring of the objects is facilitated.

Description

[0001] The present invention claims priority to Chinese patent application No. 2025106519532, filed with the Patent Office of China on May 20, 2025, entitled “Method, system, device and storage medium for identifying and associating ground monitoring data”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present invention belongs to the field of natural science research and experimental development technology, and specifically relates to a method, system, device and storage medium for identifying and associating ground monitoring data. Background Art

[0003] Ground monitoring of natural objects involves various types of objects and knowledge from various fields, which leads to different monitoring. In addition to dealing with some common problems in the natural environment and organizational management, it is also necessary to solve the personalized problems of various types of monitoring.

[0004] When addressing common and individual issues, existing technologies consider the relationships between different types of records, different records of the same type, and even records of the same object at different times, as part of ground-based monitoring. For example, if a red-billed blue tit (Urocissa erythroryncha) is found slurping nectar from a kapok tree (Bombax ceiba) in a particular plot, the plot record has an inclusion relationship with the animal and plant records, which in turn have a feeding relationship. For different records of the same type, such as a dodder (Cuscutachinensis) plant found parasitizing soybean (Glycine max) plants in a particular plot, a parasitic relationship needs to be established between the two plant records. And for records of the same object at different times, such as the annual phenological records of different kapok plants in a particular plot, a temporal relationship needs to be established with the historical records of the corresponding plants. This dynamic relationship construction can provide rich and flexible support for the study of relationships between natural objects.

[0005] However, in existing monitoring systems, due to the lack of unified and comprehensive relational model guidance, free data connections cannot be formed between records, making it difficult to meet such dynamic monitoring needs. Summary of the Invention

[0006] The purpose of the present invention is to provide a method, system, device and storage medium for identifying and associating ground monitoring data, so as to ensure the unification and association of the same objects in different monitoring tasks, so as to facilitate dynamic monitoring of the objects.

[0007] A first aspect of the present invention provides a method for identifying and associating ground monitoring data, comprising:

[0008] Receive current monitoring data of the current object and identification data of the object to be associated;

[0009] Encode the current object according to a preset encoding scheme and current monitoring data to obtain an identifier of the current object;

[0010] Determining an identifier of the object to be associated according to the identification data of the object to be associated;

[0011] An association relationship between the current object and the object to be associated is established according to the identifier of the current object and the identifier of the object to be associated.

[0012] In some implementations, when the encoding scheme is an offline encoding scheme, the encoding scheme includes:

[0013] Extracting a number, a recording timestamp, and a type code of the current object from the current monitoring data;

[0014] Concatenate the type code, number and record timestamp of the current object to form a first code;

[0015] Controlling whether to use a coding prefix according to a usage scope of the identifier of the current object, wherein the coding prefix is ​​generated according to platform coding;

[0016] In the case of using a code prefix, concatenating the code prefix and the first code to form a second code, and using the second code as an identifier of the current object;

[0017] If the code prefix is ​​not used, the first code is used as the identifier of the current object.

[0018] In some implementations, when the encoding scheme is an online encoding scheme, the encoding scheme includes:

[0019] The current monitoring data is stored in the target database, and the auto-increment primary key sequence number of the current object in the target database and the type code of the current object are obtained;

[0020] Concatenate the type code of the current object and the auto-increment primary key sequence number to form a first code;

[0021] Controlling whether to use a coding prefix according to a usage scope of the identifier of the current object, wherein the coding prefix is ​​generated according to platform coding;

[0022] In the case of using a code prefix, concatenating the code prefix and the first code to form a second code, and using the second code as an identifier of the current object;

[0023] If the code prefix is ​​not used, the first code is used as the identifier of the current object.

[0024] In some embodiments, the current monitoring data belongs to ground monitoring data, and the ground monitoring data is divided into entity data, spatial data and fragment data; the entity data includes: entity common attributes and entity individual attributes, the spatial data includes: spatial common attributes and spatial individual attributes, and the fragment data includes: fragment common attributes and fragment individual attributes.

[0025] In some embodiments, the current monitoring data is stored in a target database, and the method for building the target database includes:

[0026] Creating an entity data table for the entity data, wherein the entity data table includes entity common attributes, and the entity individual attributes are stored in a single attribute of the entity data table in the form of key-value pairs, or creating an entity data sub-table for the entity individual attributes, wherein the entity data sub-table is associated with the entity data table through an entity foreign key;

[0027] Creating a spatial data table for the spatial data, wherein the spatial data table includes spatial common attributes, and the spatial individual attributes are stored in a single attribute of the spatial data table in the form of key-value pairs, or creating a spatial data sub-table for the spatial individual attributes, wherein the spatial data sub-table is associated with the spatial data table via a spatial foreign key;

[0028] A fragment data table is created for the fragment data, wherein the fragment data table includes common attributes of the fragments, and the individual attributes of the fragments are stored in a single attribute of the fragment data table in the form of key-value pairs, or a fragment data sub-table is created for the individual attributes of the fragments, and the fragment data sub-table is associated with the fragment data table through a fragment foreign key.

[0029] In some embodiments, the current monitoring data is stored in a target database, and the method for building the target database includes:

[0030] A task data table is created according to the monitoring task, wherein the task data table includes entity common attributes, entity individual attributes, space common attributes, space individual attributes, segment common attributes, and segment individual attributes.

[0031] In some embodiments, the current object includes: a physical object, a spatial object, and a fragment object, and the association relationship includes at least any one of the following: an association relationship between a physical object and a physical object, an association relationship between a spatial object and a physical object, an association relationship between a physical object and a fragment object, and an association relationship between a spatial object and a fragment object.

[0032] A second aspect of the present invention provides a ground monitoring data identification and association system, comprising:

[0033] A data receiving module, configured to receive current monitoring data of the current object and identification data of the object to be associated;

[0034] An identifier generation module is used to encode the current object according to a preset encoding scheme and current monitoring data to obtain an identifier of the current object;

[0035] an identifier determining module, configured to determine an identifier of the object to be associated based on the identification data of the object to be associated;

[0036] The relationship establishing module is used to establish an association relationship between the current object and the object to be associated according to the identifier of the current object and the identifier of the object to be associated.

[0037] A third aspect of the present invention provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0038] A fourth aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0039] The technical solution provided by the present invention has the following advantages and effects: by judging whether there is a unique identifier at present, if there is no unique identifier, a unique identifier is assigned to the current object, so as to facilitate the subsequent establishment of association relationships between objects, unify the concepts and relationships of ground monitoring data, and provide a unified framework for the identification, organization and operation of ground monitoring data, ensuring the unification and association of the same objects in different monitoring tasks, so as to facilitate dynamic monitoring of objects. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 It is a flowchart of the method for identifying and associating ground monitoring data provided by the present invention;

[0041] Figure 2 It is a schematic diagram of the relationship between entities, spaces and fragments provided by the present invention;

[0042] Figure 3 This is a schematic diagram of a process for generating an identifier for an object through an application system on a mobile terminal provided by the present invention;

[0043] Figure 4 It is a flow chart of establishing a phenological monitoring system for an object provided by the present invention;

[0044] Figure 5 This is a structural block diagram of the ground monitoring data identification and association system provided by the present invention;

[0045] Figure 6 It is a diagram of the internal structure of a computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0046] To facilitate understanding of the present invention, specific embodiments of the present invention will be described in more detail below with reference to the accompanying drawings.

[0047] Unless otherwise specified or defined, the "first, second..." used in this article is only used to distinguish names and does not represent a specific quantity or order.

[0048] Unless stated otherwise or defined otherwise, the term "and / or" as used herein includes any and all combinations of one or more of the associated listed items.

[0049] It should be noted that, in this document, “fixed to” or “connected to” may mean directly fixing or connecting to an element, or indirectly fixing or connecting to an element.

[0050] like Figure 1 As shown, this embodiment provides a method for identifying and associating ground monitoring data, including the following steps S1 to S4:

[0051] Step S1: Receive current monitoring data of the current object and identification data of the object to be associated.

[0052] In actual applications, the current monitoring data is uploaded by monitoring personnel or automatically uploaded by monitoring equipment. The current monitoring data belongs to ground monitoring data, which refers to various types of data obtained through ground manual surveys, observations, equipment testing, monitoring, sample analysis, and research of natural objects. Ground monitoring data can include records of the discovery of various natural objects, such as specimen collection information and outdoor observation records of animals and plants; detection and analysis data of various natural samples, such as DNA sequences of insects and detection and monitoring data of water, soil and air samples at a specific time and space; research data of various natural samples, such as scientific research papers based on specimens. The natural objects refer to objects in various geological, biological, ecological, and social fields, including rock and mineral fossils, animals, plants, fungi, atmosphere, soil, and water. These natural objects can come completely from nature, such as various wild organisms, or they can be cultivated or processed by humans, such as artificially cultivated plants, dried plant specimens, and handmade plant crafts.

[0053] Specifically, the types of objects include: physical objects, spatial objects and fragment objects. The ground monitoring data can be further divided into physical data, spatial data and fragment data according to the physical objects, spatial objects and fragment objects. The current monitoring data belongs to one of physical data, spatial data and fragment data. Among them, the physical object refers to a physical object that objectively exists and has a stable monitoring property, such as long-term preserved rock and mineral fossils and animal and plant fungus specimens, wild or artificially bred living animals and plants, ultra-low temperature preserved biological germplasm resources, etc. The spatial object refers to various geographical spaces planned by humans, such as survey lines, plots, and points of animals and plants, or a road, lake, community, etc. The fragment object refers to various types of data derived from the physical object, such as DNA sequence information extracted from a specimen, published articles, etc.; or refers to dynamic data collected in a specific space, such as the pH value of water recorded at a certain time and location.

[0054] The entity data includes entity common attributes and entity individual attributes, the space data includes space common attributes and space individual attributes, and the segment data includes segment common attributes and segment individual attributes.

[0055] In practical applications, common attributes refer to attributes shared by objects of the same type. Common attributes of entities may include the recording time, discovery location, recording personnel, entity type, entity image, latitude and longitude coordinates, altitude, official name, quantity scale, and remarks, etc. The entity type can be expressed by a set of standardized optional words, such as "plant specimen record, plant observation record, insect observation record, fossil specimen record, mineral specimen record", etc. The common attributes of spatial objects may include the creation time, creation personnel, spatial type, spatial image, associated GIS file, remarks, etc. The spatial type can be expressed by a set of standardized optional words, such as "plant plot, plant sample line, animal sample point, animal sample line, urban green space, urban road, nursery garden, etc." The GIS file refers to a data file that accurately describes the geographical location or geographical scope of the spatial object, such as various GeoJson and shp files. The common attributes of fragment objects may include the submission time, submitter, fragment type, fragment image, associated files, remarks, etc. The fragment type can be expressed by a set of standardized optional words, such as "plant phenology, research literature, molecular sequence, animal behavior", etc. The associated file refers to the file pointer related to the fragment record, such as the download address of the research paper and molecular sequence file.

[0056] In practical applications, individual attributes refer to the personalized attributes of different monitoring items within the same category. For example, for physical objects, plant specimen records also need to include attributes such as collection number, abundance, life form, and morphological description. Records of plot plants need to include information such as plot number, diameter at breast height, and phenology. Records of macrofungal specimens will include attributes such as odor, cap, stipe, and hymenium. Similarly, different monitoring items for spatial objects and fragment objects will also have their own distinct attributes.

[0057] In practical applications, if the current monitoring data is entity data, the current object type is an entity object, and the type of the object to be associated can be an entity object, a spatial object, or a fragment object. If the current monitoring data is spatial data, the current object type is a spatial object, and the type of the object to be associated can be an entity object or a fragment object. If the current monitoring data is fragment data, the current object is a fragment object, and the object to be associated can be an entity object or a spatial object.

[0058] Specifically, before the current monitoring task is performed, the object to be associated typically has identification data. When readable identification data exists for the object to be associated, such as a physical or electronic tag, the tag can contain identifier information in the form of text, barcodes, QR codes, or RFID tags. These include the numbers on bird bands, barcodes on museum specimens, QR codes on tree tags or sample markers, RFID chips implanted in animals, and DOI numbers for papers. The monitoring device can obtain the identification data of the object to be associated by collecting data from the tag. If the object to be associated does not have readable identification data, the identification data can be retrieved from the target database using the object's keywords.

[0059] Step S2: Encode the current object according to a preset encoding scheme and current monitoring data to obtain an identifier of the current object.

[0060] Specifically, when the encoding scheme is an offline encoding scheme, the encoding scheme includes:

[0061] Extracting a number, a recording timestamp, and a type code of the current object from the current monitoring data;

[0062] Concatenate the type code, number and record timestamp of the current object to form a first code;

[0063] Controlling whether to use a coding prefix according to a usage scope of the identifier of the current object, wherein the coding prefix is ​​generated according to platform coding;

[0064] In the case of using a code prefix, concatenating the code prefix and the first code to form a second code, and using the second code as an identifier of the current object;

[0065] If the code prefix is ​​not used, the first code is used as the identifier of the current object.

[0066] In practical applications, in an offline state, an offline encoding scheme can be used to encode the current object to obtain an identifier for the current object. The number includes: user number (such as user ID) or device number (device ID). The first code is formed by concatenating the type code, number, and recording timestamp of the current object. This can also be obtained when the device is offline. For example, if the type of plot A is a spatial object, the first code is generated using the type code corresponding to the spatial object, user ID 456, and the recording timestamp when user 456 recorded plot A, such as Space.456.1747646125. If a Bole tree is an entity object and is recorded by user 123, the first code is generated using the type code corresponding to the entity object, user ID 123, and the recording timestamp when user 123 recorded the Bole tree. The first code is Object.123.1757646125. If user 678 sequences the Bole tree and obtains molecular sequence data B and uploads it to the monitoring platform, the type of molecular sequence data B is a fragment object. The first code is generated according to the type code corresponding to the fragment object, user id 678, and the record timestamp when user 678 generates the molecular sequence data B. The first code is Fragment.678.1767646125. After obtaining the first code, it is determined whether to use the code prefix based on the scope of use of the identifier of the current object. If the scope of use of the identifier of the current object is only used within the current platform, there is no need to use the code prefix. The current platform is the platform for uploading the current monitoring data. Then, the first code is used as the identifier of the current object, which can achieve the uniqueness of the current object within the expected range. The identifier of the current object is generated by the type code, number and record timestamp of the current object, which not only ensures the uniqueness of the object identifier in the ground monitoring data, but also supports the establishment of data relationships between different objects in an offline state. If the scope of the current object's identifier exceeds the internal scope of the current platform, using the first code as the current object's identifier will not guarantee uniqueness within the expected scope. Therefore, a code prefix is ​​required to ensure the uniqueness of the generated identifier within the expected scope. The code prefix is ​​generated based on the platform code, which is assigned by the third-party platform before the device goes offline. For example, if the current platform's registration number on the third-party platform is 33295, and the third-party platform grants the current platform the right to assign proxy identifiers to living biological resources (such as resource number 46), the code prefix for the current platform is 33295.46. Concatenating the code prefix with the first code generates a globally unique identifier, such as 33295.46.Object.123.1757646125. Depending on the identifier's scope, you can choose whether to add a code prefix when the device is offline to ensure uniqueness within the expected scope while minimizing the identifier's code length.

[0067] Optionally, in practical applications, the first code may be further encoded and encrypted to shorten the code length and improve system security and user privacy protection capabilities.

[0068] Specifically, when the encoding scheme is an online encoding scheme, the encoding scheme includes:

[0069] The current monitoring data is stored in the target database, and the auto-increment primary key sequence number of the current object in the target database and the type code of the current object are obtained;

[0070] Concatenate the type code of the current object and the auto-increment primary key sequence number to form a first code;

[0071] Controlling whether to use a coding prefix according to a usage scope of the identifier of the current object, wherein the coding prefix is ​​generated according to platform coding;

[0072] In the case of using a code prefix, concatenating the code prefix and the first code to form a second code, and using the second code as an identifier of the current object;

[0073] If the code prefix is ​​not used, the first code is used as the identifier of the current object.

[0074] In practical applications, the online encoding scheme can first store the current monitoring data in the target database, then obtain the current object's auto-incrementing primary key sequence number and the current object's type code, and concatenate the current object's type code and the current monitoring data's auto-incrementing primary key sequence number in the database to form a first code. After obtaining the first code, it is determined whether to use a coding prefix based on the usage scope of the current object's identifier. If the usage scope of the current object's identifier is only used within the current platform, there is no need to use a coding prefix. The first code is used as the current object's identifier, such as "Object.789", which can achieve the uniqueness of the current object within the expected scope. If the usage scope of the current object's identifier exceeds the internal usage scope of the current platform, a coding prefix is ​​required to ensure the uniqueness of the generated current object's identifier within the expected scope. The coding prefix is ​​generated based on the platform code, and the coding prefix and the first code are concatenated to form an identifier, such as "33295.46.Object.789", where "33295.46" is the registered platform code, Object is the type code, and 789 is the auto-incrementing primary key sequence number of the current monitoring data in the data table. The identifier generated using the online encoding solution is shorter and more readable because it is spliced ​​using the platform code, the current object's type code, and the auto-incrementing primary key number. When users see this identifier, they will know the current object's upload platform, object type, and the auto-incrementing primary key number in the data table.

[0075] Step S3: Determine the identifier of the object to be associated according to the identification data of the object to be associated.

[0076] In actual applications, the identification data of the object to be associated is obtained by identifying the tag on the object to be associated. However, the information written on the tag of the object to be associated may only be some internal numbers rather than the object identifier, such as the number of the tree in the sample plot or the collection number of the animal and plant specimen. In this case, the tag of the object to be associated does not have strict uniqueness and cannot be used as a stable and persistent identifier. However, it can be used as a keyword to retrieve the identifier of the object to be associated from the target database or offline cache. In addition, other data in the current monitoring data can also be used for data retrieval or comparison. For example, user 123 of a certain monitoring platform discovered a Bole tree in sample plot A of Nanling National Park. Among them, sample plot A is the spatial object to be associated with the Bole tree. It has previously been recorded and obtained by user 456. According to the geographical location data of the current Bole tree, the historical monitoring data (historical monitoring data is stored in the target database or cached in the local device) is queried to obtain the identifier of sample plot A, that is, the identifier of the object to be associated.

[0077] In actual use, if the current monitoring data is entity data, the identifier of the current object refers to the identifier of the current entity object, and the identifier of the object to be associated refers to the identifier of the entity object to be associated with the current entity object, the identifier of the spatial object to be associated with the current entity object, or the identifier of the fragment object to be associated with the current entity object; if the current monitoring data is spatial data, the identifier of the current object refers to the identifier of the current spatial object, and the identifier of the object to be associated refers to the identifier of the entity object to be associated with the current spatial object, or the identifier of the fragment object to be associated with the current spatial object; if the current monitoring data is fragment data, the identifier of the current object refers to the identifier of the current fragment object, and the identifier of the object to be associated refers to the identifier of the entity object to be associated with the current fragment object, or the identifier of the spatial object to be associated with the current fragment object. For example, in a ground monitoring project, it is discovered that plant B in plot A blooms at time C, where plot A is a spatial object, plant B is a physical object, and blooming at time C is a fragment object. The record of plant B is entity data, the record of plot A is spatial data, and the record of blooming at time C is fragment data. If the current object is plant B, then in this project, the identifier assigned to the record of plant B is the identifier of the current object, and in this project, the identifier assigned to the record of plot A is the identifier of the spatial object to be associated with plant B; if the current object is a fragment object, then in this project, the identifier assigned to the record of flowering at C is the identifier of the current object, and in this project, the identifier assigned to the record of plant B is the identifier of the entity object to be associated with the current object.

[0078] Step S4: establishing an association relationship between the current object identifier and the current monitoring data.

[0079] Specifically, the current monitoring data belongs to ground monitoring data and is stored in a target database. The method for building the target database includes:

[0080] Creating an entity data table for the entity data, wherein the entity data table includes entity common attributes, and the entity individual attributes are stored in a single attribute of the entity data table in the form of key-value pairs, or creating an entity data sub-table for the entity individual attributes, wherein the entity data sub-table is associated with the entity data table through an entity foreign key;

[0081] Creating a spatial data table for the spatial data, wherein the spatial data table includes spatial common attributes, and the spatial individual attributes are stored in a single attribute of the spatial data table in the form of key-value pairs, or creating a spatial data sub-table for the spatial individual attributes, wherein the spatial data sub-table is associated with the spatial data table via a spatial foreign key;

[0082] A fragment data table is created for the fragment data, wherein the fragment data table includes common attributes of the fragments, and the individual attributes of the fragments are stored in a single attribute of the fragment data table in the form of key-value pairs, or a fragment data sub-table is created for the individual attributes of the fragments, and the fragment data sub-table is associated with the fragment data table through a fragment foreign key.

[0083] In practical applications, by centrally storing the common attributes of each object and flexibly storing the individual attributes of each object in the form of key-value pairs, the flexibility of the target database is improved, and new attributes can be added without modifying the table structure. By centrally storing the common attributes of each object and storing the individual attributes of each object in the form of sub-tables, the data table structure is clear, the query efficiency is high, and strong type constraints are supported.

[0084] Specifically, in other embodiments, the method for building the target database includes:

[0085] A task data table is created according to the monitoring task, wherein the task data table includes entity common attributes, entity individual attributes, space common attributes, space individual attributes, segment common attributes, and segment individual attributes.

[0086] In actual applications, if the attributes of different monitoring tasks are quite different (for example, meteorological monitoring needs to record temperature and humidity, while soil monitoring needs to record pH value and organic matter content), a separate table can be created for each monitoring task.

[0087] Specifically, the association relationship includes at least any one of the following: an association relationship between entity objects and entity objects, an association relationship between spatial objects and entity objects, an association relationship between entity objects and fragment objects, and an association relationship between spatial objects and fragment objects.

[0088] The association relationship between the spatial object and the entity object refers to the presence of a specific entity in a specific space, such as plant a found in plot A. The association relationship between the spatial object and the entity object can be one-to-many, such as plants a, b, and c in plot A, or many-to-many, such as plant a appearing in both plot A and transect B. The association relationship between entity objects refers to the existence of a specific relationship between a specific entity and another entity, such as specimen a coming from plant A and animal a feeding on plant A. The association relationship between entity objects is determined by the implementation of the target database. For example, if the entity objects of animals and plants are stored in the same data table in the target database, different entity objects need to be connected through self-joining. If the entity objects of animals and plants are stored in different data tables, the relationship between animals and plants can be realized as a many-to-many or one-to-many relationship according to business needs. The association relationship between the entity object and the fragment object refers to the fragment object derived from a specific entity, such as the molecular sequence data extracted from a certain insect specimen; the association relationship between the entity object and the fragment object can be one-to-many, such as the annual flowering record of a certain plant, or many-to-many, such as a paper published based on one or more plant specimens. The relationship between the spatial object and the fragment object refers to the dynamic data generated in a specific space, such as the surface air humidity and temperature records collected at a certain time and place. The association relationship between the spatial object and the fragment object can be one-to-many, such as the temperature records collected continuously at a certain location, or many-to-many, such as the temperature records of a certain location are used by different spatial sampling systems.

[0089] In practical applications, such as Figure 2 As shown, the relationship between entity and space, fragment and entity, and fragment and space is usually one-to-many, and the relationship between entity and entity can be designed as a self-connected relationship. Specifically, the relationship between the identifier of the current object and the current monitoring data is established, including: supporting different objects to establish relationships based on identifiers, such as user 123 of the monitoring platform, found a Bole tree in the Lingnan National Park sample site A, and sampled the leaf material of the Bole tree, and user 678 measured the molecular sequence B of the Bole tree through the temporary sample, then an association relationship is established between the entity object Bole tree and the spatial object sample site A, in the data table corresponding to the Bole tree, the identifier of the sample site A is added to the common attributes of the Bole tree, or in the data table corresponding to the spatial object sample site A, the identifier of the Bole tree is added to the common attributes of the sample site A, so as to establish an association relationship between the entity object Bole tree and the spatial object sample site A. As Figure 3 As shown, user 123 and user 678 can generate identifiers for objects through the application system on the mobile terminal (mobile phone). The application system builds an online application based on the target database, including a mobile APP terminal and a Web terminal. The mobile APP terminal can provide natural object observation services for various users, and the Web terminal can provide data management services for various managers. The application system can realize the relationship between spatial objects and physical objects, physical objects and physical objects, physical objects and fragment objects, and spatial objects and fragment objects by associating identifiers of other objects when generating the current object. The identifiers of other objects can be obtained and associated with other object identifiers through system retrieval, information matching, barcode or QR code recognition, etc. Specifically, as Figure 4 As shown, for example, a long-term phenological monitoring system is to be established for some kapok plants in different locations in Guangzhou, so as to record the physical object of each kapok tree, generate an identifier for each physical object, and convert the identifier of each physical object into a QR code. By making the QR code into a physical sign and hanging it on the corresponding kapok plant, phenological fragment records can be added for each kapok plant by scanning the code. The long-term time series data obtained can be used for urban phenological analysis to support relevant decision-making.

[0090] like Figure 5 As shown, an embodiment of the present invention further provides a ground monitoring data identification and association system, including:

[0091] A data receiving module 10 is used to receive the current monitoring data of the current object and the identification data of the object to be associated;

[0092] An identifier generation module 20 is configured to determine a coding scheme for a current object based on a device network state, and to encode the current object based on the coding scheme and current monitoring data to obtain an identifier for the current object;

[0093] An identifier determination module 30, configured to determine an identifier of the object to be associated based on the identification data of the object to be associated;

[0094] The relationship establishing module 40 is configured to establish an association relationship between the current object and the object to be associated based on the identifier of the current object and the identifier of the object to be associated.

[0095] Each module of the aforementioned ground monitoring data identification and association system may be implemented in whole or in part through software, hardware, or a combination thereof. Each of the aforementioned modules and units may be embedded in or independent of a processor within a computer device in the form of hardware, or may be stored in a memory within the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0096] like Figure 6As shown, an embodiment of the present invention discloses a computer device, including a memory and a processor, wherein the memory stores a computer program;

[0097] The computer device may be a server, and its internal structure diagram may be as follows: Figure 6 As shown. The computer device includes a processor, a memory, a network interface, and a database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, it implements the ground monitoring data identification and association method described in the above embodiments.

[0098] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0099] An embodiment of the present invention further discloses a computer-readable storage medium storing a computer program, wherein the computer program enables a computer to execute the ground monitoring data identification and association method described in the above embodiments.

[0100] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0101] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. A method for identifying and associating ground monitoring data, characterized in that: include: Receive current monitoring data of the current object and identification data of the object to be associated; Encode the current object according to a preset encoding scheme and current monitoring data to obtain an identifier of the current object; Determining an identifier of the object to be associated according to the identification data of the object to be associated; An association relationship between the current object and the object to be associated is established according to the identifier of the current object and the identifier of the object to be associated.

2. The method for identifying and associating ground monitoring data according to claim 1, wherein: In the case where the encoding scheme is an offline encoding scheme, the encoding scheme includes: Extracting a number, a recording timestamp, and a type code of the current object from the current monitoring data; Concatenate the type code, number and record timestamp of the current object to form a first code; Controlling whether to use a coding prefix according to a usage scope of the identifier of the current object, wherein the coding prefix is ​​generated according to platform coding; In the case of using a code prefix, concatenating the code prefix and the first code to form a second code, and using the second code as an identifier of the current object; If the code prefix is ​​not used, the first code is used as the identifier of the current object.

3. The method for identifying and associating ground monitoring data according to claim 1, wherein: In the case where the encoding scheme is an online encoding scheme, the encoding scheme includes: The current monitoring data is stored in the target database, and the auto-increment primary key sequence number of the current object in the target database and the type code of the current object are obtained; Concatenate the type code of the current object and the auto-increment primary key sequence number to form a first code; Controlling whether to use a coding prefix according to a usage scope of the identifier of the current object, wherein the coding prefix is ​​generated according to platform coding; In the case of using a code prefix, concatenating the code prefix and the first code to form a second code, and using the second code as an identifier of the current object; If the code prefix is ​​not used, the first code is used as the identifier of the current object.

4. The method for identifying and associating ground monitoring data according to claim 1, wherein: The current monitoring data belongs to ground monitoring data, which is divided into entity data, spatial data and fragment data; The entity data includes entity common attributes and entity individual attributes, the space data includes space common attributes and space individual attributes, and the segment data includes segment common attributes and segment individual attributes.

5. The method for identifying and associating ground monitoring data according to claim 4, wherein: The current monitoring data is stored in a target database, and the method for building the target database includes: Creating an entity data table for the entity data, wherein the entity data table includes entity common attributes, and the entity individual attributes are stored in a single attribute of the entity data table in the form of key-value pairs, or creating an entity data sub-table for the entity individual attributes, wherein the entity data sub-table is associated with the entity data table through an entity foreign key; Creating a spatial data table for the spatial data, wherein the spatial data table includes spatial common attributes, and the spatial individual attributes are stored in a single attribute of the spatial data table in the form of key-value pairs, or creating a spatial data sub-table for the spatial individual attributes, wherein the spatial data sub-table is associated with the spatial data table via a spatial foreign key; A fragment data table is created for the fragment data, wherein the fragment data table includes common attributes of the fragments, and the individual attributes of the fragments are stored in a single attribute of the fragment data table in the form of key-value pairs, or a fragment data sub-table is created for the individual attributes of the fragments, and the fragment data sub-table is associated with the fragment data table through a fragment foreign key.

6. The method for identifying and associating ground monitoring data according to claim 4, wherein: The current monitoring data is stored in a target database, and the method for building the target database includes: A task data table is created according to the monitoring task, wherein the task data table includes entity common attributes, entity individual attributes, space common attributes, space individual attributes, segment common attributes, and segment individual attributes.

7. The method for identifying and associating ground monitoring data according to claim 1, wherein: The current object includes: a physical object, a spatial object and a fragment object, and the association relationship includes at least any one of the following: an association relationship between physical objects and physical objects, an association relationship between spatial objects and physical objects, an association relationship between physical objects and fragment objects, and an association relationship between spatial objects and fragment objects.

8. The identification and association system of ground monitoring data is characterized by: include: A data receiving module, configured to receive current monitoring data of the current object and identification data of the object to be associated; An identifier generation module is used to encode the current object according to a preset encoding scheme and current monitoring data to obtain an identifier of the current object; an identifier determining module, configured to determine an identifier of the object to be associated based on the identification data of the object to be associated; The relationship establishing module is used to establish an association relationship between the current object and the object to be associated according to the identifier of the current object and the identifier of the object to be associated.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images