Point to line offset calculator

Define what A and B represent

Enter the easting and northing of the baseline start A and end B. Their order defines the forward direction. The coordinates must use the same planar reference and horizontal unit as every target point. A baseline taken from a drawing and points exported from a receiver are not automatically compatible merely because both contain two numeric columns. Confirm the project grid, unit and axis meaning before running the calculation.

This is a straight, two-dimensional baseline calculation. It does not transform latitude and longitude, project a curved road alignment, apply a grid-to-ground factor, or interpolate heights. If your source includes X and Y rather than easting and northing, identify which axis each field means in that source. A north/east swap can produce a plausible-looking result with the wrong orientation, so a known point is useful as a preliminary check.

Read along distance and signed offset together

Along distance is measured from A toward B to the perpendicular foot F on the infinite line. A positive along distance lies forward of A; a negative value lies behind A. A value greater than the baseline length places the foot beyond B. The zero is always A, not a road station or a project chainage origin. Add a known starting chainage elsewhere only when the baseline and the chainage definition genuinely correspond.

Signed offset describes the side of the directed line. Looking from A toward B, this calculator assigns positive values to the right and negative values to the left. The magnitude is the perpendicular distance to the infinite line. A point exactly on that line has zero offset even when it lies beyond an endpoint. The report includes a separate side label and a separate projection-position label so that zero offset cannot be mistaken for being inside the finite segment.

Use the north-baseline example as a quick check

Let A be E 0, N 0 and B be E 0, N 100. For P at E 10, N 20, the perpendicular foot is E 0, N 20. The along distance is 20, and the signed offset is positive 10 because east lies to the right when looking north. Both the infinite-line distance and the segment distance are 10 because the foot lies between the endpoints. All distances use the horizontal unit selected for the calculation.

Now move P to E 3, N 104. The perpendicular foot lies at E 0, N 104, beyond B. Its distance to the infinite line is still only 3, but its nearest point on segment AB is B itself. The segment distance is 5, from the three-by-four right triangle between P and B. Selecting finite-segment mode makes 5 the selected distance while retaining the foot and the signed perpendicular offset as separate outputs.

Understand why reversing the baseline changes signs

Swapping A and B leaves the geometric line and segment in the same place but reverses the forward direction. Right becomes left, so the signed perpendicular offset changes sign. The along distance is now measured from the former endpoint in the reverse direction. The infinite-line foot and the unsigned distances remain the same. This makes a reversed calculation a useful consistency check without pretending that the two directed reports mean the same thing.

For the first example, reversing the north-facing baseline produces an along distance of 80 and an offset of negative 10. A foot that was beyond B becomes behind the new A. If another program uses positive offsets on the left, its numeric signs will differ even when the physical geometry agrees. Compare the written convention and endpoint order before interpreting a sign difference as a coordinate error.

Choose infinite line or finite segment deliberately

Use infinite-line mode when the reference is an axis that conceptually continues beyond the two points used to define it. Use finite-segment mode when the endpoints are genuine limits of the object being checked. Neither choice changes the input coordinates. Both modes retain the infinite-line foot F and the nearest point C on the finite segment, making the effect of the choice visible in the result instead of hiding it behind one distance field.

When the foot falls within AB, including the endpoints, F and C coincide. Outside that range, C is A or B, while F remains on the extension. The signed offset always refers to the infinite line, even in segment mode. A nearest-endpoint distance is not a signed perpendicular offset. Keep the two column headings intact when sharing a report so that the recipient knows which geometric quantity was used.

Calculate all records in a source file

For a batch, switch the target input to a point file, load a UTF-8 CSV or TXT, inspect the preview and confirm the column mapping. The shared importer supports explicit east and north fields and source-unit labels. Every source record is included as a target. If A or B also appears in the file, those records are retained and usually produce zero distance. Duplicate point IDs remain separate records, identified by source line. XLSX workbooks are also accepted for this input: explicitly choose the worksheet, and replace formulas, dates or error cells with plain values before importing.

The baseline is entered separately, which allows you to use a design axis that is absent from the target file. Enter its coordinates in the source file unit; changing a unit label does not rescale a number. Add a reference note describing the grid and calculation purpose, then confirm the common planar context. Records with source errors remain unresolved rather than being silently dropped. Correct the source and recalculate before relying on those rows.

Review the result before exporting

Select a source line in the paginated table to inspect the target coordinates, along distance, signed offset, side, foot and closest segment point. The diagram uses north upward and east rightward, with positions relative to A. It shows the baseline and the selected target relationship; it is not a map or a source of additional measurement precision. Coincident markers may overlap, so use the labelled coordinate values when the picture is ambiguous.

The table displays distances to six decimal places, using scientific notation for very small or large values. CSV and JSON retain the numerical calculation results and original coordinate text. Derived foot coordinates are rounded decimal strings; additional displayed digits do not establish the accuracy of the original survey. The computation preserves decimal differences before forming geometric products, reducing cancellation when a small offset is associated with a large coordinate origin. Values outside the supported numerical range are reported as unresolved.

Keep the report and its assumptions together

CSV export includes source filename, source line, point ID, original coordinates, along distance, signed offset, side, projection position, both derived points, both unsigned distances and the selected mode. Baseline coordinates, unit and reference note travel with each row. JSON additionally preserves the checked source structure and the complete calculation settings. Computed signed distances remain numeric in CSV; potentially active source text is protected for spreadsheet review.

The output is a calculation report, not a new survey point file and not an acceptance certificate. This tool does not decide whether an offset meets a project tolerance. Read the project specification and apply the appropriate criterion separately, especially when a finite object and an extended axis are both involved. Changing input or settings clears the previous result so that an old report cannot be exported under new assumptions.

Processing stays in the browser. Point files are limited to ten MiB and one hundred thousand records, and CSV reports have a ten MiB limit. For a larger report, split the source or use JSON. Calculations run separately from the page controls, with a cancel option that retains the input. No height is invented for a foot or endpoint, because every quantity on this page is horizontal.