How to Measure Distance on a Map Accurately
"How far is that?" sounds simple, but several different distances can satisfy the question. Picking the right one — and the right method — saves you from frustration later.
Three kinds of distance
- Straight-line ("as the crow flies"). The shortest path between two points, ignoring roads, terrain, and obstacles.
- Path distance. The total length of a defined route — useful for trails, fence lines, pipe runs.
- Perimeter. The boundary length around a closed shape — same math as path distance, but the path closes back on itself.
The right pick depends on the question. "How far apart are these two cities" wants straight-line. "How long is my hike" wants path distance. "How much fence do I need" wants perimeter.
Measuring straight-line distance
For two points, the simplest approach is to draw a tiny polygon (an elongated triangle, for example) where the long edge represents the line you care about. The "perimeter" the tool reports is roughly twice the line length — divide by two for the straight-line distance.
Future versions of this tool will include a dedicated distance/polyline tool that returns a single line length directly. In the meantime, the polygon trick works.
Why straight-line is rarely useful in the real world
Straight-line distance ignores:
- Roads. The highway distance from A to B is usually 20–60% longer than crow-flies.
- Trails. Hiking distances can be 2–3× the crow-flies distance with switchbacks.
- Fences and pipe. These follow boundaries, which are rarely straight from A to B.
- Terrain. A 1-mile horizontal distance over a mountain pass is much longer in actual hiked miles.
For driving distances, use a routing service (Google Maps directions, Waze, Apple Maps). Satellite measurement isn't the right tool for routes that follow roads.
Measuring path distance
For paths that follow a real route — a fence line, a trail, a pipe run — trace the route as a sequence of points using the polygon tool, but instead of closing the polygon, leave the last segment unconnected to the first.
Two practical tips:
- Click frequently on curves. A long arc traced with three points will be measured as straight segments between those points — shorter than the actual curve. Click 10–15 points for a smooth curve.
- Trace at high zoom. Lower zoom levels mean each click covers more ground and lower precision.
Measuring perimeter
The polygon tool reports perimeter automatically. This is what you want for fencing, mowing edges, walking around a parcel, or estimating the size of a fence repair.
The perimeter shown is the sum of the straight-line distances between the points you clicked. If your polygon has many small wiggles or curves you didn't capture, the actual walked perimeter could be longer.
Picking the right unit
Common choices:
- Feet. Best for fence runs, building dimensions, anything under ~500 feet.
- Meters. Default outside the U.S.; useful for technical work.
- Kilometers / miles. Best for hikes, driving distances, and longer paths.
The tool converts on the fly — pick whichever feels natural and use the dropdown to flip between units.
Common pitfalls
- Forgetting that the tool measures horizontal distance. A path up a steep hill is longer in walked feet than in horizontal feet. For most hikes the difference is small, but for very steep terrain it adds up.
- Mixing path and perimeter intentions. If you trace a fence and accidentally close the polygon, the reported length includes the closing edge.
- Measuring at low zoom. A "straight" road on satellite imagery at zoom 14 might curve more than you can see. Zoom in before you click.
How accurate is path measurement?
For a path you click carefully at high zoom, expect 1–3% accuracy versus a wheel-measured walk. The main sources of error are:
- Pixel resolution at the zoom level you used
- How many points you clicked on curves
- Whether the path is on level ground
That's good for ordering fence material, planning trail signage, or estimating a delivery route. It's not good enough for surveying a pipeline easement or anything legal.