Elevation, altitude, altitude measurement optimization… there are loads of questions of this type at our helpdesk. Altitude measuring, displaying and optimization, however, are described in our User guide in great detail but to apply those dry technical texts when tackling common daily Locus use is not always easy. That’s why we are releasing the following article trying to answer at least the most frequent questions you send to us.
Altitude or elevation?
People often mix these two terms so let’s make it clear – altitude concerns height of an object above the Earth surface (e.g. airplane), elevation concerns height of a place (a person, a vehicle…) on the Earth surface above the sea level. Locus can display both which is greatly favoured by many amateur pilots.
How does Locus measure altitude?
Primarily Locus gets the altitude values from your device (smartphone or tablet) GPS chip. It’s possible to calculate not only your horizontal position from the GPS signal but also the vertical one using larger number of satellites. Provided your device contains also barometer, Locus includes its sensor values to the altitude calculation. If you don’t have barometer or you are out of GPS signal (inside a building) Locus displays elevation values from so called HGT or SRTM files that it downloads from the Internet (when downloading LoMaps, creating routes or points). These files are freely accessible and they contain data collected by e.g. NASA. However, the are not very detailed so the values gained from them are just for basic orientation.
Why are the altitude values in paper maps or on tourist signposts different from the values measured by Locus?
Elevation of e.g. mountain peaks that we can see on a map or hiking signposts is acquired by professional measurement made by cartographic or geographic experts with proper equipment. Locus is provided only by values from sensors of personal devices that don’t have to be always as accurate. Furthermore, if we’re talking about SRTM files data.
Can Locus optimize the altitude values somehow?
Yes, in a few ways that can be set up in the Altitude manager (Settings > GPS & Location > Altitude correction):
- Optimization of GPS by elevation data – the values from the GPS chip show quite often quite big deviation, especially when the device lacks proper view of the sky. By checking this option you correct the deviation by downloaded SRTM data.
- Altitude filter – another option of the GPS deviation correction by its averaging. You can select from 5 degrees of filtration from the lightest and fastest to the heaviest requiring longer calculation time
- Altitude offset – altitude calculated by the GPS chip is acquired by a method of referencing the Earth surface that is different from what is used for masp referencing. Therefore certain offset is coming out of it and it’s needs correction. The most accurate is manual correction but you can use it only in case you know the precise value of the offset at the particular spot on the Earth. In our conditions of mobile devices the Automatic correction is very usable – it sets the offset according to the global model of geoid. Provided your device can correctly interpret NMEA messages with elevation parameters of the geoid, you can use th third method. We recommend it to the experienced users only who know what they are doing.
- Pressure – as we have already mentioned in the beginning many devices are equipped by the barometer. Such instrument measures pressure very precisely which can be used for calculation of relative changes of altitude. I.e. if you know the value of the atmospheric pressure at some altitude you can calculate changes in altitude between known and acual position. Firstly, such barometer must be calibrated, i.e. it must be given some default altitude or pressure value. Locus offers several methods: automatic using GPS values, manual inserting of pressure value at sea level and inserting particular altitude at a particular spot. Of course this is the most accurate method but relevant only locally.
Why doesn’t Locus display dynamic altitude above the cursor?
Values of the dynamic altitude are provided online by Google or offline from downloaded SRTM file of the given area. So either you aren’t online or you don’t have the particular SRTM file downloaded. How to get SRTM data can be found out in our User guide >>
I’ve imported some points from the Internet. Why doesn’t Locus display their altitude?
Obviously you haven’t downloaded the elevation data of the area where the points are located. Download them according to these instructions >>
I’ve downloaded some route to Locus from the Internet. Why doesn’t Locus render its elevation profile?
Because of the same reason as in the previous case – the route lies in an area without elevation data or altitude values weren’t included in the imported file. Download necessary elevation data as is stated here >>
I recorded track of my trip in Locus. I exported it to the web service Bikemap.net (GPSies.com, Cykloserver.cz etc.), but it shows different elevation gain than the original track – how’s it possible?
Web services usually read only trackpoint coordinates during GPX import and render them above their own 3D model of terrain. Then they calculate the resulting elevation profile from the model. However, each such model is generalized (simplified) reflection of reality and therefore the elevation gain calculated from it may differ a lot from the original.
Elevation gain values displayed during the track recording often seem unrealistic. After the record is finished and the track saved all is OK, why?
During the track recording Locus adds every centimeter of the elevation gain between individual trackpoints that may be placed just meters from each other and also raw altitude data from the GPS chip that may contain significant deviations. Due to saving the battery the data are optimized only after the record is finished and saved.
I’m not content with the values from the built-in GPS, what should I do?
Locus can communicate with external GPS devices via Bluetooth. Test it!
We’re sure you’ve got tons of other topics and questions in this area. Let us know at our helpdesk, we’ll do our best to answer them all.altitudealtitude offsetelevationpressure calibration
Quite a while ago, something changed and the elevation/distance graphs of my recorded tracks became much more jagged and erratic. Previously, these same routes had been fairly smooth and the total elevation gain/loss had been realistic. After the change, however, the gain numbers skyrocketed to 3x or more for a known route.
I won't rule out damage to my phone, but I wonder if there is some sensitivity setting within Locus that was changed. Which of the recording profile parameters would have the greatest influence on the elevation gain recording? Distance/time intervals or GPS accuracy?
I've always enjoyed looking at elevation gain numbers after my bike rides, but they've become obviously flawed. If you can help me figure this out, I'd really appreciate it. Thank You!
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
Actually, not everything I ever wanted to know. Elevation markings on the map: are they in metres? I can't find the units specified anywhere.
Hi, if the elevation markings are part of the map, e.g. accompanying the contour lines, they are in meters.