Intense-hour data near-real-time processing method

Abstract

The invention provides a near-real-time processing method for hourly data, and relates to the technical field of electric digital data process.The method is executed by a processor and comprises the steps that a standby target time data set is determined for target time; determining observation data and orbit data based on the target time data set; determining a parameter input file based on the target time data set; executing data processing; and storing and distributing the data processing result. By integrating the external script scheduling function, the system can automatically execute the preset data processing task in a timed mode, near-real-time automatic processing and business data processing flow of hourly data are achieved, and the problem that the near-real-time processing requirement of meteorological hourly observation data cannot be met due to the fact that cross-day data cannot be processed in the prior art is solved.

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, SESSION is an important concept, which is mainly used to organize and manage the entire process of data processing. As a software that is good at post-data processing, Bernese GNSS software uses one day's data as a basic processing unit by default. In the SESSIONS.SES file, the start and end time of the daily data is defined as 00:00:00-23:59:59. The correct time logic is that the "hour variable" of the data start time is less than the "hour variable" of the data end time. The data processing program will read these two variables from the SESSIONS.SES file and start the data processing process.

[0003] When processing hourly data, in order to ensure the accuracy of data processing, the "sliding time window" technology is usually applied, and a fixed time window of 8-12 hours is generally used. Taking the 12-hour fixed time window as an example, in order to process the data of the current hour, the data of the 11 hours before the current hour will be sequentially combined for processing. If the start and end times of this data combination are both within the same day (not across days), that is, the "hour variable" value of the data combination start time is less than the "hour variable" value of the data combination end time, then the time logic is correct and meets the time definition rules of SESSION.ESE. At this time, the data processing program will read these two variables from the SESSIONS.SES file and continue the subsequent processing; if the start and end times of this 12-hour data set span two days (for example: 21:00:00 of the previous day to 08:59:59 of the current day), that is, the "hour variable" value of the data start time is greater than the "hour variable" value of the data end time (21>08), the time logic is wrong and does not meet the time definition rules of SESSION.ESE. In this case, the data processing program will fail and terminate.

[0004] Based on the above, the Bernese software cannot process cross-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 meteorological hourly observation data in near real time.

[0006] The technical solution of this application: The present application provides a near real-time processing method for hourly data, which is executed by a processor and includes: Determining a target time data set to be used for target time execution; Determining observation data and orbit data based on a target time data set; Execution of a determination parameter input file based on a target time data set; Perform data processing; The data processing results are stored and distributed.

[0007] 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.

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

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

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

[0011] Furthermore, the process of determining the parameter input file based on the target time data set is as follows: Execute time variable acquisition and determine the time variable data set; Execute parameter input file copy and upload to the target directory; Execute parameter input file assignment; Call the assigned parameter input file to the original directory.

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

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

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

[0015] Furthermore, 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 inversion is performed to obtain the PWV file; Based on the PWV file, storage and recall are performed.

[0016] 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 involving the start and end times of the data set, and then starts the RNX2SNX data processing process to achieve near real-time automatic processing of hourly data and business data processing procedures. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A schematic diagram of the process for providing the present application; Figure 2 An execution flow chart corresponding to the method provided in this application; Figure 3 This is a schematic diagram of the human-computer interaction interface for the BIA2OSB.INP input file in this embodiment; Figure 4 This is a schematic diagram of the human-computer interaction interface for inputting the CCRNXO.INP file in this embodiment; Figure 5 This is a schematic diagram of the human-computer interaction interface for the POLUPD.INP input file in this embodiment; Figure 6 This is a schematic diagram of the human-computer interaction interface for CCPREORB.INP input file in this embodiment; Figure 7 This is a schematic diagram of the human-computer interaction interface for the ORBGEN.INP input file in this embodiment; Figure 8 This is a schematic diagram of the human-computer interaction interface of the SATCLK2.INP input file in this embodiment; Fig. 9 This is a schematic diagram of the human-computer interaction interface of the RNXSMT.INP input file in this embodiment; Fig.10 This is a schematic diagram of the human-computer interaction interface of the RXOBV3.INP input file in this embodiment; Fig.11 This is a schematic diagram of the human-computer interaction interface of BIA2OSB.INP in this embodiment; Fig.12 In this embodiment, BIA2OSB.INP corresponds to Fig.11 Code diagram of variable declaration in human-computer interaction interface; Fig.13In this embodiment, BIA2OSB.INP corresponds to Fig.11 Code diagram for assigning values ​​to variables in the human-computer interaction interface. DETAILED DESCRIPTION

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

