Differences in accumulated heights among GPS devices, IBPindex and data analysis apps

The impact on the reliability of the tracks' statistics of the different error treatment methods is a hot topic.

The following question of one our users shows the practical impact of those methods, and how IBPindex is implementing much more sophisticated techniques that are closer to the physical reality of the trail.

Our user question:

I would like to ask you about the noticeable differences in heights existing between the ones provided by the GPS device and the ones produced by your analysis. 

I’ve noticed that usually, the number accumulated climb is bigger in your analysis than one given by the GPS, and I have checked this with two different devices. 

For the attached tracks and the same route: the difference in the accumulated heights between the two devices is just 5 meters, 1266 in one case, 1271 in the other, versus 1718 and 136ibp and 1759 and 137ibp in your analysis. In the case of the length of the track, the numbers are nearly the same in your GPS and your system.

Could you explain to me why this difference in the accumulated climb, and not in the lengths or distances?

Our answer:

We have analyzed the files you sent us and difference in the accumulated totals stems from the error treatments methods used by the GPS devices.

The GPS related errors depend on basically: the position and number of satellites present at the horizon during the time span in which the route is recorded and the precision in the recording of the heights.
You can find more information in:

http://en.blog.ibpindex.com/2014/07/accumulated-climb-and-descent-influence.html

http://en.blog.ibpindex.com/2014/05/cumulated-height-why-same-file-produces.html

The most usual error treatment methods consist in the application of heights meshes (see the link mentioned above) or to discard any variation in heights smaller than 5 meters (as you can see in this screenshot featuring the default options of a GPS data analysis software)

The choosing of this error treatment method causes the following situations:

Let’s imagine a route of a total of 50km with constant ups and downs of 4.9m all along the road. For the cyclist would be physically very demanding but, if the GPS system discards all the slopes of less than 5m of length, you will see that the accumulated climb or descent amount to 0 !!

IBPindex uses an array of error treatment techniques much more advanced and precise than the previously mentioned truncations and substitution of the original heights, such as:

•    Detection and removal of aberrant points
•    Detection and removal of saw tooth patterns
•    Optimization of the number points fed into the analysis, to avoid that the addition of a big number of little errors generates a significant cumulated deviation.

According to our experience, those and other techniques, that we have progressively incorporated into our algorithms along the analysis of more than 2.000.00 routes, make our results given by IBPindex are the ones that describe reality the closest.

There are various open debates in Internet forums about the treatment of heights, on this link you can find another example.

http://es.blog.ibpindex.com/2016/05/tracks-ruta-monegros-bike-marathon-2016.html (in Spanish)

Please do not hesitate to ask us about any further doubt you can have related to these or other tracks.

GPS device that generates incorrect data in gpx format files

One of our users recorded a route in two GPS devices: Garmin and Polar. 

The results displayed by IBPindex were pretty similar. Oddly, the analysis of the files generated by Polar was rather different depending on whether the format of the file was GPX or TCX.

After the analysis of the files we found that, for the same route, the device included different data in the file depending on whether the format was GPX or TCX.

We quote here the question of the user:

To: info@ibpindex.com

Subject: CONSULTATION

Good evening,

I have a question I would like you to solve for me, if possible.

I have a Polar M400 and Garmin Vista HCX. Polar allows me to download data from the same route in formats GPX and TCX, and only GPX in the case of Garmin.

When analyzing the files with IBPindex, I find three different results. I could understand differences between Polar and Garmin, all in all, these are different devices and configuration settings can be also different.

But, in the case of Polar, the same track gives very different results depending on the format you download it (either GPX or TCX).

What can be happening?

I send you attached the three files.

And the conclusions of our analysis:

The correct tracks are "2016_06_05 _-_ garmin_vista_hcx.gpx" and "2016_06_05 _-_ polar_m400.tcx".  

"2016_06_05 _-_ polar_m400.gpx" is incorrect.

This image shows a comparison of the data exported from Polar in the GPX and TCX files.

The GPX height data accumulates many mistakes. It seems there may be something wrong in the conversion process to GPX. 

It would be very interesting to see if this only happens with this trails or happens in all cases.

If you can do some tests, please let me know what are the results. Is there perhaps a problem in the firmware of the device?

Joan Casares
IBPindex