A spatial database system for oil and gas exploration and a spatial data management method
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BGP INC CHINA NAT PETROLEUM CORP
- Filing Date
- 2025-12-26
- Publication Date
- 2026-05-26
Smart Images
Figure CN122086860A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of database management technology in petroleum seismic exploration, and in particular to a spatial database system and spatial data management method for oil and gas exploration. Background Technology
[0002] During oil and gas exploration, a large amount of spatial data is generated, such as the geographical coordinates of the exploration area, the spatial distribution of geological structures, and the location and extent of oil and gas reservoirs. This spatial data is crucial for accurately assessing oil and gas resources and formulating exploration plans and exploitation strategies.
[0003] However, existing database systems suffer from numerous problems when processing spatial data for oil and gas exploration. In particular, they struggle to effectively store and manage complex spatial objects such as points, lines, polygons, multipoints, and multiline strings, making it difficult to guarantee data integrity and accuracy. Furthermore, the lack of efficient querying and analysis capabilities for spatial data hinders the rapid acquisition of oil and gas exploration information relevant to specific geographical areas or geological conditions, impacting the efficiency of exploration work and the scientific rigor of decision-making. Moreover, poor compatibility between different data sources and formats makes it difficult to integrate and share multi-source, heterogeneous spatial data generated during oil and gas exploration, increasing the complexity and cost of data processing.
[0004] To address the aforementioned issues, a new scheme for constructing seismic exploration databases is urgently needed. Summary of the Invention
[0005] This application discloses an oil and gas exploration spatial database system and a spatial data management method, which aims to manage data with spatial attributes during the oil and gas exploration process to meet the data management requirements of the seismic exploration field.
[0006] In a first aspect, this application discloses a spatial database system for oil and gas exploration, the system comprising: a data interface, a unified object wrapper, a data driver, a model object table structure, an extended database, and a feature synchronization process; wherein, The data interface is the interaction interface between the system and external applications or users. It receives various data requests from the oil and gas exploration business system and supports input and output of multiple spatial object types. The data requests include at least data query, data insertion, data update, and data deletion operations. The unified object wrapper encapsulates different types of spatial objects in a unified manner, identifies and parses the attribute information of each spatial object, converts the attribute information into a database-recognizable format, and restores the data in the database to the original spatial object type when outputting data. The data driver interacts with the underlying database to execute data operation instructions; wherein, the data operation instructions include functions corresponding to database communication, and process the storage and retrieval of spatial data based on the attribute information passed by the unified object wrapper; The model object table structure stores spatial data for oil and gas exploration, and the model object table structure includes at least a geometry type field for storing geometric information of spatial objects; The extended database uses PostgreSQL as the underlying database and integrates the Postgis extension, which is a spatial database extension applied to the PostgreSQL database. The feature synchronization process synchronizes the spatial data features from the original table to the feature table, and runs automatically according to preset rules and time intervals. It monitors changes in the spatial data in the original table in real time and updates the corresponding information in the feature table in a timely manner, so as to perform query and analysis operations based on the updated spatial data.
[0007] Preferably, it further includes: an auxiliary process, which at least includes a daemon process, a conversion process, a listening process, and a subscription process; wherein, The daemon process monitors the running status of the entire database system, and issues timely alarms and takes corresponding recovery measures when the system experiences abnormalities or failures. The conversion process converts spatial data in different formats into a unified format supported by the system for storage and processing. The monitoring process listens to external data sources or internal system events and messages in real time. When new spatial data or information is generated, it captures it in a timely manner and notifies the system to process it. The subscription process monitors data changes and event triggering in the database in real time based on the subscription settings of the user or external business system. When the subscription conditions are met, the system automatically pushes the corresponding information to the subscriber, realizing real-time data push and sharing.
[0008] Optionally, the system includes a data feature acquisition module and a data compression and decompression module; The data feature acquisition module and the data compression and decompression module trigger compression and decompression rules based on the real-time features returned by the monitoring interface and the preset threshold. The data compression and decompression module is an independent class that adapts to a unified object wrapper and a data driver through an interface. The compression and decompression functions are integrated into the data driver, and the unified object sets whether to compress, compress, or decompress, thus deploying data operations in the driver.
[0009] Secondly, this application discloses a spatial data management method applied to the aforementioned oil and gas exploration spatial database system, the method comprising: External business systems send data requests containing spatial objects through data interfaces; The unified object wrapper parses and encapsulates the spatial objects in the data request, converts the spatial objects into a database-recognizable format, and passes them to the data driver. The data driver stores spatial and attribute data in a model object table structure of the PostgreSQL database, where the geometric information of the spatial objects is stored in a field of type geometry.
[0010] Preferably, the method further includes: The feature synchronization process periodically or in real-time monitors changes in spatial data in the original table; When new spatial data features or updates to existing data are detected, the changes in spatial data are synchronized to the feature table so that the spatial data in the feature table always remains consistent with the spatial data in the original table.
[0011] Preferably, the method further includes: Users initiate spatial data query requests through the data interface; The business interface passes the query request to the unified object wrapper; The unified object wrapper converts the query conditions corresponding to the query request into SQL statements that can be executed by the database.
[0012] Preferably, the method further includes: The data driver executes the transformed SQL statement, retrieves the corresponding spatial and attribute data from the database, and returns the results to the unified object wrapper. The unified object wrapper parses and encapsulates the results, restoring them to the original spatial object type, and returns the query results to the user or external business system through the data interface.
[0013] Preferably, the method further includes: The daemon process monitors the database system's operating status in real time. When it detects any abnormalities in the operating status, the daemon process takes corresponding measures to ensure the stable operation of the system. The operating status includes server resource usage, database connection status, and process running status. The monitoring process listens for external data sources or internal system events and messages in real time. When an event or message is received, the monitoring process promptly notifies the system to take corresponding actions so that the system can respond to external changes in a timely manner and maintain the real-time performance and accuracy of the data. The subscription process monitors data changes and event triggers in the database in real time based on the subscription settings of users or external business systems. When the subscription conditions are met, the subscription process automatically pushes the corresponding information to the subscribers, realizing real-time data sharing and interaction.
[0014] Thirdly, this application discloses an electronic device comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to perform the method as described in any of the preceding aspects.
[0015] Fourthly, this application discloses a non-transitory computer-readable storage medium in which, when the instructions in the storage medium are executed by a processor of an electronic device, enable the electronic device to perform the methods described in any of the preceding aspects.
[0016] Fifthly, this application discloses a computer program product in which, when the instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to perform the method described in any of the preceding aspects.
[0017] The seismic exploration database construction scheme provided in this application enables the GeoEast system to achieve efficient, flexible, and reliable database construction. Specifically, the technical solution provided in this application can include the following beneficial effects: (1) Efficient spatial data management Through a unified object wrapper and a specially designed model object table structure, various complex spatial objects can be effectively stored and managed, ensuring the integrity and accuracy of oil and gas exploration spatial data and providing a reliable data foundation for subsequent queries and analysis.
[0018] (2) Powerful spatial query and analysis capabilities With the help of the PostgreSQL database and PostGIS extensions, it provides a wealth of spatial functions and indexes, supporting efficient spatial data query and analysis operations, such as quickly locating oil and gas reservoirs in a specific geographical area and accurately calculating the area and volume of geological structures, which greatly improves the efficiency of oil and gas exploration and the scientific nature of decision-making.
[0019] (3) Good compatibility and scalability The system's conversion process can handle multi-source heterogeneous spatial data, improving the system's compatibility with different data sources and formats, and facilitating the integration and sharing of various data during oil and gas exploration. Meanwhile, the PostgreSQL-based architecture offers excellent scalability, allowing for the easy addition of new functional modules and storage space according to business needs, meeting the evolving requirements of oil and gas exploration operations.
[0020] (4) Real-time data synchronization and interaction The feature synchronization process ensures the real-time consistency of spatial data, while the listening and subscription processes enable real-time interaction and data push between the system and external data sources and other systems, improving the timeliness and utilization efficiency of data and promoting collaborative work and information sharing in oil and gas exploration operations. Attached Figure Description
[0021] Figure 1 This is a schematic diagram of the structure of the oil and gas exploration spatial database system provided in this application; Figure 2 A diagram illustrating the rapid conversion between spatial objects and business objects provided in this application; Figure 3 This is a visualization diagram of the spatial points of the grid data provided in this application; Figure 4 This is a visualization diagram of the spatial locations of the well data provided in this application; Figure 5 A flowchart of the spatial data management method provided in this application; Figure 6 Another flowchart for the spatial data management method provided in this application; Figure 7 A block diagram of an electronic device provided in this application; Figure 8 A block diagram of another electronic device provided in this application. Detailed Implementation
[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0023] This application discloses an oil and gas exploration spatial database system and a spatial data management method, which aims to manage data with spatial attributes during the oil and gas exploration process to meet the data management requirements of the seismic exploration field.
[0024] Example 1 Reference Figure 1 This application discloses a spatial database system for oil and gas exploration, the system comprising: a data interface 110, a unified object wrapper 120, a data driver 130, a model object table structure 140, an extended database 150, and a feature synchronization process 160.
[0025] The data interface 110 serves as the interaction interface between the system and external applications or users. Specifically, it is a business interface or a RESTful API that receives various data requests from the oil and gas exploration business system. It supports the input and output of various spatial object types, such as Point, LineString, Polygon, MultiPoint, and MultiLineString, to meet the processing needs of different spatial data in oil and gas exploration. The data requests include at least data query, data insertion, data update, and data deletion operations.
[0026] The unified object wrapper 120 encapsulates different types of spatial objects in a unified manner, enabling them to be processed and stored consistently in the database system. It identifies and parses the attribute information of each spatial object, converts the attribute information into a database-recognizable format, and restores the data in the database to the original spatial object type during data output. The data driver 130 interacts with the underlying database to execute data operation instructions. These instructions include functions corresponding to database communication, such as reading, writing, updating, and deleting data. It also processes the storage and retrieval of spatial data based on attribute information passed by the unified object wrapper. The data driver also supports SQL functions (such as ST_AsBinary) for various spatial operations and analyses, such as calculating the area, length, distance, and intersection relationships of spatial objects.
[0027] The model object table structure 140 stores spatial data for oil and gas exploration. The model object table structure includes at least a geometry type field for storing geometric information of spatial objects. This table structure can efficiently organize and manage spatial data, while supporting association and integration with other non-spatial data, facilitating comprehensive querying and analysis.
[0028] The extended database 150 uses PostgreSQL as its underlying database due to its powerful data management capabilities and good scalability. It also integrates the PostGIS extension, a spatial database extension for PostgreSQL databases; providing rich spatial data types, functions, and indexes, effectively supporting the storage, querying, and analysis of spatial data, meeting the high-performance requirements of oil and gas exploration spatial databases for spatial data processing.
[0029] The feature synchronization process 160 synchronizes the spatial data features from the original table to the feature table, ensuring the consistency and accuracy of the spatial data. It also runs automatically according to preset rules and time intervals, monitors changes in the spatial data in the original table in real time, and updates the corresponding information in the feature table in a timely manner so that query and analysis operations can be performed based on the updated spatial data.
[0030] Furthermore, the system may also include: auxiliary processes, which at least include a daemon process, a conversion process, a listening process, and a subscription process; wherein, the daemon process monitors the operating status of the entire database system to ensure the stability and reliability of the system, and promptly issues alarms and takes corresponding recovery measures when the system malfunctions or fails; the conversion process converts spatial data of different formats into a unified format supported by the system for storage and processing, and can handle spatial data from various data sources, such as GIS files, remote sensing image data, etc., improving the system's compatibility with multi-source heterogeneous data; the listening process monitors external data sources or internal system events and messages in real time, and when new spatial data or information is generated, it promptly captures and notifies the system to process it, such as importing new data into the database or triggering corresponding business processes; the subscription process monitors data changes and event triggering in the database in real time according to the subscription settings of users or external business systems, and when the subscription conditions are met, the system automatically pushes the corresponding information to the subscribers, realizing real-time data push and sharing, and improving data utilization efficiency and interactivity.
[0031] Furthermore, such as Figure 6 As shown, the system includes a data feature acquisition module and a data compression and decompression module. These modules trigger compression and decompression rules based on real-time features returned by the monitoring interface and preset thresholds, such as automatic compression of massive amounts of data and on-demand decompression at the receiving end. The data compression and decompression modules are independent classes that adapt to a unified object wrapper and data driver via an interface. Compression and decompression functions are integrated into the data driver. A compression flag and settings for compression or decompression are configured in the unified object. Deploying data operations within the driver reduces the complexity of the unified object's relationships and the coupling between interfaces. The compression algorithm uses floating-point data compression such as ZIP and ZFP.
[0032] The seismic exploration database construction scheme provided in this application enables the GeoEast system to achieve efficient, flexible, and reliable database construction. Specifically, the technical solution provided in this application can include the following beneficial effects: (1) Efficient spatial data management: Through a unified object wrapper and a specially designed model object table structure, it can effectively store and manage various complex spatial objects, ensuring the integrity and accuracy of oil and gas exploration spatial data, and providing a reliable data foundation for subsequent queries and analysis.
[0033] It should be noted that in the management and fusion of multi-source data in oil and gas exploration, the geometry type field is a structured data field used to describe the "spatial morphology and location" of geographic / geological targets. Based on the characteristics of oil and gas exploration data, the geometry type field is mainly divided into four categories—points, lines, surfaces, and volumes—to store spatial geometric information, corresponding to the spatial description needs of different geological targets. It is the core link connecting spatial relationships between data such as seismic data, well data, fault data, and stratigraphic data. Its core value lies in binding non-spatial data (such as well logging curves and seismic attribute values) with "subsurface location / morphology," supporting geological model construction, spatial analysis, and visualization.
[0034] (2) Powerful spatial query and analysis capabilities. With the help of the PostgreSQL database and PostGIS extension, it provides a wealth of spatial functions and indexes, supporting efficient spatial data query and analysis operations, such as quickly locating oil and gas reservoirs in a specific geographical area and accurately calculating the area and volume of geological structures, which greatly improves the efficiency of oil and gas exploration and the scientific nature of decision-making.
[0035] (3) Good compatibility and scalability: The conversion process in the system can handle multi-source heterogeneous spatial data, improving the system's compatibility with different data sources and data formats, and facilitating the integration and sharing of various data in the oil and gas exploration process. At the same time, the architecture based on the PostgreSQL database has good scalability, and new functional modules and storage space can be easily added according to business needs to meet the needs of the continuous development of oil and gas exploration business.
[0036] (4) Real-time data synchronization and interaction: The feature synchronization process ensures the real-time consistency of spatial data, while the monitoring process and subscription process enable real-time interaction and data push between the system and external data sources and other systems, improving the timeliness and utilization efficiency of data, and promoting collaborative work and information sharing in oil and gas exploration.
[0037] Example 2 Please see Figures 2 to 5 ,in, Figure 5 A flowchart of a spatial data management method provided in this application, which is applied to the oil and gas exploration spatial database system shown in Embodiment 1, the method comprising: Step S201: The external business system sends a data request containing spatial objects through the data interface.
[0038] Specifically, external business systems send data requests containing spatial objects (such as Point, LineString, etc.) through business interfaces or RESTful APIs.
[0039] Step S202: The unified object wrapper parses and encapsulates the spatial object in the data request, converts the spatial object into a database-recognizable format, and passes it to the data driver.
[0040] Step S203: The data driver stores spatial data and attribute data into the model object table structure of the PostgreSQL database, wherein the geometric information of the spatial object is stored in a field of type geometry.
[0041] Furthermore, the method also includes: a feature synchronization process periodically or in real-time monitoring changes in spatial data in the original table; when new spatial data features or updates to existing data are detected, the spatial data changes are synchronized to the feature table to ensure that the spatial data in the feature table remains consistent with the spatial data in the original table. It should be noted that during data input, if the conversion process encounters spatial data in different formats, it will convert it to a unified format supported by the system before storage to ensure data consistency and compatibility.
[0042] Furthermore, the method also includes: a user initiating a spatial data query request through a data interface, such as querying the distribution of oil and gas reservoirs in a specific area or calculating the area of a geological structure; the business interface passing the query request to a unified object wrapper; and the unified object wrapper converting the query conditions corresponding to the query request into SQL statements executable by the database, which may include spatial functions provided by PostGIS (such as ST_Intersects, ST_Area, etc.).
[0043] Furthermore, the method also includes: the data driver executing the transformed SQL statement, retrieving the corresponding spatial data and attribute data from the database, and returning the result to the unified object wrapper; the unified object wrapper parsing and encapsulating the result, restoring it to the original spatial object type, and returning the query result to the user or external business system through the data interface.
[0044] Furthermore, the method also includes: a daemon process that monitors the database system's operating status in real time. When abnormal operating status is detected, such as high server load, database connection timeout, or process crash, the daemon process takes corresponding measures to ensure stable system operation, such as automatically restarting relevant processes, adjusting server resource allocation, and sending alarm notifications to the administrator. The operating status includes server resource usage (such as CPU, memory, disk I / O), database connection status, and process running status. A listening process monitors external data sources or internal system events and messages in real time, such as new exploration data uploads and database access requests from other systems. When an event or message is received, the listening process promptly notifies the system to perform corresponding processing, such as triggering a data import process, updating the cache, or adjusting system configuration, so that the system can respond to external changes in a timely manner and maintain the real-time performance and accuracy of the data. A subscription process monitors data changes and event triggering in the database in real time according to the subscription settings of users or external business systems. When subscription conditions are met, such as updates to oil and gas exploration data in a specific area or the generation of calculation results for a geological model, the subscription process automatically pushes the corresponding information to subscribers, realizing real-time data sharing and interaction, and improving data utilization efficiency and business collaboration capabilities.
[0045] The seismic exploration database construction scheme provided in this application enables the GeoEast system to achieve efficient, flexible, and reliable database construction. Specifically, the technical solution provided in this application can include the following beneficial effects: (1) Efficient spatial data management: Through a unified object wrapper and a specially designed model object table structure, it can effectively store and manage various complex spatial objects, ensuring the integrity and accuracy of oil and gas exploration spatial data, and providing a reliable data foundation for subsequent queries and analysis.
[0046] (2) Powerful spatial query and analysis capabilities. With the help of the PostgreSQL database and PostGIS extension, it provides a wealth of spatial functions and indexes, supporting efficient spatial data query and analysis operations, such as quickly locating oil and gas reservoirs in a specific geographical area and accurately calculating the area and volume of geological structures, which greatly improves the efficiency of oil and gas exploration and the scientific nature of decision-making.
[0047] (3) Good compatibility and scalability: The conversion process in the system can handle multi-source heterogeneous spatial data, improving the system's compatibility with different data sources and data formats, and facilitating the integration and sharing of various data in the oil and gas exploration process. At the same time, the architecture based on the PostgreSQL database has good scalability, and new functional modules and storage space can be easily added according to business needs to meet the needs of the continuous development of oil and gas exploration business.
[0048] (4) Real-time data synchronization and interaction: The feature synchronization process ensures the real-time consistency of spatial data, while the monitoring process and subscription process enable real-time interaction and data push between the system and external data sources and other systems, improving the timeliness and utilization efficiency of data, and promoting collaborative work and information sharing in oil and gas exploration.
[0049] The following section provides a detailed explanation of the solution provided in this application, using a specific example.
[0050] 1. System Deployment and Configuration 1.1 Install the PostgreSQL database server and the PostGIS extension, ensuring that the relevant functions and spatial data types of PostGIS can be used normally.
[0051] Create a model object table in the database to store spatial data for oil and gas exploration, for example: CREATE TABLE oil_gas_exploration_data ( id SERIAL PRIMARY KEY, name VARCHAR(255), geometry GEOMETRY(Polygon, 4326), other_attributes VARCHAR(255) ); The geometry field stores the geometric information of spatial objects, and 4326 indicates that the spatial reference frame used is WGS84.
[0052] 1.2 Configure the business interface or RESTful API to enable it to communicate with the database server, and set the corresponding interface parameters and permission management to ensure data security and access control.
[0053] 1.3 Start the daemon process, conversion process, listening process, and subscription process, and set their running parameters and monitoring rules, such as the check interval of the daemon process, the list of data formats supported by the conversion process, the event source and message format of the listening process, and the subscription rules and push method of the subscription process.
[0054] 2. Data synchronization 2.1 Data Acquisition Polygonal spatial data of an oil and gas field region was obtained from the oil and gas exploration basin database, representing the extent of the oil and gas field. This data is provided in GeoJSON format, as shown below: json { "type": "Feature", "geometry": { "type": "Polygon", "coordinates": [ [ [10.0, 20.0], [30.0, 20.0], [30.0, 40.0], [10.0, 40.0], [10.0, 20.0] ] ] }, "properties": { "name": "Oil Field A", "production": "1000 barrels / day" } } 2.2 After receiving the GeoJSON data, the conversion process converts it into a system-supported format, such as converting the geometric information into PostGIS's WKB (Well-Known Binary) format.
[0055] 2.3 The unified object wrapper encapsulates the transformed spatial data and related attribute data, generating a database operation object containing the following information: Table name: oil_gas_exploration_data Field value: name: Oil Field A geometry: The converted WKB format polygon geometry information other_attributes:production: 1000 barrels / day 2.4 The data driver, based on information provided by the unified object wrapper, executes the following SQL insert statements to store data in the database: INSERT INTO oil_gas_exploration_data (name, geometry, other_attributes) VALUES ('Oil Field A', ST_GeomFromWKB('geo'), 'production: 1000barrels / day'); ST_GeomFromWKB is a function provided by PostGIS that is used to convert WKB format geometric information into spatial objects in a database.
[0056] 3. Spatial Data Query and Analysis A user initiates a query request through a business interface to retrieve all geological structures intersecting with Oil Field A. The query criteria can be expressed as: SELECT * FROM geological_structures WHERE ST_Intersects(geometry, (SELECT geometry FROM oil_gas_exploration_data WHERE name = 'Oil Field A')); ST_Intersects is a function provided by PostGIS for determining whether two spatial objects intersect, and geological_structures is a table that stores spatial data of geological structures.
[0057] 3.1 The business interface passes the query request to the unified object wrapper, which translates it into a database-executable SQL statement and passes it to the data driver.
[0058] 3.2 The data driver executes the SQL statement to retrieve the geological structure data that intersects with Oil Field A from the database and returns the results to the unified object wrapper.
[0059] 3.3 The unified object wrapper parses and encapsulates the results, converting the geometric information of spatial objects into the original spatial object types (such as Polygon, LineString, etc.), and returns the query results to the user through the business interface. Users can visualize this geological structure data in the client application for further analysis and research.
[0060] 4. Data synchronization and updates Suppose the extent of Oil Field A in the original table oil_gas_exploration_data has changed, and the new polygon coordinates are: json { "type": "Feature", "geometry": { "type": "Polygon", "coordinates": [ [ [15.0, 25.0], [35.0, 25.0], [35.0, 45.0], [15.0, 45.0], [15.0, 25.0] ] ] }, "properties": { "name": "Oil Field A", "production": "1200 barrels / day" } } The feature synchronization process detected a change in the spatial data of Oil Field A in the original table and retrieved the new spatial and attribute data.
[0061] The conversion process converts the new GeoJSON format spatial data to WKB format.
[0062] The unified object wrapper generates a database update operation object containing the following information: Table name: oil_gas_exploration_data Update condition: name = 'Oil Field A' Update field values: geometry: The converted polygon geometry information in the new WKB format. other_attributes:production: 1200 barrels / day The data driver executes the following SQL update statements based on the information provided by the unified object wrapper: UPDATE oil_gas_exploration_data SET geometry = ST_GeomFromWKB('...'), other_attributes = 'production:1200 barrels / day' WHERE name = 'Oil Field A'; This updates the spatial and attribute data of Oil Field A in the database to the latest values, ensuring the consistency and accuracy of the spatial data. It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions involved are not necessarily required by this application.
[0063] Example 3 Optionally, this application also provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the various processes of the above method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.
[0064] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.
[0065] Figure 7 This application provides a block diagram of an electronic device 800. For example, the electronic device 800 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.
[0066] Reference Figure 7 The electronic device 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.
[0067] Processing component 802 typically controls the overall operation of electronic device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
[0068] Memory 804 is configured to store various types of data to support the operation of device 800. Examples of this data include instructions for any application or method operating on electronic device 800, contact data, phonebook data, messages, images, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.
[0069] Power supply component 806 provides power to various components of electronic device 800. Power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 800.
[0070] Multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
[0071] Audio component 810 is configured to output and / or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when electronic device 800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.
[0072] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.
[0073] Sensor assembly 814 includes one or more sensors for providing state assessments of various aspects of electronic device 800. For example, sensor assembly 814 may detect the on / off state of device 800, the relative positioning of components such as the display and keypad of electronic device 800, changes in position of electronic device 800 or a component of electronic device 800, the presence or absence of user contact with electronic device 800, orientation or acceleration / deceleration of electronic device 800, and temperature changes of electronic device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.
[0074] Communication component 816 is configured to facilitate wired or wireless communication between electronic device 800 and other devices. Electronic device 800 can access wireless networks based on communication standards, such as WiFi, carrier networks (such as 2G, 3G, 4G, or 5G), or combinations thereof. In one exemplary embodiment, communication component 816 receives broadcast signals or broadcast operation information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 816 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
[0075] In an exemplary embodiment, the electronic device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.
[0076] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of an electronic device 800 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.
[0077] Example 4 Figure 8 A block diagram of another electronic device 1900 provided for this application. For example, electronic device 1900 may be provided as a server.
[0078] Reference Figure 8 The electronic device 1900 includes a processing component 1922, which further includes one or more processors, and memory resources represented by memory 1932 for storing instructions, such as application programs, that can be executed by the processing component 1922. The application programs stored in memory 1932 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 1922 is configured to execute instructions to perform the methods described above.
[0079] Electronic device 1900 may also include a power supply component 1926 configured to perform power management of electronic device 1900, a wired or wireless network interface 1950 configured to connect electronic device 1900 to a network, and an input / output (I / O) interface 1958. Electronic device 1900 can operate on an operating system stored in memory 1932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.
[0080] Example 5 Fifthly, this application discloses a computer program product in which, when the instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to perform the method described in any of the preceding aspects.
[0081] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0082] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0083] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.
[0084] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0085] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0086] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0087] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0088] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0089] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.
[0090] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A spatial database system for oil and gas exploration, characterized in that, The system includes: a data interface, a unified object wrapper, a data driver, a model object table structure, an extended database, and a feature synchronization process; wherein... The data interface is the interaction interface between the system and external applications or users. It receives various data requests from the oil and gas exploration business system and supports input and output of multiple spatial object types. The data requests include at least data query, data insertion, data update, and data deletion operations. The unified object wrapper encapsulates different types of spatial objects in a unified manner, identifies and parses the attribute information of each spatial object, converts the attribute information into a database-recognizable format, and restores the data in the database to the original spatial object type when outputting data. The data driver interacts with the underlying database to execute data operation instructions; wherein, the data operation instructions include functions corresponding to database communication, and process the storage and retrieval of spatial data based on the attribute information passed by the unified object wrapper; The model object table structure stores spatial data for oil and gas exploration, and the model object table structure includes at least a geometry type field for storing geometric information of spatial objects; The extended database uses PostgreSQL as the underlying database and integrates the Postgis extension, which is a spatial database extension applied to the PostgreSQL database. The feature synchronization process synchronizes the spatial data features from the original table to the feature table, and runs automatically according to preset rules and time intervals. It monitors changes in the spatial data in the original table in real time, updates the corresponding information in the feature table in a timely manner, and performs query and analysis operations based on the updated spatial data.
2. The oil and gas exploration spatial database system according to claim 1, characterized in that, Also includes: Auxiliary processes, which include at least a daemon process, a conversion process, a listening process, and a subscription process; wherein, The daemon process monitors the running status of the entire database system, and issues timely alarms and takes corresponding recovery measures when the system experiences abnormalities or failures. The conversion process converts spatial data in different formats into a unified format supported by the system for storage and processing. The monitoring process listens to external data sources or internal system events and messages in real time. When new spatial data or information is generated, it captures it in a timely manner and notifies the system to process it. The subscription process monitors data changes and event triggering in the database in real time based on the subscription settings of the user or external business system. When the subscription conditions are met, the system automatically pushes the corresponding information to the subscriber, realizing real-time data push and sharing.
3. The oil and gas exploration spatial database system according to claim 2, characterized in that, The system includes a data feature acquisition module and a data compression and decompression module; The data feature acquisition module and the data compression and decompression module trigger compression and decompression rules based on the real-time features returned by the monitoring interface and the preset threshold. The data compression and decompression module is an independent class that adapts to a unified object wrapper and a data driver through an interface. The compression and decompression functions are integrated into the data driver, and the unified object sets whether to compress, compress, or decompress, thus deploying data operations in the driver.
4. A spatial data management method, characterized in that, Applied to the oil and gas exploration spatial database system as described in any one of claims 1 to 3, the method comprises: External business systems send data requests containing spatial objects through data interfaces; The unified object wrapper parses and encapsulates the spatial objects in the data request, converts the spatial objects into a database-recognizable format, and passes them to the data driver. The data driver stores spatial and attribute data in a model object table structure of the PostgreSQL database, where the geometric information of the spatial objects is stored in a field of type geometry.
5. The spatial data management method according to claim 4, characterized in that, The method further includes: The feature synchronization process periodically or in real-time monitors changes in spatial data in the original table; When new spatial data features or updates to existing data are detected, the changes in spatial data are synchronized to the feature table so that the spatial data in the feature table always remains consistent with the spatial data in the original table.
6. The spatial data management method according to claim 5, characterized in that, The method further includes: Users initiate spatial data query requests through the data interface; The business interface passes the query request to the unified object wrapper; The unified object wrapper converts the query conditions corresponding to the query request into SQL statements that can be executed by the database.
7. The spatial data management method according to claim 6, characterized in that, The method further includes: The data driver executes the transformed SQL statement, retrieves the corresponding spatial and attribute data from the database, and returns the results to the unified object wrapper. The unified object wrapper parses and encapsulates the results, restoring them to the original spatial object type, and returns the query results to the user or external business system through the data interface.
8. The spatial data management method according to claim 6, characterized in that, The method further includes: The daemon process monitors the database system's operating status in real time. When it detects any abnormalities in the operating status, the daemon process takes corresponding measures to ensure the stable operation of the system. The operating status includes server resource usage, database connection status, and process running status. The monitoring process listens for external data sources or internal system events and messages in real time. When an event or message is received, the monitoring process promptly notifies the system to take corresponding actions so that the system can respond to external changes in a timely manner and maintain the real-time performance and accuracy of the data. The subscription process monitors data changes and event triggers in the database in real time based on the subscription settings of users or external business systems. When the subscription conditions are met, the subscription process automatically pushes the corresponding information to the subscribers, realizing real-time data sharing and interaction.
9. An electronic device, characterized in that, include: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the method as described in any one of claims 4 to 8.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 4 to 8.
11. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device implements the method as described in any one of claims 4 to 8.