September 9, 2017 at 12:30 #19952
Could you please consider including verbose tags for sac_scale in the Elevate/Elements themes for the sake of compatibility?
Locus Maps use the untransformed tags:
T1 <-> hiking
T2 <-> mountain_hiking
T3 <-> demanding_mountain_hiking
T4 <-> alpine_hiking
T5 <-> demanding_alpine_hiking
T6 <-> difficult_alpine_hiking
https://wiki.openstreetmap.org/wiki/Key:sac_scale#ValuesSeptember 9, 2017 at 20:41 #19983
I don’t have any LoMaps for testing (the free download didn’t work with my account), so I can’t test it. AFAIK there are lots of other hiking related tags that LoMaps don’t contain, so why should one use them instead of OAM for which Elevate is made?
Developer of Elevate mapstyleSeptember 9, 2017 at 22:52 #19989
Why? I have no idea to be honest but wouldn’t want to dictate what users do. Personally I aim for the widest compatibility with my themes.
I guess a Locus user might start with Locus maps, try out your themes with them, like them, and then decide to try out OAMaps and finally switch
Anyway, it’s your call..
September 10, 2017 at 10:37 #20004
- This reply was modified 1 year, 10 months ago by JohnPercy.
The basic problem in Mapsforge that causes incompatibility is the common value bug that forces Renderers to use unique values even across different tags. so, eq, the value “yes” cant be uses for different tags – it needs prefixes for different tags.
… and every renderer uses different workarounds for this problem. No idea what Petr/Menion have done for the LoMaps to solve this problem – but I’m shure their solution (for a lot of tags) is different to OAM.
This means it more than likely that tagging/theme is different in many ways.
ChristianSeptember 10, 2017 at 11:17 #20006
EmuxParticipantSeptember 10, 2017 at 12:48 #20009
Agree on that piece, Emux.
But why would Mapsforge have this “common value bug” in the first place, which drives one aspect of fragmentation … ?September 10, 2017 at 13:40 #20011
It would be nice if developers contribute any Mapsforge (LGPL) modifications all these years.
Fragmentation is never good for community.
This is more about fragmentation because of different tag-mapping solutions, not about changes to the api. I don’t know if having to settle on common tag values with all map creators for tag-mapping would justify the result that all themes can be used with all maps. Maybe nice to have, but would there really be a major benefit?
Developer of Elevate mapstyle
1 user thanked author for this post.
You must be logged in to reply to this topic.