A near real-time processing method for hourly data

Abstract

The present application provides a method for near-real-time processing of hourly data, relating to the field of electronic digital data processing technology. The method, executed by a processor, includes: determining a target time dataset to be used for a target time; determining observation data and orbit data based on the target time dataset; determining a parameter input file based on the target time dataset; performing data processing; and storing and distributing the data processing results. By integrating an external script scheduling function, the present application enables the system to automatically execute preset data processing tasks on a regular basis, achieving near-real-time automatic processing of hourly data and a business-oriented data processing flow. This solves the problem that existing technologies are unable to process cross-day data, resulting in an inability to meet the near-real-time processing requirements of hourly meteorological observation data.

Description

Technical Field

[0001] The present application relates to the technical field of electronic digital data processing, and in particular to a near real-time processing method for hourly data. Background Art

[0002] In Bernese GNSS software, the session concept is crucial for organizing and managing the entire data processing process. As software specialized in post-processing data, Bernese GNSS uses a single day's worth of data as its default processing unit. In the SESSIONS.SES file, the daily data start and end times are defined as 00:00:00-23:59:59. Correct time logic requires that the "hour variable" of the data start time be less than the "hour variable" of the data end time. The data processing program reads these two variables from the SESSIONS.SES file and begins the data processing process.

[0003] When processing hourly data, a "sliding time window" technique is often used to ensure accuracy, typically using a fixed time window of 8-12 hours. Taking a 12-hour fixed time window as an example, to process the current hour's data, the data from the 11 hours preceding the current hour is sequentially combined for processing. If the start and end times of this data combination fall within the same day (do not span multiple days), that is, the "hour variable" value at the start time of the data combination is less than the "hour variable" value at the end time of the data combination, the time logic is correct and complies with the time definition rules of SESSION.ESE. The data processing program then reads these two variables from the SESSIONS.SES file and continues processing. However, if the start and end times of this 12-hour data set span two days (for example, from 21:00:00 the previous day to 08:59:59 the current day), that is, the "hour variable" value at the start time of the data combination is greater than the "hour variable" value at the end time of the data combination (21 > 08), the time logic is incorrect and does not comply with the time definition rules of SESSION.ESE. In this case, the data processing program will error and terminate.

[0004] Based on the above, Bernese software cannot process multi-day data. If the time window of the hourly data processing program is set to 12 hours, then the data of the first 11 hours of each day cannot be processed in near real time, which cannot meet the near real-time processing requirements of hourly meteorological observation data. Summary of the Invention

[0005] The purpose of this application is to provide a near real-time processing method for hourly data, which solves the problem that the existing technology cannot process cross-day data, resulting in the inability to process hourly meteorological observation data in near real time.

[0006] The technical solution of this application:

[0007] The present application provides a near real-time processing method for hourly data, the method being executed by a processor and comprising:

[0008] determining a target time data set to be used for the target time execution;

[0009] Determining observation data and orbit data based on a target time data set;

[0010] Execution of a determined parameter input file based on a target time data set;

[0011] Perform data processing;

[0012] The data processing results are stored and distributed.

[0013] Furthermore, the observation data at least includes: hourly raw observation data collected by GNSS receivers of all GNSS water vapor monitoring stations in the target area.

[0014] Furthermore, the hourly raw observation data includes at least: epoch time, satellite number and observation value, wherein the epoch time is at least the time stamp of each observation epoch, the satellite number is at least the observed satellite number, and the observation value is at least the pseudorange, carrier phase, Doppler shift and signal strength.

[0015] Furthermore, the orbit data at least includes a GNSS orbit file published by an international GNSS service.

[0016] Furthermore, the GNSS orbit file at least includes: an SP3 format orbit file, an ERP file, and an ION file.

[0017] Furthermore, the process of determining the parameter input file based on the target time data set is as follows:

[0018] Execute time variable acquisition and determine the time variable data set;

[0019] Execute parameter input file copy and upload to the target directory;

[0020] Execute parameter input file assignment;

[0021] Call the assigned parameter input file to the original directory.

