Dawarich - Package Updates

[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)

[Package Updates]

[1.20.3]

• Update dawarich to 1.15.3
• Full Changelog
• Trips can be shared privately with family members, who see them in their trip list and a read-only map. Access follows family membership, sharing settings and privacy zones. (#3751)
• Account settings allow editing first and last names. Family maps use these names when available and fall back to email. (#3748)
• Trip pages link to the full map for the exact trip interval, preserving seconds in the date filters. (#3756)
• Shared achievement links now show a preview of the achievement card with its geography and progress. (#3721)
• Exploration achievements and printed poster ordering are available to everyone without feature flags. Existing location history is checked in the background without sending old unlock notifications. Printed poster ordering remains unavailable when PRINT_ORDER_URL is blank.
• Geocoding jobs keep their duplicate-work guard through long queues and retries, and nightly scheduling no longer queues the same pending points again. (#3754)
• GPX exports work when an older database lacks the decimal-altitude column, while retaining decimal precision when it is available. (#3752)
• Archived Immich photos are excluded from map and trip results, including results previously cached before the fix. (#3740)
• Point markers overlapping routes remain selectable. Markers with multiple points zoom until one point can be selected, and never offer to delete an arbitrary point. (#3719)
• GET /api/v1/users/me returns the user's id, as the API documentation describes. The mobile app needs it to link in-app subscriptions to the right account.

[Package Updates]

[1.21.0]

• Update dawarich to 1.16.0
• Full Changelog
• Self-hosted users with an active Pro purchase in the Dawarich mobile app now get the supporter badge. The app reports the purchase to your instance automatically; Dawarich Cloud ignores it.
• POST /api/v1/visits accepts an optional address (street, house number, postcode, city, country). A newly created place stores it, and visit responses include the place's formatted address, so apps can keep a visit's name and address separately.
• Insights show route maps on the year cards. Pro and self-hosted instances also get a year calendar coloured by country, a country timeline and a race against the previous year's distance; Cloud Lite shows a plain activity calendar and a preview of the race.
• Search trips by name, description, places and notes; sort them and filter by year, month and country.
• Visitors opening / go to the sign-in page; the landing page is removed. Sign-in and sign-up pages are redesigned. Uptime checks that probe / now get a redirect; point them at /api/v1/health.
• Achievements no longer credit any country or region for time spent in territories claimed by more than one state (Natural Earth disputed areas), and achievement cards leave those areas out; statistics, the scratch map and country attribution are unchanged. Regions lying almost entirely in such territories are no longer part of their country's set. Existing progress is recalculated in the background without notifications, and achievements already earned are kept. The upgrade loads the disputed-area boundaries and recalculates achievements once in the background; on large instances this can take a while.
• Merge duplicate legacy points before coordinate backfill so upgrades complete without unique constraint errors (#3200). On large instances still carrying legacy coordinates this step can take several minutes; let it finish.
• KMZ imports no longer repeatedly re-import their own archive and fill the import queue and storage (#3766).
• Prometheus metrics from web and Sidekiq no longer produce duplicate series when label order differs (#3769).
• Achievement backfills now restore historical visit dates, including previously earned regions and countries (#3728).

[Package Updates]

[1.21.1]

• Update base | final to 6.0.1
• security: fix eMudhra cert compromise

[Package Updates]

[1.22.0]

• Update dawarich to 1.17.0
• Full Changelog
• Import your check-in history from a Foursquare Swarm data export. Upload the whole export archive or its checkins*.json files: every check-in becomes a point, and every check-in at a venue becomes a visit at a place named after that venue. A visit lasts until your next check-in, at most two hours. The other files in the archive (tips, photos, ratings) are skipped.
• The app container in the default docker/docker-compose.yml is limited to one CPU core instead of half a core, since it also runs background jobs. Set APP_CPU_LIMIT to change it.
• The Docker image now ships Node.js 22 LTS from the official Node.js build instead of Debian's Node.js 20 package, which no longer receives upstream security fixes. Node.js runs the server-side poster renderer. #3888
• The points page and the points API page through large accounts much faster.
• Reverse geocoding gets through a backlog faster: it uses as many background threads as your provider's rate limit allows and keeps its connection to the provider open. If you use Geoapify, LocationIQ or the public Nominatim, set a requests-per-second limit in the geocoding settings or REVERSE_GEOCODING_RPS, since Dawarich does not limit those providers on its own.
• Visit detection and track generation need less memory and fewer database queries, and the place-name refresh skips months where nothing changed.
• Polish counts use the right plural form, for example "3 kraje" and "5 krajw" instead of "3 krajw" and "5 kraju". This also fixes relative times such as "okoo 3 godziny" and labels on the map.
• Trips with long recordings open quickly: the trips list, trip page, trip form and shared trip page draw routes from map tiles instead of sending every recorded coordinate, and the trip page loads points only when you open Replay, the poster or the video studio (#3867, #3783)
• Overnight stays where the phone goes quiet, for example arriving home in the evening and leaving in the morning, are now suggested as one visit across the silence instead of a few minutes after arrival. Choose Re-run detection on full history on the Visits page to fix past stays.
• Points synced from TeslaMate now get suggested visits; choose Re-run detection on full history to cover earlier drives. On Dawarich Cloud, trial accounts are now included in the nightly visit run.

[Package Updates]

[1.23.0]

• Update dawarich to 1.18.0
• Full Changelog
• Back up your database before upgrading. After the upgrade, background jobs turn Areas into Places and tidy up visit names, repair tracks from the last 12 months, recalculate months with flights and update your existing digests, recheck the Italy achievement, and detect visits again across your whole history. Rolling back does not undo this. Keep Sidekiq (or embedded jobs) running until they finish; on a small self-hosted server you can skip the visit detection by setting SKIP_VISITS_FLEET_REDETECT=1 and start it later from Visits Re-run detection on full history.
• Geofencing. Turn on "Notify on enter and leave" for a Place, and Dawarich records when you arrive and when you leave, using the points your phone or tracking app sends. Places that used to be Areas keep notifying. You'll find the events in Settings Geofencing. #2515
• Geofencing webhooks. Send every arrival and departure to Home Assistant, Node-RED, n8n or your own service. Each webhook can follow some places or all of them, shows its recent deliveries and can send a test event. Events that reach Dawarich more than 15 minutes late are logged but not sent. A webhook that fails five times in a row is switched off, and you get a notification. On Dawarich Cloud, webhooks need a Pro or Family plan and an https address, and send up to 60 events an hour. Self-hosted instances have no such limits. #2515
• Privacy zones now also hide your data on your own map, trip pages, route replay and posters, not only on shared links. A track that crosses a zone is cut at its edge. The hidden area is a little larger than the radius you set and shifted off-centre, so the place itself can't be pinpointed. Exports and statistics keep your full data. #2848
• Areas are now Places with a Visit Radius (up to 50 km) and keep their notes and visits. The Create Area tool is gone: create a Place with a Visit Radius on the map or from a visit instead.
• Breaking: a Visit's place is null when the visit has no Place or Area. Visits add display_name, custom_name (the stored name, if any) and location_label; name still holds the name to show. Sending both place_id and area_id returns 422.
• Flights synced from AirTrail now count toward your distance everywhere: Insights, the stats pages, each month's daily breakdown, digests and the API. Before, a flight only showed up on its own month's card. A month's page and each year card show how much of the total was flown, and points tracked during a flight no longer count on top of it. Months with flights, and the digests you already have, are recalculated in the background after the update. Thanks @darioackermann! (#3659)
• Map points for a single day load again in places where you have years of history, such as home. The map used to show "Could not load map tiles". (#3830)
• Tracks no longer have gaps or straight lines where points arrived late, for example from an import or a sync with another app. The last 12 months are repaired in the background after the update; for older gaps, use Recalculate tracks & stats. (#3794)
• Background Jobs dashboard actions (Delete, Retry, Kill, Clear) no longer fail with "Forbidden" when Dawarich is opened over plain HTTP on a local network. (#3907)

[Package Updates]

[1.23.1]

• Update dawarich to 1.18.1
• Full Changelog
• The Select data on map tool can now look across all your data. Turn on "Select data from all time" in the Tools panel before drawing the rectangle to get every point and visit in that area, whatever dates the map shows. When an area holds more than 10,000 points, only the most recent 10,000 are shown and a notice says so. On the Lite plan, "all time" covers the last 12 months. (#3873)
• The map runs on MapLibre GL JS 6.16.0. MapLibre now draws Arabic and Hebrew labels itself, so the separate right-to-left text plugin is no longer loaded.
• Searching for a place in the visit edit panel finds nearby places again when you type the name, for example the Burger King next to the visit. Before, typing word by word with a geocoding provider limited to one request per second, such as the public Photon server, often skipped the final search, so only saved places with that name somewhere else in the world showed up. The search now tries once more a second later. (#3590)
• Reverse geocoding through ChibiGeo uses HTTPS even when PHOTON_API_USE_HTTPS is not set. Before, a host written with a path, such as app.chibigeo.com/v1/photon, was not recognised as HTTPS-only, so Dawarich sent its requests over plain HTTP and they failed. (#3108)
• Points that arrive late inside an existing route, for example through the API or an import, now join that route instead of staying a separate line, also when they come from a device without a name. A route that gains points keeps its shared links and corrected transport modes. (#3036)
• Countries you only flew over no longer count when the flight comes from a KML file without speed data, such as a Flightradar24 export. Speed is now worked out from the time and distance between points. KML files imported earlier are updated in the background after the upgrade, and their monthly statistics, digests and trip countries are recalculated. (#3900)
• Signing in with two-factor authentication works again when the sign-in page is shown in a language other than English. Before, the code prompt appeared in English and was immediately replaced by an empty sign-in form. On installations with OIDC-only sign-in, the message that password sign-in is disabled now uses that language too. (#3908)
• The Prometheus /metrics endpoint works again on 1.18.0. Every scrape used to fail with a server error since the upgrade to Ruby 4.0. (#3910)
• The map loads again on Docker and Podman setups that start the app container without web-entrypoint.sh. Before, the persistent public volume kept the files of the previous version, the MapLibre files added in 1.15.1 were missing, and the browser blocked them with a "disallowed MIME type" error. Static files missing from the volume are now served from the copy inside the image. Files that already exist in the volume are still served from it, so keep entrypoint: web-entrypoint.sh to get updated versions of those. (#3872)
• Scheduled jobs added in a new release no longer fail in Sidekiq with undefined method 'jid=' when a Sidekiq process from an older Dawarich version still uses the same Redis. If you see these errors, stop the outdated Sidekiq process and delete the dead jobs that are already there. (#3715)

[Package Updates]

[1.24.0]

• Update dawarich to 1.19.0
• Full Changelog
• Back up your database before upgrading. The migration that keeps geofence events after their place is deleted cannot be rolled back. After the upgrade, background jobs recheck cell-tower points from the Android app and recount countries for past months.
• Archive and unarchive places from their editor or in bulk. Filter the Places list by Archived, and use Show archived places on the map to display them muted. Archiving keeps visit history and privacy masking while pausing new visits and geofencing.
• Search and filter Places by name, tags and confirmation status, and sort them by name, last visit or active visit count. The list shows tags, visit history, sources, geofences and privacy zones, with a shortcut to create a place on the map.
• Select places to add or remove tags, delete them with a summary of the consequences, or merge them into a chosen place. Possible duplicates groups places with overlapping visit radii for review; untick any place you want to keep before merging the rest.
• Geofence events stay in the log and API after their place is deleted, showing its last name.
• GPS noise filtering can hide inaccurate points again. Since 1.11.0 points with an accuracy of a few hundred metres stayed on the map, and phone tracking showed them as zig-zag lines across the route. Turn on "Hide inaccurate points" in the map settings under GPS Noise Filtering, choose a threshold between 50 and 1000 m, then press "Apply Settings" and after that "Re-evaluate past data" to hide such points in your history too. It is off by default, including for accounts that saved a threshold before 1.11.0, because Google Timeline imports report 14 km for points that still sit on the road. (#3300)
• Repeated cell-tower positions from the Android app no longer draw spikes on the map or inflate daily and monthly distance. Data recorded earlier is rechecked in the background after the upgrade. (#3417)
• Countries now count on Insights, Stats and yearly digests when reverse geocoding finds a country but no city for your points, for example in the countryside or at sea. Past months are updated gradually in the background after the upgrade. (#3598)
• Visit suggestions now run on instances without a configured geocoder. Visits without location details or a matching place display as "Unknown Location". (#3637)
• Tracks that cross the 180 meridian, such as trans-Pacific flights, are drawn across the date line again instead of as a line around the whole world. This applies to the Tracks layer, its speed colouring and trip routes. (#3921)

[Package Updates]

[1.25.0]

• Update dawarich to 1.20.0
• Full Changelog
• Migrations that install database triggers on points wait at most 5 seconds for a table lock. If one stops with a lock timeout, stop the workers or wait for running imports to finish, then restart the application; the migrations are safe to re-run.
• The initial geographic calculation runs in the background and can take longer while local boundary data is installed. The initial city and national-park catalog covers Berlin, Hamburg, Dresden, Harz, Saxon Switzerland and Eifel; it is not a worldwide catalog.
• Add personal achievement cards for city exploration, returning to places, collecting all seasons, national parks and geographic milestones. Cards include evidence, level history and opt-in public sharing with privacy-aware HTML, embeds and images.
• Collect Benelux, Baltics and Scandinavia achievement sets by visiting their three member countries. Each set shows visited countries, dates and the countries still to explore, with public sharing available when enabled. Existing location history counts automatically.
• Test a geocoding provider with your own coordinates in Instance settings, including providers with regional coverage. Leave both fields blank to use the existing default coordinates. (#3714)
• Click a photo cluster on the map to browse its photos without zooming. The gallery shows 24 thumbnails per page, supports phones and keyboard navigation, and keeps photos with identical coordinates accessible at high zoom. (#3652)
• Fog of War now follows the shared exploration cells. The per-point mode and the fog radius and threshold settings were removed.
• Full-history visit redetection now completes when legacy visits contain points without coordinates, preserving confirmed visits that have no usable observations (#3931).
• Monthly and yearly digest emails no longer enter repeated delivery retries when SMTP is not configured (#3932).
• Legacy areas with names longer than 255 characters now migrate to places without repeatedly failing, keeping their notes and visits (#3930).

[Package Updates]

[1.25.1]

• Update dawarich to 1.20.1
• Full Changelog
• Anomaly recalculation no longer fails for users who have a point without coordinates (#3936).
• Transportation-mode detection and track recalculation work on instances without the altitude_decimal column (#3951).
• Numbers in visit, place and family labels on the map render in the text font instead of as emoji (#3946).
• FIT imports assign each file its own tracker, so points from different FIT files are no longer grouped into one track (#3950).
• Polarsteps locations.json files larger than 8 KB are detected and imported (#3954).
• Trip pages no longer return an error when the trip notes contain an image with a relative URL (#3939).
• GeoJSON and GPX exports on the Points page use the dates currently set in the filter, even without pressing Search (#3952).
• Future AirTrail flights no longer create statistics for months that have not happened yet, and flights are counted in the month of their local departure date (#3935).
• Poster Studio no longer loads every point of the selected period, and Video Studio draws the route only from the selected time range (#3937, #3948).