I have another couple ideas for the GPSLogger:

1. If I have paused recording a path, is there a way that I can still mark a point on my current path while the recording is paused?

2. Is there a way I can merge 2 or more previously-recorded paths?


Also, I saw a discussion on the CrackBerry forums about the possibility of less battery drain if GPSLogger is set to sample less frequently (ex. set the sample frequency to 600 sec, which is 1 sample every 10 min). Has anyone tried this and confirmed that the battery power actually drains slower? Just curious.

Thanks again, Matthias, for all your hard work on this. It's a really fun app, and I use it all the time to make GPS track logs for fun.

thanks for all your support & suggestions... currently I am putting most of my energy into the other I am working on - but I hope there will be an updated GPSLogger soon...

Matthias

I found a work-around solution to this problem. Under Options, select "Confirm Exit of GPSLogger". This will prevent GPSLogger from unintentionally stop tracking when you press the Escape button. Instead, it will prompt you to confirm that you want to exit the application.

Apparently, the Escape button makes GPSLogger exit completely (ie. shuts down the app). That's why it stops tracking.

Just a quick tip.

update 0.4.15 is available:

What's new?

• Option to display Lon/Lat values as raw data

For OS4.6+ owners

• Virtual Compass (see attachments) - Thanks to to Rob Antonishen for the very nice compass svg file!

Get the latest version from GPSLogger Downloadpage - but please pick the "right" one for your BB OS Version!

Matthias

file share here guys.....
i need.
tannks a lot.
smart thinking for all

What in the hell is this?

I might be missing it but is there a way to rename the log files or give them a name when you start a new track?

Is there a way to assign a key to switch between tabs so that you don’t have to hit menu then the view you want. Like 0/space key cycles through the tabs?

It would also be great to be able to restart a stopped path.

And I really, really like the idea if being able to navigate to marked points from the current track, but mostly to points on tracks in the background, and to a location someone sends you or you send to them.

Thank you, and great app!

BBFileScout can do this job - but by default (and with GPSLogger only) the files get "autonames"...

not yet - but I admit it sounds quite logical to implement such a key shortcut...

mhhhhh - not 100% sure yet, IF this can be implemented... normally that's the purpose of the "Pause" function...

... if you are a OS4.6+ owner: have you seen the new compass view? -> there have to be function "guide me to..." in order to make use of this

Wirelessly posted

On my pearl I tried to rename via BBfilescout and when I go to manage my tracks the name change is not there. The track is still there with the old name, when I check it in filescout it has the new name still?

I don't have 4.6, so I can't see the compass. But if I did would it be able to track to a received GPS point or a point that I enter in or from the background?

sorry I forgot this already - in GPSLogger will display the recoded paths by it's meta data (and not the filename) - sorry for the false information

it's not there yet - it have to be implemented... and I think once that is done there will be a "simple" none SVG compass as well - we will see

Any new information on when an update that includes total elevation gained for each track will be available? Thanks for a great program.

T

in 0.4.15 you should be able to see "Details" in the Path loading Window...

I hadn't downloaded 0.4.15 yet, but now I have.

This is such a great app!!! I just started walking with my daughter during lunch and it has helped me keep track of improvments in speed and distance!! Thank you so much!!

I did a short hike today to try out the total altitude data on the details page. I went 2.7 miles and climbed a total of less than 100 feet. Yet, on the details page it showed that I had a total elevation gain of 1,355 feet and a total elevation lost of 1,317 feet. There is no way that these figures are correct. Everything else seems correct including total distance, total time, max speed, max elevation and minimum elevation. Any help on these elevation numbers would be appreciated. Thank-you.

T

I went skiing today. This app in the details page says 22k vertical and my watch said 14k. Based on the number of runs, my watch seems accurate.

mhhh - might be I am totally wrong with my calculations... but I thought the algorithm is not that complicated - allow me to explain, how these values will be generated:

Assuming we have 4 points recorded:
P1: alt 10m
P2: alt 20m
P3: alt 40m
P4: alt 30m

what the code does:
// init...
altGaind = 0
altLost = 0

//iterate though all points
P2-P1 = +10
altGaind = 10

P3-P2 = +20
altGaind = 30

P4-P3 = -10
altLost = 10

