SURCON Professional common mistakes
SURCON Professional · Understand the traps and how to avoid them.
Transposes eastings and northings when listing final coordinates or running the coordinate (shoelace) area computation, so every bearing is mirrored about the 45° line and the plan plots as a reflection of the true layout.
Computation sheets and spreadsheets are often laid out N-E while software and some textbooks output E-N (x,y); under time pressure the candidate copies columns without checking against a known bearing, and the area check still passes, so the error is never caught.
What to do instead
Before submission, plot or hand-sketch the first three points and compare the computed bearing of one line against an independent value (e.g. a known bearing to a reference beacon or a roughly estimated quadrant). Fix a personal convention - always state 'Easting, Northing (x,y)' in the column headers - and verify that increasing northing plots upward and increasing easting plots rightward.
Presents final adjusted coordinates with no angular misclosure, linear misclosure, closure ratio, or statement of the adjustment method (Bowditch/transit), so the working cannot be checked and the closure marks are lost even when the coordinates happen to be right.
Candidates have practised the adjustment but treat it as rough work and write up only the 'answer', mirroring how computation software outputs results; they misjudge how the mark scheme is weighted toward the demonstrated process.
What to do instead
Adopt a fixed write-up template for every traverse: observed angles → angular misclosure and allowable → bearing schedule → linear misclosure in ΔE/ΔN with closure ratio → adjustment method and corrected increments → final coordinates. Practise it on timed past-style computations until it is automatic.
Converts ellipsoidal distance to grid distance using the scale factor at the central meridian (e.g. 0.9996) or simply 1.0, omitting the point scale factor at the line and the sea-level (mean elevation) reduction.
The central-meridian scale factor is the number that gets memorised, and the local/point scale factor and the elevation correction appear as small terms that feel negligible; the candidate has usually done this only in the context of the central meridian in lectures.
What to do instead
Commit to the full chain: ellipsoidal distance → mean elevation (sea-level) reduction using R and mean height → grid distance using the point scale factor at mid-latitude of the line. Show each factor separately with its numerical value (e.g. 0.99962, 0.99987) so the marker can see the reasoning and partial credit survives an arithmetic slip.
Applies a sign or direction error in datum/height conversions - computing orthometric height as H = h + N instead of H = h − N, or running Helmert/Bursa–Wolf parameters in the reverse direction to the one in which they are published.
The formulas are memorised as symbol strings rather than as a picture of the three surfaces, and transformation parameters are copied from a table without checking the stated 'from' and 'to' datums, which is easy to overlook under exam pressure.
What to do instead
Sketch the ellipsoid, geoid and terrain before substituting numbers, and sanity-check the magnitude and sign: in most of West Africa the geoid lies below the ellipsoid, so N is negative and h is numerically smaller than H by the separation. For transformations, always write 'from Datum A → Datum B' above the parameter set and invert explicitly if the table is published the other way.
Substitutes flying height above mean sea level into S = f/H (and into the parallax height formula) when the datum is ground level, or uses a single H over terrain whose elevation varies by hundreds of metres without stating the mean terrain height used.
'Flying height' is read straight off the flight plan/altimeter without asking what it is referenced to, and the distinction between height above datum, above mean ground and above sea level is exactly the point the examiner is testing.
What to do instead
Before any photogrammetric calculation, write down the datum explicitly (H = altitude above MSL − mean terrain elevation) and label H in the formula as 'above ground datum'. Where terrain relief is significant, state the mean terrain elevation and note the scale variation between high and low ground.
Claims that GNSS/IMU-supported or drone photogrammetry removes the need for ground control, and quotes absolute positional accuracy from the block adjustment report without any independent check points.
Candidates import practice from commercial drone workflows, where direct georeferencing is marketed as control-free, and they confuse precision (repeatability of the adjustment) with accuracy (closeness to the national datum).
What to do instead
State the control requirement explicitly: GCPs establish the datum and absorb datum/scale errors, while check points (never used in the adjustment) are what validate accuracy. Always quote accuracy against independent check points and against the required standard, and note that direct georeferencing still needs verification against the national network.
Measures distances or computes areas on data displayed in Web Mercator, or on any conformal projection, and reports the result as a ground measurement without a scale-factor or projection correction.
GIS software reports length and area instantly in the layer's units, so the candidate forgets that a projected coordinate system is not a distance-true surface; Web Mercator's scale distortion grows strongly with latitude and is invisible on screen.
What to do instead
For any measurement answer, name the CRS and state whether it is conformal, equal-area or equidistant, then either reproject to an appropriate equal-area/equidistant system or apply the point scale factor to convert grid values to ground values. State the correction explicitly in the answer even when the numeric effect is small.
Assigns or changes a layer's coordinate system by guessing from the numerical range of the coordinates ('they look like UTM zone 31N') rather than reading the metadata, and then overlays layers that are in different datums without transformation.
Desktop GIS allows 'define projection' and on-the-fly reprojection with no error message, so a wrong assignment produces a plausible-looking, silently shifted map; the candidate has usually only worked with data already correctly tagged.
What to do instead
Treat CRS as a fact to be verified, not inferred: check the metadata/source, overlay against a known reference dataset or imagery, and record the CRS and datum on every map and in every answer. When mixing sources, state the transformation applied and its expected accuracy.
Accepts a client's instruction to shift a boundary beacon or to 'correct' an already lodged plan so it matches the client's deed, and then justifies it in the answer on the ground that the client is paying for the work.
Ethics questions are read as customer-service scenarios, and the candidate answers the commercial question rather than the professional one; the regulatory duty to the registry, adjoining owners and the public is not front of mind.
What to do instead
Use a fixed three-step frame on every ethics scenario: (1) identify the specific duty engaged (accuracy of records, duty to the council, duty to third parties, confidentiality, competence), (2) state whether the instruction breaches it, (3) state the required action - decline, advise in writing, correct the record formally, disclose a conflict, or report to the employer/council. Never let client instruction appear above statutory or survey-regulation requirements in the answer.
Answers professional-practice and ethics questions with generalities ('be honest, be professional, act with integrity') without naming the obligation, whether it has been breached, or what the surveyor must actually do next.
These questions look like short essay prompts, so candidates write reassuring prose instead of identifying the trigger facts; they also fear that naming a specific rule or reporting route could be wrong, so they hedge into vagueness.
What to do instead
Answer structurally: name the trigger fact in the scenario, name the principle or code obligation it engages in plain terms, state the decision (permit/decline/disclose/report), and state the practical consequence (written record, notification to the council or registry, scope limitation on the plan). Where unsure of an exact statutory citation, state the substance and the instrument by name rather than inventing a section number.