This commit is contained in:
Philip Sargent 2024-05-18 23:15:11 +03:00
parent c509e61225
commit 6e30dc9a36
2 changed files with 6 additions and 6 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 161 KiB

View File

@ -14,13 +14,13 @@
<p>Phones assume that you are walking along streets, or running along tracks or cycling. They are very bad at making the right guesses for the Totes Gebirge plateau.
<h3>Location, location, location</h3>
<figure class=onright>
<a href='/handbook/computing/gps-location.png'><img class="onright" alt="GPS position controls" width=60% src='/handbook/computing/gps-location.png' /></a>
<figcaption>
A rack bar showing wear from only two or three expos
</figcaption>
<figure class=onright width=500>
<a href='/handbook/computing/gps-location.png'><img class="onright" alt="GPS position controls" width=40% src='/handbook/computing/gps-location.png' /></a>
<br> <figcaption style="text-align: center"> Android GPS setting </figcaption>
</figure>
<p>Do <em>not</em> select the "high accuracy" location setting on your phone. Mostly this will snap your position to the nearest cafe or bierstube: by default it will use the nearest WiFi it can find and assume that you are there, and will ignore the perfectly good GPS position it has recorded directly.
<p>Do <em>not</em> select the "high accuracy" location setting on your phone. Mostly this will snap your position to the nearest cafe or bierstube: by default it will use the nearest WiFi it can find and assume that you are there, and will ignore the perfectly reasonable GPS position it has recorded directly.
<p>This is all explained by Google <a href="https://support.google.com/maps/answer/2839911?hl=en&co=GENIE.Platform=Android">here</a>.
<p>On the plateau, this "high accuracy" mode will simply give you the <em>wrong</em> position if it can't get a decent GPS fix. There is poor cell tower reception too, so trying to use that for location is just as bad.