Finding and preventing wrong GNSS base coordinates
A stable RTK solution can inherit a wrong base position. Build checks that expose the resulting common offset.
Recognize a common reference error
A single base RTK workflow determines the rover relative to a reference receiver and its assigned coordinate. If that coordinate is wrong, the rover results can be internally consistent while displaced from the intended project system. The crew may see repeated fixed solutions and small displayed estimates even though the deliverable has a common offset. This makes the base coordinate one of the most consequential values in the setup.
Begin an investigation by asking how the coordinate was obtained. It may come from established control, an approved processing result, a previous project record or an approximate autonomous position. Those sources are not interchangeable. An approximate coordinate can support some relative tasks, but it must not be silently presented as a verified connection to the project reference system when that connection has not been established.
Continue learning Base and rover setup: getting the relationship right
Trace the coordinate definition
Record the reference frame, epoch where relevant, coordinate type, units and height definition. A number without these labels is incomplete survey information. Latitude and longitude order, projected grid coordinates and geocentric coordinates require different interpretations. A familiar looking value is not sufficient evidence that the controller field expects that representation. Confirm the input convention in the equipment instructions before entering the coordinate.
Height deserves a separate check. Ellipsoidal height, an orthometric height and an antenna reference point height describe different things. A geoid model can be applied in one part of a workflow and omitted or applied again in another. Draw the vertical reference chain when the setup is unclear. This is more effective than adjusting the base height repeatedly until one nearby point seems to agree.
Continue learning A daily GNSS base setup workflow for survey crews
Check the physical point and antenna setup
Verify that the coordinate belongs to the mark actually occupied. Similar point names, replaced monuments and nearby witness marks can create a plausible but incorrect selection. Recover the mark using its description and photographs. If it appears disturbed, preserve that observation and consult the project procedure before treating the old coordinate as unquestionable control.
Measure the antenna height to the correct reference point using the supported method. The assigned mark coordinate and the antenna measurement are related but separate inputs. A correct mark coordinate combined with an incorrect height can create a vertical error that appears to be a bad base coordinate. Record the raw measurement and the selected antenna model so the office can reconstruct the reduction instead of seeing only a final corrected value.
Continue learning Choosing and documenting a temporary GNSS base mark
Prevent transcription mistakes
Use a controlled coordinate file where the equipment supports import, and inspect the imported result before starting the base. Include point identifier, coordinate system and source in the approval record. If manual entry is necessary, use an independent read back or comparison. Pay attention to signs, decimal placement, units and digit groups; a visually tidy screen can still contain a consequential entry error.
Avoid copying values from an unlabelled screenshot or an old controller job. Those records may use another transformation or height model. Keep the approved coordinate source in the project folder and label revisions clearly. If a corrected value is issued, identify which setup dates used the earlier coordinate. This makes it possible to assess affected work rather than leaving several competing base positions in circulation.
Continue learning Coordinate axis order in GNSS data: preventing plausible mistakes
Use independent checks early
After starting the reference station, occupy suitable known points before collecting production data. Compare horizontal and vertical components in the intended project system. More than one distributed check helps distinguish a common translation from a problem that changes across the site. A check used to define a local transformation should not be the only evidence used to validate that transformation.
If several checks show a similar displacement, review the reference coordinate and job settings before changing individual rover points. If only one check fails, investigate its identity and condition as well as the measurement. The pattern guides diagnosis but does not prove a cause by itself. Preserve the comparison table and the initial setup so the investigation can be reviewed after corrective action is taken.
Continue learning Base and rover setup: getting the relationship right
Correct the affected work transparently
When a base error is confirmed, stop and identify the affected interval. Preserve the original observations and configuration. Decide, under the project workflow, whether valid relative observations can be reprocessed or whether points require remeasurement. Do not apply an undocumented shift to a final export simply because it makes one point fit. A coordinate correction needs a defined basis and checks across the affected area.
Document the old coordinate, approved replacement, reason for the change and method used to update the results. Recheck independent points after processing. If multiple bases or local transformations were involved, assess each work zone separately. The same numerical correction may not be appropriate for every dataset. A transparent correction record protects the meaning of the coordinates and helps prevent the old result from being reused accidentally.
Continue learning A daily GNSS base setup workflow for survey crews
Build a base approval routine
Use a short setup approval that combines mark identity, coordinate source, antenna measurement and initial check results. Make the approved values visible to the operator without exposing unrelated account credentials. Reconfirm them after a receiver reset, base move or job import. Routine repetition is justified here because the consequence of one wrong reference value can extend across many otherwise careful observations.
In the final report, identify the reference coordinates actually used and any corrections made during the project. Keep source records and raw observations linked by date and setup identifier. The aim is not to claim that mistakes never occur. It is to make a wrong base coordinate easy to detect, contain and correct before an internally consistent but displaced dataset reaches the next stage of design or mapping.
Continue learning Choosing and documenting a temporary GNSS base mark
Containing a coordinate entry incident
Suppose a base coordinate is found to have been entered from an earlier provisional file. The first useful record is the setup identifier and the time range using that value. Preserve the provisional source, approved replacement and rover observations before making any edits. Compare distributed checks and determine which files share the same reference and transformation. That assessment establishes the scope of the incident more reliably than applying one guessed shift to every file in the project folder.
If reprocessing is appropriate, keep original and revised outputs clearly named and document the method. Verify the revised dataset against independent points and retire superseded deliverables so they are not reused accidentally. If the evidence is insufficient, remeasurement may be required. The important operational lesson is that a coordinate error should produce a traceable correction history. Replacing the base value in the current controller job does not by itself repair or explain measurements already collected under the earlier setup.
Continue learning Coordinate axis order in GNSS data: preventing plausible mistakes
Practical checklist
- Preserve the source and definition of the approved base coordinate.
- Verify mark identity and antenna height independently.
- Check distributed control before production and document any correction.
Plan your GNSS setup
Compare the EQ10 and EQ20 receiver specifications, then discuss the configuration and support your project needs.
Compare GNSS receivers
