This object is in archive!
Elevation profile completely wrong
Not a Problem
In the beginning the elevation profiles were ok, but starting from few days ago they are completely wrong. They elevation remains constant, then suddenly makes a Jump, then goes negative
The same problem 
Version Is 3.50.1
Attached a sample picture with its gpx track
Version Is 3.50.1
Attached a sample picture with its gpx track
Hello,
Locus Map processes elevation gain from the data it receives from your phone GPS.
If the data are incorrect or contain huge deviations, then the resulting elevation gain is also incorrect.
Locus Map, however, offers a few methods on how to limit these deviations. Open Locus settings > GPS&sensors:
- Location filter > select medium or heavier filter
- Google Services assisted location > turn it ON
- Altitude manager > settings tab > SRTM data - select "Optimize GPS values" or "Replace GPS values"
- Altitude manager > settings tab > Pressure sensor > turn ON (if available)
- Altitude manager > settings tab > Altitude filter - select medium or heavier filter
Have a nice day
Andrea
Hello,
Locus Map processes elevation gain from the data it receives from your phone GPS.
If the data are incorrect or contain huge deviations, then the resulting elevation gain is also incorrect.
Locus Map, however, offers a few methods on how to limit these deviations. Open Locus settings > GPS&sensors:
- Location filter > select medium or heavier filter
- Google Services assisted location > turn it ON
- Altitude manager > settings tab > SRTM data - select "Optimize GPS values" or "Replace GPS values"
- Altitude manager > settings tab > Pressure sensor > turn ON (if available)
- Altitude manager > settings tab > Altitude filter - select medium or heavier filter
Have a nice day
Andrea
Hi Andrea,
last weekend I’ve upgraded my smartphone with Android 11 and the problem is solved.
Thanks for your help.
Pier Luigi
Da: Locus Map <locus.map@asamm.com>
Inviato: lunedì 15 febbraio 2021 19:05
A: Pier Luigi <pierluigi.medolago@alice.it>
Oggetto: New Comment in "Elevation profile completely wrong"
Hi Andrea,
last weekend I’ve upgraded my smartphone with Android 11 and the problem is solved.
Thanks for your help.
Pier Luigi
Da: Locus Map <locus.map@asamm.com>
Inviato: lunedì 15 febbraio 2021 19:05
A: Pier Luigi <pierluigi.medolago@alice.it>
Oggetto: New Comment in "Elevation profile completely wrong"
Similar problem here. A couple weeks ago, a typical nordic ski at my local area showed an elevation chart between 925 and 1075m, which seems about what the map says. The last two skis last week and today, it's shown an elevation chart between 197 and 205m, which is way lower and less variable than it should be. I don't think I had the pressure sensor turned on. If I try to set it, then close and re-open the settings, it's unset again. Also running 3.50.1.
Similar problem here. A couple weeks ago, a typical nordic ski at my local area showed an elevation chart between 925 and 1075m, which seems about what the map says. The last two skis last week and today, it's shown an elevation chart between 197 and 205m, which is way lower and less variable than it should be. I don't think I had the pressure sensor turned on. If I try to set it, then close and re-open the settings, it's unset again. Also running 3.50.1.
Hi Andrea,
unfortunately, contrary to the one previously communicated, even with android 11 and yours suggestions for the setup, the problem is still present
I don’t have a pressure sensor.
by
Pier Luigi
Da: Locus Map <locus.map@asamm.com>
Inviato: sabato 27 febbraio 2021 03:50
A: Pier Luigi <pierluigi.medolago@alice.it>
Oggetto: New Comment in "Elevation profile completely wrong"
Hi Andrea,
unfortunately, contrary to the one previously communicated, even with android 11 and yours suggestions for the setup, the problem is still present
I don’t have a pressure sensor.
by
Pier Luigi
Da: Locus Map <locus.map@asamm.com>
Inviato: sabato 27 febbraio 2021 03:50
A: Pier Luigi <pierluigi.medolago@alice.it>
Oggetto: New Comment in "Elevation profile completely wrong"
Hello Pier,
Have you tried all the recommended settings (see below), including deactivating the pressure sensor?
Thank you
Have a nice day
Andrea
Hello Pier,
Have you tried all the recommended settings (see below), including deactivating the pressure sensor?
Thank you
Have a nice day
Andrea
Ho lo stesso problema da diverse settimane ho provato i rimedi suggeriti ma niente. Ho registrato contemporaneamente un percorso con Strava, ottenendo ottimi risultati, non con locus. Posso inviare le trance.
Ho lo stesso problema da diverse settimane ho provato i rimedi suggeriti ma niente. Ho registrato contemporaneamente un percorso con Strava, ottenendo ottimi risultati, non con locus. Posso inviare le trance.
Hi all,
we've been tackling this issue for some time. Unfortunately, it occurs only on some device-OS configurations so it is complicated to simulate it and find out its cause. Please be patient, we're working on it. Thank you for understanding.
Hi all,
we've been tackling this issue for some time. Unfortunately, it occurs only on some device-OS configurations so it is complicated to simulate it and find out its cause. Please be patient, we're working on it. Thank you for understanding.
Same issue with the elevation snafu. I just switched from a Pixel 2 to Galaxy S20FE running Android 11 OS. The GPS "geographical direction" track recording is accurate, it's just the elevation changes that don't make any sense. See attachments. No problems with my Pixel 2 prior to this.
lebo
Same issue with the elevation snafu. I just switched from a Pixel 2 to Galaxy S20FE running Android 11 OS. The GPS "geographical direction" track recording is accurate, it's just the elevation changes that don't make any sense. See attachments. No problems with my Pixel 2 prior to this.
lebo
My phone did do an OS upgrade, which also meant it turned itself off and on again. I tracked a bike ride in town, and the elevation profile was only partially wrong some of the time. Aren't intermittent bugs the funnest to track down? If it's useful, attached the altitude as measured by Locus (and then imported into strava; makes it a similar shape) compared to an elevation profile as determined by mapometer.ca for the ride:
My phone did do an OS upgrade, which also meant it turned itself off and on again. I tracked a bike ride in town, and the elevation profile was only partially wrong some of the time. Aren't intermittent bugs the funnest to track down? If it's useful, attached the altitude as measured by Locus (and then imported into strava; makes it a similar shape) compared to an elevation profile as determined by mapometer.ca for the ride:
Hi all,
before we solve this issue, please change your app settings this way:
- open Locus settings > GPS&sensors > Altitude manager
- on the "settings" tab > SRTM data > select "Replace GPS values"
Hi all,
before we solve this issue, please change your app settings this way:
- open Locus settings > GPS&sensors > Altitude manager
- on the "settings" tab > SRTM data > select "Replace GPS values"
I've been having similar problems for the past few weeks. My wife and I record tracks while out snowmobiling and found the horizontal is correct but the elevation doesn't change, at least not more than a foot, where we go a few thousand feet for the track. When I run GPS Status app it provides the correct elevation, where locus maintains the starting elevation. Here's a screenshot of Locus recording a few miles into the track and GPS Status mini window with its information. Locus report 6832ft where GPS Status reports 8413.2ft. Another screenshot of the elevation profile from the finished track. We're seeing the issue on Pixel 5 and Pixel 3.
I've been having similar problems for the past few weeks. My wife and I record tracks while out snowmobiling and found the horizontal is correct but the elevation doesn't change, at least not more than a foot, where we go a few thousand feet for the track. When I run GPS Status app it provides the correct elevation, where locus maintains the starting elevation. Here's a screenshot of Locus recording a few miles into the track and GPS Status mini window with its information. Locus report 6832ft where GPS Status reports 8413.2ft. Another screenshot of the elevation profile from the finished track. We're seeing the issue on Pixel 5 and Pixel 3.
Hello,
We apologize for the inconvenience, we know about the bug, and we're working to fix it.
In the meantime, try the procedure described below.
Thank you for understanding
Have a nice day
Andrea
Hello,
We apologize for the inconvenience, we know about the bug, and we're working to fix it.
In the meantime, try the procedure described below.
Thank you for understanding
Have a nice day
Andrea
Hi everyone,
we've detected the origin of the error, here's the workaround for the time being:
Go to Locus settings > GPS&sensors > Google Services assisted location - switch this OFF. Something has changed in this service and Locus returns the wrong altitude when using it. We're digging more!
Hi everyone,
we've detected the origin of the error, here's the workaround for the time being:
Go to Locus settings > GPS&sensors > Google Services assisted location - switch this OFF. Something has changed in this service and Locus returns the wrong altitude when using it. We're digging more!
Yes. Now altitude seems working
Thanks a lot
Yes. Now altitude seems working
Thanks a lot
Hello ,
Thanks for the news.
Have a nice day
Andrea
Hello ,
Thanks for the news.
Have a nice day
Andrea
Thanks for the update, I've made no adjustment to my settings, including having Google Service assistance enabled, and my recent trip showed no problems for elevation recording, screenshot/track attached. I did recently have an OS update that could have helped resolve the issue. Thank you for your efforts in addressing these issues, I love the app and have been using it since 2012. Keep up the good work!
Thanks for the update, I've made no adjustment to my settings, including having Google Service assistance enabled, and my recent trip showed no problems for elevation recording, screenshot/track attached. I did recently have an OS update that could have helped resolve the issue. Thank you for your efforts in addressing these issues, I love the app and have been using it since 2012. Keep up the good work!
Replies have been locked on this page!