Until now, you could only unsubscribe from all mails in general. Now there are various mail types for subscription to better support future features.

If you receive incorrect mails, please notify us.

See even more statistics in your equipment overview (distribution)

Syncing nightly HRV average (summary) supported by e.g. by Garmin Forerunner 995

The selection tooltip can now show the range (min/max) in addition to the average.

Will be correct now for all new sleep/hrv data

Polars "old" notification system for new exercises seems to be broken. We switched to the new one now and figured out the missing activities by looking into our logs. Most of the missing activities should be there by now.

You cannot switch the Polar file format anymore. It's now always fit format.

We added the sync of Coros Health data (sleep and resting heart rate data). We will not provide a historical sync for Coros health data at the moment.

Important: The REM/Deep/Light/awake duration is not provided via that API at the moment. We already requested that at Coros.

Really often requested: Default Equipment (per Sport) can now be set in the Equipment (Category) settings and is taken into account when automatically importing new activities. Go to https://runalyze.com/my/equipment/overview and edit your equipment categories.

(Configuration -> General Settings -> Activity Form -> Sort: equipment)

If you have activated the equipment panel, then instead of linking to the search, it now links to the new equipment view, which includes a histogram and progression graph, as well as other details.

Look at where you've been exercising and try to maximize your visited tiles. This is the purpose of our Tiles counter tool.

https://runalyze.com/help/article/tool-tiles-counter

You may need to adjust your sport setting if you have a custom "Walking" type

The cadence unit can now be set individually for each sport.

Mountainbike Grit/Flow data series is now imported for fit files. For historical ones this will be done in a later process.

This has been fixed and after the next "social" login (via Google, Facebook, Apple) it will be active again.

Internal upgrades on the framework & oAuth API Server

Sign in via Apple is possible now

We have added today a bunch of new sports (>40) and icons into Runalyze to improve the automatic mapping of the synchronized activities.

Due to the fact that many of these sports have already been created in many accounts via custom sports, we have tried to adapt these created sports accordingly so that it maps to the "internal" sports.

However, due to the different naming and languages, it is not possible for us to do this for all custom sports. Therefore, it may be necessary to do this manually.

For this there is this help article: https://runalyze.com/help/article/adjust-sport-mapping

Added a history import function for adidas Running. Important: As we are not able to do many requests to the API this process can take a bit longer.

We do now estimate the Peak EPOC for every activity based on your heart rate data.

The maps were dropped by the provider.

From now on, we also store developer session fields from FIT files, which were not mapped to native fields internally before. The field names coming from the files are sometimes a bit cryptic, so you have the possibility to configure the field names and units for the activity view. For historical activities imported in FIT format after 10/13/2019, the information will also be available in the future. The process for this should start in Feburary and will take a while to process the files again.

Updated the device detection list (including some version of the Garmin Fenix 7)

All following fit file imports will import the original values for ascent/descent. You can choose to display those values instead of the ones calculated by Runalyze. Still, when looking at segments of a route (e.g. for climb score or when analyzing laps) calculated values will be used/shown.

We show the ascent/descent values in the moment for all files imported since today. For historical activities imported in FIT format after 10/13/2019 these information will be available in the near future too.

We have slightly modernized and extended the trend analysis tool within Runalyze. The tool can be used to examine trends in the development of individual activity values. For this purpose, the respective value is displayed in the course of time over the different months (and years) as a dot diagram.

This is new:

• Option to group by day / week / month / year
• Possibility to display several diagrams one below the other
• Improved tooltip (incl. link to the activity if you “fix” the tooltip by clicking on it and then click on the date)
• Expert settings to change size/color
• Data is loaded only once, changes can be displayed directly
• Minor optical changes

It's possible to sync activities without GPS data from Adidas Running now.

Marathon shape, progression graph and quality sessions had an issue with displaying all weeks correctly in 2022.

You are now able to add custom data fields for your equipment.

