Traverse DeskGet COGO
Coordinate geometry

Compute station and signed offset from two control points

Project a survey point onto an oblique baseline, check its side and recover the original coordinate from the reported station and offset.

Worked exampleAlong-line and perpendicular unit vectors · dot product 0
On this pageBuild forward and right unit directionsResolve the point relative to the lineVerify distance with a different triangleTake the result back to the crew

Two stations define a straight line. A third point is neither on the line nor directly east or north of its start. Subtracting the eastings alone gives neither its chainage nor its lateral offset. The practical solution is to express the coordinate difference in a pair of axes that follow the baseline.

Build forward and right unit directions

Use northing and easting in that order. The baseline runs from A at N 1000, E 2000 to B at N 1080, E 2060 m. Its displacement is (+80, +60), and its horizontal length is exactly 100 m. Divide by 100 to get the forward unit direction (+0.8, +0.6). Looking along A–B, the right-hand perpendicular points southeast, with unit components (−0.6, +0.8).

The dot product of those two unit directions is 0.8 × (−0.6) + 0.6 × 0.8 = 0. They are perpendicular, and each has length one. Write this once in the calculation sheet. It catches an accidental swap between a left-positive and right-positive convention before you report a row of offsets.

Resolve the point relative to the line

Suppose P is N 1027, E 2044. Relative to A the point is 27 m north and 44 m east. Project that displacement onto the forward unit direction: 27 × 0.8 + 44 × 0.6 = 48 m. Then project it onto the right direction: 27 × (−0.6) + 44 × 0.8 = +19 m.

If A has station 12+00.00 under a 100-unit station convention, P’s perpendicular foot has station 12+48.00. Record P as 19.00 m right looking toward increasing station. A left-positive project setup would report the same physical offset with a negative sign. State the sign convention beside the result.

Position North m East m
Baseline start A 1000.0 2000.0
Perpendicular foot 1038.4 2028.8
Point P 1027.0 2044.0

The foot comes from traveling 48 × (0.8, 0.6) from A. From that foot, travel 19 × (−0.6, 0.8). The reconstructed P matches the observed coordinate exactly. This inverse reconstruction is often a better check on spreadsheet signs than comparing two visually similar sketches.

Verify distance with a different triangle

The direct distance A–P is √(27² + 44²), about 51.624 m. The projected right triangle gives √(48² + 19²), the same value. An along-line distance and a signed offset are two components of the same displacement. Using the direct A–P distance as chainage would put the station several metres too far forward.

The chainage here falls between 0 and the line length of 100 m. A negative projection or a value beyond 100 would put the foot on the extended line. Decide whether the task requires extension, a clipped segment or a different segment of a longer alignment. The closest point on a finite segment may be an endpoint rather than the perpendicular foot.

Take the result back to the crew

Include the stationing origin, exact direction of increasing station, coordinate basis, unit and side convention in the point note. A reversal of the baseline changes both the distance origin and the side. An alignment with station equations or curves requires its own alignment model rather than a single straight baseline.

The closure calculation method uses the same signed component convention for each observed course. Station and offset use those components for a different purpose: locating one independent point relative to an oriented line. Keep this worksheet beside your point coordinates when handing off an offset without its original sketch.

As a reversal check in this example, measuring forward from B toward A puts the same foot 52 m from B and the point 19 m to the left. The two chain distances add back to the 100 m baseline. If they add to 96 m, both calculations have used the original origin.

References

Check traverses offline with COGO