Two friends in different towns want to meet halfway. A delivery driver wants the point equidistant from two depots. A hiker wants the coordinate at the center of a route's two ends. All of them are asking for the same object, the midpoint between two coordinates, and most of the time the answer is disarmingly simple: average the two latitudes, average the two longitudes, done. This guide teaches that average properly, with the arithmetic shown, and then does the part most guides skip: it shows exactly when the average stops being true, across long distances where the Earth's curve bends the answer, and at the antimeridian, where the naive average of two Pacific longitudes lands in the South Atlantic. If your two points are close together, the first section is all you need. If they are an ocean apart, the later sections are the difference between a midpoint and a mirage.
Home / Coordinates and Location Formats
How to Find the Coordinates of a Midpoint: The Average, and When It Lies

Photo: Curtis Adams / Pexels
Coordinate Explorer: Average the Pair
Click two points on the map and read their coordinates; the midpoint is the average of the two latitudes and the average of the two longitudes. Try a nearby pair first, then two cities an ocean apart, and watch the simple average drift from the great-circle answer this article derives.
Map data © OpenStreetMap contributors. Coordinates are read from the map itself, in the WGS 84 system your phone uses.
The Simple Average: Two Additions, Two Divisions
Take the two points in decimal degrees, the format our guide to latitude and longitude format explains in full. Add the two latitudes and divide by two. Add the two longitudes and divide by two, keeping the signs: west longitudes and south latitudes are negative, and the signs are not decoration, they are what make the arithmetic land on the right continent. Worked example, London at 51.5074, -0.1278 and Oxford at 51.7527, -1.2577. Latitude: 51.5074 plus 51.7527 is 103.2601, divided by two is 51.6301. Longitude: -0.1278 plus -1.2577 is -1.3855, divided by two is -0.6928. The midpoint is 51.6301, -0.6928, a point in the Buckinghamshire countryside between the two cities, which is exactly where common sense wants it. That is the whole method, and for the great majority of real questions, two points in the same region, the same state, the same small country, it is the right method too. The averaging works because over short distances the Earth's surface is nearly flat, so latitude and longitude behave like the x and y of a school graph. The rest of this article is about the two situations where that flatness runs out, and both are worth understanding before you trust an average with a long journey or a Pacific crossing.
When the Average Is Good Enough, in Numbers
How wrong can the average be? The error grows with the distance between the points, and it grows politely at first. For two points across one city, the simple average and the true spherical midpoint agree to within a few meters, far inside the accuracy of the coordinates you typed. For London and Oxford, about ninety kilometers apart, the two methods disagree by roughly 180 meters: noticeable to a surveyor, irrelevant to anyone choosing a meeting town. The reason is geometry. The true midpoint lies on the great circle, the shortest path over the sphere, and that path bows away from the straight line you draw on a flat map. The longer the span, the higher the bow, and the further the flat average sags from the spherical truth. A useful rule of thumb: if your two points fit inside one day's drive and the answer only needs to name a town or a neighborhood, average without fear. If the points are separated by a continent or an ocean, or the answer will be typed into a boat's or an aircraft's navigation, the average is no longer an approximation of the midpoint. It is a different point, and the next section computes the real one.
The Great-Circle Midpoint: The Formula That Respects the Sphere
For long spans, compute the midpoint on the sphere. Convert both points to radians. Let the longitudes differ by dLon, the second minus the first. Then build two helpers from the second point: Bx equals cos of lat2 times cos of dLon, and By equals cos of lat2 times sin of dLon. The midpoint latitude is the arctangent of (sin lat1 plus sin lat2) over the square root of (cos lat1 plus Bx) squared plus By squared. The midpoint longitude is lon1 plus the arctangent of By over (cos lat1 plus Bx). Convert back to degrees and you hold the true halfway point of the great-circle path. Worked example, New York at 40.7128, -74.0060 and Los Angeles at 34.0522, -118.2437. The simple average gives 37.3825, -96.1249, in Kansas. The great-circle formula gives 39.5103, -97.1601, also in Kansas, but about 253 kilometers further north. Both answers cannot be the halfway point of the same journey, and the spherical one is: the shortest path from New York to Los Angeles bows north across the plains, and its true middle sits up on that bow, while the flat average cuts the corner through the map's fiction. The tool above this article lets you feel the same effect: click two distant cities and compare the pair you get with what the average of their coordinates predicts.