[0022] Furthermore, the execution parameter input file assignment at least executes radio button assignment and time variable assignment.

[0023] Furthermore, the parameter input file at least includes: an INP file.

[0024] Furthermore, the process of performing data processing is: performing data preprocessing, orbit and clock error processing, site coordinate estimation, parameter optimization and SINEX file generation.

[0025] Furthermore, the process of storing and distributing the data processing results is as follows:

[0026] Based on the TRP file, combined with the ground temperature and air pressure of each station, the atmospheric water vapor content is inverted to obtain the PWV file;

[0027] Based on the PWV file, storage and recall are performed.

[0028] According to the above technical features, the beneficial effects of the present application are as follows: the method provided by the present application breaks away from the limitations of the SESSION concept in the Berenese GNSS software, and does not use the human-computer interaction interface provided by the software. Instead, it uses an external program to automatically modify the 12 parameters in the Berenese GNSS software related to the start and end time of the data set, and then starts the RNX2SNX data processing process, realizing near-real-time automatic processing of hourly data and business-oriented data processing procedures. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 A flowchart of the method provided for this application;

[0030] Figure 2 Flowchart of the execution corresponding to the method provided in this application;

[0031] Figure 3 This is a schematic diagram of the human-computer interaction interface for the BIA2OSB.INP input file in this embodiment;

[0032] Figure 4 This is a schematic diagram of the human-computer interaction interface for inputting the CCRNXO.INP file in this embodiment;

[0033] Figure 5 This is a schematic diagram of the human-computer interaction interface for the POLUPD.INP input file in this embodiment;

[0034] Figure 6 Schematic diagram of the human-computer interaction interface for inputting the CCPREORB.INP file in this embodiment;

[0035] Figure 7 This is a schematic diagram of the human-computer interaction interface for inputting the ORBGEN.INP file in this embodiment;

[0036] Figure 8 This is a schematic diagram of the human-computer interaction interface for inputting the SATCLK2.INP file in this embodiment;

[0037] Figure 9This is a schematic diagram of the human-computer interaction interface for the RNXSMT.INP input file in this embodiment;

[0038] Figure 10 This is a schematic diagram of the human-computer interaction interface for the RXOBV3.INP input file in this embodiment;

[0039] Figure 11 This is a schematic diagram of the human-computer interaction interface of BIA2OSB.INP in this embodiment;

[0040] Figure 12 In this embodiment, BIA2OSB.INP corresponds to Figure 11 Code diagram of variable declaration in human-computer interaction interface;

[0041] Figure 13 In this embodiment, BIA2OSB.INP corresponds to Figure 11 Code diagram for variable assignment in the human-computer interaction interface. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0043] Example

[0044] The embodiment of this application provides a near real-time processing method for hourly data. Please refer to Figures 1-13 The method is performed by a processor. The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0045] Specifically, the method includes: determining a target time dataset to be used for the target time; determining observation data and orbit data based on the target time dataset; determining a parameter input file based on the target time dataset; performing data processing; and storing and distributing the data processing results. Based on this, the near-real-time hourly data processing method provided in this embodiment further enhances the system's real-time processing capabilities while maintaining its high-precision data processing performance. By integrating an external script scheduling function, the system can automatically execute preset data processing tasks on a regular basis, achieving near-real-time automatic processing of hourly data and a business-oriented data processing process. This enables scientific research institutions and industry users to more efficiently utilize the software to carry out GNSS data processing, providing a more flexible and reliable solution for future application scenarios.

[0046] In some possible implementations, the observation data includes at least hourly raw observation data collected by GNSS receivers at all GNSS water vapor monitoring stations within the target area. It is worth noting that the number of GNSS water vapor monitoring stations in the target area is greater than two, and the data format of the hourly raw observation data collected by GNSS receivers at all GNSS water vapor monitoring stations in the target area is RINEX 3.0 or higher, and the file content includes at least a file header, wherein the file header includes:

[0047] 1. The version number is in RINEX format;

[0048] 2. The file type is identified as observation data file (O file);

