Open map settings
Open Map, then review the personal data layers.
Private GPS heatmap
See where your archive is most concentrated.
Turn imported activities into a density layer on your own map. The heatmap follows the active track filter, so you can compare selected activities, years, areas, or custom groups.
Enable the layer from the map.
The heatmap can be shown with the normal GPS track lines or used on its own.
Turn on Heatmap
Enable the density overlay. It uses the tracks in the current active selection.
Adjust opacity
Change the heatmap strength so the background map and track lines remain readable.
Change the filter
Select a different activity, year, or saved filter and the density view updates to the same subset.
Filter-aware density
Ask focused questions of the same archive.
Heatmap selection is shared with the normal map, track browser, statistics, related tracks, and segment analysis.
- Compare cycling, hiking, running, or other activity groups.
- Limit the view to one year or a selected time period.
- Use geographic or SQL-backed custom filters.
- Review the new density after importing or removing tracks.
Keep the activity archive on your host.
The heatmap is derived from tracks indexed by your MTL Explorer instance. It does not require publishing the activity history to a social fitness service.
Private track source
Your activity files and processed archive remain in the directories and database controlled by your installation.
Optional local maps
The standard setup can use hosted background map tiles. Enable the local map sidecar when the basemap should also stay on the host.
No public profile
The core heatmap workflow does not require an external account, public activity page, or shared GPS history.
Same access control
The heatmap is part of the authenticated MTL Explorer interface and follows the instance login configuration.