From now on you can view the progress chart for the different sports and time periods on Runalyze.
Compare your distance, duration, ascending altitude, TRIMP or number of activities in the current period (year/month/week) with a previous one (up to the beginning of last year at the most), and keep track of where you will end up.
Fix reading developer fields for multisession files
Fix gps parser for non-defined namespace extensions
Support for all developer fields from FIT files
Runalyze does now import and store all developer fields from FIT files. Read more at our blog.
Fix default privacy for all sports
Due to a bug in the new account setup guide we had to reset the privacy settings for all users in the sports to private. If you want to have the activities automatically set to public when importing, you have to reconfigure that setting for each sport.
Easy account setup
Athletes can now easily set up their account to provide all the data necessary for specific calculations. Read more at our blog.
Fix best sub segments for non-equidistant data
There was a bug resulting in wrong best sub segments for power data in case of non-equidistant data. This behavior has been fixed.
Fix false duplicates for short transitions
Multisport sessions (e.g. Triathlon) with short transitions (less than one minute) led to false duplicates.
Fix time zone issue for sports panel
The sports panel did ignore the user's time zone when showing e.g. current week.
Fix imperial units in plot tooltip
Plot tooltips in activity view did not respect imperial units.
Option to recalculate a single activity
It is now possible to recalculate TRIMP, VO2max and altitude for an individual activity.
Activity view: dynamically show inactive laps
History import for Decathlon
You can now take over your complete history via Decathlon sync.
Support for treadmill incline from Runn sensor
We have added support for incline data from Runn™ Smart Treadmill Sensor from North Pole Engineering.
New beta features: improved views for marathon shape and running performance status
For users with supporter status there are two new views for the current marathon shape and for the running performance status. We explain the new Marathon Shape View in detail on our blog and an article on the running performance status view will follow. After a few weeks those features will be freely available for every user.
Various minor improvements for activity view
We have internally refactored the activity view (to get rid of some legacy code) and added a few improvements. Heart rate and pace zone tables as well as computed laps do now show average power and power zone table does now show average pace.
Fix Google login for some users
The Google login did not work for everyone lately. We have fixed the issue by updating a third-party library.
Decathlon: automatic synchronization
Direct synchronization with Decathlon & Domyos E-Connected is now possible. Read more at our blog.
Glossary: running dynamics
We have added various new entries in our glossary for running dynamics (cadence, stride length, ground contact time/balance, vertical oscillation/ratio, flight time/ratio).
Climb score: show avg. power
Average power was added to the Climb Score view. You can switch between pace and power now.
Increased max length of equipment notes
NEW: Become a RUNALYZE SUPPORTER
To be able to invest more time in RUNALYZE in the long term, we are now launching a subscription model. You can become a RUNALYZE supporter. Read more at our blog.
Special event: Easter Run 2020
In view of the current situation and numerous cancelled events, we have organised a virtual Easter run. Read more at our blog.
Fix map for poster tool
Coros added export to RUNALYZE
Read more at our blog.
Internal refactoring for account activation/deletion and password recovery
TCX export of activities without datapoints
Revert using fit files for Polar sync
Polar sync now uses *.fit-files by default
Polar sync now uses *.fit-files by default. The option to switch formats has been removed.
New elevation correction config option
The user can switch between "Never correct", "Only if device has no barometer" or "Always". The new option "Always" is intended for cases when the barometer of a device is broken or provides useless data.
Do not correct elevation for devices with barometer
If a device that has a barometer is detected during import, no automatic altitude correction is performed, even if it is activated in the configuration. Barometric altitude data is usually much more accurate than data corrected by satellite data. A manual correction is still possible afterwards.
Fix altitude data from barometer
Elevation data from a device with a barometer was erroneously stored as 'corrected' data. Affected are activities between 13 and 17 March. In this case the data was not corrected, only the displayed message is incorrect.
Automatic device detection
When importing fit files, the device is now automatically detected in almost all cases.
Suunto: Force sync of individual activities
Sometimes Suunto only informs us with a significant time delay if a new activity is available. If in doubt, you can now directly trigger a sync of individual activities.
Fix invalid vo2max correction factors
In rare cases an invalid vo2max correction factor was calculated.
Fix generation of social images
After a recent change the generation of the images did not work anymore.
Anova and trend analysis: total strokes and swolf
We have added the swim metrics total strokes and SWOLF to our anova and trend analysis tools.
Fix account deletion link
The link to delete the account in the account settings was temporarily not available.
Limit number of zones
We have limited the maximum number of zones you can set per metric (heart rate, pace, power) to 20.
Add range for easy trimp
Instead of a single value (to reach TSB = 0) 'Easy TRIMP' now shows a range to keep an optimal workload ratio of 0.8 < A:C < 1.3.
Fix anova tool
The anova tool wasn't available after our latest internal framework update.
Internal framework update
We have updated the framework we use internally.
Fix menu on mobile devices (logout link was not reachable)
Running Effectiveness: clearify 'levels'
The levels we have shown so far for Running Effectiveness are only valid for data coming from Stryd. Running Effectiveness based on calculated power data (as done by us via GOVSS) do not have a high information content.
Fix power calculation for files with only zeros in power stream
Power values have not been calculated if the imported file contained only zeros. This behavior has been fixed now.
Fixed Polar History Import tool
Due to another uncommunicated change on Polar's side our history import for your Polar data did not work correctly.
Gravatar as profile image (optional)
You now have the option to use the gravatar as profile image (shown in the upper right corner of the dashboard and your public athlete page).
Race performance chart: date on x-axis
The Race Performance Chart has a new option to use the date as x-axis.
FIT files: support for Anaerobic Training Effect
Fix adding race result for activities with very long titles
Mapzen is the new default service for elevation correction
The elevation data from Mapzen has been set as the default elevation service. The service uses the terrain tiles dataset from AWS' open data registry.
User Backup creation failed
Backups were not working since 4th December. This has been fixed now.
Disabled Runtastic converter
Runtastic's official backup does include gpx files with heart rate and altimeter information from now on. The converter is not required anymore and has been disabled.
Ascent/Descent instead of a single elevation value
Ascent and descent can now be edited and can be entered for activities without elevation profile. So far, most sections used only a single elevation value (which was the maximum of ascent/descent). From now on, a single elevation value always shows the ascent.
New power value: xPower
xPower is a weighted average of your power output and serves as an alternative stress metric.
Read more in our glossary.
FIT files: support for description field by Suunto
From now on the developer field "description" Suunto uses in FIT files is mapped to our description field in RUNALYZE.
Fix for imports of invalid power data
Invalid power values (e.g. negative values) are now ignored when parsing a file. We discovered some tcx files that failed while importing because of those invalid values.
Export of a single activity: use correct laps
Exported activities (e.g. as tcx file) will now contain the correct laps instead of default 1k auto-lap.
Acute:Chronic workload ratio in calculations panel
The Acute:Chronic workload ratio (ACWR), which is simply the ratio of ATL and CTL, is now shown in the calculations panel. It can be used to determine injury risk.
Read more in our glossary.
RSS Feed for this changelog
You can now also subscribe to the changelog as an RSS feed.
Fix for poincaré plots
Until now, poincaré plots of hrv data always displayed only one (the last) y-value for an x-value. This behavior has now been fixed.
FIT files: support for estimated vo2max by Suunto
From now on the estimated vo2max by Suunto is mapped to our internal "estimated vo2max field" from fit files. You can activate this value in your dataset.
We have fixed a configuration that resulted in slower page calls.
Various bugfixes and improvements in our activity importer
Fix 'remember me' for login
The "remember me" functionality has not worked correctly since our recent redesign. This bug has now been fixed so that users can stay logged in for a longer period of time.
Automatic time zone detection for file imports
The time zone detection, based on the activity's coordinates, was broken for some time. During that time, we only used the user's default time zone which may be incorrect in case of e.g. vacations.
Auto-fill route names with start location
The start location is now automatically added to the "Route" field if the activity contains gps coordinates.
New design for landing page, login, registration, ...
We have redesigned the publicly accessible pages such as the landing page, login and registration or our glossary and help pages.
Calculated power is now correctly updated when the sport or altitude profile is changed
For all running and cycling activities for which no recorded power is available, power is automatically calculated. This calculation is now correctly performed (or removed) even if the sport is changed later and updated if the elevation profile is changed (by elevation correction or removing a data series).
Suunto Sync: Fixing laps
When syncing Suunto activities there were problems with the laps. We only support flat laps. This if fixed for all future activities.
TCX files: Fix empty altitude values
Missing altitude values were wrongly imported as "0", which leads to different problems. These values are now imported correctly as unknown.
Power calculation for running: Fix for potentially negative values
Illegally high speeds (e.g. due to errors in data recording) may have led to negative power values. This behavior is now suppressed.
Automatic translation of help articles
Help articles will be automatically translated into German, French, Spanish, Portuguese, Dutch, Italian, Polish or Russian if we have not translated them yet manually.
Activity data: New data series for Air Power from Stryd
Air Power data streams by Stryd will be imported for all upcoming activities. Still, we don't show the data in the activity view yet.
Storing original FIT files
From now on we are storing all uploaded fit files. You can download them from every individual activity.
Show/Add equipment categories in sport settings
In the sports configuration, the individual equipment categories of a sport can now be viewed, assigned and removed.
GOVSS/Running power for everyone
The automatic estimation of power data, if no recorded data is available, was previously only available for cycling. We now have such an estimate for running activities as well.
Read more in our blog post Running Power for everyone.
Workaround for activity upload from mobile devices
Mobile browsers like Safari do not support the list of supported file extensions. We added a temporary workaround until all mobile browsers fix that issue.
Fix stats view for some rare cases
Fix table headers in statistics plugin for year on year view
Added a changelog
We work on RUNALYZE day in and day out. To give you a better idea of all the changes, bugfixes and new features we're releasing, we've added a public changelog.
Centralized logging for the growing infrastructure
Fix trimp calculation after removing heart rate series
Fix for calculated training paces
The calculation of the paces in the section "Training paces" contained a small error. Speeds below 100% were a bit too fast, above 100% a bit too slow.
Design: Adjust colors to match logo
Fix fit parser for swimming heart rate in multisport files
Problem was caused by swimming heart rate, which is at the end of the file but belongs to the second session.
Show dataset labels in statistics
Elevation calculation: Correctly respect pauses
Tracked pauses must cause elevation calculation to split trackdata into different segments and add ascent/descent values of all segments separately to total ascent/descent.
Single queue for activity import
As a preparation for scaling the activity import, activities from history import, API import and normal sync now end up in the same queue.
New service for elevation data: Mapzen
We are evaluating new data sources for elevation data and added Mapzen as a new elevation service. The service uses the terrain tiles dataset from AWS' open data registry.
Sport type can be guessed by title
Activity titles (as provided in some file types) will be used to guess the user's correct sport type.
New tool: Convert Runtastic backup to gpx files
Runtastic has decided to discontinue its web platform. Downloading all your data from Runtastic is easy, but the data is stored in a non-usual format. We made a converter written by Glenn Reyes available to let you get your activity files in a standard gpx format. You can find our converter at runalyze.com/runtastic-converter.
Fix social image download
Internal framework update
We have updated the framework we use internally by some versions.
Refresh Suunto API Tokens automatically
Fitbit sync: Ignore duplicate notifications
Garmin sync: Check content type
Garmin's new API provides information about the file type. Unfortunately, for older activities, this is always mistakenly FIT, whether or not the file type is actually GPX. Garmin knows the bug but will not fix it. We now check the file content so that the import works accordingly.
Single fields for ascent/descent in tools and dataset
FIT files: Recovery heart rate 2 Minutes after end of activity
Removed dataset style option
Remove old Garmin api
The outdated Garmin api has been removed. Users that have not switched to the new api will not have any activities synchronized until they have connected to the new api.
FIT files: Update for internal fit parser module
Fix multisession files from Suunto
Activity data: Added Peak EPOC and support for recovery time from Suunto
Activity data: New data series for Respiratory Rate from Garmin devices
FIT files: Support for Power by IQ app Running Power Estimator
Power by Garmin Connect IQ app Running Power Estimator does not use the standard power field to store power data. This is now mapped to the power field in Runalyze.
Full Garmin import via new api
We are now able to provide a full history import (except third party activities and manual activities) from Garmin.
Subjective feeling in activity
Gradient distribution in climb score
Polar Sync: Option to choose between fit and tcx format
Fix social images to correctly respect pauses
Adjust tile url for hikebikemap
Stride length available in anova and trend analysis
New uploader: Zip is extracted in browser
Fix wind chill to ignore temperatures above 10°C
Fix climb score view for imperial units
Improved fitlog import
Fix reading gpx extension values (ns1)
Fix Suunto API deauthorization
Full Suunto import (with range option)
Improved requeuing of activity sync and import
Shape plot: New option 'Last 24 months'
Fix dashboard for users without active statistic plugins
New Help and Support section
We have introduced a new Help and Support section at runalyze.com/help trying to answer the most frequent questions.
Update Facebook share feature
FIT files: Fix idle laps in swim files
Emoji support for various comment fields