SURCON Technologist common mistakes
SURCON Technologist · Understand the traps and how to avoid them.
Treating a coordinate transformation as a one-step operation: converting between two projected systems (for example, between two Transverse Mercator zones or between a local grid and UTM) by applying a single scale factor and rotation instead of going through geographic coordinates and a datum transformation.
Candidates memorize a single 'shift plus rotation' formula from coursework and reuse it even when the source and target use different datums or projection parameters; they do not check whether the ellipsoid, central meridian, or false origin differ, so residuals are absorbed silently into the coordinates.
What to do instead
Always decompose the problem: inverse-project to latitude/longitude on the source ellipsoid, apply the datum transformation (with published parameters or a Helmert set), then forward-project onto the target grid. Verify with at least one independent check point and report the residual; if the residual exceeds the expected tolerance, the datum step is wrong, not the projection step.
Confusing grid convergence and magnetic declination, or omitting the convergence correction when reducing a bearing observed on the grid to a true azimuth (or the reverse).
Both are small angular corrections expressed in degrees and minutes and both are called 'declination' in casual speech; candidates apply whichever number appears on the map margin without checking its sign convention or epoch.
What to do instead
State the reduction chain explicitly on paper: grid bearing + grid convergence = true bearing; true bearing + magnetic declination (with sign and epoch) = magnetic bearing. Compute convergence from the projection formula or the map's stated value for the point's longitude offset from the central meridian, and always carry the sign convention with the number.
Closing a traverse by adjusting the angular misclosure and the linear misclosure in the wrong order, or distributing linear misclosure by simple proportion along the legs rather than by the compass/Bowditch or least-squares rule appropriate to the survey.
Textbook procedures are memorized as a sequence of keystrokes without understanding that angular misclosure must be removed before coordinates are computed, and that misclosure distribution depends on the relative precision of the observations.
What to do instead
Follow a fixed written sequence: compute angular misclosure, compare with the permissible value for the instrument and number of setups, distribute it (usually equally per angle), recompute bearings, compute coordinate misclosure, then distribute linear misclosure. Show the permissible angular and linear tolerances and compare against them before adjusting.
Reporting a cadastral boundary from coordinates alone without reconciling it against the record (title diagram, deed distances, and occupation on the ground), and ignoring a discrepancy because the computed coordinates 'close'.
Candidates treat the coordinate database as authoritative and forget that in cadastral work the registered record, the original survey measurements, and evidence of occupation may rank above a modern recomputation; a mathematically closed figure can still be the wrong boundary.
What to do instead
Adopt an explicit hierarchy of evidence for each boundary: registered plan and deed measurements first, then monument evidence and occupation, then recomputed coordinates. Where they conflict, quantify the discrepancy, state which source you followed and why, and flag it for the client or authority rather than overwriting the record with your coordinates.
Confusing the different cadastral plan types and their purposes, for example treating a compiled or diagrammatic plan as if it were a survey-accurate plan, or misdescribing the effect of registering a plan (whether it creates, extinguishes, or merely evidences title).
The terminology of plan classes and their legal effect is administrative rather than mathematical, so candidates skim it, then answer questions about what a plan does to boundaries using intuition from their own jurisdiction.
What to do instead
Build a one-page table of plan types with three columns: how the data were obtained (field survey, compilation, photogrammetry), the accuracy standard attached, and the legal effect on the parcel and its boundaries. Learn the difference between a plan that defines a new boundary and one that only records an existing one, and answer from that table.
Mishandling geoid–ellipsoid relationships: quoting an orthometric height as an ellipsoidal height, or applying a geoid separation with the wrong sign when converting between GNSS-derived heights and levelled heights.
The formula h = H + N is simple, but candidates forget which quantity their GNSS receiver outputs and which one a benchmark carries, and the sign of N is easily inverted when the local geoid model is below the ellipsoid.
What to do instead
Write the relation with a sketch every time: ellipsoidal height h equals orthometric height H plus geoid separation N, with N positive where the geoid lies above the ellipsoid. Identify each input's type before substituting, and sanity-check the result against the expected magnitude of N (tens of metres, not millimetres) and against a known benchmark.
Designing or assessing a GNSS survey without checking the geometry and redundancy needed to support the stated accuracy: using a single reference station over a long baseline, short observation sessions on long baselines, or no independent check on the network.
Candidates equate 'RTK' or 'static' with a guaranteed accuracy figure and do not connect baseline length, satellite geometry, session duration, and redundancy to the achievable precision; they also skip the independent check because the software reported a fixed solution.
What to do instead
For each survey, state the required accuracy, then justify baseline lengths, session durations, and the number of independent baselines or repeat observations against that requirement. Include at least one independent check (a different reference station, a repeated baseline, or a connection to a published control point) and compare the result with the survey tolerance before accepting the network.
Using an inappropriate map projection or scale for the task, for example measuring areas or long distances directly on a conformal projection without accounting for scale factor, or choosing a projection whose distortion is unacceptable for the area of interest.
Candidates learn that conformal projections preserve angles and then assume distances and areas are also reliable, and they do not check the point scale factor or the line scale factor for the extent of the project.
What to do instead
Before measuring, identify what the projection preserves and compute the point and line scale factors for the area in question; apply the combined scale factor (grid to ground) when converting measured distances, and choose an equal-area projection when areas are the deliverable. State the projection, datum, and scale factor used in the report.
Answering ethics and regulatory questions from personal or commercial convenience rather than from the professional obligation: accepting an engagement outside competence, certifying work not personally checked, or disclosing client data without authority.
These questions are phrased as realistic dilemmas, and candidates default to 'help the client' or 'keep the job' instead of recalling the specific duties of competence, supervision, confidentiality, and integrity that the regulator imposes.
What to do instead
Memorize the core duties as a short checklist (competence and due care, honesty in reporting, confidentiality, conflicts of interest, records and traceability, compliance with survey regulations) and test each scenario answer against it. Where a scenario involves work outside your competence or pressure to alter a result, the correct answer is normally to decline, disclose, or escalate in writing, not to comply.
Ignoring the record-keeping and traceability requirements: submitting results without the observation records, adjustment report, coordinate system definition, or metadata needed for another surveyor to reproduce the work.
Candidates focus on the final coordinates and treat documentation as administrative overhead, and they do not realize that an unreproducible survey cannot be defended or relied upon by the next surveyor.
What to do instead
Assemble a standard deliverable pack for every exercise: datum and projection definition with parameters, control used and its provenance, raw observations, adjustment method and residuals, final coordinates with precision, and a statement of the checks performed. If any element is missing, the survey is incomplete regardless of how good the coordinates look.