Aktuelles Kartenmaterial für Wahoo ELEMNT BOLT, ROAM, ELEMNT selbst generieren

[Chris 5000]

@Chris 5000 Hate to ask, but are you sure you are using the January maps? Not those from 2 weeks ago?
I just got feedback in the telegram group from a German person telling (and showing) it works on his Roam 2.
Bolt and Roam should be the same.

Probably an Ace thing but I had to redo map update and theme update a number of times for it to work.


Have fun!

Yes it does work with the January 25 maps.

At first they didn't show up, i don't know why exactly, but now it works.

 

[Ebe66]

Thanks! Same question I asked the guy in the telegram group: Do you think this would be useful and/or readable?
The other person is going to try it out while riding this weekend.

Anyway, again, thanks for trying!

 

[Chris 5000]

Thanks! Same question I asked the guy in the telegram group: Do you think this would be useful and/or readable?
The other person is going to try it out while riding this weekend.

Anyway, again, thanks for trying!

Yes it's pretty useful, the readability is ok i guess, at the moment i cannot test outside. The zoom-levels are just right. Thanks again for your effort!

 

[spclzd]

Ich stecke mal wieder in einer Optimierungsschleife in meinem Theme und habe zwei Probleme bzw. Fragen:

Im x-ten Versuch habe ich es nun geschafft, Einzelbäume (Node mit natural=tree) ins Theme zu bekommen. Angezeigt ein grüner Kreis mit schwarzem Punkt in der Mitte (SVG-Datei). Leider überlagert diese Grafik die Linien der Wege. Mein Gedanke war, dass ich das Code-Schnipsel dafür im Theme weiter vorne platziere, also zwischen Flächen und Wegen - annehmend, dass das alles in der Reihenfolge gerendert wird und somit die Wege über die Bäume gezeichnet werden. Das haut so aber nicht hin. Hat jemand eine Idee, wie ich das gelöst bekomme?

Eine Hütte, die als Node mit dem Key amenity=shelter angelegt ist, bekomme ich ja schon lange wunderbar im Theme angezeigt. Ich hätte aber gerne auch Bushaltestellen, wo shelter=yes als ein Key von vielen an der Node hängt, angezeigt. Das klappt aber irgendwie noch nicht, ich fürchte das VTM-Theme kann grundsätzlich keine Keys mit =yes verarbeiten. Außerdem könnte problematisch sein, dass der Key shelter=yes an nodes und ways hängen kann.

---

Beispiel in OSM:

bench=yes
bin=yes
bus=yes
covered=no
departures_board=timetable
lit=yes
public_transport=platform
shelter=yes
tactile_paving=yes

---

Mein vtm-elemnt.xml dazu (Ausschnitt, grün funktioniert, rot nicht):

<m k="amenity">
<m v="cafe">
<symbol src="icons/symbols/cafe.svg" symbol-percent="150"/>
</m>
<m v="drinking_water">
<symbol src="icons/symbols/drinkingtap.svg" symbol-percent="150"/>
</m>
<m v="water_point">
<symbol src="icons/symbols/drinkingtap.svg" symbol-percent="150"/>
</m>
<m v="fast_food">
<symbol src="icons/symbols/fastfood.svg" symbol-percent="150"/>
</m>
<m v="fuel">
<symbol src="icons/symbols/fuel.svg" symbol-percent="150"/>
</m>
<m v="fast_food">
<symbol src="icons/symbols/fastfood.svg" symbol-percent="150"/>
</m>
<m v="shelter">
<symbol src="icons/symbols/shelter.svg" symbol-percent="150"/>
</m>
<m v="toilets">
<symbol src="icons/symbols/toilets.svg" symbol-percent="150"/>
</m>
<m v="bicycle_repair_station">
<symbol src="icons/symbols/bicycle.svg" symbol-percent="150"/>
</m>
<m v="ferry_terminal">
<symbol src="icons/symbols/ferry.svg" symbol-percent="150"/>
</m>
</m>
<m k="shop">
<m v="bakery">
<symbol src="icons/symbols/bakery.svg" symbol-percent="150"/>
</m>
<m v="bicycle">
<symbol src="icons/symbols/bicycle.svg" symbol-percent="150"/>
</m>
<m v="supermarket">
<symbol src="icons/symbols/supermarket.svg" symbol-percent="150"/>
</m>
</m>

