Spatiotemporal data engine and grid data access and retrieval method
By defining the indexing mode and mapping of spatiotemporal data in Elasticsearch, a logical indexing system is built, which solves the problem of accuracy and low efficiency of existing spatiotemporal data engines in large-scale spatiotemporal data retrieval, and realizes efficient and flexible spatiotemporal data retrieval and grid data management.
Patent Information
- Application Number
- CN202410939660.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-15
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2044-07-15
AI Technical Summary
Existing spatiotemporal data engines have problems with retrieval accuracy and inefficiency when processing large-scale spatiotemporal data, especially when processing grid data, which requires complex preprocessing and postprocessing steps, resulting in low efficiency.
A spatiotemporal data engine was designed, including a spatiotemporal data model building module, a spatiotemporal data mapping building module, a spatiotemporal data import module and a query execution unit. Elasticsearch is used for indexing and querying, and by defining the index pattern, specifying field types and analyzers, it can realize Efficient storage and retrieval of data, and a logical indexing system is built through the grid data connection method, generating grid encoding, and supporting rapid positioning and filtering.
It realizes efficient and accurate spatio-temporal data retrieval, improves retrieval efficiency and scalability, meets the flexible search needs of different users, and maintains good expansion capabilities when the data volume increases.
Smart Images

Figure CN118467860B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to spatiotemporal data processing, and in particular to a spatiotemporal data engine and a grid data connection and retrieval method. Background Art
[0002] With the development of information technology, the scale and complexity of spatiotemporal data are increasing. How to efficiently store, retrieve and manage this data has become a current research hotspot. Traditional database systems (such as Cassandra) face performance bottlenecks and scalability issues when processing large-scale spatiotemporal data. Elasticsearch, as a distributed search and analysis engine at the core of ElasticStack, provides very powerful data indexing and search capabilities, which is very suitable for processing large-scale spatiotemporal data.
[0003] Existing spatiotemporal data engines mostly rely on the query language and index mechanism of specific databases, lacking flexibility and scalability. In addition, when processing grid data, they often need to perform complex pre-processing and post-processing steps, which is inefficient. Summary of the invention
[0004] In view of the above-mentioned shortcomings of the prior art, the present invention provides a spatiotemporal data engine and a grid data access and retrieval method, which can effectively overcome the defects of the prior art in low retrieval accuracy and low retrieval efficiency for large-scale spatiotemporal data.
[0005] To achieve the above objectives, the present invention is implemented through the following technical solutions:
[0006] A spatiotemporal data engine, including a spatiotemporal data model building module, a spatiotemporal data mapping building module, a spatiotemporal data import module and a query execution unit;
[0007] The spatiotemporal data model building module defines one or more index patterns for managing spatiotemporal data in Elasticsearch;
[0008] The spatiotemporal data mapping building block defines the mapping of how spatiotemporal data is stored and indexed in Elasticsearch, and specifies the type of each field, the indexing strategy, and any custom analyzers or filters in the mapping;
[0009] The spatiotemporal data import module imports spatiotemporal data into Elasticsearch and stores and indexes the imported spatiotemporal data based on mapping;
[0010] The query execution unit uses the query DSL to execute real-time data query or data analysis query.
[0011] Preferably, each index pattern defined by the spatiotemporal data model building module in Elasticsearch includes necessary field definitions;
[0012] The necessary field definitions include a geographic location field using the Geo-Point type, a timestamp field using the Date type, and other related attribute fields.
[0013] Preferably, when importing the spatiotemporal data into Elasticsearch, the spatiotemporal data import module ensures that the data format complies with the mapping, and the spatiotemporal data import module imports the spatiotemporal data in batches through the Bulk API of Elasticsearch.
[0014] Preferably, the query execution unit includes a query DSL construction module, a spatiotemporal data query execution module, an optimization and maintenance module, and a backup and recovery module;
[0015] Query DSL building module, build a query DSL for spatiotemporal data in Elasticsearch;
[0016] The spatiotemporal data query execution module uses the query DSL to execute real-time data query or data analysis query;
[0017] Optimize the maintenance module, regularly query and analyze index performance, and optimize and adjust the mapping;
[0018] The backup and recovery module backs up index data regularly and restores data when needed.
[0019] Preferably, the query DSL constructed by the query DSL construction module includes spatial query and temporal query;
[0020] Among them, spatial queries include Geo-Bounding Box and Geo-Polygon, and time queries include RangeQuery and Date Range Query.
[0021] Preferably, the optimization and maintenance module regularly queries and analyzes index performance through various tools and APIs provided by Elasticsearch for monitoring index performance, and optimizes and adjusts the mapping to ensure efficient operation of the spatiotemporal data engine;
[0022] The backup and restore module creates snapshots of the index through the Snapshot and Restore function of Elasticsearch, regularly backs up index data, and restores data when needed.
[0023] The grid data connection method comprises the following steps:
[0024] S1. The user imports spatiotemporal data of various data types and creates corresponding data sources for the imported spatiotemporal data;
[0025] S2, the spatiotemporal data engine parses the spatiotemporal data according to the data type of the data source datasource, extracts the geometry information of the elements, builds a logical index system, and generates one or more grid codes;
[0026] S3, the spatiotemporal data engine creates a grid data object based on the data analysis results;
[0027] S4. The spatiotemporal data engine imports the created grid data object into the data index library of Elasticsearch.
[0028] Preferably, in S1, the user imports spatiotemporal data of various data types, and creates a corresponding data source datasource for the imported spatiotemporal data, including:
[0029] When creating a corresponding data source datasource for the imported spatiotemporal data, the user needs to define and start a data coding and storage task for parsing the imported spatiotemporal data and preparing it for storage.
[0030] Preferably, the grid data object includes the grid code stored in the grid code field geoNum, the geometry information of the element stored in the geometry field iwhereGeometry, and user-defined or system-required information stored in other related fields.
[0031] The grid data retrieval method comprises the following steps:
[0032] S1, the user inputs the spatial range, grid code, search target, and query condition related information used to construct the search rule;
[0033] S2, the spatiotemporal data engine builds search rules based on user input information;
[0034] S3, the spatiotemporal data engine creates a query request in Elasticsearch based on the constructed retrieval rules;
[0035] S4, Elasticsearch returns the corresponding query results according to the search rules;
[0036] The query results include the spatiotemporal data required by the user, and these spatiotemporal data have been processed according to the user's sorting and filtering rules.
[0037] Preferably, the search rules include:
[0038] The prefix matching rule geonumQuery is used for fast positioning based on the grid code;
[0039] Time code query rule timeCodeQuery is used to filter spatiotemporal data within the time range set by the user;
[0040] The property query rule propertyQuery is used to filter spatiotemporal data based on user-defined attributes;
[0041] Sorting rule sortOption is used to sort the query results according to the sorting rule set by the user;
[0042] The filter rule excludes is used to delete unnecessary attribute fields from the query results according to the filter rules set by the user.
[0043] An electronic device, characterized in that it includes at least one processor and a memory communicatively connected to the at least one processor, the memory storing instructions executable by the at least one processor, the instructions being executed by the at least one processor so that the at least one processor can execute any of the methods described above.
[0044] A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to execute any of the above-described methods.
[0045] A computer program product, characterized in that it comprises a computer program, and when the computer program is executed by a processor, it implements any of the methods described above.
[0046] Compared with the prior art, the spatiotemporal data engine and grid data access and retrieval method provided by the present invention have the following beneficial effects:
[0047] 1) Accuracy: The precise grid coding and logical indexing system ensure the accuracy of the retrieval results;
[0048] 2) Efficiency: The optimized indexing and search mechanism based on Elasticsearch can greatly improve the retrieval efficiency of spatiotemporal data;
[0049] 3) Flexibility: It supports the import of spatiotemporal data of various data types and the flexible construction of retrieval rules to meet the retrieval needs of different users;
[0050] 4) Scalability: Elasticsearch’s distributed architecture ensures the scalability of the spatiotemporal data engine as the amount of data grows. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] 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 prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0052] Figure 1 It is a schematic diagram of the architecture of the spatiotemporal data engine in the present invention;
[0053] Figure 2 It is a schematic diagram of the process of grid data connection in the present invention;
[0054] Figure 3 It is a schematic diagram of the process of grid data retrieval in the present invention;
[0055] Figure 4 It is a schematic diagram of the structure of an electronic device for implementing an embodiment of the present invention. DETAILED DESCRIPTION
[0056] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of 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.
[0057] Spatiotemporal data engines, such as Figure 1 As shown, it includes a spatiotemporal data model building module, a spatiotemporal data mapping building module, a spatiotemporal data importing module and a query execution unit;
[0058] The spatiotemporal data model building module defines one or more index patterns for managing spatiotemporal data in Elasticsearch;
[0059] The spatiotemporal data mapping building block defines the mapping of how spatiotemporal data is stored and indexed in Elasticsearch, and specifies the type of each field, the indexing strategy, and any custom analyzers or filters in the mapping;
[0060] The spatiotemporal data import module imports spatiotemporal data into Elasticsearch and stores and indexes the imported spatiotemporal data based on mapping;
[0061] The query execution unit uses the query DSL to execute real-time data query or data analysis query.
[0062] ① Each index pattern defined in Elasticsearch by the spatiotemporal data model building module contains the necessary field definitions;
[0063] The necessary field definitions include a geographic location field using the Geo-Point type, a timestamp field using the Date type, and other related attribute fields.
[0064] ② For spatiotemporal data, the custom analyzers specified in the spatiotemporal data mapping construction module in the mapping include geospatial analyzers (such as Geo-Point) and time analyzers (such as Date Format).
[0065] ③ When the spatiotemporal data import module imports spatiotemporal data into Elasticsearch, it ensures that the data format conforms to the mapping. The spatiotemporal data import module imports spatiotemporal data in batches through the Bulk API of Elasticsearch.
[0066] ④ The query execution unit includes a query DSL construction module, a spatiotemporal data query execution module, an optimization and maintenance module, and a backup and recovery module;
[0067] Query DSL building module, build a query DSL for spatiotemporal data in Elasticsearch;
[0068] The spatiotemporal data query execution module uses the query DSL to execute real-time data query or data analysis query;
[0069] Optimize the maintenance module, regularly query and analyze index performance, and optimize and adjust the mapping;
[0070] The backup and recovery module backs up index data regularly and restores data when needed.
[0071] 1) The query DSL constructed by the query DSL construction module includes spatial query and temporal query;
[0072] Among them, spatial queries include Geo-Bounding Box and Geo-Polygon, and time queries include RangeQuery and Date Range Query.
[0073] 2) The spatiotemporal data query execution module uses the query DSL to execute real-time data queries or data analysis queries. In Elasticsearch, a rich API is provided to execute these queries, including REST API and various client libraries.
[0074] 3) The optimization and maintenance module regularly queries and analyzes index performance through various tools and APIs provided by Elasticsearch for monitoring index performance, and optimizes and adjusts the mapping to ensure efficient operation of the spatiotemporal data engine.
[0075] 4) The backup and recovery module creates snapshots of the index through the Snapshot and Restore function of Elasticsearch, regularly backs up index data, and restores data when needed.
[0076] Through the above technical solution, Elasticsearch can be effectively used to implement the application of spatiotemporal data engine, which can not only provide powerful search and analysis capabilities, but also better support the storage and indexing needs of spatiotemporal data.
[0077] In the technical solution of this application, based on the above-mentioned spatiotemporal data engine, a grid data connection method is proposed, such as Figure 2 As shown, the following steps are included:
[0078] S1. The user imports spatiotemporal data of various data types and creates corresponding data sources for the imported spatiotemporal data;
[0079] S2. The spatiotemporal data engine parses the spatiotemporal data according to the data type of the data source, extracts the geometry information of the elements, builds a logical index system, and generates one or more grid codes (these grid codes facilitate subsequent rapid data retrieval and efficient data management).
[0080] S3, the spatiotemporal data engine creates a grid data object based on the data analysis results;
[0081] S4. The spatiotemporal data engine imports the created grid data objects into the data index library of Elasticsearch to ensure that the grid data can be efficiently accessed by subsequent data retrieval.
[0082] ① The user imports spatiotemporal data of various data types and creates corresponding data sources for the imported spatiotemporal data, including:
[0083] When creating a corresponding data source datasource for the imported spatiotemporal data, the user needs to define and start a data coding and storage task for parsing the imported spatiotemporal data and preparing it for storage.
[0084] ② The grid data object includes the grid code stored in the grid code field geoNum, the geometry information of the feature stored in the geometry field iwhereGeometry, and user-defined or system-required information stored in other related fields.
[0085] In the technical solution of this application, based on the above-mentioned spatiotemporal data engine and grid data access method, a grid data retrieval method is proposed, such as Figure 3 As shown, the following steps are included:
[0086] S1, the user inputs the spatial range, grid code, search target, and query condition related information used to construct the search rule;
[0087] S2, the spatiotemporal data engine builds search rules based on user input information;
[0088] S3, the spatiotemporal data engine creates query requests in Elasticsearch based on the constructed retrieval rules (these query requests utilize the powerful search capabilities of Elasticsearch and combine the characteristics of spatiotemporal data to efficiently perform query operations);
[0089] S4, Elasticsearch returns the corresponding query results according to the search rules;
[0090] The query results include the spatiotemporal data required by the user, and these spatiotemporal data have been processed according to the user's sorting and filtering rules.
[0091] Specifically, the search rules include:
[0092] The prefix matching rule geonumQuery is used for fast positioning based on the grid code;
[0093] Time code query rule timeCodeQuery is used to filter spatiotemporal data within the time range set by the user;
[0094] The property query rule propertyQuery is used to filter spatiotemporal data based on user-defined attributes;
[0095] Sorting rule sortOption is used to sort the query results according to the sorting rule set by the user;
[0096] The filter rule excludes is used to delete unnecessary attribute fields from the query results according to the filter rules set by the user.
[0097] Through the above technical solution, an efficient, flexible and scalable spatiotemporal data engine can be implemented, which can access and retrieve large-scale spatiotemporal data sets. By utilizing the characteristics of Elasticsearch, the spatiotemporal data engine can provide users with accurate and fast data query and analysis capabilities to meet the spatiotemporal data needs in different scenarios.
[0098] Suppose you need to build a city traffic management system that needs to process a large amount of vehicle location data. Users can import the vehicle's GPS data into the system, and the system automatically parses the vehicle's location information and generates a grid code (the above process corresponds to grid data import).
[0099] When users need to query the distribution of vehicles in a specific area, they only need to enter conditions such as spatial range and query time, and the system can quickly return the location information of vehicles that meet the conditions (the above process corresponds to grid data retrieval). Using the technical solution of this application, the urban traffic management system can efficiently process and retrieve large-scale vehicle location data, providing strong support for traffic planning and management.
[0100] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements will not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.
[0101] According to the above embodiments, the technical solution of the present application also provides an electronic device, a computer-readable storage medium and a computer program product.
[0102] Figure 4 A schematic diagram of the structure of an electronic device 800 for implementing an embodiment of the present invention is provided. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or claimed herein.
[0103] like Figure 4As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM 802) or a computer program loaded from a storage unit 808 to a random access memory (RAM 803). In the RAM 803, various programs and data required for the operation of the electronic device 800 can also be stored. The computing unit 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output interface (I / O interface 805) is also connected to the bus 804.
[0104] Multiple components in the electronic device 800 are connected to the I / O interface 805, including: an input unit 806, such as a keyboard, a mouse, etc.; an output unit 807, such as various types of displays, speakers, etc.; a storage unit 808, such as a disk, an optical disk, etc.; and a communication unit 809, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 809 allows the electronic device 800 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0105] The computing unit 801 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 801 performs the various methods and processes described above, such as the grid data interface method and the grid data retrieval method. For example, in some embodiments, the grid data interface method and the grid data retrieval method may be implemented as a computer software program, which is tangibly included in a machine-readable medium, such as a storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 800 via the ROM 802 and / or the communication unit 809. When the computer program is loaded into the RAM 803 and executed by the computing unit 801, one or more steps of the grid data interface method and the grid data retrieval method described above may be executed. Alternatively, in other embodiments, the computing unit 801 may be configured to execute the grid data access method and the grid data retrieval method in any other appropriate manner (eg, by means of firmware).
[0106] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0107] The program code for implementing the method of the present invention can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or server.
[0108] In the context of the present invention, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0109] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0110] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.
[0111] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.
[0112] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in the present disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution disclosed in the present invention can be achieved, and this document is not limited here.
[0113] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims
1. Spatiotemporal data engine, Features: It includes a spatiotemporal data model building module, a spatiotemporal data mapping building module, a spatiotemporal data importing module and a query execution unit; The spatiotemporal data model building module defines one or more index patterns for managing spatiotemporal data in Elasticsearch; The spatiotemporal data mapping building block defines the mapping of how spatiotemporal data is stored and indexed in Elasticsearch, and specifies the type of each field, the indexing strategy, and any custom analyzers or filters in the mapping; The spatiotemporal data import module imports spatiotemporal data into Elasticsearch and stores and indexes the imported spatiotemporal data based on mapping; The query execution unit uses the query DSL to execute real-time data query or data analysis query; Each index pattern defined by the spatiotemporal data model building module in Elasticsearch contains necessary field definitions; The necessary field definitions include the geographic location field using the Geo-Point type, the timestamp field using the Date type, and other related attribute fields; When the spatiotemporal data import module imports the spatiotemporal data into Elasticsearch, it ensures that the data format conforms to the mapping, and the spatiotemporal data import module imports the spatiotemporal data in batches through the Bulk API of Elasticsearch; The query execution unit includes a query DSL construction module, a spatiotemporal data query execution module, an optimization and maintenance module, and a backup and recovery module; Query DSL building module, build a query DSL for spatiotemporal data in Elasticsearch; The spatiotemporal data query execution module uses the query DSL to execute real-time data query or data analysis query; Optimize the maintenance module, regularly query and analyze index performance, and optimize the mapping; Backup and recovery module, regularly backing up index data and restoring data when needed; The spatiotemporal data engine performs data analysis on the spatiotemporal data according to the data type of the data source datasource, extracts the geometry information of the elements, and constructs a logical index system to generate one or more grid codes. The spatiotemporal data engine creates a grid data object according to the data analysis result; The data source datasource is created by the spatiotemporal data engine based on the spatiotemporal data of various data types imported by the user; The grid data object includes the grid code stored in the grid code field geoNum, the geometry information of the element stored in the geometry field iwhereGeometry, and the user-defined or system-required information stored in other related fields.
2. The spatiotemporal data engine according to claim 1, Features: The query DSL constructed by the query DSL construction module includes spatial query and temporal query; Among them, spatial queries include Geo-Bounding Box and Geo-Polygon, and time queries include Range Query and Date Range Query.
3. The spatiotemporal data engine according to claim 1, Features: The optimization and maintenance module regularly queries and analyzes index performance through various tools and APIs provided by Elasticsearch for monitoring index performance, and optimizes and adjusts the mapping to ensure efficient operation of the spatiotemporal data engine; The backup and restore module creates snapshots of the index through the Snapshot and Restore function of Elasticsearch, regularly backs up index data, and restores data when needed.
4. A grid data connection method, applied to the spatiotemporal data engine according to claim 1, Features: The following steps are involved: S1. The user imports spatiotemporal data of various data types and creates corresponding data sources for the imported spatiotemporal data; S2, the spatiotemporal data engine parses the spatiotemporal data according to the data type of the data source datasource, extracts the geometry information of the elements, builds a logical index system, and generates one or more grid codes; S3, the spatiotemporal data engine creates a grid data object based on the data analysis results; S4. The spatiotemporal data engine imports the created grid data object into the data index library of Elasticsearch.
5. The grid data access method according to claim 4, Features: In S1, users import spatiotemporal data of various data types and create corresponding data sources for the imported spatiotemporal data, including: When creating a corresponding data source datasource for the imported spatiotemporal data, the user needs to define and start a data coding and storage task for parsing the imported spatiotemporal data and preparing it for storage.
6. The grid data connection method according to claim 4, Features: The grid data object includes the grid code stored in the grid code field geoNum, the geometry information of the element stored in the geometry field iwhereGeometry, and the user-defined or system-required information stored in other related fields.
7. A grid data retrieval method, applied to the grid data access method according to claim 4, Features: The following steps are involved: S1, the user inputs the spatial range, grid code, search target, and query condition related information used to construct the search rule; S2, the spatiotemporal data engine builds search rules based on user input information; S3, the spatiotemporal data engine creates a query request in Elasticsearch based on the constructed retrieval rules; S4, Elasticsearch returns the corresponding query results according to the search rules; The query results include the spatiotemporal data required by the user, and these spatiotemporal data have been processed according to the user's sorting and filtering rules.
8. The grid data retrieval method according to claim 7, Features: The search rules include: The prefix matching rule geonumQuery is used for fast positioning based on the grid code; Time code query rule timeCodeQuery is used to filter spatiotemporal data within the time range set by the user; The property query rule propertyQuery is used to filter spatiotemporal data based on user-defined attributes; Sorting rule sortOption is used to sort the query results according to the sorting rule set by the user; The filter rule excludes is used to delete unnecessary attribute fields from the query results according to the filter rules set by the user.
9. An electronic device, Features: It includes at least one processor and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method as described in any one of claims 4 to 8.
10. A non-transitory computer-readable storage medium storing computer instructions, Features: The computer instructions are used to make the computer execute the method according to any one of claims 4 to 8.
11. A computer program product, Features: The method comprises a computer program which, when executed by a processor, implements the method according to any one of claims 4 to 8.
