Cartesian coordinates are the friendliest coordinate system ever invented, and the one most often fumbled by a single habit: reading the numbers in the wrong order. A Cartesian pair is just two counts from a fixed origin, horizontal first, vertical second, with signs set by which quadrant the point sits in. Everything else, distance, polar conversion, the map connection, is arithmetic built on that one habit. This guide builds the habit properly: the counting method, the signs, the conversions in both directions with examples worked to checkable answers, and the bridge to the map grids where the same two counts wear different names.
Home / Coordinates and Location Formats
How to Find Cartesian Coordinates: Read X and Y Right, Then Convert Polar Both Ways

Photo: cottonbro studio / Pexels
Coordinate Explorer: X and Y on a Real Map
Click any point and read its pair. On a map, longitude behaves like x and latitude like y, and map grids rename them easting and northing. The order rule from this article, x first, then y, is the same rule that keeps GIS imports out of the ocean.
Map data © OpenStreetMap contributors. Coordinates are read from the map itself, in the WGS 84 system your phone uses.
The Counting Method: Along, Then Up
Picture the grid: two axes crossing at the origin, the point (0, 0). The x axis runs horizontally, positive to the right. The y axis runs vertically, positive upward. To find the coordinates of any point, start at the origin and count: first along the x axis until you are directly below or above the point, that count, with its sign, is x. Then count vertically to the point, that count, with its sign, is y. Write the pair as (x, y), x always first.
The schoolroom mnemonic earns its keep: along the corridor, then up the stairs. It is the same rule that governs map grids, where easting is read before northing, and the same rule whose violation swaps more real world points than any other error in coordinates. A point 4 right and 3 up is (4, 3). A point 3 right and 4 up is (3, 4). They are different points, a fact that matters the first time a swapped pair moves a delivery, a game character, or a surveyed corner.
The Quadrants: Where the Signs Come From
| Quadrant | Position | x sign | y sign | Example |
|---|---|---|---|---|
| I | Right and up | + | + | (3, 4) |
| II | Left and up | minus | + | (minus 6, 8) |
| III | Left and down | minus | minus | (minus 2, minus 5) |
| IV | Right and down | + | minus | (5, minus 1) |
Points on the axes belong to no quadrant and need no sign decisions: (0, 5) is straight up the y axis, (minus 7, 0) is straight left along the x axis. When you read a pair back from a graph, the quadrant is your error check: if the point sits up and to the left and either number is positive in the wrong slot, you have misread one of the counts.
Distance Between Two Points: Pythagoras on the Grid
The grid's first real power is distance. Between (x1, y1) and (x2, y2), the horizontal gap is the difference of the x values, the vertical gap is the difference of the y values, and the straight distance is the square root of the sum of their squares. Worked example: from (1, 1) to (4, 5), the gaps are 3 across and 4 up, and the distance is the square root of 9 + 16, which is the square root of 25: exactly 5. The 3-4-5 triangle is the grid's hello. Once you see it, you see why the map distance tools work as they do; our distance between coordinates guide runs the same idea on the curved Earth, where Pythagoras needs help from the haversine formula.
Polar to Cartesian: From an Angle and a Length
Polar coordinates describe a point the way a compass and a pace count do: a distance r from the origin, and an angle, measured from the positive x axis, counterclockwise. Converting to Cartesian is two multiplications: x = r times the cosine of the angle, y = r times the sine of the angle.
Worked example one. r = 10, angle = 60 degrees. Cosine of 60 is 0.5, so x = 10 times 0.5 = 5.00. Sine of 60 is about 0.866, so y = 10 times 0.866 = 8.66. The point is (5.00, 8.66).
Worked example two. r = 5, angle = 45 degrees. Cosine and sine of 45 are both about 0.7071, so x = 3.54 and y = 3.54: the point sits exactly on the diagonal, as a 45 degree point must. That symmetry is your check.
Worked example three. r = 13, angle = 53.13 degrees. Cosine is 0.6, sine is 0.8, so x = 7.80 and y = 10.40. Notice the family resemblance to the 3-4-5 triangle, scaled: polar and Cartesian are two descriptions of the same right triangle, one by its hypotenuse and angle, one by its legs.
Cartesian to Polar: The Return Trip
Going back, the distance is Pythagoras again: r = the square root of x squared plus y squared. The angle comes from the arctangent of y divided by x, with one honest complication: the arctangent alone cannot tell quadrants apart, so you adjust by where the point sits.
Worked example one. (3, 4): r = square root of 9 + 16 = 5. The angle is the arctangent of 4/3, which is 53.13 degrees. Quadrant I, no adjustment: polar form is r = 5, angle 53.13 degrees, the same triangle as before, read backward.
Worked example two. (minus 6, 8): r = square root of 36 + 64 = 10. The raw arctangent of 8 divided by minus 6 gives minus 53.13 degrees, which points into the wrong quadrant entirely. The point sits in Quadrant II, so the true angle is 180 minus 53.13 = 126.87 degrees. This adjustment is not a technicality; skipping it is the standard way this conversion goes wrong, and every calculator's atan2 function exists precisely to do it for you: give atan2 the y and the x separately, and it returns the angle in the correct quadrant.

