Skip to content

geopulse

Dashboards & Home Pages

An open‑source, privacy‑first Google Timeline alternative that turns GPS data from multiple sources into a searchable personal location history.

Java Latest v1.30.0 · 17d ago Security brief →

Features

  • Automatically converts raw GPS points into stays, trips and gaps (smart detection).
  • Supports many input sources – OwnTracks, Overland, GPX, CSV, Google Timeline imports, etc.
  • Integrates with Immich/Home Assistant to overlay photos on the map timeline.
  • Offers per‑user sharing controls, guest links and optional OIDC/SSO authentication.
  • Lightweight self‑hosted deployment via Docker Compose or Kubernetes/Helm.

Recent releases

View all 32 releases →
No immediate action
v1.30.0 New feature

Apprise notifications + mobile client

v1.29.1 New feature
⚠ Upgrade required
  • Regenerate timelines if affected by previous over‑matching issues; adjust `GEOPULSE_GEOCODING_CACHE_MAX_BBOX_AREA_KM2` for stricter matching as needed.
Notable features
  • Configurable `GEOPULSE_GEOCODING_CACHE_MAX_BBOX_AREA_KM2` with default 5000 km² to limit bounding‑box size
  • Automatic dropping of provider entries whose bounding boxes exceed the configured maximum
Full changelog

GeoPulse v1.29.1

This is a focused patch release that hardens reverse-geocoding cache behavior and prevents broad location over-matching caused by oversized provider bounding boxes.

Highlights

  • Added a bounding-box safety guard for reverse geocoding cache entries.
  • Oversized provider bounding boxes are now dropped automatically.
  • Added configurable maximum bbox area:
    • GEOPULSE_GEOCODING_CACHE_MAX_BBOX_AREA_KM2
    • Default: 5000 km²

In some datasets, very large provider bounding boxes could cause unrelated points to be matched to the same cached geocoding location. This patch reduces that risk and improves location grouping reliability.

Configuration

You can tune the safeguard with:

  • GEOPULSE_GEOCODING_CACHE_MAX_BBOX_AREA_KM2=5000 (default)

Set it lower for stricter matching behavior.

You might want to regenerate your timeline (Timeline Preferences -> Regenerate Timeline) if you're affected by this issue.

v1.29.0 New feature
Notable features
  • City/country normalization mapping on Reverse Geocoding page for standardizing location names
  • New travel achievements for trains and flights
  • "Open in Google Maps" action added to Friend Live tooltip
Full changelog

GeoPulse 1.29.0

This release focuses on better location quality, richer achievements, smoother map behavior, and stronger backend
stability.

New Features

  • Added city/country normalization mapping on the Reverse Geocoding page, so location names can be standardized more
    reliably. You can add rules how to rename existing and new country or city based on your preference / language.
  • Added new travel achievements for trains and flights, giving more milestone coverage as your trip history grows.
  • Added an "Open in Google Maps" action in the Friend Live tooltip for faster external navigation.

Improvements

  • Improved Friend Live UX by keeping your manual map position instead of forcing re-centering in case if the user
    moved mouse after selecting a friend.
  • Improved mobile readability on Timeline Reports with updated responsive table styles.
  • Upgraded Quarkus and backend libraries to current stable versions for better platform health and maintainability.

Bug Fixes

  • Fixed timeline edge cases by including short trips between stays, preventing disconnected stay-to-stay segments.
  • Fixed Friend Live e2e-related regressions and supporting test stability updates.
v1.28.2 New feature
Notable features
  • Added search capability for places during Trip planning
  • Displays last known battery level on Friends Live tab
Full changelog

GeoPulse 1.28.2

Re-implemented how we add new places during Trip planning

Improved how we add new places we want to visit during a Trip planning. Added option to Search the place, not only pointing it on the map

Added last known battery level on Friends Live tab

See https://github.com/tess1o/geopulse/issues/459

Do not fail when Admin deletes an invited user

See https://github.com/tess1o/geopulse/issues/457

v1.28.1 New feature
Notable features
  • Search option for Add Missing Timeline Data journey
  • Improved UI/UX for Edit Trip dialog
  • Photon enabled and fallback geocoding provider by default
Full changelog

GeoPulse 1.28.1

Added Search option on the [Add Missing Timeline Data] journey. You can search for the place from your selected Geocoding provider

When you're trying to recreate your timeline (when you don't have GPS data available) you can now search for places using Geocoding services instead of manually clicking on the map

Improved UI/UX for [Edit Trip] dialog

Made the datepicker smaller, fixed colors for datepicker in dark mode, etc

Improved UI validations on [Create Share Links] journey

When password doesn't match minimum length requirement we now show proper validation message

Made Photon enabled and fallback geocoding provider by default

Previously Nominatim was used as Primary provider and fallback was disabled. Now default settings (for everyone who did not override it) are: Nominatim - primary, Photon fallback. If you changed these settings previously - no changes to you

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

About

Stars
870
Forks
38
Languages
Java Vue JavaScript

Install & Platforms

Install via
docker helm

Alternative to

Google Timeline

Beta — feedback welcome: [email protected]