User Tools

Site Tools


manual:faq:wrong_gps_data

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
manual:faq:wrong_gps_data [2023/10/11 16:23] mstupkamanual:faq:wrong_gps_data [2025/08/18 11:01] (current) – [Custom altitude threshold] mstupka
Line 1: Line 1:
-====== Inaccurate or wrong GPS location and elevation ======+====== None, inaccurate or wrong GPS location and elevation ======
  
 ---- ----
Line 8: Line 8:
 </WRAP> </WRAP>
  
-Locus Map processes location and elevation gain from the data it receives from **your phone GPS** and other location/orientation sensors. If the data is incorrect or contains deviations, the resulting location fix and elevation gain are incorrect. Locus Map, however, offers a few methods on how to limit these deviations.+Locus Map processes location and elevation gain from the data it receives from **your phone GPS** and other location/orientation sensors. If the data is incorrect or contains deviations, the resulting location fix and elevation gain are incorrect. Locus Map, however, offers a few methods for limiting these deviations. 
 +===== No location at all ===== 
 +There are a few reasons why the app might not show your location on the map: 
 +==== Access to GNSS data is turned off in Locus Map ==== 
 +  * the GPS indicator is white:\\ {{ :manual:faq:badgps01.jpg?nolink |}} 
 +  * tap it and then tap either the skyplot or the button to **turn on getting location**:\\ {{ :manual:faq:badgps02.jpg?nolink |}} 
 + 
 +==== The phone's GNSS is turned off ==== 
 +  * the GPS indicator is orange, there is a badge on the centering button and a warning emerges:\\ {{ :manual:faq:badgps03.jpg?nolink |}} 
 +  * **turn on your phone's GNSS**:\\ {{ :manual:faq:badgps06.jpg?nolink |}} 
 + 
 +==== No location permission for Locus Map ==== 
 +  * the GPS indicator is white and tapping the centering button or the GPS skyplot displays a warning:\\ {{ :manual:faq:badgps04.jpg?nolink |}} 
 +  * in system settings, allow Locus Map access to precise location **all the time**:\\ {{ :manual:faq:badgps05.jpg?nolink |}} 
 ===== Light deviations ===== ===== Light deviations =====
  
Line 18: Line 32:
   * Altitude manager > settings tab > Pressure sensor > **turn ON** (if available)   * Altitude manager > settings tab > Pressure sensor > **turn ON** (if available)
   * Altitude manager > settings tab > Altitude filter - select **medium or heavier filter**   * Altitude manager > settings tab > Altitude filter - select **medium or heavier filter**
 +
 ===== Stronger deviations ===== ===== Stronger deviations =====
 Sometimes it happens that the GPS chip is malfunctioning or terrain/weather conditions are so demanding that elevation data is incorrect even after applying the measures mentioned above. Then try the following: Sometimes it happens that the GPS chip is malfunctioning or terrain/weather conditions are so demanding that elevation data is incorrect even after applying the measures mentioned above. Then try the following:
-   * **Open Locus Map settings > GPS&sensors > Altitude manager > settings tab > SRTM data - select **Replace GPS values** - this option calculates elevation gain from **offline elevation data** without using GPS +   * Open Locus Map settings > GPS&sensors > Altitude manager > settings tab > SRTM data - select **Replace GPS values** - this option calculates elevation gain from **offline elevation data** without using GPS 
-===== Custom altitude threshold =====+ 
 +==== Custom altitude threshold ====
 Those who are still unsatisfied with the result can change the elevation gain calculation by applying a custom altitude threshold: Those who are still unsatisfied with the result can change the elevation gain calculation by applying a custom altitude threshold:
   * open **[[manual:advanced:customization:config#expert_settings|Expert settings]]** > Customize altitude threshold > enable it   * open **[[manual:advanced:customization:config#expert_settings|Expert settings]]** > Customize altitude threshold > enable it
-  * open a track or route detail > select **Edit* from the bottom menu+  * open a track or route detail > select **Edit** from the bottom menu
   * change altitude threshold with the slider\\ {{ :manual:faq:threshold.jpg?nolink |}}   * change altitude threshold with the slider\\ {{ :manual:faq:threshold.jpg?nolink |}}
 +
 +<WRAP center round info>
 +By default, the altitude threshold in the app is not fixed. It is based on the source of the elevation. App decides by following the check (in this order):
 +  * if you use a pressure sensor, the app sets the threshold to "2"
 +  * if you use elevation data (enabled in "[[..:user_guide:tools:altitude|Altitude manager]]"), the threshold is set to "3"
 +  * if you have Android 12+, the threshold is set to "5"
 +  * otherwise it is set to "10"
 +  * generally, the default value is "5". It should be set to all imported tracks or to old tracks recorded before this parameter was introduced
 +</WRAP>
 +
manual/faq/wrong_gps_data.1697034193.txt.gz · Last modified: by mstupka