We adjusted/improved the Fitbit Sync and added a force/download option (linked at the service overview page at https://runalyze.com/activity/sync)

It's now possible to send HRV entries via external apps or own integration (Personal API) to Runalyze

For more than a year now there is the possibility to support us as a “Runalyze Supporter” and thus ensure the further development of Runalyze. To all the supporters out there: You bring us a bit closer to our goal of being able to run Runalyze not only on a part-time basis. Thank you very much!

But as mentioned at that time, there will be another level for additional and especially cost-intensive features. The time has come now and we start with “Runalyze Early Premium“. As a premium user you have the possibility to raise your training analysis to a new level and get the best out of your training.

• New analysis tool: Quality Sessions
• New analysis tool: Best segments
• New analysis tool: Moving average mileage
• Poster tool: Show all years at once and/or use map background for heatmap
• Performance curves for any period (not only last 90 days)
• Progression graph for all years (not only current and last year)
• Historic hrv values in trend analysis and anova
• Colored tracks based on various metrics (not only pace)
• Additional map layers: OpenCycleMap, Outdoors Map

Read more on our blog

Duplicates still occured and latest sleep entries were not correctly synced. We change the duplicate detection.

We have recently added the option to add trackdata from a new file into an existing activity. As of today, merging is also possible based on the timestamps. Unlike the other methods, different start and end times of the files are correctly taken into account.

Pushing activities from Coros APP to our API wasn't possible because of an library issue. The direct sync with our connection to Coros API was operational the whole time.

You can now merge trackdata from an uploaded file into an existing activity. This is useful when recording an activity with different devices, e.g. when using Zwift where Zwift itself records the gps route but your own device (e.g. Garmin/...) records all other data. You can now upload the Zwift file afterwards (via Merge file into activity) and select which data series to copy.

The settings have a new section Health where you can hide specific parts of Runalyze Health that you don't track, e.g. blood glucose or blood pressure.

A bug introduced with a bigger internal release a few days ago has been fixed.

Data series can now be exported as csv file for each activity.

In some cases the video export was not successful.

Sport types in gpx files from Strava and at least running and walking from Amazfit devices will be recognized (as long as the internal sport type is correctly set in your settings.

We are getting multiple informations for one activity by Coros. We try to prevent duplicates at an earlier processing point for Coros.

If manual edits are made on our side after syncing data, data may get overwritten if one adding new entries on Garmin for the same day.

Our health section does now support HRV entries. They will be synced automatically from Garmin and Oura or you can enter them by hand.

You can now go back week by week to have a look at your marathon shape for previous dates. Just click the arrow(s) when hovering the date in the header.

See your recovery status and our glossary.

To get the full history of your polar activities request your Polar data backup

You can now specify a custom range (from ... to ...) which will be used to estimate your aerobic threshold based on DFA-a1 values (based on HRV data).

Sleep and weight are now synced automatically from Fitbit.

Tracking of menstrual cycle details has been added as a first alpha version.

Updates on Strava titles are getting now forwarded to already synced activities from Strava.

Privacy zones have been added to Runalyze as beta (still verifying some edge cases), see your privacy settings.

Adjusted max zoom for all map layers. OpenMapSurfer and Hydda have been removed. Mapbox has been fixed.

In addition, we've improved the download speed.

Title/Notes will be updated if you update these at Garmin Connect. This works for all Garmin activities since May 2021.

Some connections to Concept2 were affected by a bug that prevented synchronization.

We have a new expert editing tool for correcting the distance data series. You can now fix the distance data of your activity in case of gps issues based on a new total distance or piecewise values based on your rounds.

You can find the tool in the drop-down with editing tools located in the header of the full activity view.

For all cyclists out there: We have added a new map layer for the activity view: CycleOSM

The zone statistics (Pace/Power/HR) in the histogram tool are now based on the recorded data series and no longer only based on the average values.

There was an bug in our duplicate detection which resulted in missing session from multi sport files. This has been fixed now for future activities.

The data export failed in some cases because it required too much resources more for "large" accounts. We have improved the way it works.

You can now merge the csv generated by the HRV Logger app into your activity.

We now correctly detrend rr intervals for DFA-alpha1 estimation (as part of the Aerobic Threshold Estimation based on HRV). Bruce Rogers has taken a closer look at the improved variant in his blog and showes another example.

We changed a lot of internal stuff recently and introduced a few minor bugs when releasing the changes. Those minor bugs (gap was missing in plot, avg. distance per week/month in year-on-year view was missing, ...) have been fixed now.

As we have a different RPE scale the values from Garmin will be adjusted to our scale.

We now offer the possibility to merge the Polar HRV-CSV file into the activity. That HRV-CSV file is available in Polar Flow if you have an Polar Vantage 2 or record activities with the H10 sensor.

Synchronization with Concept2 Logbook is now available for everyone (as beta)

As you may have noticed, Garmin no longer syncs third-party activities (e.g. Zwift) to us. As Zwift and other manufacturers do not yet have an API or do not want to connect us, we have now connected Strava as an option.

By default, only activities that are not already covered by direct connections are synchronized.

For example, Strava always exports the original activities in the data backup compressed in *(tcx|fit).gz format.

We have deployed a cleary improved location name detection. There will always be edge cases where the name doesn't fit perfectly.

Garmin has extended the API and now we can also access the titles and descriptions. This only happens during the initial sync of the activity.

Almost all stats from the "Training times" stats are still available in the Histogram tool.

For the past year, Garmin also synced third-party activities to platforms like ours.G armin has now disabled this and activities such as from Zwift can no longer be synced to us via Garmin. We hope that Zwift and co will provide an API in the future. But so far there seemed to be no interest there.

See also Feature Request "Sync with Zwift"

Runalyze now offers a possibility to directly assess the intensity of an activity in the calendar view at a glance: Color bars for zone distribution.

Read more

Due a change on Polar's site we are not able to offer the Polar history import anymore.

We've added further lap intensity options. Laps can now be marked as 'Interval/Active', 'Recovery', 'Warm-up', 'Cool-down' and 'Rest'.

Runalyze is now able to import vendor-specific trimp values stored in *.fit files.

We changed some defaults after registration. We removed the activity type for 'Warm-up' (which motivated people to split workouts into three activities), renamed 'Jogging' to 'Eas run' and 'Long Slow Distance' to 'Long Run' and removed default clothes. Nevertheless, this does only apply for upcoming registrations and as usual every user can define his own activity types and equipment categories (and rename the existing ones).

We have improved the duplicate detection during activity import.

It took a while until we have found why some data is missing. This has been fixed now and some activities are reprocessing. You should see all data until tomorrow evening.

Internally we already track all your feature requests and try to see what we develop next. Now we've just added a Feature Voting Plattform, where you can submit feature requests, upvote existing requests and also get notified when there is a new status of your request.

The performance curves have been added for individual activities some time ago. We now have the performance curves for last 90 days live. You can find them in the list of tools or directly at https://runalyze.com/my/performance-curves.

Zone statistics (for pace/power/hr in the statistics tab) based on recorded data series are now available for everyone. These statistics were based until now only on the average values of the activities.

Synchronization with Oura (http://ouraring.com/) is now possible. So far only sleep data, as we do not yet support HRV data outside of individual activities. In the same move, we added two more data fields to the sleep data (average heart rate and resting rate

Zone statistics* (Pace/Power/HR) based on recorded data series are now available for Runalyze Supporter as beta feature. These statistics were based until now only on the average values of the activities.

*Only at the Analysis-Statistic plugin yet

You are now able to sync our activities from Wahoo to Runalyze automatically. Read more

If you have a connected Suunto account at Runalyze you can now upload a Fit file directly to Suunto app.

Virtual activities (e.g. Zwift rides/runs) can now be filtered when searching for activities.

We have added glossary entries for Climb Score and Percentage hilly.

Runalyze has a new experimental feature: for activities with HRV data (or RR intervals) the aerobic threshold can be estimated (or at least it’s tried to do so).

Read more in our latest blog article.

With the latest update, Runalyze can now display power, pace and heart rate performance graphs for individual activities. These graphs show the best or maximum performance for all possible time periods – from one second to the entire activity duration.

Read more in our latest blog article.

At some places week numbers at turn of the year were not correctly taken into account.

We are currently testing new features based on the long-term trend of histograms, duration curves, and route data. This includes power duration curves, which are now available for the first beta testers.

FIT details (performance condition, recovery time, estimated VO2max by file, ...) are now available in the miscellaneous section of the activity view. They have been visible in the dataset only so far.

If you have a connected Suunto account at Runalyze you can now upload a GPX route directly to Suunto app and thus to your watch.

Since 1st December, the initial trimp calculation may have been off. This has been fixed now.

There's a new feature (for supporters only): The poster tool has a new option to generate the heatmap (or grid layout) for a single month.

Up to now the weather data was always queried for the beginning of the activity. This has now changed and we now request the weather at the middle of the activity.

We have added a new configuration option Round laps to full seconds which defaults to true. Unchecking this option will give you lap times with tenths of a second for future imports.

• Respect date related weight, maximum/resting heart rate in tools and dataset
• Add Running Effectiveness to tools
• Add Relative Running Economy to dataset and tools

A third party library we were using used some old invalid urls to request tokens. This has been fixed. If you have problems with the Withings connection please disconnect and reconnect.

Read more in our help article or start by generating your own token in your account.

Our API got an bulk endpoint for health metrics.

Our "PrivacyGuard" had a bug which caused the graphs/raw data to be missing for some activities. If you are affected by such an activity, you have to import this activity again.

We have extended our API for our partners.

Two months ago we started respecting the 'main' privacy settings from your dataset. Now, almost all privacy settings are respected. For example, if you set your average heart rate to private, the heart rate data series for other people will also be hidden.

VAM is the average ascent speed in meters per hour, calculated based on all classified climbs in Runalyze. This value is now available for all upcoming activities (with at least one classified climb).

You can now set all your activities public or private with one click from your privacy settings.

The activity view now includes a plot for flight time (assuming cadence and ground contact time are available).

Our ANOVA tool can now group values additionally by month (and year), weekday and daytime.

We have upgraded several internal dependencies of Runalyze.

Due to a bug no weight or rest heart rate data was received. This should work again for future entries.

Runalyze can automatically calculate power for running and cycling activities. Previously, this was always done when no recorded data was available. From now on you can choose for each sport whether Runalyze should calculate power always, never or only when empty.

Runalyze now has same settings for limiting Polar Sync as for Garmin Sync. Still, sleep sync is not yet available for Polar due to problems on Polar's side

As some users have requested we have now created a setting to restrict the Garmin synchronization.

Select whether you want to have the resting heart rate, sleep data and/or body composition automatically synchronized. Default remains "yes"

In rare cases an invalid connection to these services resulted in problems disconnecting those accounts. This has been fixed.

You can now set your locale dependent date, time and number format in your account settings.

Garmin beat us to it a few days ago, but this feature has also been on our wish list for a long time. Now it’s done and you can also colorize all your tracks by speed in Runalyze. So you can see directly on which sections you were especially fast or slow.

Read more at our blog.

Some activities were assigned to the wrong day within the poster tool.

Gradients above 40% (or below -40%) were incorrectly evaluated when calculating the Grade Adjusted Pace.

We have updated our device list and are now able to detect a lot of new devices and vendors.

Synchronization of health data from Withings is now enabled for Runalyze Supporters.

The Garmin history import can now be used again without any limitation by Garmin. Requesting more than 1000 days of history is possible again.

Body composition, sleep data and resting heart rate are now available for syncing too. Duplicates can occur for health data if entries already exist for requested time period.

The recovery heart rate (2 minutes after stopping) had been available as dataset value and is now shown in the activity view as well.

Relative TRIMP is simply TRIMP per hour. It can be used as an intensity metric, similar to average heart rate, but taking into account the changing workloads during the activity.

The 'main' privacy settings from your dataset are now respected for your shared activities (daytime, title, notes, route name, training partners, tags and equipment). You may want to set those fields to private in your dataset settings.

Resting heart rate and weight should now also be automatically synchronized from Polar to Runalyze. Sleep data cannot yet be synchronized due to a problem with Polar.

Due to a misunderstanding of sleep and resting heart rate synchronization with Garmin, there were many duplicates. A fix was applied. Most duplicates for Resting Heart Rate and sleeps have been removed.

All kind of health data like weight, sleep, mental state, blood pressure, maxium heart rate and resting heart rate have their own tables now where you can edit and delete all entries.

The Garmin history import is available again. But as we are limited temporarily by Garmin with 1000 days/minute the tool maybe shows an information that you need to wait a minute.

Weight and sleep data is now synced automatically from Garmin to Runalyze. Resting heart rate should be synced automatically too.

New health section: We have migrated all data to the new health section.

A blog post with all changes will be available in the end of the next week.

Mood, fatigue and stress can have quite an impact on everyday training. Both positive and negative. Looking at these values over a longer period of time is therefore not only important for training, but also to be able to counteract in everyday life if the fatigue and stress continues for too long.

You can track your blood pressure. Automatic sync with e.g. Withings is in work

We will explain to you in detail what the values mean in detail soon. But you can already find the values for all future (!) activities in the activity view, in the dataset (must be activated) and in the usual tools (trend analysis, ANOVA, sorting by search). - And you can find a short info about the values in our glossary.

We know that you would like to see the values for all past activities - so would we. But this requires the re-processing of many millions of activities. We have this on our radar and will let you know as soon as this is possible or available.

We have rebuilt, updated and extended our database infrastructure.

After a long time in beta status, the Grade Adjusted Pace (GAP) is finally here. We have made some adjustments to the calculation parameters and from now on we will show you the GAP for the running activities, for single laps and for climbs.

We have added the total distance to the shown streak (statistics 'plugin' below calendar view).

The full equipment table has a new column for the last use of each object.

Climbs are now available in the activity view. In addition, you can activate the number of climbs (and their categories) in your dataset for the calendar view.

Some weather conditions were wrongly assigned for data of the service provider darksky with us.

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.

Runalyze does now import and store all developer fields from FIT files. Read more at our blog.

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.

Athletes can now easily set up their account to provide all the data necessary for specific calculations. Read more at our blog.

There was a bug resulting in wrong best sub segments for power data in case of non-equidistant data. This behavior has been fixed.

Multisport sessions (e.g. Triathlon) with short transitions (less than one minute) led to false duplicates.

The sports panel did ignore the user's time zone when showing e.g. current week.

Our two new views for the current marathon shape and for the running performance status are now available for all users. Read more on marathon shape view and running performance status at our blog.

Plot tooltips in activity view did not respect imperial units.

It is now possible to recalculate TRIMP, VO2max and altitude for an individual activity.

You can now take over your complete history via Decathlon sync.

We have added support for incline data from Runn™ Smart Treadmill Sensor from North Pole Engineering.

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.

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.

The Google login did not work for everyone lately. We have fixed the issue by updating a third-party library.

Direct synchronization with Decathlon & Domyos E-Connected is now possible. Read more at our blog.

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).

Average power was added to the Climb Score view. You can switch between pace and power now.

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.

In view of the current situation and numerous cancelled events, we have organised a virtual Easter run. Read more at our blog.

Read more at our blog.

Polar sync now uses *.fit-files by default. The option to switch formats has been removed.

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.

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.

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.

Due to some recurring questions, we have added new glossary entries for rest days and calculated power.

When importing fit files, the device is now automatically detected in almost all cases.

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.

In rare cases an invalid vo2max correction factor was calculated.

After a recent change the generation of the images did not work anymore.

We have added the swim metrics total strokes and SWOLF to our anova and trend analysis tools.

The link to delete the account in the account settings was temporarily not available.

We have limited the maximum number of zones you can set per metric (heart rate, pace, power) to 20.

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.

The anova tool wasn't available after our latest internal framework update.

We have updated the framework we use internally.

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.

Power values have not been calculated if the imported file contained only zeros. This behavior has been fixed now.

Due to another uncommunicated change on Polar's side our history import for your Polar data did not work correctly.

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).

The Race Performance Chart has a new option to use the date as x-axis.

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.

Backups were not working since 4th December. This has been fixed now.

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 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.

xPower is a weighted average of your power output and serves as an alternative stress metric.

Read more in our glossary.

From now on the developer field "description" Suunto uses in FIT files is mapped to our description field in RUNALYZE.

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.

Exported activities (e.g. as tcx file) will now contain the correct laps instead of default 1k auto-lap.

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.

You can now also subscribe to the changelog as an RSS feed.

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.

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.

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.

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.

The start location is now automatically added to the "Route" field if the activity contains gps coordinates.

We have redesigned the publicly accessible pages such as the landing page, login and registration or our glossary and help pages.

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).

When syncing Suunto activities there were problems with the laps. We only support flat laps. This if fixed for all future activities.

Missing altitude values were wrongly imported as "0", which leads to different problems. These values are now imported correctly as unknown.

Illegally high speeds (e.g. due to errors in data recording) may have led to negative power values. This behavior is now suppressed.

Help articles will be automatically translated into German, French, Spanish, Portuguese, Dutch, Italian, Polish or Russian if we have not translated them yet manually.

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.

From now on we are storing all uploaded fit files. You can download them from every individual activity.

In the sports configuration, the individual equipment categories of a sport can now be viewed, assigned and removed.

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.

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.

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.

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.

Problem was caused by swimming heart rate, which is at the end of the file but belongs to the second session.

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.

As a preparation for scaling the activity import, activities from history import, API import and normal sync now end up in the same queue.

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.

Activity titles (as provided in some file types) will be used to guess the user's correct sport type.

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.

We have updated the framework we use internally by some versions.

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.

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.

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.

We are now able to provide a full history import (except third party activities and manual activities) from Garmin.

We have introduced a new Help and Support section at runalyze.com/help trying to answer the most frequent questions.