<m k="tourism">
<m v="alpine_hut">
<symbol src="icons/symbols/alpinehut.svg" symbol-percent="150"/>
</m>
</m>

<m k="route">
<m v="ferry">
<symbol src="icons/symbols/ferry.svg" symbol-percent="150"/>
</m>
</m>

<m k="natural">
<m v="spring">
<symbol src="icons/symbols/fountain.svg" symbol-percent="150"/>
</m>
</m>

<m k="shelter">
<m v="yes">
<symbol src="icons/symbols/shelter.svg" symbol-percent="150"/>
</m>
</m>

---

tags-to-keep.json (Ausschnitt, grün funktioniert, rot nicht):

"amenity": [
"fuel",
"cafe",
"fast_food",
"restaurant",
"drinking_water",
"shelter",
"ferry_terminal",
"bicycle_repair_station",
"toilets",
"water_point",
"school",
"university",
"college",
"kindergarten",
"social_facility",
"courthouse",
"hospital",
"theatre",
"public_bath",
"parking"
],
"shop": [
"bakery",
"bicycle",
"supermarket",
"mall"
],
"highway": [
"abandoned",
"bus_guideway",
"disused",
"bridleway",
"byway",
"construction",
"cycleway",
"footway",
"living_street",
"motorway",
"motorway_link",
"path",
"pedestrian",
"primary",
"primary_link",
"residential",
"road",
"secondary",
"secondary_link",
"service",
"steps",
"tertiary",
"tertiary_link",
"track",
"trunk",
"trunk_link",
"unclassified"
],
"natural": [
"coastline",
"nosea",
"sea",
"beach",
"land",
"sand",
"scrub",
"water",
"wetland",
"grassland",
"wood",
"heath",
"scrub",
"shrubbery",
"tree_row",
"tree",
"scree",
"bare_rock",
"glacier",
"fell",
"spring"
],
"barrier": [
"hedge",
"wall",
"fence"
],
"landuse": [
"forest",
"commercial",
"industrial",
"residential",
"retail",
"farmyard",
"grass",
"cemetery",
"allotments",
"plant_nursery",
"orchard",
"meadow",
"farmland",
"quarry",
"construction",
"greenfield",
"brownfield",
"military"
],
"leisure": [
"park",
"garden",
"nature_reserve",
"pitch",
"stadium",
"track",
"golf_course",
"playground",
"sports_centre",
"water_park"
],
"railway": [
"rail",
"tram",
"station",
"stop"
],
"route": [
"ferry_terminal",
"ferry"
],
"surface": "",
"tracktype": "",
"tunnel": "",
"waterway": [
"canal",
"drain",
"river",
"riverbank",
"stream",
"ditch"
],
"wood": "deciduous",
"tourism": "alpine_hut",
"shelter": "yes"
},

---

tag-wahoo-poi.xml (Ausschnitt, grün funktioniert, rot nicht):

<pois>
<osm-tag key="amenity" value="fuel" zoom-appear="14" />
<osm-tag key="amenity" value="cafe" zoom-appear="14" />
<osm-tag key="amenity" value="drinking_water" zoom-appear="14" />
<osm-tag key="amenity" value="water_point" zoom-appear="14" />
<osm-tag key="amenity" value="shelter" zoom-appear="14" />
<osm-tag key="amenity" value="restaurant" zoom-appear="14" />
<osm-tag key="amenity" value="fast_food" zoom-appear="14" />
<osm-tag key="amenity" value="bicycle_repair_station" zoom-appear="14" />
<osm-tag key="amenity" value="ferry_terminal" zoom-appear="12" />
<osm-tag key="shop" value="bakery" zoom-appear="14" />
<osm-tag key="shop" value="bicycle" zoom-appear="14" />
<osm-tag key="shop" value="supermarket" zoom-appear="14" />
<osm-tag key="railway" value="station" zoom-appear="12" />
<osm-tag key="railway" value="stop" zoom-appear="12" />
<osm-tag key="tourism" value="alpine_hut" zoom-appear="14" />
<osm-tag key="shelter" value="yes" zoom-appear="12" />
<osm-tag key="natural" value="tree" zoom-appear="14" />
<osm-tag key="natural" value="spring" zoom-appear="14" />
</pois>

 

