location

GPS location tracking logs places you visit by recording pings into a per-user location database. You can save, update, and delete named places with coordinates and radius, then inspect visit statistics and movement patterns via CLI commands.

Yes, calendar attendance integration cross-references GPS pings with CalDAV calendar events. By supplying optional CalDAV credentials, the system matches your physical location data against scheduled events to confirm attendance automatically.

Cluster discovery identifies groups of stationary GPS pings that have not yet been saved as named places. You can dismiss unwanted clusters to avoid repeated suggestions, managing discovered zones through CLI commands or the web UI.

Yes, the framework geocoding cache requires the ISTOTA_DB_PATH environment variable to be set. This cache supports the per-user location database by querying external geocoding services to resolve coordinates into readable addresses.

You can inspect recent GPS pings and filter location history by date using CLI commands. This allows you to trace movement patterns and review personalized insights derived directly from the per-user location database.

Yes, the place-stats subcommand calculates visit statistics for your saved places. It reads from the per-user location database to summarize how frequently you visit specific named locations, including coordinates, radius, and notes.