The accuracy of the workout is visibly lost when exporting or uploading to the service. Most of the curves are "short-cut" and little details have disappeared. Why is that?
I found this problem with using the ST Website with LONG tracks (e.g. 1 hour or more):
1) Live track will show accuracy on the map, but the speed graph has the curves "short-cut" and I can't work out the speed at most points on the graph.
2) Non-Live track, that is uploaded later does not show accuracy on the map or the speed graph. The web shows that I drive through buildings and all sorts with a non-live track that is uploaded later! One of my tracks only showed *** 4 Points *** over a 10 km range. (it was a 19 hour track)
To get around this I find that I can save a file on the phone, and then import it to the computer (say with bluetooth) and I get all the fidelity of a non-live track back. But 'uploading' the track to the web looses most of the fidelity. The phone maps show all the detail, it is just the ST Website. Saving and transferring tracks is too time consuming so I am limiting the use of ST.
I love the app however.
The SportsTracker mobile app records tracks in rather fine detail. Waypoints are recorded at one (1) second intervals which can result in a large volume of data.
Workouts uploaded to the SportsTracker website are filtered, the results of which can seem "choppy". The reasons for the filter are for fewer spikes from waypoint errors and overall smaller NST databases.
If you export a workout directly from the mobile app in GPX, KML, etc., the result will be a file with complete waypoint data. Open the KML in GoogleEarth for an example.
****NOTE**** The KML file export option on the website will generate a summarized file with less detail than a KML file exported direct from your mobile. Export from the mobile app for accuracy of recorded track information.
-David
Current setup: e61 unbranded product code 0529654 Euro-B1 Silver. Firmware: 3.0633.09.04. Theme: Ovi blue. Service provider: 3 Sweden. Peripherals: Bluemax ext BT GPS module
I fully understand the view, that too much detail (1s resolution in time) and unfiltered data CAN result in spiky graphs, but the current level of filtering applied during workout upload is literally destroying the quality of the uploaded data, if it exceeds a duration of an hour or something like that. The raw files - exported from the mobile device - are good to very good in quality (at least for the accuracy of the geographical coordinates, not the altitude...), and the built in GPS filtering option is working well also, so for quality reasons, there is noo need for filtering during upload. For avoiding large volume of data on the NST servers, it is also a non-sense, because one long workout (5-6 hours) produces a .dat file of 210 kB on the phone. This is equal (er even less than) to one 3 megapixel photograph saved in medium quality on a compact camera! This is nothing! Why do Nokia have to make even smaller files - and meanwhile destroy the level of detail of the track which is later visible for the community on the NST website? Only a few points/km?! This must be a joke!!! Sorry, but this destroys a project which could be perfect without the detail-killer filtering! Ok, if they want smooth curves (like the speed diagrams of Nike+) on the graphs, lets give the option to the user to create averaged curves (as it is already possible with the mobile interface), or make a check-box - "I don't need my uploaded data to be filtered!".
I have to agree with the points raised in this post, maybe some filtering needs to occur to minimize bandwidth but I think that it is being over zealous, according to today's results I can walk on water :)
I am assuming this could also be the cause of problems with placing photos, today I stopped and took a picture of a viaduct as it came into our view. According to NST the photo was taken about 10 minutes later whilst we where stood on the viaduct !!!
I second your posts.
In my opinion, the real reason for the crazy filtering is to avoid payments to your mobile operator for the Internet (data). That's a good reason Nokia, but I have 1000MBs per month for free, so please let me choose!
It completely destroys the route and the thing I loved about sportstracker the most - I need to press 2 buttons to have my workout accessible to everyone (now I have to do that long scaring export-import stuff). It mixes photos (positions) as well - It even put photos in wrong order on the route LOL...
Data use should not be a reason for chopping up workouts transmitted to the web. Very long routes have small files on the memory card!!! Extremely small compared to the amount of data used during a "live track".
I don't know why the data is chopped up when it is sent to the web service, but I agree, it shouldn't be chopped up!!!
Nokia E51 W/ Bluetooth LD3W GPS.