The Antimeridian Trap: When the Average Crosses the World
One failure of the average has nothing to do with curvature and everything to do with the calendar line of longitude. Take two points in Fiji: -17.7134, 178.0650 and -17.0000, -179.9000. They are close neighbors in the Pacific, a short flight apart. Average the longitudes naively: 178.0650 plus -179.9000 is -1.8350, divided by two is -0.9175. Plot -17.3567, -0.9175 and you are in the South Atlantic, off the coast of Namibia, roughly as far from Fiji as it is possible to be. The bug is that longitude wraps: 178 degrees east and 179.9 degrees west are 2 degrees apart across the 180 line, not 358 degrees apart the long way around, and the naive sum walks the long way. The fix is mechanical. When the two longitudes straddle the antimeridian, one near +180 and one near -180, add 360 to the negative one before averaging, then subtract 360 from the result if it exceeds 180. Here: -179.9000 plus 360 is 180.1000; average with 178.0650 gives 179.0825, which normalizes to 179.0825, in Fiji's waters where it belongs. Any midpoint calculator worth using, including the explorer above, handles this wrap for you, but knowing the trap exists is what stops you from trusting a hand average computed on a ship near the date line.
A Midpoint Is Not a Halfway Meeting Point
One last separation, because it is the mistake that turns correct arithmetic into a bad plan. The midpoint of two coordinates is halfway in straight-line distance over the Earth's surface. It is not halfway in travel time, and on real terrain the two can differ wildly. The geographic midpoint of two towns separated by a mountain range may sit on a peak with no road within twenty kilometers; the fair meeting point is a town on the road network that equalizes the two drives, which is a routing question, not an averaging one. Rivers, borders, one-way systems, and ferry schedules all bend travel time the same way. So use each tool for its own question. If you need the coordinate at the center, for a dataset, a boundary, a search area, a fair split of straight-line distance, compute the midpoint as this article teaches; our guide to finding coordinates on a map covers getting the two endpoint pairs in the first place, and the reverse problem, recovering endpoints when the midpoint is given, has its own treatment in how to find coordinates when the midpoint is given. If you need two people to arrive at the same time, open a route planner, price both drives to a few candidate towns near the geographic midpoint, and let the roads, not the sphere, cast the deciding vote.
Three Points and Beyond: Centroids and Weighted Middles
The midpoint idea generalizes, and the generalizations answer real questions. With three points, the average of all three coordinates gives the centroid of the triangle they form, the balance point of the three corners, which is the natural "middle of the three of us" for a trio meeting from three towns; our companion article on the centroid of a triangle works that case in full. With many points, the same averaging gives the center of a set, the middle of a delivery territory's stops, the center of a search area's sightings, with the same caveats scaled up: it is a flat average, honest locally, and increasingly a lie as the set spreads across the sphere. Weighting refines the idea usefully. If one endpoint matters more, a depot with three trucks against a depot with one, average with weights, counting the busier point three times in both sums, and the "midpoint" slides toward the place that generates more journeys, which is often the point a business actually wants. Every one of these variants inherits the two traps from the main method, so the discipline travels with them: mind the signs, mind the antimeridian, and once the span grows continental, move the computation onto the sphere, where the great-circle logic of this article's main formula extends to the averaged direction of all the points. The average is a humble tool. Used inside its limits, it is also an exact one.
Related Guides
This guide does not stand alone. The coordinates guides below take up the questions it leads into:
- How to Find Coordinates From Slope-Intercept Form: Build (x, y) Points From y = mx + b: An equation in slope-intercept form, y = mx + b, is a machine for producing coordinates: choose any x, run it through the equation, and the y that...
- How to Find Coordinates on a Garmin GPS: Handhelds, Car Units, and Watches, in the Right Format: A Garmin always knows where it is; the skill is persuading it to show you the number, in a format you can use.
- How to Find Coordinates in Google Earth: Cursor Readout, Placemarks, and Formats: Google Earth shows the coordinates of any point in the lower right corner as your cursor moves, but most people never notice the readout, and...
- How to Find Coordinates in QGIS: Status Bar, Copy Coordinates, and Field Calculator: QGIS shows coordinates in more places than any other GIS, and each answers a different question.
- How to Find Coordinates on the Unit Circle: Build Every Point From Two Triangles: Every coordinate on the unit circle comes from one rule and two triangles.
- How to Find Coordinates Rotated 90 Degrees: The Rules for Clockwise, Counterclockwise, and Any Center: Rotating a point 90 degrees is a swap and a sign change: counterclockwise about the origin, (x, y) becomes (-y, x); clockwise, it becomes (y, -x).
Frequently Asked Questions
How do I find the midpoint between two coordinates?
For nearby points, average them: add the two latitudes and divide by two, then add the two longitudes and divide by two, keeping negative signs for south and west. For points a continent or ocean apart, use the great-circle midpoint formula so the answer follows the sphere.
What is the midpoint between New York and Los Angeles?
The great-circle midpoint is about 39.5103, -97.1601, in Kansas. The simple average gives 37.3825, -96.1249, which is roughly 253 kilometers too far south, because the shortest path between the coasts bows north and its true middle sits on that bow.
Why did my midpoint land in the wrong ocean?
Almost certainly the antimeridian. If one longitude is near +180 and the other near -180, a naive average wraps the long way around the world. Add 360 to the negative longitude before averaging, then normalize the result back into the -180 to 180 range.
Is the midpoint the best place to meet halfway?
It is the fairest point in straight-line distance, which is not the same as equal travel time. Roads, mountains, and borders distort drive times, so use the midpoint as the center of your search, then compare actual drives to towns near it.
How accurate is the simple average for points in one city?
Effectively exact for everyday purposes. Across a city, the average and the great-circle midpoint agree within a few meters. The methods only part company over long spans, about 180 meters at ninety kilometers and hundreds of kilometers across a continent.
Photo credits: Curtis Adams (Pexels); Marina Leonova (Pexels). Photos are served from this site; follow the credit to the library page for the original.