do you agree, that this approach is the right one? (comparing current Point with previous point - calculating the difference and ig it's positive, that we add this difference to the "altGaind" value, if it was negative we add the absolute value to altLost)...

so assuming we have recorded 1000 points like this
P0001: alt = 1m
P0002: alt = 2m
P0003: alt = 1m
P0004: alt = 2m
P0005: alt = 1m
...
P0999: alt = 1m
P1000: alt = 2m

what would be the altGaind value? -> 500 is that correct? (altLost = 499)...

I would just like to confirm, that I have understood your expectations concerning the altGain value calculation correctly.

Thanks for your feedback!

Your approach appears to be correct but there has to be something amiss to generate numbers that are so far from being actual. Thanks.

T

... might be helpfull if you can email me your gpl file (the contact email at the GPSLogger HP)...

but I assume, you are going 2km flat out - but each point you have recorded have a small altitude difference compared to the other... as it's said with the 1000 points recorded... the total alt gained is 500m (even if you had the feeling just to go straight ahead)

I emailed the file.

T

I think many culmulative altimeters filter out small changes so that in your example, the total might have been near zero rather than 500m. I think my bike computer/altimeter only records (adds) changes over 10 feet (3 meters, more or less).

I have not read the manual for my "watch altimeter" in a while but I think it may also do some filtering.

Your method might actually be more accurate in some circumstances and it certainly helps MAGNIFY all those tiny ups/downs. Depending on where folks carry the BB's, just each stride or up/down-turn on a ski slope could raise/lower the BB's location. Skiing for instance - dip body into turn, rise up after turn (loss then gain), now repeat over and over............

Interesting point. I do agree that the intervals would have to be similar to get the same readings. I don't know what my watch is. Sunnto Vector, and will have to go home and compare to what is set for this program. I can tell you in my early post it seems way to much though for a variance based on this alone.

Are you "lift assisted" or do you manually yo-yo those slopes?

what do you thing about the following algorithm:

collect all points that have been recorded in 1min and calculate the average altitude from that points - and the altitudeGained/lost will be calculated then on the "average altitude" values...

what do you think?

@at.rex - with the new algorithm you would had gained 552feet... (sounds that better to you)?

I would hope someone more knowledgeable in math/formulas/filtering than I jumps in - this probably can be quite complicated.

I am leaving momentarily on a 35 mile bike ride with approximately 1,700 feet of elevation gain (those hills do go down again). So I will see how the current version does against known facts and report back (HOURS and hours from now - I'm out of shape!!!)

you could email me the GPL file and then I can let it run though the new implementation...

Just received Stinsonddog GPL file - and with the new impl GPSLogger calculates 15882ft for this ski trip...

Hey, someone help me - where do you see the total elevation gain? Details page?

I have pages for path, elevation, speed on each I see the duration and the distance at the end of the data display.

I did email my bike trip.

That is still almost 500 feet too much.

If you have downloaded the latest version you will find details page under options when your track is highlighted.

Thanks. I was trying to find it when the path was active.

Hmmm, not a bad bike ride - 8,500 ft of gain over 33.8 miles - I'm ready for the Tour de France!!! (Actually, I feel like that's accurate unfortunately. Not that I'm ready but it felt like 8,500 feet)

It should be closer to 1,600 - a shade over...........

... I have difficulties to agree with you here (after i have seen the data) - I will send you some data detail this afternoon/evening when I am back home (when you agree, I would prefer top post it here in public to be able to discuss it with a larger audience) - there you can see the average data that was recorded during your trip - and form that data the 500ft are quite reasonable...

But I can understand, that it sounds indeed quite much when I look at the area where you made that trip (I am still jealous/envious)

I did a 30 mile bike ride that I broke into two tracks. I used my bike computer with altimeter and also a Garmin CS60 GPS unit. On the first part of the ride I went 12.5 miles and climbed a total of 711 feet according to the two units. GPSLogger recorded 1070 feet. On the second part of the ride I went 18 miles and climbed a total of 1106 feet according to the two units. GPSLogger recorded 1711 feet.

T

Looks like you had a better workout than I did.

T

It's difficult for me to express what I wanted to say - I don't doubt, that the results GPSLogger currently reports are not the values you expect...

Ride 1: 12.5 miles and climbed a total of 711 feet
Ride 2: 18 miles and climbed a total of 1106 feet

Is the first one you send me? [or are you now talking about different ride again?] I am sorry I am a bit confused

... What I wanted to say with my '500ft' post question was, that I have already locally adjusted the GPSLogger code - and with that adjustment the dialogue say: gained 552feet.

I agree, that 522ft does not equal 711ft... It's quite difficult to find a good/reasonable algorithm that reflects:

a) GPS data accuracy failures (deviation)
b) Logging interval

Concerning the 1000 point example I have given view posts above - with the Old Code we would had get 500m gained - with the new implementation we would had get more or less 0m gained... so IMHO it's getting closer...

So what I am asking you is for "good" additional ideas/algorithms that could by allied.

No, this was a bike ride that I haven't sent to you. The one I sent you was of a short hike. I just posted the bike ride results so you could see the difference between a dedicated GPS and GPSLogger. I wish I could help with your efforts but I don't understand why there is such a great difference between the readings. And, I want to thank you again for all your time and effort that you are putting into this problem.

T

Would it be possible for you to email me also that GPL file? [so then there is a good reference to other other devices where we "know" the alt gain values the dedicated devices have printed...] even if I hope, that you understand, that the algorithm I have used right now (and that is build in 0.4.15) is also "correct" - but (when you look at the 1000Point example) quite strange...

It's always difficult since as a human beeing you have a certain expectation [but when a computer just accumulate facts, that the picture could be totally different]...

would this work on black berry 8320? and do i need maps or does it included?
and do i have to enable to data? i turn data off so in case i don't have to use data to be charged.

Mathias:

I sent you an email (at least, I tried) yesterday with a gpl file with a 33 mile bike ride that showed approximately 8,500 feet of elevation gain. My bike computer/altimeter (Cateye older model but pretty accurate) showed about 1,600 feet.

You can try your new method on it and report back.

As I wrote above, I can see your method picking up minor undulations in the road (up a foot, down a foot, up a small two feet, down a foot, etc) which could really add up even when the terrain feels flat. And depending on where the BB is located (I had mine in a hip pouch), each time I stand on the pedals and lower myself, could be added to elevation gain and that is probably not reflective of reality.