Hi,
I am using NST on my E71 for months and enjoy it very much. I recently updated to 2.06.
It is an helpful toy for sport tracking. I am also using it during my photo trips with my DSLR. I synchronize the exported GPX with my pictures with geosetter.
However, IMHO, there is a conceptual problem with the data saved: AFAIK, NST does not save the absolute date time but relative timestamps from the beginning.
For a better understanding, this 2 following steps below are extracted from a gpx file exported from NST. Please note the jump in the coordinate and the almost continuing time. The time information is unfortunately not the real time. This occurs particularly when you use "pause" or "auto pause", and was the main reason I disabled "auto pause" for all profiles in v1.x. This was a good work around. Unfortunately, it seems to me that does not work in the same way with v2.x.
454.0
1.4
330.6
Speed 1.4 km/h Distance 0.03 km
2009-07-19T12:41:37.16
32
443.5
0.5
22.2
Speed 0.5 km/h Distance 0.03 km
2009-07-19T12:41:38.00
33
(Edit: why are the tags removed in the forum, is there a way to display the real text, I tried [quote] and html comments, but nothing helped)
So first, did somebody around there experiment the same "problem" in gpx export?
Second, will it be possible to change the behavior and always save the real absolute date in the tracking, ideally the real GPS date (UTC) and not the time set in the phone (time zone dependent). IMHO, doing so would enhance the tracking accuracy and avoid many side effects users are experimented in this forum.
The "pause" concept should be implemented in an other way. An idea could be to mark the last step before "pause" and the first after "pause" with a special attribute. This attribute will be considerated by the software algo to plot the graphs: it could remove the time difference to the steps after pause. The data are saved in the .dat file. I do not know the structure of your dat file, but you could also save 2 differents dates: the real date on one hand, and the relative timestamp on the other hand. Only this timestamp would be considerated for the graph, and only the real timestamp for the gpx export.
Any suggestion will be welcomed, and a feed back from developer team even more!
By the way, if the NFS team or company is too small, why not ask the community support by revealing some part of the code? I do not mean a complete open-source project as one can found on http://opensource.nokia.com, but more on what even Microsoft is starting to do in its developer framework [more precisely, the .NET Framework intern code visible to developers in debug mode in Visual Studio].
In the NST community, there are surely many competent developers would could help the team for reviewing the code...
Anyway, what I ask is a proper GPX export. It should not be that complicated!