Suggestions here still holds:
http://www.usglobalsat.com/forum/index.php?topic=4136.msg12095#msg12095Some clarifications:
Layout: The nice display is not used in a good way.
Make numbers bigger is most important - I have problem seeing the numbers.
It seems like I run a lot in dusk and rain (still loving it.)
Will not comment on the individual suggestions previously, several combined:
* Remove black borders above/below in Chrono mode. Time/charge could be visible in Time-of-day. Custom 1 or so I do not need to see at all. GB-580 is better here.
* Normally use max 3 numbers for digits. Maybe pace should be 4. I could live with that also for pace, pace slower than 10 min/mile is unreliable anyway (I use km, even better). Seeing 11:30 or 11,5 /km is not a problem.
* Much small/abbreviate content label - I know what I have added anyway.
* Much smaller units, I know what they are (only reason to see them at all is that I may want to be sure that I have set min/km and not min/mile).
Improve distance calculation.
Pauses: The Globalsat protocol has no notion of pauses. It is therefore impossible to merge with other data if you have paused, intentionally, auto-pause or bumped the buttons.
Suggestion: Use the PwrCadence field to include the total time in seconds between two points.
I would rather use a special point with illegal GPS, but existing applications may not handle this.
Always add points at pauses. Will improve pause handling, as well as the annoying bug with no point added at end but at reset connecting to PC.
Some shortcut to GPS Info etc as suggested in thread started by AndersBrontosaurus
Accuracy data field
Hybrid Recording (start without GPS) as in the gb580
---
Regarding lap at point: I advise against that. Just the discussion here shows that this is more difficult than you may expect.
I have tried to use the functionality in another device but have given up: GPS is not precise enough for a track and it is to cumbersome to set up for trails.
I instead got involved with a SportTracks plugin to analyze trails based on GPS positions: Trails. (I do not want to think of all hours I have spent on the detection algorithm.)