Angle Between Lines Calculator

What does this angle between lines calculator compute?

The principal angle θ between two undirected lines A₁x + B₁y + C₁ = 0 and A₂x + B₂y + C₂ = 0 is arccos(|A₁A₂ + B₁B₂| / (√(A₁²+B₁²) √(A₂²+B₂²))), in [0°, 90°]. For oblique lines this is the acute angle.

The published formula or method is θ = arccos(|A₁A₂ + B₁B₂| / (√(A₁²+B₁²) √(A₂²+B₂²))). The following references support the stated mathematics or method:

• Margaret Stevens — The Maths Workbook (University of Oxford): Linear-function slopes and point-slope equations, and simultaneous linear equations in two variables. Line intersection is the corresponding system solution; vertical lines use an implicit rather than finite-slope representation. Mathematical reference only; not implementation validation or an endorsement of CalculatorX.
• Gilbert Strang, Calculus — Chapter 11: Vectors and Matrices (MIT OpenCourseWare): Vector components and magnitudes, dot product and angle/projection relations, and cross product/determinant orientation and area. Projecting a point displacement onto the unit normal to Ax+By+C=0 gives distance |Ax₀+By₀+C|/sqrt(A²+B²); this planar expression is derived from the projection formula. Mathematical reference only; not implementation validation or an endorsement of CalculatorX.

Which inputs and limits should you check?

Keep both points and line coefficients in the same coordinate system. Parallel, coincident, or degenerate lines require their own result classifications.

The worked example uses (0, 0)–(2, 2) and (0, 0)–(2, 0) with arccos(1/√2). Compare it with the Example calculations and the complete result for the same inputs.

How do agents discover the angle contract and units?

Call inspect_capability with capability_id: "math.geometry.coordinate" and operation: "angle". Its operation input Schema requires mode: "angle" and all eight endpoint coordinates. Decimal strings follow the same numeric range checks as the generic contract. Distinct-point lines and numerical range are checked during execution.

REST result_detail.field_units and MCP result.field_units / result_detail.field_units identify angle_deg: "deg", angle_rad: "rad", and supplement_deg: "deg". The mixed result's scalar unit stays null; coordinate and line-coefficient fields do not inherit an angular unit. Output Schema annotations also specify each angle field's display unit and capability-scoped plane-angle kind.

The display unit tokens remain stable. field_unit_refs on REST result_detail and MCP result / result_detail associates the same fields with UUCE cx:deg or cx:rad, definition revision 1.0.0, snapshot 0.3.0-preview.3, content/dependency digests, plane-angle kind, scalar role and SI dimension vector. inspect_capability exposes these as output_field_unit_refs; Output Schema uses x-unit-id, x-dimension and x-uuce-unit annotations.

These references pin the UUCE Preview definitions: one degree is exactly π/180 radians, and plane angle remains distinct from solid angle and generic ratios despite its zero dimension vector. They do not change the calculator's floating-point numerical policy, perform automatic angle wrapping, or migrate calculation to the UUCE converter. Definition exactness is separate from numerical result accuracy.

How can you verify and cite this result?

CalculatorX is responsible for this page. The mathematical references above explain the model; implementation checks and their scope are documented separately in the math.geometry.coordinate v1.8.0 Evidence and capability contract. Read the displayed verification and production state together with the specification's numerical limits.

Use the clean calculator URL to cite the tool. A shared input link identifies a particular calculation. Content updates, numerical verification, and domain reviews have separate dates and scopes.

Numerical domain and interpretation

Coordinates are Cartesian values in one consistent length unit. Inputs accept finite decimal numbers or decimal strings; nonzero coordinates and published numeric outputs must be normal binary64 (absolute value at least 2⁻¹⁰²²). Nonzero text that converts to zero is rejected as NUMERIC_UNDERFLOW. NUMERIC_RANGE means translate or rescale your inputs. Explicit empty fields are errors, not defaults.

All seven operations use the same engine. Distance and midpoint allow identical points; slope and line operations require distinct defining points. A vertical line has null slope and intercept. Intersections concern infinite lines, not segments: parallel distinct lines return empty, coincident lines return coincident, and both have null intersection coordinates.

Exact dyadic predicates classify the normalized binary64 directions without an absolute geometric epsilon. The principal undirected angle is atan2(|d₁×d₂|, |d₁·d₂|), in [0°,90°], with radians also available. A rounded angle of90° does not itself imply an exact perpendicular classification. Nearly parallel lines are sensitive to input rounding; exact predicates do not recover decimal information lost before computation. Typical well-conditioned scalar comparisons use relative2e−12; no input perturbation or intersection-position bound is claimed.

Line coefficients use integer gcd only for exact safe integers; otherwise they share a power-of-two normalization and canonical sign. Display equations are floating presentations. The uniformly scaled figure is schematic; close labels may merge, and an unrepresentable plotting range is explicitly omitted. Complete numerical results and raw supplied inputs are available in exports.

Browser calculations run locally. A shared URL sends its parameters to the server and may appear in service logs; REST/MCP also send inputs. This page makes no claim about a fixed log retention period or processing region.