Messages

i'm looking forward to the next version.

Ahhh, i'm not in time and not up to date :-(
Sorry for that.
I tried new Altitude Manager only the settings. No recordings has been done so far...

And you are right, i started comparison with Garmin stuff .-)
Its difficult to have different track recordings from one unique route / way. I will try to find some.

Hi guys,
sorry for any delay. I was offline and mountainbiking for 2 weeks :-)

I would like to separate the problem:

1: get correct(ed) elevation data during recording
2: computation of uphill / downhill / flat section of a recorded / downloaded track and got elevation values from STRM files

for 1 i have no idea.
for 2 i think its the best to use a simple methode like this:
ele point A + ele point B - ele point C(if C is smaller than B)

I guess with SRTM files we have all we need....
@menion: is it too simple?


I would like to avoid using philosophy of other devices in Locus.
Christian

Hmm are you sure? I think this "map_items_track_highlight_enabled" parameter in configuration file should work ...

Wich file?

You want that locus automatically generate some random colors for tracks?

Yes . When an additional track is on Display...

Hi Menion,
Thanx for your answer. Sorry, this was my fault. I thought the computation problem ist already solved together with the Altitude Manager (nice piece!!!)

I'm not a mathematician but if i have values from the SRTM files and the track-  what's the problem with the computation of uphill, downhill and flat ? Am i wrong?

This become an idea. Fine. (I could not vote because i have no 'Spyware' account. But the idea its not built in yet.

Another idea / intent: different colors for different tracks in one display. I know a lot of GPX editors they change the colors of any additionally opened track. So Locus should do this also...
Hope for a fast solution.

(Can anybody put this into satisfaction ? Thanx!)

Anybody out there?

you are funny, man :-)

But... the reason why we - especially you - started the thread still exists: values of 0 for the flat. Means only values for uphill and downhill and these are wrong :-(
Any suggestions?

I 'm surpriced of the new altitude manager. great work!
So i checked most of my tracks to re-calculate the altitudes. But i'm not sure... after re-calculation all the values are 0 (NULL).
:-(
Is this a bug or a feature?
All settings in altitude manager are on default.
Christian

once again: don't hurry. better to do it in a relaxed manner...

Great! But don't hurry...

We should wait for Galileo system  

No, i'm wrong. All tracks updated with SRTM files has distances in flat area = 0 m.

So i guess its easy to calibrate the algorithm within Locus with support of SRTM values...

After track recording you now can write height data from SRTM in Locus! Open Track information window, click on down-right button with two cogwheels and choose "Set height".
I agree to use combination of GPS and SRTM but also don't forget about most precise method - pressure sensor. On that devices that can use it (Sony for example).

Ahhh, thanx for the information. I tried this some times before but the values are not changing until the window with track details is closed and re-opened...
So i checked my favourite track with the values from SRTM files and the ascendency are quite right. That means ...Locus is computing the uphill and downhill and flat area in the right way but with wrong data. I'm right?

@tommi: "average" is always ...un-exactly.

edith says: using my old but reliable HD2 sensor data are not available. So i would prefer a final solution without pressure sensor data.

Hi guys,
i'm the one who started the discussion via email with Menion. Thanx to Menion for the support (even during weekend) and the thread here. Sorry for the delay. I was biking the last days in the spring.
I'm not the specialist in programming or GPS related stuff. I'm just a user who want to use the nice app for mountainbiking (planning tours in / over) alps.
So i understand that :
: GPS ist not precise in recording heights,
: Filters can work, mostly not
: pressure sensor as well,
: different devices from different manufacturer computing ascendency in different ways.

For me a "fix point" in this universe could be solution. Means calibrated values from satellites in SRTM Files.
If i record a track in traditional way - like possible in Locus just now - i will get values with "noises", means wrong data due to influences from the environment during recording. This is what we have now. In some cases the accumulated values of ascendency differ up to 30% from other recordings. (Not unimportant when you are in the alps! Thats why i started the discussion)
May be there is a solution if i had the possibility to compare the recorded values with values of SRTM files. Better Locus should compare this for me.

possibility 1:
point A: recorded height in traditional way: 5m
point B: recorded height in traditional way: 25m
point C: recorded height in traditional way: 7m

point A: height value from SRTM file: 5m
point B: height value from SRTM file: 8m
point C: height value from SRTM file: 6m

Locus can straighten the values.


possibility 2:
give users a choice to use values from SRTM files for their recordings (before or after record) or use the values from their device.


English is not my native language. So if there are any blurs don't hesitate to ask :-)

Christian