[0019] Example The embodiments of this application provide a near real-time processing method for hourly data. Please refer to Figure 1-Figure 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 the processor may be any conventional processor, etc.

[0020] In detail, the method includes: determining the target time data set to be used for the target time; determining the observation data and orbit data based on the target time data set; determining the parameter input file based on the target time data set; performing data processing; storing and distributing the data processing results. Based on this, the near-real-time processing method for hourly data provided in this embodiment further improves the real-time processing capability of the system while maintaining its high-precision data processing performance. By integrating the external script scheduling function, the system can automatically execute preset data processing tasks at a fixed time, realize near-real-time automatic processing of hourly data and business data processing procedures, thereby enabling scientific research institutions and industry users to use the software more efficiently to carry out GNSS data processing work, and provide more flexible and reliable solutions for future application scenarios.

[0021] In some possible implementations, 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. It is worth noting that the number of GNSS water vapor monitoring stations in the target area is greater than 2, and the data format of the hourly raw observation data collected by GNSS receivers of all GNSS water vapor monitoring stations in the target area is RINEX 3.0 or above, and the file content includes at least a file header, wherein the file header includes: 1. The version number is in RINEX format; 2. The file type is identified as observation data file (O file); 3. Receiver information includes at least receiver type, serial number and firmware version; 4. Antenna information includes at least antenna type and antenna height; 5. Observation type, lists the types of observations contained in the file (such as pseudorange, carrier phase, etc.); 6. Time system: The time system to be used must be specified (e.g. GPS time, UTC, etc.); 7. Additional explanatory information is provided in the notes.

[0022] In some possible implementations, 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.

[0023] 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, wherein 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, and the observation value includes pseudorange, carrier phase, Doppler frequency shift and signal strength, etc.

[0024] In some possible implementations, the orbital data includes at least a GNSS orbital file published by an international GNSS service. The GNSS orbital file includes at least: an SP3 format orbital file, an ERP file, and an ION file. The SP3 format orbital file, i.e., the SP3 (Standard Product 3) format orbital file, contains at least the satellite's position and velocity information, which is usually provided at intervals of 15 minutes; the ERP file, i.e., the ERP (Earth Rotation Parameters) file, contains at least the Earth's rotation parameters, such as polar motion, day length changes, etc.; the ION file, i.e., the ION (Ionosphere) file, contains at least ionospheric delay information.

[0025] In some possible implementations, the process of determining the parameter input file based on the target time data set is: executing time variable acquisition to determine the time variable data set; executing parameter input file copying and uploading to the target directory; executing parameter input file assignment; calling the parameter input file after assignment to the original directory. Among them, executing parameter input file assignment at least executes radio button assignment and time variable assignment.

[0026] It is worth noting that if Figure 2 As shown, this embodiment automatically writes the start and end time parameters of the data set 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: 1.BIA2OSB.INP input file; 2.CCRNXO.INP input file; 3.CCRNXO.INP input file; 4.CCRNXO.INP input file; 5.ORBGEN.INP input file; 6.SATCLK2.INP input file; 7.RNXSMT.INP input file; 8.RXOBV3.INP input file.

