Altitude indicator not showing

Hello Ben

since last update V 3.21.1 "Fill elevation" funktion completely moved to Locus Map Pro only"

take a look at:

menu/About application/About applicatio/Release Notes

Wolfgang

Thanks for that, but unfortunately that's not correct.

The last screen shot was provided by Locus Maps themselves via Facebook chat. They were on the free version and on 3.21.1

Fill elevation is where you want the app to provide the elevation.

Not sure if related... Did the "Dynamic Elevation" setting turn itself off in Pro during the last release? Yesterday I noticed it was gone, but didn't bother looking for the setting. This post reminded me; I found it to be off but I don't remember turning it off.

This is with Pro, though I've been using Free (beta) intermittently. Maybe that's why.

Good day Ben,

elevation value in this popup window is visible with two conditions:

1. you have enabled this option in Settings > Maps > points & tracks > Points popup content > elevation value, this is anyway enabled by default, so it is enabled in Free version

2. point you try to display has defined elevation

Do you see in detail of point elevation value (like on image below)?

And what balloni wrote is correct. There seems to be small issue in latest version when elevation values are filled for new points from SRTM files, this will be "fixed" in next version as well. So in the end, SRTM files won't work at all in next Locus Map Free, which also means, that new created points won't have automatically filled elevation values like now.

Menion

I have reset the preferences in the app, so everything is default, so it should show the marker.

I do not see an altitude option on the pin, nor in the details section

I loaded the points via KMZ file, and the KMZ file has the altitudes as part of it, which is confirmed in my last screen shot, which is from Locus support, using the free version 3.21.1

I know the SRTM is being removed as an option from the free version, but if the KMZ/KML etc contain the altitude, then it should show, as confirmed above

Hello Ben,

I'm little bit confused now, sorry.

> I loaded the points via KMZ file, and the KMZ file has the altitudes as

part of it, which is confirmed in my last screen shot, which is from

Locus support, using the free version 3.21.1

Fine, I see, so elevation values are visible in case, point has elevation value defined.

Then what exactly is the problem? Fact that you do not see elevation on first screenshot? From where is this point? If you edit this point, is elevation value defined? If this comes from any KML/KMZ file, please share this file so I may verify this problem in Locus/file.

All of the screen shots, apart from the last are of my app.

As you can see on the pin popup, or in the details section, the altitude part doesn't show

The last screen shot is from Locus Maps support via facebook (off their app), as you can see, it does show as 0. They're using 3.21.1 Free

This webpage won't allow me to add a KMZ file. I'll rename it to TXT, you'll need to rename it back

Also, to get to this screen " Settings > Maps > points & tracks > Points popup content " you need Pro

If you are using pro, the elevation will show fine

This query is for the free version only

Good day Ben,

thanks for a file.

As I see in it's content:

1. Line 73: <coordinates>-4.817934,56.2655328</coordinates>
2. Line 94: <coordinates>-5.384581,56.976925</coordinates>
3. Line 115: <coordinates>-4.346507,58.4268887</coordinates>
4. Line 136: <coordinates>-3.911569,56.839873</coordinates>
5. Line 157: <coordinates>-6.085086,55.785439</coordinates>
6. Line 178: <coordinates>-3.711638,52.926199</coordinates>
7. Line 199: <coordinates>-5.29884,57.434317</coordinates>
8. Line 220: <coordinates>-4.459073,56.779015</coordinates>
9. Line 241: <coordinates>-4.671936,57.088227</coordinates>
10. Line 262: <coordinates>-3.553528,55.346553</coordinates>
11. Line 283: <coordinates>-3.621375,55.284074</coordinates>
12. Line 304: <coordinates>-5.17501,56.484526</coordinates>
13. Line 325: <coordinates>-4.2108268,52.9860929</coordinates>
14. Line 346: <coordinates>-3.352843,56.943635</coordinates>
15. Line 367: <coordinates>-6.1099005,57.1898437</coordinates>
16. Line 388: <coordinates>-5.310819,56.144795</coordinates>
17. ....

all coordinates contains only two numbers (latitude & longitude) no elevation (that should be as third number). Which is the reason, why Locus Map do not display any elevation values from points from this file.

Now that is odd, as on another device, and on the Locus Maps facebook support app, the altitudes showed, using the KML as the import file

I uploaded the original KMZ file to http://www.gpsvisualizer.com/map_input?form=googleearth and then set the way point altitude mode to "Absolute , floating"

KMZ1.1 is the result of doing this, and it shows the elevation fine on the other devices, but not on my device

Here is the chat from Locus Facebook support

• 11/01/2017 10:44
  
  Locus MapI understand. It's weird - even the new file displays correctly in my device. KML-included elevation should display
  
• ">11/01/2017 10:48
  
  Ben Mortonshould or will? :)
  is yours pro or standard?
  
• 11/01/2017 10:49
  
  Locus Mapwell, noone can be sure in anything these days :)
  I'm testing on Free
  
• ">11/01/2017 10:49
  
  Ben Mortongreat
  

In current public version 3.21.1 is small remaining issue when Locus Map used offline elevation data and filled elevations for imported points. This is anyway part of change and will be removed as well in next version.

Probably because of this, my colleague on Facebook saw elevation value. Because Locus Map used previously downloaded elevation files and filled elevations to points from your file.

Ok, does that mean the next update should show imported elevation data on the free app?

Locus Map should imported elevations data even now! But file you have send me, does not contains any elevation data!

Ok, I thought using http://www.gpsvisualizer.com/map_input?form=googleearth had added them.

Do you know a way of adding them?

With mentioned tool, it seems to be able to achieve what you need.

I've selected your file and also selected "Add DEM elevation data" : "best possible source"

Result is file with elevation values as may be seen in it's content ... coordinates contains three numbers (latitude,longitude,elevation).

1. Line 73: <coordinates>-4.817934,56.2655328,255.605</coordinates>
2. Line 94: <coordinates>-5.384581,56.976925,103.086</coordinates>
3. Line 115: <coordinates>-4.346507,58.4268887,148.803</coordinates>
4. Line 136: <coordinates>-3.911569,56.839873,457.598</coordinates>
5. Line 157: <coordinates>-6.085086,55.785439,2.638</coordinates>
6. Line 178: <coordinates>-3.711638,52.926199,407.653</coordinates>
7. Line 199: <coordinates>-5.29884,57.434317,283.624</coordinates>
8. Line 220: <coordinates>-4.459073,56.779015,363</coordinates>
9. Line 241: <coordinates>-4.671936,57.088227,343.97</coordinates>
10. ...

Ah thank you! I didn't realise I'd selected the wrong option.

I'll reimport the new files into my app. Am I right in thinking I can then copy waypoints.db from my device to another device to populate the waypoints on there? Do I need the journal file too?

I've raised another question around getting pictures into the app. I'd love you to take a look

Perfect, you are welcome. I'm sure you will succeed.

*.journal file is just helping temporary file for database, it is not necessary to do anything with it, so leave it where is. Just suggest to copy both databases, waypoints.db and tracks.db between devices. They both are connected and needs to be shared together.

I've noticed your another question. I'll look at it.

You are welcome!

Does the track file need to be copied as well? As each device will have their own tracks

Waypoints of tracks are stored in waypoints.db, so to keep databases valid and without errors, they needs to be kept together. If you do not have any attached waypoints to tracks, then you may risk it, but I really can't recommend these steps.

I'll move both for now, thanks again