This is a major release that introduces several new features and integrations, including Map Matching for cleaner trip routes, Backup & Restore with scheduled automatic backups, embeddable shared locations, custom reverse geocoding providers, and more.
🗺️ Map Matching
See the detailed explanation in #589.
Map Matching makes trip routes easier to read by aligning noisy GPS points with roads and paths from OpenStreetMap. Instead of displaying every GPS wobble or inaccuracy, GeoPulse can show a cleaner route that follows the path you most likely traveled.
Important
Map Matching is a display-only feature. Your original GPS points remain unchanged, and GeoPulse continues to use the raw GPS data for timeline detection, trip classification, exports, analytics, and other processing.
How to enable it
First, an administrator needs to configure Valhalla under:
Menu → Admin Settings → Map Matching
The administrator can then enable Map Matching globally and, optionally, enable historical backfill to process existing trips.
Once enabled globally, each user can turn on Map Matching in their profile:
Menu → Profile → Display → Enable Map Matching
Example
Without Map Matching — raw GPS data
Notice the upper part of the route near the corner, where the GPS path does not properly follow the road.
With Map Matching
The route now follows the road much more closely.
In the timeline UI, you can switch between:
- Map Matched — the matched route
- Raw GPS — the original GPS points
- Comparison — Map Matched route as a solid line and Raw GPS as a dashed line
💾 Backup & Restore
See #590.
GeoPulse can now create and restore full application backups, including your data and configuration, directly from the Admin UI:
Menu → Admin Settings → Backup & Restore
You can:
- Create backups manually
- Download a backup directly
- Store backups in the configured backup directory
- Restore GeoPulse from an existing backup
- Configure scheduled automatic backups
Important
To store backups on the server, you need to mount a backup directory into the GeoPulse container.
For example:
volumes:
- ./backups:/data/geopulse-backupsNew Docker Compose files already include this configuration. Existing installations need to add the volume manually.
You might also need to fix permissions to make the backup folder writable by geopulse backend. Check documentation for more information.
mkdir -p backups
sudo chown -R 1001:0 backups
sudo chmod -R g+rwX backups
Note
All backups are password-protected because they may contain sensitive personal data and configuration.
📖 Backup & Restore Documentation
User interface
🔗 Embeddable Shared Locations
See #594 for examples and screenshots.
Shared locations can now be displayed in an embedded view without the regular GeoPulse menus, navigation bar, and other UI elements.
This is useful when you want to display a shared map + timeline, or just the map, inside another application or website — for example, a Home Assistant dashboard.
Embedded mode can be configured when creating a Share link.
🌍 Custom Reverse Geocoding Providers
See #591.
The Geocoding administration page now supports adding custom reverse geocoding providers:
Menu → Admin Settings → Geocoding
You can configure any Nominatim- or Photon-compatible API as a reverse geocoding provider.
This makes it possible to build more flexible setups. For example, you can use a public Photon server as your primary provider and a self-hosted Photon instance as a fallback — or vice versa.
Previously, GeoPulse supported configuring only a single Photon instance.
🛠️ Fixed MultiJson Support for GeoJSON
See #586.
Fixed GeoJSON import support for MultiJson data.