[0049] 3. Receiver information includes at least receiver type, serial number, and firmware version;

[0050] 4. Antenna information includes at least antenna type and antenna height;

[0051] 5. Observation type, lists the types of observations contained in the file (such as pseudorange, carrier phase, etc.);

[0052] 6. Time system: The time system to be used must be specified (e.g. GPS time, UTC, etc.);

[0053] 7. Notes provide additional explanatory information.

[0054] In some possible implementations, the hourly raw observation data includes at least: epoch time, satellite number, and observation value. The epoch time is at least the time stamp of each observation epoch, the satellite number is at least the number of the observed satellite, and the observation value is at least the pseudorange, carrier phase, Doppler shift, and signal strength.

[0055] In detail, the file content also includes observation data, that is, the original observation data at least includes observation data, and the observation data at least includes epoch time, satellite number, and observation value. The epoch time is the time stamp for each observation epoch, and the satellite number is the number of the observed satellite, such as G01 represents GPS satellite No. 1. The observation value includes pseudorange, carrier phase, Doppler frequency shift and signal strength, etc.

[0056] In some possible implementations, the orbital data includes at least GNSS orbit files published by international GNSS services. GNSS orbit files include at least SP3 format orbit files, ERP files, and ION files. SP3 format orbit files, also known as SP3 (Standard Product 3) format orbit files, contain at least satellite position and velocity information, typically provided at 15-minute intervals. ERP files, also known as ERP (Earth Rotation Parameters) files, contain at least Earth rotation parameters, such as polar motion and day length variation. ION files, also known as IONosphere files, contain at least ionospheric delay information.

[0057] In some possible implementations, the process of determining a parameter input file based on a target time dataset includes: acquiring time variables to determine a time variable dataset; copying the parameter input file and uploading it to a target directory; assigning values to the parameter input file; and retrieving the assigned parameter input file to the original directory. The parameter input file assignment involves at least assigning values to radio buttons and time variables.

[0058] It is worth noting that if Figure 2 As shown, this embodiment automatically writes the start and end time parameters of the dataset to be processed into the relevant parameter input files before running the RNX2SNX data processing program by starting the command line script at a fixed time. This embodiment involves the automatic modification of at least 8 parameter input files, which are located in the / BERN54 / GPSUSER / OPT / R2S_GEN / directory and include at least:

[0059] 1.BIA2OSB.INP input file;

[0060] 2. CCRNXO.INP input file;

[0061] 3. CCRNXO.INP input file;

[0062] 4.CCRNXO.INP input file;

[0063] 5.ORBGEN.INP input file;

[0064] 6.SATCLK2.INP input file;

[0065] 7.RNXSMT.INP input file;

[0066] 8.RXOBV3.INP input file.

[0067] In detail:

[0068] like Figure 3 As shown in the figure, the detailed process for inputting the BIA2OSB.INP file is as follows: When entering the start and end times of multi-day data through the human-computer interaction interface, in the "Time Window Settings" panel, select one of the three options: "Take all the records," "Defined by Year and Session identifier," and "Defined by Start and End times." Click the radio button to the left of "Defined by Start and End times" to activate the text box for entering the start and end times of the time window. You need to assign values to the three radio buttons in the "Time Window Settings" panel in the BIA2OSB.INP file:

[0069] "RADIO_0 = 0 (option off)

[0070] RADIO_1 = 0 (option off)

[0071] RADIO_2 = 1 (activate option)".

[0072] Next, use the start and end time (year, month, day, hour, minute, second) of the cross-day data as input data to replace the value of the specified field in the BIA2OSB.INP file, specifically:

[0073] Assign the value of the "STADAT" field in the BIA2OSB.INP file using a string consisting of the data start date (year, month, day);

[0074] Assign the value of the "STATIM" field in the BIA2OSB.INP file using the string concatenated with the data start time (hour, minute, second);

[0075] Assign the value of the "ENDDAT" field in the BIA2OSB.INP file with the string consisting of the data end date (year, month, day);