[Ebe66]

My gut feeling is that symbols will always be drawn on top of map elements. It's not very clear in the vtm documentation, but you might try priority=, but I suspect this only works for text and captions.

Don't directly see why shelter=yes would not work. First step would be to check if it is in the generated map file.
Just open the map file in a editor like notepad++, at the top the included ways and poi's are shown. Check if shelter=yes is there.

 

[spclzd]

My gut feeling is that symbols will always be drawn on top of map elements. It's not very clear in the vtm documentation, but you might try priority=, but I suspect this only works for text and captions.

I had a go with 'priority=' before I came here to ask. Doesn't seem to work, tried different values. But I don't know if everything else needs priority tags than, too.
Where can I find the documentation?

Don't directly see why shelter=yes would not work. First step would be to check if it is in the generated map file.
Just open the map file in a editor like notepad++, at the top the included ways and poi's are shown. Check if shelter=yes is there.

shelter=yes is not included, although it's in the tags-to-keep.json:
"TAGS_TO_KEEP_UNIVERSAL": {
"shelter": "yes"
],

and tag-wahoo-poi.xml:
<!-- OTHER TAGS -->
<ways>
<osm-tag key="area" value="yes" zoom-appear="3" />
<osm-tag key="shelter" value="yes" zoom-appear="16" />
<osm-tag key="admin_level" value="2" zoom-appear="3" force-polygon-line="true"/>
</ways>

also tried it in the tag-wahoo-poi.xml as:
<!-- ************* POIS *************** -->
<pois>
<osm-tag key="shelter" value="yes" zoom-appear="16" />
</pois>

 

[Ebe66]

Writing this from my bed after a very long work day, but priority 0 is the default and that also is the highest priority. The documentation is on the mapsforge/vtm GitHub page. If I remember I'll post the link tomorrow

For the shelter issue, the next step would be to edit benjamins source to prevent the deletion of the filtered input file and check if shelter=yes is in the filtered file. You can check this with either osmconvert or osmfilter. Not sure which one from the top of my head but one of those has an option like. List-keys

 

[Tonno_A]

@All - after I read through all 50 pages, I indeed succeeded to upload the (non-routing) map of @Ebe66 for Upper Bavaria as well as his vtm-elemnt file onto the device (Roam 1) and the first impression is really good.

Indeed, I experienced some issues, that I will share in the next few days, including not getting elemntry running (neither on Win nor on Mac - on Mac possibly ADB issue, on WIn - no idear). Also some questions remain on some files and how to treat the icons for display of PoIs.

Thanks to the community for this thrilling project!

 

[Ebe66]

Where can I find the documentation?

@Tonno_A Thanks for the indirect reminder

@spclzd
Documentation is at:
https://github.com/mapsforge/vtm/bl...6361745865c433e64fe/resources/rendertheme.xsd for the options file
The project itself: https://github.com/mapsforge/vtm/tree/283e9ebaa1a4b7c798f1a6361745865c433e64fe
The render theme "documentation" in the docs folder: https://github.com/mapsforge/vtm/blob/283e9ebaa1a4b7c798f1a6361745865c433e64fe/docs/Rendertheme.md
It isn't much I think, I miss lots and lots of examples for instance but it is all we have to work with to my knowledge.

 

[Ebe66]

Thanks to the community for this thrilling project!

@Tonno_A thanks for that.
Do you mean you really can't get the app to start or do you mean it starts but you can't get a connections with the Wahoo? Never heard of anybody not being able to start the app, let alone on two os'es.
Authentication the Wahoo can be a pain in the toessie with the roam2/bolt2/ace but on the original Elemntary , bolt 1 and roam 1 it should be a breeze.

