Quick answer

Coordinate mode uses vector components directly. Point mode builds v = (to - from) for each arrow, then runs the standard angle formula on those components.

Formula

  • Coordinate: use (x, y) or (x, y, z) as given
  • Point: v = (x₁ - x₀, y₁ - y₀, z₁ - z₀)

Introduction

On the home calculator, vector a and vector b each have their own representation toggle. You can mix styles: coordinates for a displacement you already solved and points for a second arrow still tied to map corners.

After both vectors exist in component form, the angle math is identical. See how to use the angle between two vectors calculator for a control-by-control tour, or how to find the angle step by step for the full numeric path.

What is the difference in practice?

Coordinate mode assumes you already know the vector as a direction and length encoded in components, often because the vector starts at the origin conceptually.

Point mode assumes you know where an arrow starts and ends. The vector is the change from start to finish, not the raw corner coordinates alone.

Survey stakes, game world positions, and CAD nodes usually arrive as point pairs. Physics homework often gives components after a diagram is drawn at the origin.

Mixing modes on one problem is normal: you might know one displacement from a diagram and read a second arrow from two map clicks.

Displacement before dot product

  • Given points P₀(x₀, y₀, z₀) and P₁(x₁, y₁, z₁)
  • v = (x₁ - x₀, y₁ - y₀, z₁ - z₀)
  • θ from cos θ = (a · b) / (|a| |b|)

Subtract in the same order your diagram uses: from → to. Reversing start and end flips the vector direction and can change θ to its supplement in colinear cases.

The dot product story still helps here: once displacements are built, read dot product and vector angle explained if you want to interpret signs and magnitudes.

Workflow for each representation

  1. Label the start and end of each arrow. Write From and To for vector a, repeat for vector b. Confusing the two corners is the fastest way to get a plausible but wrong angle.
  2. Subtract component-wise. In 2D, subtract x and y separately. In 3D, include z. Use the calculator’s Point fields so the tool performs the same subtraction.
  3. Switch to Coordinate mode to verify. After manual subtraction, re-enter the displacement as components. Matching results between modes is a strong sanity check.
  4. Run the angle and compare units. Keep feet with feet and meters with meters. Mixed units distort both displacements and θ.
  5. Archive the from/to pairs in project notes. Future you will need the same corners when a reviewer asks why θ changed after a coordinate fix.

Point form example

Vector a runs from (0, 0) to (3, 0), so a = (3, 0). Vector b runs from (0, 0) to (3, 4), so b = (3, 4). The angle matches the classic 53.13° triangle.

If one arrow had a nonzero start, say a from (1, 2) to (4, 2), the displacement is still (3, 0). Treating (1, 2) as the vector itself would be incorrect. When depth appears, switch to 3D and read 2D vs 3D vector angles before you lock a mode.

3D point sample: a from (0, 0, 0) to (1, 0, 1) gives (1, 0, 1). b from (2, 1, 0) to (2, 1, 1) gives (0, 0, 1). Build both displacements before you dot; the angle is about those directions, not the raw corner lists.