Baseline Processing Settings
Use baseline processing settings to configure how baselines are processed into vectors.
To access the settings:
- Select Project Settings in the Quick Access Toolbar.
The Project Settings dialog displays.
- Click Baseline Processing in the left pane.
Note: The minimum time required for a static observation to be used in a session is 10 seconds.
Options |
|
Baseline processing styles | |
General: Baseline Processing |
|
Auto start processing |
Yes - Select this to have processing start as soon as the Baseline Processing menu item or toolbar icon is selected. No - Select this to prevent automatic processing when the command begins. |
Store continuous as trajectory |
Yes - Select this to combine individual vectors into a single object called a trajectory, preserving system memory and processing speed. No - Select this to store each vector separately. |
Start automatic ID numbering |
Type a starting point ID to use when automatically naming points in trajectories. This is needed when the associated file from the field software is not present with the raw GNSS data file. |
Antenna model |
Trimble Relative - Trimble Business Center will load the antenna phase center (APC) correction models for the base and rover antennas from the *.pct files associated with the antennas. If Trimble relative APC correction models are not available for both the base and rover antenna, processing will fail. NGS Relative – Trimble Business Center will load APC correction models for the base and rover antennas from the *.ngs files associated with each of the antennas. If NGS relative APC correction models are not available for both the base and rover antenna, processing will fail. NGS Absolute – Trimble Business Center will load APC correction models for the base and rover antennas from the NGS ANTEX file ngs_antennas.atx. If NGS absolute APC correction models are not available for both the base and rover antenna, processing will fail. IGS Absolute – Trimble Business Center will load APC correction models for the base and rover antennas from the IGS ANTEX file igs_antennas.atx and the Trimble file trimble_antennas.atx. If IGS absolute APC correction models are not available for both the base and rover antenna, processing will fail. Automatic – Trimble Business Center will automatically determine the APC correction model to use for both the base and rover antennas, using the following priority:
|
Ephemeris type |
Automatic - Select this to process data using precise ephemeris when available, and broadcast ephemeris for all other data. Broadcast - Select this to process all data using only broadcast ephemeris. Precise - Select this to process only data for which precise ephemeris is available. Warning: If the ephemeris type you select does not cover all of the data in your project, only the data it covers is processed. |
General: Event Markers |
|
Event interpolation type |
Specify which kind of curve (linear, quadratic, or cubic) will be fit through the nearest points in time in order to interpolate event positions. |
Event interpolation points |
Type the number of points to use in the curve fit. It must be at least 2 for linear, 3 for quadratic, or 4 for cubic. |
Missing data points allowed |
Type a value representing the maximum increase in the search window for event interpolation points to use. For example, if this setting is 2 and the Event interpolation points setting is 4, the largest search window is -3 to +3 epochs. If four valid points are not found in this window, no interpolated position will be computed. |
Create points from events |
Specify whether or not to create points from interpolated event positions. The point IDs are created when the trajectory is created. |
User defined numbering |
Do either of the following:
|
Processing |
|
Solution type |
Fixed - Select this to allow either fixed or float solutions, based on how the processor is able to resolve the integer ambiguity search. Float - Select this to allow float solutions only. |
Frequency
|
Single frequency - Select this to process only data transmitted on an L1 frequency. All frequencies - Select this to process data transmitted on L1, L2, and L5 frequencies (requires an appropriate product license). |
Processing interval |
Choose the interval (in seconds) at which you want to select field data to process baselines, or choose Automatic (the default) to specify that the software determine the best processing interval to use. If you choose an interval that is shorter than the interval at which the data was collected, the interval at which the data was collected is used. Tip: Choosing a longer interval causes baseline processing to complete more quickly. |
Trajectory solution type |
Select Fixed only to specify that the trajectory points will be limited to fixed solutions and float solutions will be discarded. Select Fixed and float to specify that the trajectory points can be either fixed or float solutions. |
Maximum baseline length when using VRS |
Specify the length of a Virtual Reference Station (VRS) baseline that, when exceeded, causes a warning flag to be displayed after baseline processing. All values are rounded to the nearest 1/10th kilometer or mile. For more information about importing and processing VRS data, see Check In Raw GNSS Data |
GIS Processing |
|
GIS processing type |
Select the processing mode for GIS data imported in TerraSync SSF files:
|
Quality |
|
Acceptance criteria |
Uncheck either box to keep horizontal or vertical precision from being used in passing or failing a baseline (acceptance criteria). If you keep the criteria enabled, type tolerance values in the Flag and Fail boxes in the format constant unit + parts per million unit to specify the required horizontal and vertical precision to use for flagging or failing a processed baseline. If a baseline fails, it will be deselected, and cannot be saved in the project. |
Use optional acceptance criteria |
Check this box to open the Optional Acceptance Criteria boxes, if needed. |
Optional acceptance criteria |
If RMS (L1 only) > - Uncheck this to keep Root Mean Square (RMS) from being used in acceptance criteria for L1 only data. If RMS (dual frequency) > - Uncheck this to keep RMS from being used in acceptance criteria for L1/L2 data. RMS is a measure of noise in the measurements; smaller values for RMS are considered better. Note: This option is available only if you are licensed for multi-frequency / GLONASS processing. |
Satellites |
|
Elevation mask |
Type a vertical angle (in degrees) below which satellite data should be ignored during processing. Adjust this mask as necessary based on any obstructions in the project area. |
GPS, GLONASS, Galileo, BeiDou, and QZSS |
Uncheck satellites numbers on these tabs to ignore their data during processing. If a satellite was unhealthy during the survey, uncheck the box. Trimble receivers automatically pass unhealthy status messages to this software. RINEX files, however, may not properly indicate unhealthy status. In this case, use these setting to ignore unhealthy satellites during processing. This is also useful if a satellite with a lower elevation is causing a noisy solution. Note: If an "unknown" satellite (that is, a satellite that is not included in this list ) is imported into a project from raw data files, TBC automatically sets the satellite's baseline processing status to "ignore" so it is not included in the processing (just as if you had unchecked it in this list had it appeared here). |
All None |
Click these to check or uncheck all of the satellite boxes. |