geopulse

v1.29.1 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 27d Dashboards & Home Pages

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

gps-tracker gps-tracking java owntracks postgis postgis-database

+7 more

postgresql privacy quarkus quarkus-native self-hosted timeline vue3

Summary

AI summary

Added a configurable maximum bounding-box area guard that drops oversized provider bounding boxes, reducing over-matching in reverse-geocoding cache.

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.

View diff on GitHub

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.

Share this release

Share on X Share on Bluesky

Track geopulse

Get notified when new releases ship.

About geopulse

A self-hosted, privacy-first location timeline platform: an open-source alternative to Google Timeline with automatic trip detection, Immich integration, and rich analytics.

All releases →