Suggestion, for everybody here really, join the Telegram group. It's reasonably low in message volume, but english is the main language.
Henk Stubbe is there who made the very first linux version. Benjamin/treee111 from the first post in this thread is there (but not so active anymore alas). Also VTI from the Elemntary app is there (also not so active anymore. and silly me of course.
Invite link for the telegram group

 

[Tonno_A]

Do you mean you really can't get the app to start or do you mean it starts but you can't get a connections with the Wahoo?

On MacOS, App works, but connection to wahoo is not established. {now it works, but do not know what I made differently}

On Windows, it does not start at all.

This is, however, currently not an issue for me, as copying is at the moment sufficient for me.

 

[Tonno_A]

I am working myself into the details of this amazing enhancement of the Wahoo. I am on a Roam v1 and currently have the maps from the higli-onedrive loaded.

If I may, I would like to have input to my below questions:

• The tag-wahoo.xlm file: What is this used for, i.e. what is its function? I understand that this needs to go into the sub-folder vtm-elemnt on the wahoo.
• The maps forge-roam.xml file: What is this used for, i.e. what is its function? Where would it need to be stored on the Wahoo?
• If I wish to show (or not to show) Icons for POIs, do I only need to adjust the vtm-elemnt.xml or do I may need self-created maps or adjust other files (obviously I need to upload the symbols/icons into VTM-elemnt folder, if I am not mistaken; anything else)
• The routing tiles are only needed if I wish to let me route by the wahoo itself (I normally use brouter/bikerouter, so this should not be needed for me, if I understand correctly)

A short, high-level response would suffice for the moment. Many thanks in advance.

Have a nice weekend

Andreas

 

[Ebe66]

Hi Andreas / @Tonno_A ,

Good to hear it's working for you!

As requested, high level answers

• tag-wahoo.xml (which I think/hope is not on the OneDrive?) is used during the creation of the maps. It's a whole process of downloading source maps, finding out which files are needed, filtering them, cutting them down to a thing called slippy tiles and combining them to a single tile. This tile is than converted to a tile the wahoo devices use by osmosis in combination with the mapsforge mapwriter. You tell this mapwriter what to include and at which zoom level with the tag-wahoo.xml (or now tag-wahoo-z13.xml). It is not needed nor used on the device. In short, unless you are creating your own maps you don't need it.
• mapsforge-roam.xml file: I don't know what you have done so far of course, but this is (part of) the custom theme file for the Roam v1 devices using the old mapsforge rendering engine. Using the custom maps without uploading any theme gives you updated maps, but nothing more. Considering you question about en/dis-abling poi's and the vtm theme suggests you did upload a theme?
• - Using the custom mapsforge theme (upload with Elemntary app!) gives you added features like colors, elevation lines and pois within the limits of this rendering engine. For example it is not possible to have a text label follow the path of the road/river etc. Uploading the vtm-forced roam-1 theme uses the new vtm rendering engine. For it to become active, you need to tick the vtm_rendering option in the Elemntary app (I can't connect my device atm so not 100% sure about the name in the app). Don't recall the differences from the top of my head but sufice to say it enhances the display further. Warning though, if your device is already natively using vtm rendering (v1 should not) do NOT tick the option in Elemntary!
• Icons for poi's: If you are actually using the vtm-elemnt.xml file/theme you can comment out the display of a certain type of poi by doing this: Lets say you want to disable pubs (stupid example for a german (or me!)), find the code block in the xml file that contains pub. In this case it looks like this:

<m v="pub">
<symbol src="icons/symbols/food/pub.svg" symbol-percent="150"/>
</m>
Change this to to this to disable the pub pois (shudders at the thought! )
<!--
< m v="pub">
<symbol src="icons/symbols/food/pub.svg" symbol-percent="150"/>
</m>
-->
This <!-- something --> is basically a rem statement/block.
- routing tiles: You do not need them, if i'm correct the roam 1 does not even use them? (i have a bolt 1 and ace myself). If you do not use the device for routing (if it supports it) than the only thing you are missing out on i think is the display of the streetname you are on.

Hope I answered everything.

Have a great weekend!

 

[Tonno_A]

Thanks for the explanation.

Until now I have used the vtm-elemnt.xml as Theme. Is mapsforge just another kind of theme system and exchangeable with vtm-elemnt or is this something else needed in addition to vtm-elemnt.xml?

So your maps include all customary POIs (I read somewhere, that you do not include fuel stations; just in your vtm-elemnt or also in the maps themselves)?

Andreas

 

[Ebe66]

Hey @Tonno_A ,
Not 100% sure what you are asking but: look at it this way, mapsforge is a brand and the mapsforge rendering engine was v1 like quick basic ( yes, I'm old) later they developed the vtm rendering engine like python. Both systems are kind of programming languages, but they are not interchangeable.
The vtm-elemnt.xml like the name suggests is used by the vtm rendering engine which is used by default by the bolt 2/roam 2 and ace

My maps do not contain all poi's, there is an insane amount of them. The challenge is deciding which to include. As you can see one page or two back, you can include singular trees or house numbers or lamppost or.... You name it. But are those usefull? Everything you add to the map makes the files bigger and the screen fuller.
I do include fuel stations, I think I always did. Only discussion I remember is someone wanting to have them displayed at a really high zoom level that would work for him in rural somewhere but that would fill the screen with them where I live. Other issue I remember is that somewhere they where on the OpenStreetMap as relations and were not displayed because of that. Don't want to go too deep but relations are (still) hard to process

 

[Tonno_A]

many thanks, @Ebe66 - all understood. Now it is on me to make the best out of it.

Andreas

 

[spclzd]

@Tonno_A Ich kann dir kein komplettes Tutorial liefern, aber ich habe hier im Thread mal ausführlicher beschrieben, wie ich für mein Theme vorgegangen bin und welche OSM-Tags ich in meine Karten integriert habe und wie sie dargestellt werden. Das könnte für dich vielleicht ein Anfang sein.

 

[Tonno_A]

Das könnte für dich vielleicht ein Anfang sein.

Danke. Das werde ich mir mal in Ruhe zu Gemüte führen. Auch die Icons sehen gut aus!

 

[spclzd]

Seit dem hat sich mein Theme natürlich auch weiterentwickelt, vielleicht kriege ich es gebacken, hier demnächst Mal den aktuellen Stand einzustellen.

 

[spclzd]

Now I had some time to work on the shelter-issue again. Long story short: I'm giving up on this now, but not because I didn't find a solution, but because the key I'm interested in is used so inconsistently, it would clutter my maps.

Long story long:
Because I wasn't sure, what you meant with

to edit benjamins source to prevent the deletion of the filtered input file and check if shelter=yes is in the filtered file

or which file to check exactly, I tried '.\wahooMapsCreatorData\_tiles\germany\filtered.o5m' first. With osmfilter I could find the following keys:
160 shelter:check_date
1 shelter:left
1 shelter:name
2 shelter: perator
1 shelter:ref
2 shelter:register
1 shelter:register:note
1 shelter:style
9 shelter_shape
1 shelter_size
63850 shelter_type
1 shelter_type_1

There is no "shelter" without additional ":" or "_". So if I'm not mistaken a node or way with just the key "shelter=yes" would not be included in the file, right?

If I compare this with other keys, e.g. waterway, the other keys are always available in a pure form, without additional ":" or "_". And unsurprisingly, they have the highest count:
1641366 waterway
1 waterway:-2021
4904 waterway:category
1 waterway:de
5 waterway:distance
1 waterway:hazard
119 waterway:kilometer
5 waterway:lock:height
5 waterway:lock:length
1 waterway:lock: phone
1 waterway:lock:width
7 waterway:maxheight
145 waterway:maxspeed
7 waterway:maxspeed:motorboat
1 waterway:milestone
4 waterway:mindepth
2 waterway: position
619 waterway:sign
6 waterway:type
6 waterway:ukw_channel
3 waterway:vehicle
1 waterway:vhf_channel
2 waterway_1
2 waterway_category: DE-NI
333 waterway_category:NDS

Moving forward I wanted to test if I could include nodes or ways with the key "shelter_type=*" in my map files and display them in my theme. Using overpass I was looking for such an object in my vicinity so I could check it in the map tile I normally use to build my theme. I found some objects nearby, but all of them would have been in my theme anyway because they also contained the key "amenity=shelter".

This made me think about the key "shelter=yes" once again. Using overpass once more I checked how the key is used in my vicinity. And what I found made me drop the idea: often times the key "shelter=yes" is used multiple times per single bus stop because it is used on a way in addition to "public_transport=platform", on a node in addition to "public_transport=stop_position" and on top of that on a node with the key "public_transport=platform", too. So in the worst case my theme would display three shelter-icons when there's just one shelter in reality.