[0076] Assign the value of the "ENDTIM" field in the BIA2OSB.INP file using a string consisting of the data end time (year, month, day).

[0077] like Figure 4 As shown in the figure, the detailed process of inputting the CCRNXO.INP file is as follows: When entering the start and end times of cross-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select one of the two options: "Defined by Year and Session identifier" and "Defined by Start and End times". Click the radio button to the left of "Defined by Start and End times" to activate the text box for entering the start and end times of the time window. You need to assign values to the two radio buttons in the "Observation Window" panel in the CCRNXO.INP file:

[0078] "RADIO_1 = 0 (option off)

[0079] RADIO_2 = 1 (activate option)".

[0080] Next, use the start and end time (year, month, day, hour, minute, second) of the cross-day data as input data to replace the value of the specified field in the CCRNXO.INP file, specifically:

[0081] Assign the value of the "STADAT" field in the CCRNXO.INP file using the string concatenated with the data start date (year, month, day);

[0082] Assign the value of the "STATIM" field in the CCRNXO.INP file using the string of the data start time (hour, minute, second);

[0083] Assign the value of the "ENDDAT" field in the CCRNXO.INP file with the string of the data end date (year, month, day);

[0084] Assign the value of the "ENDTIM" field in the CCRNXO.INP file using a string consisting of the data end time (year, month, day).

[0085] like Figure 5 As shown in the figure, the detailed process of POLUPD.INP input file is as follows: through the human-computer interaction interface ( Figure 3) When entering the start and end times for multi-day data, in the "Time Window" panel, you need to select one of "Defined by Year and Session identifier" and "Defined by Start and End times." Click the radio button to the left of "Defined by Start and End times" to activate the text box for entering the start and end times of the time window. You need to assign values to the two radio buttons in the "Time Window" panel in the POLUPD.INP file:

[0086] "RADIO_1 = 0 (option off)

[0087] RADIO_2 = 1 (activate option)".

[0088] Next, use the start and end time (year, month, day, hour, minute, second) of the cross-day data as input data to replace the value of the specified field in the POLUPD.INP file, specifically:

[0089] Assign the value of the "STADAT" field in the POLUPD.INP file using the string concatenated with the data start date (year, month, day);

[0090] Assign the value of the "STATIM" field in the POLUPD.INP file using the string concatenated with the data start time (hour, minute, second);

[0091] Assign the value of the "ENDDAT" field in the POLUPD.INP file with the string of the data end date (year, month, day);

[0092] Assign the value of the "ENDTIM" field in the POLUPD.INP file using a string consisting of the data end time (year, month, day).

[0093] like Figure 6 As shown in the figure, the detailed process of inputting the CCPREORB.INP file is as follows: When entering the start and end times of cross-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select one of the two options: "Defined by Year and Session identifier" and "Defined by Start and End times". Click the radio button to the left of "Defined by Start and End times" to activate the text box for entering the start and end times of the time window. You need to assign values to the two radio buttons in the "Observation Window" panel in the CCPREORB.INP file:

[0094] "RADIO_1 = 0 (option off)

[0095] RADIO_2 = 1 (activate option)".

[0096] Next, use the start and end time (year, month, day, hour, minute, second) of the cross-day data as input data to replace the value of the specified field in the CCPREORB.INP file, specifically:

[0097] Assign the value of the "STADAT" field in the CCPREORB.INP file using a string consisting of the data start date (year, month, day);

[0098] Assign the value of the "STATIM" field in the CCPREORB.INP file using the string concatenated with the data start time (hour, minute, second);

[0099] Assign the value of the "ENDDAT" field in the CCPREORB.INP file using the string concatenated with the data end date (year, month, day);

[0100] Assign a value to the "ENDTIM" field in the CCPREORB.INP file using a string consisting of the data end time (year, month, day).