[0027] In detail: like Figure 3 As shown in the figure, the detailed process of BIA2OSB.INP input file is as follows: when entering the start and end time of cross-day data through the human-computer interaction interface, in the "Time Window Settings" panel, select 1 from "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 time 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: "RADIO_0 = 0 (option off) RADIO_1 = 0 (option off) RADIO_2 = 1 (activate option)".

[0028] 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: Assign the value of the "STADAT" field in the BIA2OSB.INP file using the string concatenated with the data start date (year, month, day); Assign the value of the "STATIM" field in the BIA2OSB.INP file using the string concatenated with the data start time (hour, minute, second); Assign the value of the "ENDDAT" field in the BIA2OSB.INP file with a string consisting of the data end date (year, month, day); Assign the value of the "ENDTIM" field in the BIA2OSB.INP file using a string consisting of the data end time (year, month, day).

[0029] like Figure 4 As shown in the figure, the detailed process of CCRNXO.INP input file is as follows: when entering the start and end time of cross-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select 1 from "Defined by Year and Sessionidentifier" and "Defined by Start and End times", click the radio button to the left of "Defined by Start andEnd times" to activate the text box for entering the start and end time of the time window. You need to assign values ​​to the two radio buttons in the "Observation Window" panel in the CCRNXO.INP file: "RADIO_1 = 0 (option off) RADIO_2 = 1 (activate option)".

[0030] 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: Assign the value of the "STADAT" field in the CCRNXO.INP file using the string concatenated with the data start date (year, month, day); Assign the value of the "STATIM" field in the CCRNXO.INP file using the string concatenated with the data start time (hour, minute, second); Assign the value of the "ENDDAT" field in the CCRNXO.INP file with the string concatenated with the data end date (year, month, day); Assign a value to the "ENDTIM" field in the CCRNXO.INP file using a string consisting of the data end time (year, month, day).

[0031] 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 time of cross-day data, in the "Time Window" panel, you need to choose 1 between "Defined by Year and Sessionidentifier" and "Defined by Start and End times". Click the radio button to the left of "Defined by Start andEnd times" to activate the text box for entering the start and end time of the time window. You need to assign values ​​to the two radio buttons in the "Time Window" panel in the POLUPD.INP file: "RADIO_1 = 0 (option off) RADIO_2 = 1 (activate option)".

[0032] 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: Assign the value of the "STADAT" field in the POLUPD.INP file using the string concatenated with the data start date (year, month, day); Assign the value of the "STATIM" field in the POLUPD.INP file using the string concatenated with the data start time (hour, minute, second); Assign the value of the "ENDDAT" field in the POLUPD.INP file with the string concatenated with the data end date (year, month, day); Assign a value to the "ENDTIM" field in the POLUPD.INP file using a string consisting of the data end time (year, month, day).

[0033] like Figure 6As shown in the figure, the detailed process of CCPREORB.INP input file is as follows: When inputting the start and end time of cross-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select 1 between "Defined by Year and Sessionidentifier" and "Defined by Start and End times", click the radio button to the left of "Defined by Start andEnd times" to activate the text box for inputting the start and end time of the time window. You need to assign values ​​to the two radio buttons in the "Observation Window" panel in the CCPREORB.INP file: "RADIO_1 = 0 (option off) RADIO_2 = 1 (activate option)".

[0034] 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: Assign the value of the "STADAT" field in the CCPREORB.INP file using the string concatenated with the data start date (year, month, day); Assign the value of the "STATIM" field in the CCPREORB.INP file using the string concatenated with the data start time (hour, minute, second); Assign the value of the "ENDDAT" field in the CCPREORB.INP file with the string concatenated with the data end date (year, month, day); Assign a value to the "ENDTIM" field in the CCPREORB.INP file using a string consisting of the data end time (year, month, day).

