Colota - Android GPS Location tracker
chore(map): align with hillshade removal from tile server
Max Dietrichac03d4df5d72
diff --git a/apps/docs/docs/guides/backup-restore.md b/apps/docs/docs/guides/backup-restore.mdindex 36c3432c..b67c8d16 100644--- a/apps/docs/docs/guides/backup-restore.md+++ b/apps/docs/docs/guides/backup-restore.md@@ -39,7 +39,7 @@ The app encrypts the file as it writes. You can leave the screen and the backupA random 16-character password from a password manager, or a 4-5 word passphrase, both clear the bar comfortably. Common words and short tweaks of dictionary words do not.-:::warning+:::warning[No password recovery]No password recovery If you lose the password, the backup cannot be opened. Ever. There is no recovery code, no email reset, no developer override. Store the password somewhere you trust before you create the backup.@@ -47,7 +47,7 @@ No password recovery If you lose the password, the backup cannot be opened. Ever## Restoring from a Backup-:::danger+:::danger[Data will be overwritten]Replaces all current data Restoring overwrites every location, setting, geofence and credential currently on the device. There is no merge mode and no undo. Take a backup of the current device first if you might want to roll back.diff --git a/apps/docs/docs/guides/data-export.md b/apps/docs/docs/guides/data-export.mdindex c47be0fa..a2e71298 100644--- a/apps/docs/docs/guides/data-export.md+++ b/apps/docs/docs/guides/data-export.md@@ -6,7 +6,7 @@ sidebar_position: 2Export your location history in multiple formats.-:::tip Looking for a full archive?+:::tip[Looking for a full archive?]Data Export produces shareable, human-readable formats (CSV, GeoJSON, GPX, KML) of your location history. If you instead want a single password-encrypted archive of **everything** - locations, settings, geofences and credentials - for device migration or offsite storage, use [Backup & Restore](backup-restore.md).@@ -90,7 +90,7 @@ By default, auto-export keeps the last **10** export files and deletes older one- A notification is shown after each export with the file name and location count- Old export files beyond the retention limit are cleaned up after each successful export-:::note+:::note[Frequency]**Monthly** frequency uses a calendar month (e.g. Jan 15 to Feb 15), not a fixed 30-day interval. If the chosen day-of-month doesn't exist in a given month (e.g. day 31 in February), the export runs on the last day of that month instead. **Daily**, **Weekly** and **Monthly** intervals fire at the chosen wall-clock time via Android AlarmManager. Typical accuracy is within minutes.diff --git a/apps/docs/docs/guides/data-import.md b/apps/docs/docs/guides/data-import.mdindex 92ea57d0..d0c24e51 100644--- a/apps/docs/docs/guides/data-import.md+++ b/apps/docs/docs/guides/data-import.md@@ -6,7 +6,7 @@ sidebar_position: 3Merge location history from external files into your Colota database.-:::tip Looking for a full archive restore?+:::tip[Looking for a full archive restore?]Data Import is **additive**: existing locations are preserved and duplicates are skipped. Use this to recover from a Colota export, migrate from Google Timeline, or pull historical data from another tracker. If you want to **replace everything** on the device from an encrypted Colota archive (locations, settings, credentials), use [Backup & Restore](backup-restore.md).@@ -86,7 +86,7 @@ If you've configured an optional sync backend in **Settings → Connection**, thThis button is **only shown when a sync endpoint is configured and offline mode is off**. If it's missing, configure sync in **Settings → Connection** first.-:::warning Queueing fans the points out to your backend - irreversible there+:::warning[Queueing fans the points out to your backend - irreversible there]Once queued, the rows are uploaded as soon as the next sync runs. Removing them from the backend afterwards isn't something Colota can do for you. If you're importing a multi-year archive (100k+ points), expect the queue to fire that many upload requests against your backend; make sure it can handle the load.diff --git a/apps/docs/docs/guides/tile-server.md b/apps/docs/docs/guides/tile-server.mdindex 3e7d7f28..cb433743 100644--- a/apps/docs/docs/guides/tile-server.md+++ b/apps/docs/docs/guides/tile-server.md@@ -8,7 +8,7 @@ By default, Colota loads maps from [maps.mxd.codes](https://maps.mxd.codes) - a## Default Server-maps.mxd.codes runs [tileserver-gl](https://github.com/maptiler/tileserver-gl) on a netcup VPS. Two styles are served - bright for light mode, dark for dark mode.+maps.mxd.codes runs [tileserver-gl](https://github.com/maptiler/tileserver-gl) on a netcup VPS. Two styles are served - bright for light mode, dark for dark mode. Styles are vector-only to keep offline map packs lean.**Technical details**diff --git a/apps/mobile/src/components/features/map/ColotaMapView.tsx b/apps/mobile/src/components/features/map/ColotaMapView.tsxindex f5399503..74ef2757 100644--- a/apps/mobile/src/components/features/map/ColotaMapView.tsx+++ b/apps/mobile/src/components/features/map/ColotaMapView.tsx@@ -21,12 +21,13 @@ interface AttributionLink {label: string}-// Keep in sync with the attribution in maps.mxd.codes/styles/*/style.json.+// Used when the style fetch fails or returns no attribution. Must cover+// anything legally required for the default tile sources (OSM ODbL,+// OpenMapTiles CC-BY) so attribution is never silently hidden.const FALLBACK_ATTRIBUTION_LINKS: AttributionLink[] = [{ url: "https://www.openstreetmap.org/copyright", label: "© OpenStreetMap contributors" },{ url: "https://maps.mxd.codes", label: "© maps.mxd.codes" },- { url: "https://openmaptiles.org", label: "© OpenMapTiles" },- { url: "https://github.com/tilezen/joerd/blob/master/docs/attribution.md", label: "Mapzen Terrain Tiles" }+ { url: "https://openmaptiles.org", label: "© OpenMapTiles" }]function parseStyleAttribution(sources: unknown): AttributionLink[] {