From 64fe64fdd1ee48816fe3c0cfc6560966e121264e Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 25 Apr 2022 21:02:15 +0200 Subject: [PATCH] adjust documentation --- docs/COPY_TO_WAHOO.md | 17 ++++++++++------- docs/TAGS_ON_MAP_AND_DEVICE.md | 14 ++++++++++++-- 2 files changed, 22 insertions(+), 9 deletions(-) diff --git a/docs/COPY_TO_WAHOO.md b/docs/COPY_TO_WAHOO.md index 7a18ca68..377f936f 100644 --- a/docs/COPY_TO_WAHOO.md +++ b/docs/COPY_TO_WAHOO.md @@ -49,13 +49,16 @@ According to [the Wahoo documentation](https://support.wahoofitness.com/hc/en-us ## Copy device theme Device themes are described [here](TAGS_ON_MAP_AND_DEVICE.md#Device-Theme) -A theme can be copied to your device like that: -- ELEMNT/BOLT - - copy "mapsforge-bolt.xml” of folder `common_resources/theme_adjusted` to `maps/mapsforge-bolt/mapsforge-bolt.xml` (just posted this in the google groups) -- BOLTv2 - - copy `assets/maps/vtm-elemnt/vtm-elemnt.xml` from the apk. Modify and copy the theme to `maps/vtm-elemnt/vtm-elemnt.xml` -- ROAM - - copy `mapsforge-bolt.xml` of folder `common_resources/theme_adjusted` to `maps/mapsforge-roam/mapsforge-roam.xml` +In this repo, device themes are stored in folder `device_themes`. There are initial versions and adjusted versions. Both can be further changed to your requirements! + +The following table shows the file per device and the location where the device theme needs to be copied to. + +| device | file | location | +| ------ | -------------------- | ---------------------------------------- | +| BOLTv2 | `vtm-elemnt.xml` | `maps/vtm-elemnt/vtm-elemnt.xml` | +| ROAM | `mapsforge-roam.xml` | `maps/mapsforge-roam/mapsforge-roam.xml` | +| BOLTv1 | `mapsforge-bolt.xml` | `maps/mapsforge-bolt/mapsforge-bolt.xml` | +| ELEMNT | `mapsforge-bolt.xml` | `maps/mapsforge-bolt/mapsforge-bolt.xml` | # Delete temp-files and Clear Cache - delete all files from \ELEMNT-BOLT\USB storage\maps\temp\ diff --git a/docs/TAGS_ON_MAP_AND_DEVICE.md b/docs/TAGS_ON_MAP_AND_DEVICE.md index 84b2161f..b2760fb6 100644 --- a/docs/TAGS_ON_MAP_AND_DEVICE.md +++ b/docs/TAGS_ON_MAP_AND_DEVICE.md @@ -34,9 +34,19 @@ E.g. roads, locations, ... Each entry has a "zoom-appear" attribute, which defines from which zoom level onwards the element will be stored in the map. If zoom-appear is set to 13, the OSM-tag will be stored in the 500m, 200m and 100m zoom levels and therefore could be rendered. # Device-Theme -The theme defines, which OSM-tags are shown on the device or in cruiser where the theme should be used if you preview generated maps on your computer. +The device theme defines, which OSM-tags are rendered on the device. In cruiser, you can also apply the device theme to preview generated maps on your computer. -The theme is named `mapsforge-bolt.xml` or `mapsforge-roam.xml` and is content-wise equal to the `tag-wahoo.xml` +There are two types of rendering methods: VTM and non-VTM rendering. This table shows the default rendering per device: +| device | default rendering | +| ------ | :---------------: | +| BOLTv2 | VTM | +| ROAM | non-VTM | +| BOLTv1 | non-VTM | +| ELEMNT | non-VTM | + +You can enable the VTM rendering method on Wahoo devices other than BOLTv2 by creating a empty file on the device with the name "cfg_BHomeActivity_VtmMaps" in the root folder. + +The theme is named `mapsforge-bolt.xml` or `mapsforge-roam.xml` for non-VTM rendering and `vtm-elemnt.xml` for VTM-rendering. It's content is more or less equal to the `tag-wahoo.xml` files. ## Attribute "zoom-min" Each entry in the theme has a "zoom-min" attribute, which defines from which zoom level onwards the element will be shown. If zoom-min is set to 13, the OSM-tag will be displayed in zoom level 500m, 200m and 100m.