[0035] like Figure 7 As shown in the figure, the detailed process of inputting the ORBGEN.INP file is as follows: when inputting the start and end time of the cross-day data through the human-computer interaction interface, in the "Orbital Arc Definition" panel, you need to select 1 from "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 inputting the start and end time 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: "RADIO_1 = 0 (option off) RADIO_2 = 1 (activate option)" 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: Assign the value of the "STADAT" field in the ORBGEN.INP file using the string concatenated with the data start date (year, month, day); Assign the value of the "STATIM" field in the ORBGEN.INP file using the string concatenated with the data start time (hour, minute, second); Assign the value of the "ENDDAT" field in the ORBGEN.INP file with the string concatenated with the data end date (year, month, day); Assign a value to the "ENDTIM" field in the ORBGEN.INP file using a string consisting of the data end time (year, month, day).

[0036] like Figure 8 As shown in the figure, the detailed process of SATCLK2.INP input file is as follows: when inputting the start and end time of cross-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select 1 from "Take all clock records", "Defined by Year and Session identifier" and "Defined by Start and End times", and click the radio button to the left of "Defined by Start and End times" to activate the text box for inputting the start and end time of the time window. You need to assign values ​​to the three radio buttons in the "Observation Window" panel in the SATCLK2.INP file: "RADIO_0 = 0 (option off) RADIO_1 = 0 (option off) RADIO_2 = 1 (activate option)".

[0037] 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: Assign the value of the "STADAT" field in the SATCLK2.INP file using the string concatenated with the data start date (year, month, day); Assign the value of the "STATIM" field in the SATCLK2.INP file using the string of data start time (hour, minute, second); Assign the value of the "ENDDAT" field in the SATCLK2.INP file with the string concatenated with the data end date (year, month, day); Assign the value of the "ENDTIM" field in the SATCLK2.INP file using a string concatenated with the data end time (year, month, day).

[0038] like Fig. 9 As shown in the figure, the detailed process of RNXSMT.INP input file is as follows: when entering the start and end time of cross-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select 1 from "Defined by Year and Session identifier" and "Defined by Start and End times", click the radio button to the left of "Defined by Start andEnd times" to activate the text box for entering the start and end time of the time window. You need to assign values ​​to the two radio buttons in the "Observation Window" panel in the RNXSMT.INP file: "RADIO_1 = 0 (option off) RADIO_2 = 1 (activate option)".

[0039] 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: Assign the value of the "STADAT" field in the RNXSMT.INP file using the string concatenated with the data start date (year, month, day); Assign the value of the "STATIM" field in the RNXSMT.INP file using the string concatenated with the data start time (hour, minute, second); Assign the value of the "ENDDAT" field in the RNXSMT.INP file with the string concatenated with the data end date (year, month, day); Assign the value of the "ENDTIM" field in the RNXSMT.INP file with the string concatenated with the data end time (year, month, day); Assign the value of the "ENDTIM" field in the SATCLK2.INP file using a string concatenated with the data end time (year, month, day).

[0040] like Fig.10As shown in the figure, the detailed process of RXOBV3.INP input file is as follows: when entering the start and end time of the cross-day data through the human-computer interaction interface, in the "Observation Window" panel, you need to select 1 from "Defined by Year and Sessionidentifier" and "Defined by Start and End times", click the radio button to the left of "Defined by Start andEnd times" to activate the text box for entering the start and end time of the time window. You need to assign values ​​to the two radio buttons in the "Observation Window" panel in the RXOBV3.INP file: "RADIO_1 = 0 (option off) RADIO_2 = 1 (activate option)".

[0041] 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: Assign the value of the "STADAT" field in the RXOBV3.INP file using the string concatenated with the data start date (year, month, day); Assign the value of the "STATIM" field in the RXOBV3.INP file using the string concatenated with the data start time (hour, minute, second); Assign the value of the "ENDDAT" field in the RXOBV3.INP file with the string concatenated with the data end date (year, month, day); Assign a value to the "ENDTIM" field in the RXOBV3.INP file using a string consisting of the data end time (year, month, day).

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