The Bridge to Maps: Easting Is X, Northing Is Y
Here is the connection that makes this article belong on a map site. Every flat map grid is a Cartesian system wearing work clothes. On a projected map, the easting is the x: the count eastward from the grid's origin. The northing is the y: the count northward. When a GIS asks you to import a table of x and y values, it is asking for eastings and northings, in that order, which is the along-then-up rule again. Our northing and easting guide covers the grids themselves; the point here is that the counting skill transfers whole.
What does not transfer is latitude and longitude. Those are angles on a sphere, not counts on a plane, and treating a longitude as an x coordinate is the classic beginner's GIS error: it works approximately near the equator and distorts everywhere else, because a degree of longitude shrinks toward the poles while a unit of x never does. The Coordinate Explorer above makes the distinction touchable: click and you get angles, latitude and longitude, which a projection would then have to flatten into Cartesian x and y before grid arithmetic applies. Coordinates in their several families, angles, grid counts, and three dimensional values, are organized in our guide to coordinate systems; Cartesian is the family where the counting is honest and the plane is flat, which is why every other family borrows its habits.
Finding Coordinates on Screen and on Paper
On a printed graph or map, find a point by the counts: locate the origin or the grid lines, count right for x, count up for y, and interpolate between grid lines by eye when the point falls between them, estimating tenths. On a screen, in a spreadsheet chart, a CAD view, or a game editor, the readout at the cursor is doing the counting for you; your job is the order check and the sign check. In both worlds the discipline is identical: x first, y second, signs from the quadrant, and a backward glance at the picture to confirm the pair describes the point you are actually looking at. That backward glance catches swapped pairs, dropped minus signs, and misread grid lines, which between them account for nearly every Cartesian error ever made.
Cartesian Coordinates in the Wild: Screens, Spreadsheets, and Games
You already use this system daily in disguise, and two of its disguises carry a trap. Spreadsheet charts plot Cartesian honestly: the first column drives x, the second y, and a scatter plot of swapped columns is the office version of the swapped pair, instantly visible because the chart's shape turns wrong. Game grids and map editors are Cartesian with a chosen unit: a tile is one unit, and positions are tile counts from an origin corner, which is why game coordinates feel like the counting method with a costume on. Screen pixels are the trap: a screen's coordinate system puts its origin at the top left and counts y downward, inverting the mathematical convention, so a point's screen y grows as the point descends. Every programmer meets this once, usually by drawing a chart upside down. The lesson generalizes beyond screens: whenever you meet a coordinate pair, ask three questions before using it. Where is the origin? Which way do the axes point? What unit is the count in? Cartesian is a family of agreements, not a single law of nature, and those three questions read any member of the family, from a child's graph book to the grid under a GIS. Our overview of coordinate systems lines the whole family up side by side.
Related Guides
Readers working through this topic usually need its closest companions too. These coordinates guides cover the neighboring ground:
- How to Find NAD83 Coordinates: Convert, Look Up, or Read Them Off Control Points: Your GPS speaks WGS84, but American surveying, state GIS data, and federal maps speak NAD83, and the two differ by a meter or two.
- How to Find the Centroid Coordinates of a Triangle: Average the Vertices, Then Prove It With the Medians: The centroid of a triangle is the average of its three vertices: add the three x coordinates and divide by three, add the three y coordinates and...
- 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.
Frequently Asked Questions
What are Cartesian coordinates in simple terms?
Two counts from a fixed starting point called the origin: how far along horizontally (x), then how far up vertically (y), written as (x, y). The system is named for Rene Descartes. It is the coordinate system of graph paper, spreadsheets, game worlds, and, under the names easting and northing, every flat map grid.
Which comes first, x or y?
X always comes first: along the corridor, then up the stairs. (4, 3) and (3, 4) are different points. The same order rule appears in map grids as easting before northing, and its violation, reading the pair backward, is the most common coordinate error in both mathematics and GIS.
How do I convert polar coordinates to Cartesian?
Multiply: x = r times the cosine of the angle, y = r times the sine of the angle. Example: r = 10 at 60 degrees gives x = 5.00 and y = 8.66, because the cosine of 60 degrees is 0.5 and the sine is about 0.866. Check your answer by squaring: x squared plus y squared should equal r squared.
How do I convert Cartesian coordinates to polar?
The distance is r = the square root of x squared plus y squared. The angle is the arctangent of y over x, adjusted into the point's quadrant: for (minus 6, 8), r = 10 and the angle is 126.87 degrees, not the minus 53.13 the raw arctangent suggests. A calculator's atan2(y, x) function performs the adjustment automatically.
Are latitude and longitude Cartesian coordinates?
No. Latitude and longitude are angles on a sphere; Cartesian coordinates are distances on a flat plane. Map projections convert the angles into plane coordinates, eastings and northings, which then behave as x and y. Treating longitude as x directly distorts distances everywhere except near the equator.
How do I find the distance between two Cartesian points?
Subtract the x values for the horizontal gap, subtract the y values for the vertical gap, then take the square root of the sum of their squares. From (1, 1) to (4, 5): gaps of 3 and 4, distance the square root of 25, exactly 5. It is the Pythagorean theorem, and it only works this simply on a flat plane, which is what Cartesian coordinates guarantee.
Photo credits: cottonbro studio (Pexels); Monstera Production (Pexels). Photos are served from this site; follow the credit to the library page for the original.