[0101] like Figure 7 As shown in the figure, the detailed process of inputting the ORBGEN.INP file is as follows: When entering the start and end times of cross-day data through the human-computer interaction interface, in the "Orbital Arc Definition" panel, you need to select one of the two options: "Defined by Year and Session identifier" and "Defined by Start and End times". Click the radio button to the left of "Defined by Start and End times" to activate the text box for entering the start and end times of the time window. You need to assign values to the two radio buttons in the "Orbital Arc Definition" panel in the ORBGEN.INP file:

[0102] "RADIO_1 = 0 (option off)

[0103] RADIO_2 = 1 (activate option)"

[0104] Next, use the start and end time (year, month, day, hour, minute, second) of the cross-day data as input data to replace the value of the specified field in the ORBGEN.INP file, specifically:

[0105] Assign the value of the "STADAT" field in the ORBGEN.INP file using the string concatenated with the data start date (year, month, day);

[0106] Assign the value of the "STATIM" field in the ORBGEN.INP file using the string of the data start time (hour, minute, second);

[0107] Assign the value of the "ENDDAT" field in the ORBGEN.INP file with the string of the data end date (year, month, day);

[0108] Assign the value of the "ENDTIM" field in the ORBGEN.INP file using a string consisting of the data end time (year, month, day).

[0109] like Figure 8 As shown in the figure, the detailed process of inputting the SATCLK2.INP file is as follows: When entering the start and end times of cross-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select one of the three options: "Take all clock records", "Defined by Year and Session identifier", and "Defined by Start and End times". Click the radio button to the left of "Defined by Start and End times" to activate the text box for entering the start and end times of the time window. You need to assign values to the three radio buttons in the "Observation Window" panel in the SATCLK2.INP file:

[0110] "RADIO_0 = 0 (option off)

[0111] RADIO_1 = 0 (option off)

[0112] RADIO_2 = 1 (activate option)".

[0113] Next, use the start and end time (year, month, day, hour, minute, second) of the cross-day data as input data to replace the value of the specified field in the SATCLK2.INP file:

[0114] Assign the value of the "STADAT" field in the SATCLK2.INP file using the string concatenated with the data start date (year, month, day);

[0115] Assign the value of the "STATIM" field in the SATCLK2.INP file using the string of data start time (hour, minute, second);

[0116] Assign the value of the "ENDDAT" field in the SATCLK2.INP file with the string of the data end date (year, month, day);

[0117] Assign the value of the "ENDTIM" field in the SATCLK2.INP file using a string consisting of the data end time (year, month, day).

[0118] like Figure 9 As shown in the figure, the detailed process of inputting the RNXSMT.INP file is as follows: When entering the start and end times of cross-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select one of the two options: "Defined by Year and Session identifier" and "Defined by Start and End times". Click the radio button to the left of "Defined by Start and End times" to activate the text box for entering the start and end times of the time window. You need to assign values to the two radio buttons in the "Observation Window" panel in the RNXSMT.INP file:

[0119] "RADIO_1 = 0 (option off)

[0120] RADIO_2 = 1 (activate option)".

[0121] Next, use the start and end time (year, month, day, hour, minute, second) of the cross-day data as input data to replace the value of the specified field in the RNXSMT.INP file, specifically:

[0122] Assign the value of the "STADAT" field in the RNXSMT.INP file using the string concatenated with the data start date (year, month, day);

[0123] Assign the value of the "STATIM" field in the RNXSMT.INP file using the string of the data start time (hour, minute, second);

[0124] Assign the value of the "ENDDAT" field in the RNXSMT.INP file with the string of the data end date (year, month, day);

[0125] Assign the value of the "ENDTIM" field in the RNXSMT.INP file with the string of the data end time (year, month, day);

[0126] Assign the value of the "ENDTIM" field in the SATCLK2.INP file using a string consisting of the data end time (year, month, day).

[0127] like Figure 10 As shown, the detailed process for inputting the RXOBV3.INP file is as follows: When entering the start and end times for multi-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select one of "Defined by Year and Session identifier" and "Defined by Start and End times." Click the radio button to the left of "Defined by Start and End times" to activate the text box for entering the start and end times of the time window. You need to assign values to the two radio buttons in the "Observation Window" panel in the RXOBV3.INP file:

[0128] "RADIO_1 = 0 (option off)

[0129] RADIO_2 = 1 (activate option)".

[0130] Next, use the start and end time (year, month, day, hour, minute, second) of the cross-day data as input data to replace the value of the specified field in the RXOBV3.INP file, specifically:

[0131] Assign the value of the "STADAT" field in the RXOBV3.INP file using the string concatenated with the data start date (year, month, day);

[0132] Assign the value of the "STATIM" field in the RXOBV3.INP file using the string concatenated with the data start time (hour, minute, second);

[0133] Assign the value of the "ENDDAT" field in the RXOBV3.INP file with the string consisting of the data end date (year, month, day);

[0134] Assign the value of the "ENDTIM" field in the RXOBV3.INP file using a string consisting of the data end time (year, month, day).

[0135] In some possible implementations, the parameter input file includes at least: an INP file.

[0136] The parameter input file refers to the INP file (Input File) in the Bernese GNSS software. In the Bernese GNSS software, the INP file (Input File) is a key file type used to define various parameters and configurations in the GNSS data processing process. It is an important medium for users to interact with the software. It exists in the form of a text file that users can edit directly or generate through the software. In the Bernese software, after loading the INP file through the command line or interface, the software will perform the corresponding processing tasks based on the file content. The Bernese GNSS software provides a graphical interface to modify the INP file through human-computer interaction. This application uses the "replace specified field" method to directly assign values to variables in the relevant INP, such as Figure 11 As shown, taking BIA2OSB.INP as an example, the definition of the "Time Window Settings" dialog box in BIA2OSB.INP corresponds to the following code: Figure 12 As shown in the code, there are 9 variables in this dialog box, namely:

[0137] "3 radio button variables: RADIO_0, RADIO_1, RADIO_2

[0138] 2 SESSION variables: SESSION_YEAR, SESSION_STRG

[0139] There are 4 start and end time variables: STADAT, STATIM, ENDDAT, ENDTIM".

[0140] The codes corresponding to the actual assignment of the above variables are as follows Figure 13 As shown in the figure, for radio buttons, "1" indicates active, and "0" indicates disabled. For SESSION variables and start and end time variables, the content within the double quotes to the right of the variable name is the variable value. Given known start and end times for the observation data, the year, month, day, hour, minute, and second of the start and end times are combined into strings in the "YYYY MM DD" and "HH:MM:SS" formats, respectively. Calling the rplcln program replaces the specified field in the specified INP file with the specified string, thus assigning the value to the specified variable.

[0141] In some possible implementations, the process of performing data processing includes: performing data preprocessing, orbit and clock processing, station coordinate estimation, parameter optimization, and SINEX file generation.

[0142] Specifically, data processing is performed by launching the RNXSNX.BPE data processing flow in the Bernese GNSS software (the launch command is: perl rnx2snx_pcs.pl). RNXSNX.BPE is the key batch file used in the Bernese GNSS software to convert RINEX observation data into the SINEX format. This process includes data preprocessing, orbit and clock error processing, station coordinate estimation, parameter optimization, and SINEX file generation. Through this process, users can obtain high-precision station coordinates, Earth reference frame data, and atmospheric tropospheric parameters at the station zenith, suitable for applications such as crustal deformation monitoring, reference frame maintenance, and atmospheric water vapor monitoring.

[0143] In some possible implementations, the process of storing and distributing the data processing results is as follows:

[0144] Based on the TRP file, combined with the ground temperature and air pressure of each station, the atmospheric water vapor content is inverted to obtain the PWV file;

[0145] Based on the PWV file, storage and recall are performed.

[0146] Specifically, the TRP file, or TRP file (Tropospheric Parameters File), is the main result file obtained from data processing and is used to store parameter estimation results related to tropospheric delay. Tropospheric delay is one of the important error sources in the GNSS signal propagation process, and its accurate modeling and estimation are crucial for high-precision positioning. The TRP file contains the tropospheric delay information of the station location and is used for meteorological research and GNSS data processing. After obtaining the TRP result file, it is combined with the ground temperature and air pressure of each station, and then the atmospheric water vapor content (PWV, Precipitable Water Vapor) is inverted to obtain the PWV file, which is used for weather forecasting and climate research. After obtaining the above result file, the system automatically stores it in the specified location on the server and sends it to the designated user via the network.