[0043] 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 fields" method to directly assign values ​​to variables in the relevant INP, such as Fig.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 Fig.12 As shown in the code, there are 9 variables in this dialog box, namely: "3 radio button variables: RADIO_0, RADIO_1, RADIO_2 2 SESSION variables: SESSION_YEAR, SESSION_STRG There are 4 start and end time variables: STADAT, STATIM, ENDDAT, ENDTIM".

[0044] The codes corresponding to the actual assignment of the above variables are as follows Fig.13 As shown in the figure, it can be seen that for radio buttons, "1" means activation and "0" means disablement. For SESSION variables and start and end time variables, the content in the double quotes on the far right of the variable name is the value of the variable. The start and end time of the observation data are known. The year, month, day and hour, minute and second of the start and end time are combined into strings in the format of "YYYY MM DD" and "HH:MM:SS" respectively. Calling the rplcln program can replace the specified field in the specified INP file with the specified string to complete the assignment of the specified variable.

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

[0046] In detail, executing data processing is to start the RNXSNX.BPE data processing flow of the Bernese GNSS software (the startup 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 SINEX format. Its processing 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, which are suitable for applications such as crustal deformation monitoring, reference frame maintenance, and atmospheric water vapor monitoring.

[0047] In some possible implementations, 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 inversion is performed to obtain the PWV file; Based on the PWV file, storage and recall are performed.

[0048] In detail, the TRP file, namely the TRP file (Tropospheric Parameters File), is the main result file obtained from data processing, which is used to store parameter estimation results related to tropospheric delay. Tropospheric delay is one of the important error sources in the propagation process of GNSS signals, and accurate modeling and estimation of it is crucial for high-precision positioning. The TRP file contains the tropospheric delay information of the site location, which 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 site, and then the atmospheric water vapor content (PWV, Precipitable Water Vapor) is inverted to obtain the PWV file for weather forecasting and climate research. After obtaining the above result file, the system will automatically store it in the specified location of the server and send it to the specified user through the network.

[0049] It is understandable that: since the Bernese GNSS software provides a method for manually defining the start and end time of data through the human-computer interaction interface, users can manually modify the 12 parameters of the start and end year, month, day, hour, minute, and second of the data set according to the start and end time of the data set, and start the hourly data processing process at any time according to their needs. However, the automatically running system relies on autonomy, and manual modification of parameters will break this autonomy. There is a conflict between the two in terms of concept and operation. The method of manually defining the start and end time of data through the human-computer interaction interface still cannot meet the near real-time processing of business observation data.

[0050] 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 and in real time updating the time window related variable values ​​in a specific parameter input file, thereby realizing real-time setting of the time window parameters.

[0051] So far, various embodiments of the present disclosure have been described in detail. In order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed here.

[0052] Although some specific embodiments of the present disclosure have been described in detail by way of examples, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It should be understood by those skilled in the art that the above embodiments may be modified or some technical features may be replaced by 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 target time execution; Determining observation data and orbit data based on a target time data set; Execution of a determination parameter input file based on a target time data set; 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 include: 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 at least includes: epoch time, satellite number and observation value, wherein the epoch time is at least the time mark 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 at least includes: an SP3 format orbit file, an ERP file and an ION file.

6. The method according to claim 5, characterized in that The process of determining the parameter input file based on the target time data set is as follows: Execute time variable acquisition and determine the time variable data set; Execute parameter input file copy and upload to the target directory; Execute parameter input file assignment; Call the assigned parameter input file to the original directory.

7. The method according to claim 6, characterized in that The execution parameter input file assignment at least executes radio button assignment and time variable assignment.

8. The method according to claim 7, characterized in that The parameter input file at least includes: an INP file.

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

10. The method according to claim 9, 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 inversion is performed to obtain the PWV file; Based on the PWV file, storage and recall are performed.

Images