Presentation Transpyr 2017, 7 stages with average IBP of 194
IBPindex analyzed data from the Grand Raid MTB 2017
Friday, May 19, 2017
Tuesday, March 28, 2017
KML files now supported by IBPindex
We are pleased to inform you that IBPindex can analise tracks in .KML format on both our website and through our API's.
Listening to your suggestions we now support this format promoted by Google and used in such as popular apps as Google Maps and Google Earth. Do not forget to include the associated heights in the track you want to analyse!
As always we welcome your suggestions, and we encourage you to send us any improvement idea you might have for our website.
Listening to your suggestions we now support this format promoted by Google and used in such as popular apps as Google Maps and Google Earth. Do not forget to include the associated heights in the track you want to analyse!
As always we welcome your suggestions, and we encourage you to send us any improvement idea you might have for our website.
Friday, March 3, 2017
IBPindex participates in the IV Congress of Scientific Entrepreneurship
Our company was invited to present its developments in this prestigious event held in Barcelona on February 24 and 25, 2017.
The congress looks forward to promoting that scientific and technical research reverts back to society as daily life products and businesses.
Besides, our participation in the activities, on February 24 we introduced our company and technologies to the scientists, engineers, investors and institutions attending the plenary sessions.
On February 25, our CEO Joan Casares joined the round table “From theory to practice. Experiences in entrepreneurship based on science and technology”
We shared with the participants how the development of the IBPindex has intermingled with the organizational and finance-related aspects associated with the creation and growth of a start-up.
The congress involved more than 40 speakers, a pool of more than 20 partners (comprising Universities, Science and Technical Foundations and EU organizations such as EIT Health) and more than 300 registered participants.
The congress looks forward to promoting that scientific and technical research reverts back to society as daily life products and businesses.
Besides, our participation in the activities, on February 24 we introduced our company and technologies to the scientists, engineers, investors and institutions attending the plenary sessions.
On February 25, our CEO Joan Casares joined the round table “From theory to practice. Experiences in entrepreneurship based on science and technology”
We shared with the participants how the development of the IBPindex has intermingled with the organizational and finance-related aspects associated with the creation and growth of a start-up.
The congress involved more than 40 speakers, a pool of more than 20 partners (comprising Universities, Science and Technical Foundations and EU organizations such as EIT Health) and more than 300 registered participants.
Thursday, December 15, 2016
New tool for detecting ledges and steep slopes on a trail
Would you like to know all the steep slopes and ledges present in a trail? At just a glance?
We've just released a new feature in IBPindex that detects any slope bigger than either 5, 10, 15, 20 or 25% pinpointing them on the trail.
and calculating the length of each of them.
As you can see on the screenshots, you can also download as a waypoint any slope so your GPS can automatically warn you when you approach it.
This new development comes from the suggestions and requests received from event and race organizers and, also, sports practitioners that train semi-professionally to improve their marks.
We invite you to check it out and send us your comments and suggestions.
We've just released a new feature in IBPindex that detects any slope bigger than either 5, 10, 15, 20 or 25% pinpointing them on the trail.
and calculating the length of each of them.
As you can see on the screenshots, you can also download as a waypoint any slope so your GPS can automatically warn you when you approach it.
This new development comes from the suggestions and requests received from event and race organizers and, also, sports practitioners that train semi-professionally to improve their marks.
We invite you to check it out and send us your comments and suggestions.
Tuesday, August 16, 2016
Measuring improvements in your fitness with IBPfit
IBPfit can help you measure the impact of your training if you consistently gauge your performance against a set of training trails.
We reproduce here the answer to a question of one of our users explaining how IBPfit works and how it can help you to train.
The user question:
I have entered two trails I made last week, for the analysis: my physical condition was the same, but I got 'fit index' 37 for one, and 62 for the other one??
They were two different trails (one easier - index 37, the other one much more difficult - index 62), but my fitness condition was the same (I rode the trails a few days from each other)
So I expected to get the same fitness index in both cases (with a reasonable tolerance), shouldn't I?
Our answer:
We’ve checked the tracks and their work correctly.
If we review the IBPfit associated to each of the tracks, we see the following:
1.- “Campomulo…gpx” your IBPfit is 62, the system says:
“We have found 2250 trails with the same conditions as yours (±5%)
IBP = 64,
Total Length 30.461 Km,
Accumulated climb 780.59 m,
With your time at 10.7 Km/h, in a race with 100 participants, you would be in the position number: 62”
This means that out of 2250 bike rides with the similar to yours, and according to the time you achieved, your performance is better than the 38% of the other bikers and lower than the other 61%.
2.- . “Treschè…gpx” the IBPfit is 37
In comparison with the other 690 people that have ridden a similar trail, and according to your time, your performance is better than the 67% of the other bikers, and you have been surpassed by 32% of them.
The value of IBPfit is that enables you to monitor the progress in your physical condition if you upload the information of your training routes. So in your case:
• If you would consistently use these two trails as training routes, you could track the progress of your fitness condition checking out whether your IBPfit remains the same or, hopefully, decreases.
• In the case that it decreases it will tell you that your performance is becoming better in comparison with the other bikers.
Last but not least, and for your information, the IBPfit rate is only calculated with the sample of comparable trails is big enough as to make it statistically significant.
We reproduce here the answer to a question of one of our users explaining how IBPfit works and how it can help you to train.
The user question:
I have entered two trails I made last week, for the analysis: my physical condition was the same, but I got 'fit index' 37 for one, and 62 for the other one??
They were two different trails (one easier - index 37, the other one much more difficult - index 62), but my fitness condition was the same (I rode the trails a few days from each other)
So I expected to get the same fitness index in both cases (with a reasonable tolerance), shouldn't I?
Our answer:
We’ve checked the tracks and their work correctly.
If we review the IBPfit associated to each of the tracks, we see the following:
1.- “Campomulo…gpx” your IBPfit is 62, the system says:
“We have found 2250 trails with the same conditions as yours (±5%)
IBP = 64,
Total Length 30.461 Km,
Accumulated climb 780.59 m,
With your time at 10.7 Km/h, in a race with 100 participants, you would be in the position number: 62”
This means that out of 2250 bike rides with the similar to yours, and according to the time you achieved, your performance is better than the 38% of the other bikers and lower than the other 61%.
2.- . “Treschè…gpx” the IBPfit is 37
In comparison with the other 690 people that have ridden a similar trail, and according to your time, your performance is better than the 67% of the other bikers, and you have been surpassed by 32% of them.
The value of IBPfit is that enables you to monitor the progress in your physical condition if you upload the information of your training routes. So in your case:
• If you would consistently use these two trails as training routes, you could track the progress of your fitness condition checking out whether your IBPfit remains the same or, hopefully, decreases.
• In the case that it decreases it will tell you that your performance is becoming better in comparison with the other bikers.
Last but not least, and for your information, the IBPfit rate is only calculated with the sample of comparable trails is big enough as to make it statistically significant.
Friday, August 5, 2016
Know the IBPindex of any activity from Strava, Garmin Connect or Wikiloc while you are browsing their websites
Do you want to know the IBPindex of any route of Strava, Garmin Connect or Wikiloc while you are on their website and without having to log into the site?
With our extensions for Google Chrome, this is now possible.
You just need to click on the button that activates the extension when you are on a route from one of these sites
and you can:
1. Know the IBP index of the route/activity
2. Access the full detailed analysis of the route/activity
3. Download the original track in GPX format, in case this option is not available on the website you are browsing
4. Know the IBP index of the trail for the other two sports
All this without needing to be logged in the web you are checking the route out.
For the moment you need to use a different extension for each one of the three websites. Thus, if you want to analyze activities from Strava you need to install the Strava IBP extension; in the case of Garmin Connect activities, the Garmin IBP extension, and the same in the case of Wikiloc. You can have them all installed simultaneously.
What are we currently working on?
We are developing extensions for more sport related websites and, also, an evolution of this technology that will allow including all the websites in one single extension.
Stay tuned!!
Direct download links from Google Play
Garmin Connect IBP
Strava IBP
Wikiloc IBP
Strava, Wikiloc, Garmin Connect, Google Chrome are registered trademarks and brands.
With our extensions for Google Chrome, this is now possible.
You just need to click on the button that activates the extension when you are on a route from one of these sites
and you can:
1. Know the IBP index of the route/activity
2. Access the full detailed analysis of the route/activity
3. Download the original track in GPX format, in case this option is not available on the website you are browsing
4. Know the IBP index of the trail for the other two sports
All this without needing to be logged in the web you are checking the route out.
For the moment you need to use a different extension for each one of the three websites. Thus, if you want to analyze activities from Strava you need to install the Strava IBP extension; in the case of Garmin Connect activities, the Garmin IBP extension, and the same in the case of Wikiloc. You can have them all installed simultaneously.
What are we currently working on?
We are developing extensions for more sport related websites and, also, an evolution of this technology that will allow including all the websites in one single extension.
Stay tuned!!
Direct download links from Google Play
Garmin Connect IBP
Strava IBP
Wikiloc IBP
Strava, Wikiloc, Garmin Connect, Google Chrome are registered trademarks and brands.
Wednesday, July 6, 2016
Reliability of the calculation of total distances and accumulated heights: original versus optimized tracks
We reproduce here some questions from one user related to the reliability of the calculation of the height and, also, cumulated climb and descent in the case of both the original track and the optimized track.
Also, we will seize this opportunity to give a brief overview of our error treatment processes.
A summary of the questions of our user:
How reliable is the calculation of the distance and height difference your tracks and traces optimized?
I would like to know the most reliable figure for the distance and the accumulated climb in the case of the attached track.
Also, when I open the link " info points list" on the right side of the table which appears there, there is an "optimized trace" with a cumulated climb of 537.43m.
As I understand, your system detects the GPS system's recording errors and also corrects the optimized trace?
So in summary, the result obtained is generated from the corrected trace.
In this case, I note that reliability of the original track is D (= bad) and correction level 3.
And the final result for the distance and cumulated climb: 14.143 km and D + 466 to 469m.
Is this the right answer?
Here is a summary of our responses:
Indeed, 14,143 km and D + 466 to 469m are the figures describing your track
On this screenshot, we can see that for this part of the track...
was recorded with this profile by the GPS device.
That is why our system has applied the corrective algorithms.
One can intuitively see that it is very unlikely that the track’s original data, without the corrections we will write about further in this post, is describing the real profile of the physical path traveled by hikers.
We take the opportunity of this example and your questions to describe our error handling process briefly.
This is a schematic description of the data processing process IBPIndex:
1. Resolution of different problems caused by the GPS recording device in the .gpx track "original" essentially:
• Analysis of abnormal points
• Jumps / Steps in the profile of heights product, for example, of stops on the route or geographical elements that blocked or prevent a proper reception of the GPS signal
• Optimization of the number of points recorded on the track: the more points are recorded, the bigger the accumulated mistake is introduced in the calculations.
• Other error treatments methods...
…and we obtain the optimized track
2. On the optimized track, we apply a series of other correction mechanisms.
The main one is an automatic correction system working in 8 possible degree levels ranging: from level "0" no correction, no correction only optimization only, up to level "7" maximum correction.
Once the data has been again revised/corrected we assign a reliability degree to the track, according to the following scale:
"A" = Very Good
"B" = Good
"C" = Fair
"D" = Bad
"E" = Very Bad
And after this final set of analysis and corrections, the "Final Track" is obtained.
This "Final Track" is the base on which IBPindex calculates the final statistics of the tracks that you see on our website: positive and negative cumulative altitude difference, percentage rise, etc.
Also, we will seize this opportunity to give a brief overview of our error treatment processes.
A summary of the questions of our user:
How reliable is the calculation of the distance and height difference your tracks and traces optimized?
I would like to know the most reliable figure for the distance and the accumulated climb in the case of the attached track.
Also, when I open the link " info points list" on the right side of the table which appears there, there is an "optimized trace" with a cumulated climb of 537.43m.
As I understand, your system detects the GPS system's recording errors and also corrects the optimized trace?
So in summary, the result obtained is generated from the corrected trace.
In this case, I note that reliability of the original track is D (= bad) and correction level 3.
And the final result for the distance and cumulated climb: 14.143 km and D + 466 to 469m.
Is this the right answer?
Here is a summary of our responses:
Indeed, 14,143 km and D + 466 to 469m are the figures describing your track
On this screenshot, we can see that for this part of the track...
was recorded with this profile by the GPS device.
That is why our system has applied the corrective algorithms.
One can intuitively see that it is very unlikely that the track’s original data, without the corrections we will write about further in this post, is describing the real profile of the physical path traveled by hikers.
We take the opportunity of this example and your questions to describe our error handling process briefly.
This is a schematic description of the data processing process IBPIndex:
1. Resolution of different problems caused by the GPS recording device in the .gpx track "original" essentially:
• Analysis of abnormal points
• Jumps / Steps in the profile of heights product, for example, of stops on the route or geographical elements that blocked or prevent a proper reception of the GPS signal
• Optimization of the number of points recorded on the track: the more points are recorded, the bigger the accumulated mistake is introduced in the calculations.
• Other error treatments methods...
…and we obtain the optimized track
2. On the optimized track, we apply a series of other correction mechanisms.
The main one is an automatic correction system working in 8 possible degree levels ranging: from level "0" no correction, no correction only optimization only, up to level "7" maximum correction.
Once the data has been again revised/corrected we assign a reliability degree to the track, according to the following scale:
"A" = Very Good
"B" = Good
"C" = Fair
"D" = Bad
"E" = Very Bad
And after this final set of analysis and corrections, the "Final Track" is obtained.
This "Final Track" is the base on which IBPindex calculates the final statistics of the tracks that you see on our website: positive and negative cumulative altitude difference, percentage rise, etc.
Subscribe to:
Posts (Atom)