Heart rate on tracks and segments
View heart rate beside elevation and other track graphs. Check average heart rate for a whole track or a selected segment. This needs a track with timestamps and heart-rate data for the same time.
Optional Google Health connection (beta)
Bring your health records into your own archive.
Combine your GPS tracks with heart rate. Browse activity, sleep, and health trends in your own MTL Explorer installation.
Google Health is a beta feature. Setup and synchronization may still encounter errors or interruptions.
API access prerequisite. You need your own Google Cloud project with Google Health API access. Google may limit new API projects. Check Google's current setup requirements first. Your Google Account must also be linked to an active Google Health profile.
The personal setup uses Google's Testing mode, so you need to reconnect once a week. Your stored data stays. See Google's token-lifetime documentation.
Recorded separately. Viewed together.
Record a ride on your Garmin and wear your Fitbit. Import the track and connect Google Health. MTL Explorer automatically matches the available heart-rate samples by time, even if they were never part of the GPS recording.
Health trends
Browse steps, sleep, resting heart rate, and body measurements. Choose a date range and group charts by day, week, month, or year.
Automatic sync
Keep a local copy of available records. Sync starts with recent data and then works back through your history. Exercises with a GPS route are added to your tracks.
Browse the records
Filter stored records by type, source, and date. Open a record to see its details and check which periods are available.
Data availability depends on your device and what it shares through the Google Health API. The connection is optional and read-only. When synthetic health data is enabled, the demo shows generated records and matching track heart rate. It cannot connect to a Google account or run live Google synchronization.
The current app with synthetic data.
Captured from MTL Explorer on 3 October 2026. These are real application screens with generated records; no personal health data or Google account is used. Select an image to view its full resolution.
The connection stays installation-specific.
MTL Explorer does not operate a central Google Health account or data service.
Separate OAuth client
Each administrator uses their own Google Cloud project with API access and a Desktop OAuth client for their installation.
Read-only access
The connector requests read-only scopes. It does not add, edit, or delete records in Google Health.
Direct connection
The self-hosted server exchanges tokens and reads records directly from Google. The MTL Explorer project does not receive them.
Local controls
You can disconnect Google, delete the local copy, and revoke access in your Google Account.
Data requested by MTL Explorer.
The connector requests four Google Health read-only categories. The user reviews these permissions during Google consent.
Activity and fitness
Exercise, activity, steps, distance, energy, and related summaries supported by the API.
Health measurements
Available body measurements, observations, vital signs, and exact heart-rate samples.
Sleep
Sleep sessions and their available stages or measurements.
Location
Route points attached to exercise records. Valid routes can be imported as locally managed tracks.
Use of these shared pages.
These URLs may be referenced by personal, self-hosted MTL Explorer OAuth clients when this information accurately describes the installation.
This permission does not grant domain ownership or Google verification.
Public services, materially changed integrations, and rebranded products should publish their own information on a domain controlled by their operator.