COGO Calculators for Survey Coordinates

Choose the direction of the calculation

Coordinate geometry, often called COGO, connects positions, directions and distances. The first decision is whether you know points and need a relationship, or know a relationship and need a new point. With two confirmed coordinates, use the inverse calculator for directed differences, horizontal distance and azimuth. With a confirmed origin, direction and horizontal distance, use the forward calculator to generate a position. Reversing these tasks mentally is a common source of sign and direction mistakes.

An independent inverse of a generated point is a useful check because it returns to the quantities you started with. It does not prove that the starting control or bearing was correct, but it can expose a wrong angle convention, a mistaken unit or a swapped coordinate column. Preserve both the original input and the generated result so that the check remains reproducible after a file is passed to someone else.

Set axes, units and direction conventions first

These planar tools use explicit Easting and Northing. A north-clockwise azimuth of zero points north, ninety points east, one hundred eighty points south and two hundred seventy points west. A mathematical angle measured counterclockwise from east follows a different convention. Do not copy an angle from a drawing into a survey azimuth field until its reference direction and rotation sense are known. A point name or an X heading cannot establish that convention for you.

Horizontal and vertical units can differ in a source file. Record each before interpreting a height difference or slope. A unit label identifies a number; it is not an automatic conversion. Likewise, metre coordinates in two local grids are not comparable merely because their units agree. If the task actually involves known projections, go to the batch coordinate converter. If parameters must be estimated from common controls, use the two-dimensional fitting tool with separate check points.

Distinguish horizontal distance from a sloping observation

Forward coordinate generation needs the distance in the horizontal plane. A total station may instead provide a slope distance and a zenith or vertical angle. Reduce that observation first, using the explicitly selected angle convention and the relevant instrument and target heights. The observation-reduction tool keeps the raw quantities beside the result, including invalid rows. It does not silently apply prism constants, weather corrections or instrument calibration that were never supplied.

The slope calculator solves a different problem from an observation reducer: it relates a rise to a horizontal run, percent, angle or horizontal-to-vertical ratio. A negative rise is meaningful and should not be removed merely to make the output look positive. If you need a point elevation, a relative height difference alone is insufficient without a stated starting elevation and datum. Missing heights remain missing instead of turning into convenient zeroes.

Use intersections only when the constraints identify them

An intersection can come from two directions, a direction and a distance, two distances or two explicitly defined lines. Choose the mode that describes the original information rather than converting everything into an improvised sketch. Some combinations have no solution; others have two possible positions. Both outcomes are useful. A calculation that returns two candidates is asking for another field or design condition, not inviting the software to pick the visually nearest point.

Check whether the problem concerns forward rays, infinite lines or bounded segments. A mathematically valid intersection behind an observation station may not satisfy a forward sight. Keep the candidate list and the selection basis with the output. Very shallow intersections can be sensitive to small input changes even when arithmetic succeeds, so numerical completion should not be treated as a statement about the quality of the geometry or its practical uncertainty.

Check offsets and boundaries with their order intact

For one baseline and many targets, the point-to-line tool reports a perpendicular foot, a signed side and an along distance. The distance to an infinite line differs from the nearest distance to a finite segment when the foot lies beyond an endpoint. Select the appropriate interpretation before evaluating a setback or locating a point. Reversing the baseline reverses side semantics, which is why the endpoint order belongs in the calculation record.

Area calculation similarly depends on order. Supply the vertices of a simple boundary in their intended sequence; a bag of points is not yet a polygon. Review self-intersections, repeated vertices and degenerate edges before using the area. The tool calculates a planar boundary, not an ellipsoidal parcel area or a terrain surface area. Multiple rings, holes and complex cadastral topology need a method that explicitly represents those structures instead of flattening them into one list.

Generate new points without hiding the construction

Use straight-line division for a segment count or fixed spacing between known endpoints. Decide whether to include the start and end and whether known endpoint heights may be interpolated. A final short interval is part of a fixed-spacing schedule, not an error to hide. Appending new points should retain the original records and avoid identifier collisions. A point generated halfway in plan is not automatically a measured terrain point halfway along a slope.

For a known local rotation, translation and optional scale, use the coordinate transformation tool and specify the center and operation order. Rotating then translating generally differs from translating then rotating. A separate height shift must be intentional; it cannot stand in for a vertical datum conversion. Keep the before-and-after table so that the operation can be checked against a control rather than judged only by whether the transformed cloud appears in a convenient place.

Build a small independent check before processing a batch

Use a deliberately asymmetric example: A at E100, N200 and B at E130, N240 has differences thirty east and forty north, and a horizontal distance of fifty. Swapping both axes preserves that distance, which shows why distance alone cannot validate the mapping. Its north-clockwise azimuth is approximately 36.869897646 degrees. Starting at A with that azimuth and a horizontal distance of fifty should recover B within the displayed numerical precision.

After a simple check, inspect the batch summary and every invalid record. Download the full report when an output table shows only a page of rows. Preserve the formula context, units, source filenames and coordinate basis alongside the points. A coordinate geometry tool helps reproduce a specified construction; it does not establish legal boundaries, approve a design, replace instrument checks or certify control accuracy. Those decisions require the applicable project evidence and responsible professional review.

Questions and answers