Dawarich - Package Updates

[Package Updates]

[1.17.2]

• Update dawarich to 1.12.2
• Full Changelog
• Dawarich Cloud can now credit sign-ups to affiliate partners. Self-hosted instances are unaffected both the tracking script and the attribution call stay off unless the Cloud-only PARTNERO_PROGRAM_ID and PARTNERO_API_KEY are set.
• Consolidated points table indexes: a new (user_id, timestamp, lonlat) unique index replaces three redundant indexes, roughly halving the write cost of every point. The index is built by the boot-time migration; on instances with millions of points this can take several minutes, during which the container waits before serving requests. The points table itself stays fully usable while the index builds.
• Automatic daily track generation no longer rebuilds a user's entire history when their tracks are missing and their history exceeds 100k points. On Dawarich Cloud such histories are backfilled automatically at a throttled rate; self-hosted instances still rebuild directly, as fast as their own hardware allows.
• The map no longer stays blank after an upgrade when the dawarich_public Docker volume still holds precompiled assets from an older version. The asset manifest now ships inside the app image instead of the public volume, the boot-time asset sync stages from inside the app directory (a tmpfs-mounted /tmp can no longer skip it), and the container logs a warning if the sync still cannot run. (#3346)
• User data exports no longer fail when a legacy place has no spatial coordinates. (#3344)
• The Tracks layer toggle on the map now reflects your saved setting after a page reload; previously it always showed as off even though the setting was saved and tracks were loaded. (#736)
• The map no longer leaps to a just-left place or a phantom spot off your route: iOS visit reports delivered after departure and coarse cell-tower fixes without motion data are now filtered out as anomalies. Existing histories are re-evaluated automatically after the upgrade, and tracks and stats are rebuilt along the way.
• The Family page no longer fails to load, and the family map no longer places a member at the wrong spot dated 1970, when someone's history contains legacy points missing a timestamp or coordinates. Such points are also left out of shared location history, and a member whose points are all incomplete is omitted from the map rather than shown somewhere wrong. (#3254)
• Google Timeline phone exports no longer lose altitude, accuracy and speed on points taken from the rawSignals section those fields were read from the wrong nesting level and came back empty. Points already imported keep their empty values, and importing the same file again skips them; delete the old import first, then import the file again. (#3337)
• Daily and monthly distance no longer counts a jump across a tracking gap longer than your "minutes between routes" setting when the two points come from different imports, from live tracking, or from a photo integration (Immich, PhotoPrism, Google Photos). Points inside one imported file still count as continuous history regardless of gaps, so sparse sources such as Google Timeline keep their full distance. Existing months keep their old numbers run Map v2 Settings Recalculate tracks & stats once after upgrading to apply the fix to past months. (#2689)

[Package Updates]

[1.18.0]

• Update dawarich to 1.13.0
• Full Changelog
• The map has a new opt-in "Tiled rendering" beta in map settings: the points layer is drawn from vector tiles built by the database, so the browser only downloads what the current view needs. Dense areas arrive as aggregated markers carrying a point count the heatmap weighs them accordingly and long date ranges over large histories pan and zoom smoothly instead of stalling on one huge download. On a test account with 1 million points, opening the full three-year history classically pulls the whole range up front 992 requests and roughly 590 MB of JSON, which crashed the browser tab a third of the way in; tiled rendering drew the same city view from 12 requests and 146 KB in a fraction of a second, and re-opening the map shortly after costs no requests at all. Individual points keep their popups, though a merged marker has no single point to open zoom in to separate it. Dragging points to edit them is unavailable while tiled mode is on, and turning on Routes, Fog of War or Scratch map temporarily switches back to classic loading (the settings panel says which layer is blocking). Tiles are cached privately in the browser and refresh automatically when your location history changes, so the live trail can lag up to five minutes behind. (#2691)
• Removed three superseded points indexes (the old dedup index and two composites) now that the consolidated (user_id, timestamp, lonlat) index from 1.12.2 serves their queries. The migration cleans up any invalid leftover index first, rebuilds the consolidated index automatically when an interrupted build left it invalid, and refuses to run only when it is missing entirely. Frees several gigabytes on large instances and further reduces the write cost of every point.
• The nightly cache preheat now runs as one background job per user instead of a single job looping over every user. Its duration is bounded by the slowest individual user rather than by the sum of all of them, so one account with a large history no longer delays the preheat for everyone else. On Dawarich Cloud it now only preheats active and trial accounts; self-hosted instances continue to preheat every user.
• Four scheduled jobs (app version check, cache preheat, family location request expiry, points counter correction) were queued onto default instead of the queues their job classes declare, so they competed with higher-priority work the cache preheat in particular could hold up imports, track generation and stats for minutes at a time. They now run on app_version_checking, cache, families and low_priority respectively.

[Package Updates]

[1.18.1]

• Update dawarich to 1.13.1
• Full Changelog
• The mobile apps can now use the family feature: see who is in your family, who is sharing their location, and respond to location requests. New endpoints: GET /api/v1/families/mine, PATCH /api/v1/families/sharing, POST /api/v1/families/location_requests, and POST /api/v1/families/location_requests/:id/accept and /decline. The overview carries no coordinates locations stay in the existing family locations endpoints.
• Tracks are now served as vector tiles from GET /api/v1/tiles/tracks/:z/:x/:y.mvt.
• Saving family sharing settings without picking a duration no longer turns a timed share into a permanent one, and re-enabling a lapsed share restores its duration.
• Each account can now pick its own geocoding provider Photon, Geoapify, Nominatim or LocationIQ under Settings Integrations, with a button to test it. The PHOTON_API_HOST, GEOAPIFY_API_KEY, NOMINATIM_API_HOST and LOCATIONIQ_API_KEY variables keep working and take precedence.
• A custom basemap that covers only part of the world can now fill the gaps with the built-in tiles. Turn on "Fill gaps with the default basemap" under Custom Basemap URL. It is off by default, because filling the gaps means requesting tiles from Dawarich's tile server.
• Geocoding settings now take a requests-per-second limit, and lookups are paced to stay inside it, so a bulk backfill no longer floods a server that asked for one request a second. komoot is pinned to its published 1/s and ChibiGeo to your plan's limit. Set the same ceiling instance-wide with REVERSE_GEOCODING_RPS, and raise REVERSE_GEOCODING_CONCURRENCY if your provider has no limit worth respecting. (#3343)
• Device and importer details are no longer repeated on every point, which noticeably shrinks large histories. Existing points are migrated by a background job after upgrading; on millions of points expect it to run for hours and the database to grow temporarily first. Nothing changes in the UI while it runs, and it can be re-run at any time to pick up rows it has not reached. Adding the linking column briefly locks points at startup; an instance with heavy write traffic that cannot get the lock defers the change to a background job, so booting still completes. To opt out, set SKIP_POINT_DIMENSION_BACKFILL=1 before migrating, on every service including Sidekiq.
• Tiled rendering (beta) now covers Routes, Tracks and Fog of War, leaving only the Scratch map on the classic full download. Under tiles, routes are colored per track, the route-splitting sliders no longer apply, and clicking a track opens its details.
• The vector tile query timeout is now configurable with VECTOR_TILES_QUERY_TIMEOUT_MS (default 5000 ms), for self-hosted instances where very large date ranges exceeded the old limit. (#3386)
• The Integrations settings page shows one service at a time, picked from a sidebar, each with a connection indicator. Geocoding settings moved here from their own tab; the old address redirects. (#3393)

[Package Updates]

[1.19.0]

• Update dawarich to 1.14.0
• Full Changelog
• PATCH /api/v1/settings/mobile now takes a row lock around its read-merge-write, so a mobile settings change no longer discards a concurrent write to another settings section or from another device.
• Dawarich can now be used in Polish: pick it under Settings General. Thanks @Kliiper for the translation! (#3357)
• Dawarich can now be used in Catalan: pick it under Settings General. Thanks @ArnyminerZ for the translation! (#3349)
• API for getting geodata extracted from mobile phone photos

[Package Updates]

[1.19.1]

• Update dawarich to 1.14.1
• Full Changelog
• Point reads the API responses, the map's point payloads and the user-data export now serve the device and importer metadata (tracker, topic, connection, battery state and friends) through the point_sources reference table on rows linked to it, with the original columns still serving unlinked rows. Payloads are unchanged; this is groundwork for slimming the points table itself.
• OwnTracks in HTTP mode now shows your family members on its own map: every location upload is answered with the latest position of each family member sharing with you, so they appear as friends in the app alongside the Dawarich map.
• AirTrail flights now show as their own figure on the monthly stats page and in the monthly digest. Flight distance is reported next to the distance Dawarich tracked rather than added into it, so neither number changes meaning.
• Importing a user-data export no longer mis-stores the OwnTracks region columns (inrids, in_regions the export writes them in Postgres array notation, and the importer previously passed that notation through, which also linked such points to a device signature that matched nothing.
• Track generation no longer reports a failure when its temporary progress session expires during finalization.
• Trip distance recalculation no longer fails when the computed distance exceeds the 4-byte integer limit, which GPS noise on a long trip can produce.
• Integration settings now show bounded connection errors instead of failing when an upstream service returns an oversized malformed response.
• Enhanced import extraction now retries transient database deadlocks instead of failing immediately.
• A malformed or truncated upload no longer returns a server error; the API now rejects it cleanly.
• OAuth sign-in now shows clear retry guidance while an account with the same email is still being deleted.

[Package Updates]

[1.19.2]

• Update dawarich to 1.14.2
• Full Changelog
• GPX waypoints are now imported as places, so a favourites.gpx exported from OsmAnd+ and similar apps no longer imports as nothing at all. Each waypoint's category becomes a tag, re-importing an updated file does not duplicate anything, and waypoints never become timeline points, so they do not affect your distance or statistics. (#1261)
• The API now accepts visits in batches: POST /api/v1/visits/batch takes up to 100 visits in one request and reports each one's outcome separately, so a single rejected visit no longer costs the whole sync. The mobile apps previously had to send one request per detected visit.
• Starting a Family plan now creates your family automatically, with location sharing on, and the family page walks you through inviting your first member.
• Family members you invite are set up on the Pro plan for as long as your plan runs, and are emailed an explanation when it ends. Changing your own plan does not cut them off early: they keep access until the period you have already paid for runs out.
• The "Max Gap Between Points" setting has been removed. It existed to compensate for the city-duration bug fixed below, and its lowest values were the ones that hid cities; how long a tracking silence still counts as staying put is now handled consistently for everyone: a silence of up to seven days that starts and ends in the same city counts as time spent there, unless points recorded in between show you moving at flight speed, which ends the stay. "Min Minutes in City" is unchanged.
• Cities where you stayed but your phone reported infrequently are counted again. Time spent in a city was measured from how often your device sent points rather than from how long you were there, so a stationary phone saving battery could be credited no time at all and drop the city including your home city from statistics and from the map's visited-cities view. Recalculated months will generally show higher numbers than before. Existing months keep their old numbers until recalculated: press "Update stats" on the Stats page. (#2207)
• Changing "Min Minutes in City" now recalculates your existing statistics, instead of leaving old numbers in place until you refreshed them by hand (#2207).
• Photos are now matched to a trip or map range on the photo's UTC timestamp rather than its local wall-clock time. Previously a trip could hide photos taken in its final hours, drop one taken exactly on its start or end boundary, or when it began or ended near midnight lose photos before they were even fetched. A photo with a missing or unreadable timestamp is now skipped instead of failing the whole fetch. (#1137)
• Route videos now play forwards. When the map was showing Tracks rather than Routes, the video studio drew the day in the order the tracks API returns them newest first so the route animated from evening back to morning while the clock counted forwards.
• Restoring a user-data export no longer reports success while importing nothing. An archive carrying a point column this version no longer has aborted every batch; unknown columns are now ignored and the points are restored.

[Package Updates]

[1.19.3]

• Update dawarich to 1.14.4
• Full Changelog
• Manual OIDC endpoints and signing keys can be configured without changing existing discovery setups.
• Place tag filters remain applied after returning to the map or reloading it.
• Statistics include valid segments crossing midnight and older calculations are scheduled for repair.
• Dawarich can now be used in Simplified Chinese: pick it under Settings General. Thanks @AwHsR15 for the translation! (#3354)
• TeslaMateApi can now sync completed-drive positions from every configured car into Dawarich, manually or once a day.
• GET /api/v1/users/me now returns a top-level features object, and GET /api/v1/families/mine answers 200 with lapsed: true when a family membership outlives its entitlement.
• Stored monthly and daily stats are now rebuilt automatically after a calculation change, so historical distances no longer need a manual Update all stats. Changing your timezone rebuilds them too. (#2069)
• Traccar latitude/longitude form uploads now save points, including Unix timestamps in seconds or milliseconds. (#3299)
• Speed coloring in tiled maps now reflects individual route segments when zoomed in, instead of the average speed of the whole track. (#3425)
• Pages no longer wait for GitHub when checking for a newer version; update checks now run only in the background and ignore stale releases cached before an upgrade (#3485)

[Package Updates]

[1.19.4]

• Update dawarich to 1.14.5
• Full Changelog
• Video Studio can select exact start and end times for map ranges.
• Video Studio adds a Fog of War mode with adjustable overlay colour and opacity, independent route and marker visibility, and preview buttons for visualization modes and output formats.
• Family members can consent to sharing location history recorded before they started sharing.
• The import edit page can change or clear an import's source.
• Visit detection no longer sends a notification for every new suggested visit.
• Poster Studio waits for the map to load the selected date range and disables the studio switch while loading.
• Yearly digests for cloud-Lite users read seasonality and country time spent from the same data window as monthly distances and toponyms.
• The per-email API login brute-force throttle now counts application/json request bodies, so password grinding against POST /api/v1/auth/login is bounded per account even when an attacker rotates source IPs.
• API sign-in ignores leading and trailing spaces in the email address.
• Manual OIDC configuration falls back to the default port when OIDC_PORT is blank, non-numeric or out of range.

[Package Updates]

[1.20.0]

• Update dawarich to 1.15.0
• Full Changelog
• Trips can be imported from TREK (Settings Integrations). A TREK trip shows its plan above the recorded days, a trip with nothing recorded yet draws the planned stops on its map and card preview, a recorded trip can lay its plan over the track, and TREK day notes fill in the trip's day notes and stay in sync until you edit them in Dawarich. (#3615)
• Admins can configure geocoding for the whole instance in Settings Instance without a redeploy, and test the connection there. A set environment variable still wins and shows its field read-only.
• Map points and tracks can be edited directly over the vector-tile renderer; a completed drag atomically saves the point, recalculates its track and segments, and synchronizes other open sessions. With Edit points on, a point can be dragged straight from the map at zoom 14 and closer, a long press starts the drag on touch screens, and an edit history panel on the map undoes and redoes the last 5 moves.
• The main map now always renders points and tracks from vector tiles. The classic renderer, its rendering preferences, and the separate main-map Routes layer have been removed; Trip day routes are unchanged.
• Geocoding is no longer configured per user: it moved from Integrations to Settings Instance, and Integrations links there. On upgrade, environment variables that are set are copied into Instance settings, so removing one later keeps its value; without a provider variable, existing per-user settings are carried over when every user agrees on one, or else when the administrators do, and Settings Instance says when they were not. Per-user settings themselves are left untouched.
• Installation guides moved out of the repository's docs folder to dawarich.app/docs: Synology (with its compose and .env templates), Kubernetes, Docker, reverse proxy and photo geodata.
• A trip recorded by several devices at once no longer zigzags between them: its line, distance and day routes follow the busiest of the devices that were recording at the same time. Devices that recorded one after another GPX segments, imported activities, a phone swapped mid-trip all stay on the trip. For trips calculated before this release, press Recalculate on the trip page to update the saved route and distance.
• User profile archives uploaded through the regular Imports page are now restored as profile backups instead of failing the multi-file archive size limit. (#3011)
• Trip and track distance is calculated in the database, so large trips no longer run out of memory and leave the distance empty. Press Recalculate on an affected trip to fill it in.
• Days per Country now uses a more varied color palette so countries are easier to distinguish (#3602).

[Package Updates]

[1.20.1]

• Update dawarich to 1.15.1
• Full Changelog
• Map track lines, including the highlight shown after clicking a track, now respect the selected date range, so Today and custom searches no longer show portions of overlapping tracks from outside that range. (#3679)
• A position far off your route is now flagged as an anomaly even when the tracking app uploads one point at a time: it is judged again once the next point arrives, instead of staying on the map until the anomaly filter is re-applied. (#3664)
• The family map no longer draws a member's points that were flagged as anomalies: their history trail, their "last seen" marker and the locations sent to OwnTracks friends skip them, as the member's own map already does. (#3663)
• Opening monthly insights no longer fails when concurrent requests create the same digest.
• Immich photo enrichment now interpolates positions along the globe instead of across flat latitude/longitude coordinates, so photos taken near a pole or the antimeridian receive the correct location (#3262)

[Package Updates]

[1.20.2]

• Update dawarich to 1.15.2
• Full Changelog
• Add an experimental read-only MCP endpoint at /api/v1/mcp for Pro and Family plans (and every self-hosted user), authenticated with the existing API key as a bearer token. MCP clients can read a timeline of up to 7 days, the latest location, and search visits by place, city, country or area name. See the MCP documentation.
• Exploration achievements: every country gets a collectible card, and 183 of them a grid of their first-level regions. A region counts as explored once time spent inside it passes your "minimum minutes spent in city" setting, so pass-throughs don't count. Earned regions are never revoked. Behind the achievements feature flag. (#3121)
• Updating a point's coordinates through PUT /api/v1/points/:id refreshes its country and looks its address up again, as moving it on the map already does, instead of keeping the old city. (#3121)
• Point uploads now accept Unix timestamps and return a validation error for malformed timestamps instead of failing internally.
• Account deletion no longer fails when saved posters, route videos, flights, notes, service settings, or suggested-place links remain.
• SMTP delivery and other outgoing connections now use a host's IPv4 address when it has one, so they work on servers where IPv6 is configured but not routable. Integration URLs are checked against every address their host resolves to, and integration URLs with a bracketed IPv6 address such as http://[fd00::5]:2283 are accepted (#3591).
• Map v2 route-gap settings now accept custom distances and durations above the former 5,000m and 180-minute slider limits. Trip maps and shared trip links split day routes by your saved time gap instead of a fixed 60 minutes. (#3381)