expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-08 14:54:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Phone Camera GPS 60m wrong

Browse Source
This commit is contained in:
Philip Sargent
2025-04-14 14:25:18 +01:00
parent 52b3437619
commit 40f089e725
5 changed files with 61 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
years/2024/i/PXL_20240721_082604148.NIGHT.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 431 KiB

BIN
years/2024/images/bad-gps.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 19 KiB

30
years/2024/l/PXL_20240721_082604148.NIGHT.html Normal file
View File

@@ -0,0 +1,30 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf8" />
<title>
EXIF GPS errors on photos
</title>
<link rel="stylesheet" type="text/css" href="/css/main2.css" />
</head>
<body>
<H1>EXIF GPS errors on photos</H1>
<div class="centre"><img alt="Along the well-maintained path" src="/years/2024/i/PXL_20240721_082604148.NIGHT.jpg" />
</div>
<p>Along the well-maintained path along the foot of the Brauning Wall, just by a nice shady cliff at 47.68113100 N 13.80087050 E
But the GPS data stored in the EXIF on the JPG (below) is wrong: and has it about 60m north of this point.<br /><br />
Direction of view: NE (30&deg;Magnetic)<br />
<a href="https://www.openstreetmap.org/?mlat=47.68154722222222&mlon=13.800536111111112">47.681547 N, 013.800536 E</a><br />
1743m above sea-level</br />2024:07:21 08:26:03 +00:00 UTC<br />
2024:07:21 10:26:04 +02:00</p>
<p class="caption">Photo &copy; Philip Sargent, 2024</p>
<hr />
</body>
</html>

32
years/2024/logbook.html
View File

@@ -16,7 +16,7 @@ re-written. This is prevent spurious re-orderings and spurious git commit lines
Sorry about all the crap that surrounds the image tags which has been imported along with the content
when UK Caving blogs have been parsed.
Exported on 2025-04-14 13:04 using either the control panel webpage or when editing a logbook entry online
Exported on 2025-04-14 14:04 using either the control panel webpage or when editing a logbook entry online
See troggle/code/views/other.py and core.models/logbooks.py writelogbook(year, filename)
-->
<body>
@@ -1119,6 +1119,36 @@ Track online at <a href="/expofiles/gpslogs/2024/PhilipSargent/2024-07-21_geschw
<p>
ADDENDUM 26th July:
<br>Bing <a href="https://www.bing.com/maps/?cp=47.6652%7E13.763353&lvl=17.6&style=h">aerial photos show the forestry track</a> and much of the path from Geschwandalm, it shows that the track does not go to Bla Alm at all, but apparently ends only about 150m beyond where the path joins it.
<br>
<div class="timeug">T/U: 0.0 hours</div>
<div class="editentry"><br /><a href="/logbookedit/2024-07-21b">Edit this entry</a><br /></div>
<hr />
<div class="tripdate" id="2024-07-21d">2024-07-21</div>
<div class="trippeople"><u>Philip S.</u></div>
<div class="triptitle">Photo GPS is unreliable</div>
During this same trip walking to Geschandalm, later analysis of the GPS locations of various photos showed a lot of variability.
This is a particularly clear example where the location is obvious in the photo (it is definitely on the path)
but the GPS location stored by the phone camera is 60m away.
<p>
I had one phone (Xioami) continually tracking my location (using OSMand) which produced the GPX track,
and another (Pixel) used for photographs.
The GPS data in the photos is clearly completely wrong for some of the photos -
presumably because I hadn't left enough time for it to get a decent GPS fix before taking the photo.
This is particularly clear when there is a well-identified spot in the photo,
such as this one right by the shady cliff (photo EXIF GPS locations are orange dots):<br>
<a href="/years/2024/images/bad-gps.jpg">
<img width=20% src="/years/2024/images/bad-gps.jpg"></a>&nbsp;
<a href='/years/2024/l/PXL_20240721_082604148.NIGHT.html'><img src='/years/2024/t/PXL_20240721_082604148.NIGHT.jpg' /></a>&nbsp;
<p>
The lesson to take away from this is to always take TWO photos at any one position, and throw away the first one.
This will nearly always work for most people, and is sufficiently simple that even undergraduates can remember it.
ALternatively, always continually record a GPS track on the phone you are using to take photos with -
though this is unfortunately not always reliable either, as the camera app tends to cache locations and doesn't always
get a fresh one from the "location" module in the phone.
</p>
<br>
<div class="timeug">T/U: 0.0 hours</div>
<div class="editentry"><br /><a href="/logbookedit/2024-07-21b">Edit this entry</a><br /></div>
<hr />

BIN
years/2024/t/PXL_20240721_082604148.NIGHT.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB