<p><strong>It's almost certainly a difference in the UTM zones.</strong></p>

<p>In most zones, the <a href="https://www.maptools.com/tutorials/utm/details" rel="nofollow noreferrer">minimum easting value</a> is 160,000 mE and the max is 834,000 mE (at the equator). People sometimes use the 'wrong' zone (i.e. not the zone that the location is actually in) if it's more convenient to use a neighbouring zone for some reason. For instance, maybe I have coordinates for 100 points but a few are in a neighbouring zone; it's probably easier to tolerate the location inaccuracy than to reference them to a different UTM zone.</p>

<p>The other thing that <em>can</em> create discrepancies is different datums (e.g. WGS84 in Google Earth, and some other probably local datum for your survey), but that's not what's going on here. </p>

<p><strong>To sum up, it looks like the coordinates you were given are referenced to Zone 19K, to the east of Zone 18K, so the easting is smaller than the usual minimum. The correctly referenced Zone 18K coordinate is the one in Google Earth.</strong></p>

<p>Last thing: I just want to connect with <a href="https://earthscience.stackexchange.com/questions/6676/what-is-the-maximum-value-of-easting-in-utm-coordinates/6677#6677">this related question.</a></p>

<hr>

<h3>EDIT: Conversion</h3>

<p>Converting to the correct coordinates is a little risky without knowing exactly how the original coordinates were arrived at. But if they were indeed simply given in UTM Zone 19, then <a href="http://www.ngs.noaa.gov/TOOLS/utm.shtml" rel="nofollow noreferrer">a round-trip conversion via lat-lon</a> shows that they are equivalent to 781493.139 mE, 8177491.483 mN in UTM Zone 18. </p>

<p>We can confirm this with <a href="https://pypi.python.org/pypi/pyproj?" rel="nofollow noreferrer">PyProj</a> using the zones' <a href="http://www.spatialreference.org/ref/epsg/wgs-84-utm-zone-18s/" rel="nofollow noreferrer">EPSG codes</a>:</p>

<pre><code>&gt;&gt;&gt; import pyproj
&gt;&gt;&gt; x, y = 140800, 8176337  # Zone 19S we think
&gt;&gt;&gt; utm18_wgs84 = pp.Proj(init='epsg:32718') 
&gt;&gt;&gt; utm19_wgs84 = pp.Proj(init='epsg:32719')
&gt;&gt;&gt; pyproj.transform(utm19_wgs84, utm18_wgs84, x, y)
(781493.1384182497, 8177491.482738381)
</code></pre>

<p>So, if that's what originally happened, these new coordinates are what you want.</p>

CC BY-SA 3.0
2015-11-02T22:04:06.483Z
Thank you very much for the fast response! One question: if they used the wrong Zone (19k) for the E coordinate, is there a way I can convert that coordinate back to the right Zone (18k)?
user4732
CC BY-SA 3.0
2015-11-02T22:50:57.770Z
You could use [this tool](http://www.ngs.noaa.gov/TOOLS/utm.shtml) to convert to lat-lon, then convert back to UTM in some other zone. Does that make sense? (Or, if you know Python, use the PyProj library to convert without going via some other system.)
Matt Hall
CC BY-SA 3.0
2015-11-03T00:32:58.933Z
I added the conversion. Caveat emptor!
Matt Hall
CC BY-SA 3.0
2015-11-02T14:19:56.667Z
2015-11-03T00:32:06.353Z
2017-04-13T12:50:30.540Z
Matt Hall
<p>For a piece of land in Peru (Zone 18K), I was provided the following UTM coordinates (showing just one): 140800 E 8176337 N. However, when I look up the site on Google Earth, while the N coordinate is identical, the E one is 779875.</p>

<p>Anybody know what the issue might be?</p>

<cartography><mapping><projection>
Inconsistency between topographic survey and Google Earth
user4732
# Inconsistency between topographic survey and Google Earth

(Asked by: username_0 on 2015-11-02)

For a piece of land in Peru (Zone 18K), I was provided the following UTM coordinates (showing just one): 140800 E 8176337 N. However, when I look up the site on Google Earth, while the N coordinate is identical, the E one is 779875.

Anybody know what the issue might be?

**Tags:** cartography, mapping, projection


---

## 1 answers

### Answer by username_1 on 2015-11-02. Score: 6

**It's almost certainly a difference in the UTM zones.**

In most zones, the [minimum easting value](https://www.maptools.com/tutorials/utm/details) is 160,000 mE and the max is 834,000 mE (at the equator). People sometimes use the 'wrong' zone (i.e. not the zone that the location is actually in) if it's more convenient to use a neighbouring zone for some reason. For instance, maybe I have coordinates for 100 points but a few are in a neighbouring zone; it's probably easier to tolerate the location inaccuracy than to reference them to a different UTM zone.

The other thing that *can* create discrepancies is different datums (e.g. WGS84 in Google Earth, and some other probably local datum for your survey), but that's not what's going on here.

**To sum up, it looks like the coordinates you were given are referenced to Zone 19K, to the east of Zone 18K, so the easting is smaller than the usual minimum. The correctly referenced Zone 18K coordinate is the one in Google Earth.**

Last thing: I just want to connect with [this related question.](https://earthscience.stackexchange.com/questions/6676/what-is-the-maximum-value-of-easting-in-utm-coordinates/6677#6677)

---

### EDIT: Conversion

Converting to the correct coordinates is a little risky without knowing exactly how the original coordinates were arrived at. But if they were indeed simply given in UTM Zone 19, then [a round-trip conversion via lat-lon](http://www.ngs.noaa.gov/TOOLS/utm.shtml) shows that they are equivalent to 781493.139 mE, 8177491.483 mN in UTM Zone 18.

We can confirm this with [PyProj](https://pypi.python.org/pypi/pyproj?) using the zones' [EPSG codes](http://www.spatialreference.org/ref/epsg/wgs-84-utm-zone-18s/):

```
>>> import pyproj
>>> x, y = 140800, 8176337  # Zone 19S we think
>>> utm18_wgs84 = pp.Proj(init='epsg:32718') 
>>> utm19_wgs84 = pp.Proj(init='epsg:32719')
>>> pyproj.transform(utm19_wgs84, utm18_wgs84, x, y)
(781493.1384182497, 8177491.482738381)

```

So, if that's what originally happened, these new coordinates are what you want.

> **Comments:**
> **username_0**: Thank you very much for the fast response! One question: if they used the wrong Zone (19k) for the E coordinate, is there a way I can convert that coordinate back to the right Zone (18k)?  
> **username_1**: You could use [this tool](http://www.ngs.noaa.gov/TOOLS/utm.shtml) to convert to lat-lon, then convert back to UTM in some other zone. Does that make sense? (Or, if you know Python, use the PyProj library to convert without going via some other system.)  
> **username_1**: I added the conversion. Caveat emptor!  

---