[0147] Understandably, since the Bernese GNSS software provides a method for manually defining data start and end times through a human-computer interface, users can manually modify the 12 parameters (year, month, day, hour, minute, and second) for a dataset's start and end times, and then initiate hourly data processing as needed. However, automated systems rely on autonomy, and manually modifying parameters disrupts this autonomy. This conflicting approach, both in concept and in practice, means that manually defining data start and end times through the human-computer interface still cannot meet the requirements for near-real-time processing of operational observation data.

[0148] The method provided in this embodiment can also be implemented through a fully automatic time window parameter update strategy, completely abandoning the human-computer interaction interface, and specifically through script execution, automatically updating the time window related variable values in the specific parameter input file in real time, thereby realizing real-time setting of the time window parameters.

[0149] Thus far, various embodiments of the present disclosure have been described in detail. To avoid obscuring the concept of the present disclosure, some details known in the art have not been described. Based on the above description, those skilled in the art can fully understand how to implement the technical solutions disclosed herein.

[0150] Although some specific embodiments of the present disclosure have been described in detail through examples, those skilled in the art will understand that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. Those skilled in the art will understand that the above embodiments may be modified or some technical features may be replaced with equivalents without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.

Claims

1. A near real-time processing method for hourly data, the method being executed by a processor, characterized in that: include: determining a target time data set to be used for the target time execution; Determining observation data and orbit data based on a target time data set; The parameter input file is determined based on the target time data set. The process is as follows: Execute time variable acquisition and determine the time variable data set; execute parameter input file copy and upload it to the target directory; execute parameter input file assignment, at least execute radio button assignment and time variable assignment; Call the assigned parameter input file to the original directory; The parameter input file includes at least: an INP file; bypassing the Bernese human-computer interaction interface, using an external script to directly modify 12 time parameters, specifically: by timing the command line script to automatically write the start and end time parameters of the data set to be processed into the relevant parameter input file before running the RNX2SNX data processing program; involving the automatic modification of at least 8 parameter input files, which are located in the / BERN54 / GPSUSER / OPT / R2S_GEN / directory and include at least: BIA2OSB.INP input file, CCRNXO.INP input file, POLUPD.INP input file, CCPREORB.INP input file, ORBGEN.INP input file, SATCLK2.INP input file, RNXSMT.INP input file, and RXOBV3.INP input file; The parameter input file assignment includes assigning values to the radio buttons and time variables related to the time window settings in the above 8 input files, using the start and end times of the cross-day data as input data to replace the values of the specified fields in the INP file; Perform data processing; The data processing results are stored and distributed.

2. The method according to claim 1, characterized in that The observation data at least includes: hourly raw observation data collected by GNSS receivers of all GNSS water vapor monitoring stations in the target area.

3. The method according to claim 2, characterized in that The hourly raw observation data includes at least: epoch time, satellite number and observation value, wherein the epoch time is at least the time stamp of each observation epoch, the satellite number is at least the observed satellite number, and the observation value is at least the pseudorange, carrier phase, Doppler frequency shift and signal strength.

4. The method according to claim 3, characterized in that The orbit data at least includes a GNSS orbit file published by an international GNSS service.

5. The method according to claim 4, characterized in that The GNSS orbit file includes at least: an SP3 format orbit file, an ERP file, and an ION file.

6. The method according to claim 1, characterized in that The data processing process includes: data preprocessing, orbit and clock error processing, station coordinate estimation, parameter optimization and SINEX file generation.

7. The method according to claim 6, characterized in that The process of storing and distributing the data processing results is as follows: Based on the TRP file, combined with the ground temperature and air pressure of each station, the atmospheric water vapor content is inverted to obtain the PWV file; Based on the PWV file, storage and recall are performed.

Images