Results of RINEX Data Request
The “RINEX Data” tab of the “Post-Processing > Results” page on the SBC Portal contains a list of all the requests triggered by the user. RINEX files corresponding to requests not older than 5 days can be downloaded either altogether or one by one. For data older than 5 days, a new request with the same settings for the existing requests can be submitted via “Request Again” button.
Results of Virtual RINEX Request
For each completed Virtual RINEX request, the output is a zipped folder containing an observation file that is compliant with the user-defined input parameters (marker name and number, start time, duration, observation rate and approximate position) and a navigation file for each of the available constellations in the real (reference and network correction) data.
Virtual RINEX results are included on the “Results” page and are accessible via the “Virtual RINEX Data” tab. The results are stored in the database and are always available (subject to Virtual RINEX results retention) for download from the “Results” page.
Downloading the files will deliver them to the local Download directory.
The zipped folder name complies with the RINEX naming convention and contains the first four characters of the user-defined marker name, followed by the day of the year and the start time of the output data. If no marker name is entered by the user, “virt” will be used in the folder name.
Results of Coordinate Computation
The “Coordinate Computations” tab of the “Post-Processing > Results” page contains a list of all computations triggered by the user. Each entry in the list displays some basic information at a glance, and an expander on the right can be used to view more details about the computed coordinates and the quality of the solution. If the computation was successful, it is possible to visualise rover file details and open an HTML report with thorough results on all the computed baselines which lead to the averaged final position when an entry is in expanded mode.
For each selected rover file, multiple reference stations are usually found, all of which provide reference data for the computation. It is also possible to select multiple files for the same rover, each referring to a different time interval (multiple point occupation). Consequently, multiple baselines can be formed during the computation process, each contributing to the final point solution. The post-processed, accurate rover position is a weighted average of the positions provided by all the involved baselines. This is why Coordinate Computation reports are usually organised into three sections:
-
Point Result: The coordinates (and corresponding standard deviations) of one point are averaged over all the baselines involved in the computation, with that point acting as the rover. In the case of multiple point occupations, the results are also averaged over time intervals. Point coordinates are always expressed in WGS84 and organised into two tables: one for Geodetic coordinates and the other for Cartesian coordinates. Additional tables displaying either Local or Grid coordinates can be displayed according to the target coordinate system chosen by the user.
-
Point Occupation Results: Point coordinates refer to a specific time interval (occupation). This section of the report consists of two parts: the Averaged Point Summary (1) and the Baseline Summary (2). The former displays the averaged marker coordinates and standard deviations for one occupation, computed by taking all available baselines into account. The latter consists of a table summarising all baseline results (just rover coordinates, quality, and baseline vector components) relating to the corresponding occupation.
-
Baseline Results: It displays detailed information about each computed baseline without grouping. This includes the computed coordinates, quality parameters and processing settings in use.
As mentioned, the X-pos Coordinate Computation service can process different data types. For Static Rover data, the results report is organised as described above. If Stop&Go or Kinematic data is used, however, some adjustments are needed:
-
Stop&Go: Stop&Go files contain multiple markers. The computation report contains a “Point Results” section which displays the averaged positions in WGS84 and, if present, in the target coordinate system for each marker. The “Point Occupation” and “Baseline Results” sections then follow, as each marker in the Stop&Go file is a static occupation.
-
Kinematic: In the case of kinematic data, rovers cover a trajectory by occupying different positions at each epoch. The computation report displays a list of the positions occupied by the rover along its trajectory, known as the “Kinematic Point Results”: one position per epoch is displayed. If more than one reference station is used, each position represents the average of the positions obtained for each baseline at a specific epoch. The number of baselines contributing to each result is also displayed for each point in the trajectory. The kinematic processing report does not contain any point, point occupation or baseline results.
On the “Results” page, a link can be clicked in expanded mode to display the rover's trajectory (track) for kinematic computations. It is also possible to export the trajectory in CSV and GeoJSON formats.
The “Full Report”, which is available on the “Results” page, brings together all the results in a single file. When the computation results are in expanded mode, it is possible to visualise a report for each individual point or track that has been processed by clicking on the “Show Results” icon.
In SBC, processing Static/Stop&Go and Kinematic files is allowed by two different products: “X-pos Coordinate Computation STATIC” and “X-pos Coordinate Computation KINEMATIC”. Users of SBC who need to process all types of rover data must have both subscriptions active. The former covers computations for both Static and Stop&Go files.
Results of Coordinate Transformation
The “Results” page includes coordinate transformation results, which are accessible via the “Coordinate Transformations” tab.
The results are stored in the database and are always available (subject to Transformation results retention) for download from the “Results” page. An accordion is available here: when expanded, the results can be visualised in a table and exported to CSV format. The “Export” button is visible inside the open accordion at the top right of the table. If more than one file was uploaded for the transformation, it is possible to export all the results in one file (using the “Export” button) or to export the results relating to one file at a time (using the “Export” icon in the table next to each file).
The output file is a CSV file with fields separated by a semicolon. Basically, the output coordinates are structured in the same way as the supported input format. Stochastics for points that have them in the input file will be ignored in the transformation. According to the target coordinate system chosen by the user, the output file will contain Local Cartesian and Geodetic coordinates, as well as Local Grid ones if supported.
Coordinate Transformation of Existing Coordinate Computation Results
When coordinate computations are run using WGS84 as the target coordinate system, it is possible to transform the results of these computations to different target coordinate systems. In such cases, the “Transform points” button appears when the corresponding entry is expanded on the “Results” page in the “Coordinate Computations” tab.
Clicking on this button redirects you to the “Transformation” page, where the input points are already displayed on the map using the results of the selected coordinate computation. If available, the project name is also inherited from the Coordinate Computation. The workflow for submitting the coordinate transformation is as described previously.
Currently, transformation from WGS84 coordinates is only supported, so only coordinate computations run using WGS84 as the target coordinate system provide the “Transform points” button in the corresponding result. Also, transformation of the results of kinematic coordinate computations is not currently supported. Hence, only Static and Stop&Go coordinate computation results expressed in WGS84 are candidates for coordinate transformation.