Messages

Well, could I add "location=underground" to LoMaps for the next release if that helps?

Hello,
I'm sorry, but I'm not sure I understand your question. Are there any roads missing from the map? Or is the problem in the navigation - between points 1 - 2? What navigation profile (Walking, Cycling,...) are you using, please?

Thanks, Petr

@Viajero Perdido
captions - that would be nice but maybe later
forest areas - I see the next maps will contain fores/wood from ZL=9

It is difficult to say what happened. In any case, please contact us if this happens again.

It wasn't updated regularly because of the size and time of generation. But the generation without contour lines should be quicker. Regarding the broken view - is it possible that there was a combination of LoMaps V4 and old V3 generation when the old V3 map isn't auto-loaded when another V4 map is selected?

The map seems to be working properly. It's smaller in size because it doesn't include contour lines (due to the map size). Greenland has never been updated regularly, but we'll add it for the next generation.

this is more on @Menion ..he has a couple of days off, but I think he'll notice it and tweak it later.
Thanks, Petr

I checked your account and I see that you have downloaded a lot of maps in version 2023.03.23.
Today you updated several maps (Czech Republic, Austria, Switzerland, Germany...) to version 2023.05.05.
Sorry, but the update seems to work correctly. Could you please check the version of the maps before and after the update?

Dobrý den,
bohužel se nám dokončení podmíněného stylování poněkud protáhlo, ale v příští verzi by již mělo být k dispozici.
Děkuji za pochopení

@john_percy
Disused route
I'm sorry but I don't understand - the relation https://www.openstreetmap.org/relation/2003487 isn't shown in the latest offline LoMaps

Tunnel
Dartford East Tunnel is in layer=-1 and this situation isn't still improved in the LoMaps. I think that OAM edits the layer tag to "solve" this issue. I think we could also try something similar sometime in future versions.

@john_percy
Disused route: I hope I found the correct ways you mentioned as problematic (see bellow). I'm sorry but both ways are members of valid relation and should be displayed? Did I miss something?
https://www.openstreetmap.org/way/27282386
https://www.openstreetmap.org/way/4421231 

Tunnels - what exactly do you mean? (the link is about viaduct). Anyway, the hiking/cycling ways should contain tunnels and bridge tags inherited from the original ways. The problem with layer=-1 for tunnels isn't still fixed - maybe later in 2023/2024

@karlchick
"lm_highway" has the same values as the original "highway" tag. The other tags (except mentioned tunnel/bridge) aren't inherited.
"Designation" tag can not be added at this moment. I'm sorry but Mapsforge can handle OSM features if they have a maximum of 15 tags. The hiking/cycling ways are on the edge of this limit (because custom tags like lm_highway, osmc foreground/background, colors, text, length of text, bridge,tunnel...)

Contour lines, OS data - maybe later

@john_percy ahh I'm sorry. I thought that everybody here is a Gold member I'll discuss it with @Menion and I think we can add some maps again on GD as before.

@john_percy @karlchick
The new version of LoMaps 2023.05.05 is available in the store. It supports new tags and also some changes in Hike&Bike routes (problem with planned or unused routes). Please check & test
Thanks, Petr

[_]

@john_percy
The naming convention for "poi" theme is nameOfBaseMapTheme_layerId.poi.xml
When the layerId id of layer is defined in <stylemenu> of the base map theme.

Anyway, only the internal theme supports this special "poi" themes. It is not yet fully implemented for alternative themes, but there are plans to support it...

@Tapio
Please see https://github.com/asamm/lomaps-mapsforge#poi-themes

Thank you for the report but to be honest I'll check it later (hope it isn't such a big problem . Only for the explanation - Worldbase map is generated from Natural Earth Data (not OSM). I guess the M25 ring isn't properly closed and it cause this issue.