MTL Explorer Release v.0.9.0

Released

On this page

Improved segment comparison and replay, route planning with saved places, and optional health data.

Changes since v.0.8.1, ordered by user impact.

Important before updating

An in-place upgrade should work. For this release, we recommend a fresh PostgreSQL database to rebuild derived data consistently.

Back up before resetting: a reset deletes saved plans and manual edits. Preserve anything you need, then start with a fresh database. Keep original GPS and media files and other data folders. See Updating for the installation guide.

Calories and energy estimates

See calorie estimates.

Segment comparison and replay

See segment analysis.

GPS reliability and review

See Review and motion analysis.

Maps and points of interest

Route planning

Google Health beta

Automatically match heart rate to GPS tracks from independent devices. Record GPS on a Garmin and heart rate on a Fitbit, for example. MTL Explorer matches recorded times after import, without device pairing or manual linking.

The optional, read-only connection also imports exercise, sleep, steps, daily activity, body measurements, and health observations. Available data depends on your account and devices.

Setup requires your own Google Cloud project with Google Health API access and a Google Account linked to an active Google Health profile. Google may limit new API projects; check the setup requirements before you start. The supported personal setup uses Testing mode, which requires reauthorization after seven days. Imported history stays available. Setup and sync may still encounter errors or interruptions.

See the Health guide.

Filters and statistics

See media filtering.

Photos and video

Settings and background processing

Updating

Read the database notice above before upgrading. Review the updated installation guide for custom mounts and configuration, then follow Updates.

All releasesView on GitHub