Messages

Hi,

I'm sorry for the late reply. Finally, it's some time to focus on the map again
@karlchick
- railway=miniature added
- natural=mud - thank you for the report - my mistake. I added the natural=mud only into POINT section and WAYS were omitted (will be fixed in the next LoMaps)
- leisure=nature_reserve - I'm testing the latest LoMaps and seems to be OK (would you please check it again)
- icn&ncn available from zl=8 and rcn available from zl=10

This icon represents a general gate (without type specification). I can understand that city areas are overcrowded with these symbols but they are useful for cyclists (especially in the UK).

Anyway, you found a bug because offline LoMaps use the old symbol for the gateway. For online LoMaps we have prepared a new and less distinctive symbol. We have fixed it in offline LoMaps as well. It's still not ideal, but hopefully, it's better than before. See the attached screenshotYou cannot view this attachment.

fine, it'll be available in the next version of LoMaps...

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

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

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 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
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

Hi,

you're right. Maps for these regions are really missing. To be honest I can't remember why we haven't added prepared them. Maybe because of the size of map or unsufficient map scale.
Anyway, I'll contact our BRMB and find out more info if we can add these regions...

Thanks, Petr

@john_percy Thank you for your report/feedback
You're right we ignore mentioned proposed or disused tags. I'll improve it.
Anyway, do you know more about tag type=disused_route ? I can't find any official documentation for this tags. I'm also wonder if there are more disused combinations...

- lm_highway=construction is really missing and will be improved in the next version of LoMaps

@karlchick
Point 13
I see. I added:

Code Select Expand


<osm-tag key="service" value="alley" zoom-appear="13" />
<osm-tag key="service" value="driveway" zoom-appear="13" />
<osm-tag key="service" value="emergency_access " zoom-appear="13" />
<osm-tag key="service" value="parking_aisle" zoom-appear="13" />
<osm-tag key="service" value="slipway" zoom-appear="13" />


@john_percy
Mapsforge now supports any "key" that can be used as a text value. So you can, for example, display the value of the key "highway"

Code Select Expand

<pathText k="highway" font-style="normal" font-size=....
Anyway, you are right - "osmc_text" and "osmc_text_length" are really missing in the latest LoMaps. The latest version of LoMaps was released in version 4 which doesn't contain variable "tag-values" (%s, %f)

Anyway, I generated a new version of LoMaps (see attached map of Monaco) as version 5. The mentioned "osmc_text" and "osmc_text_length" tags should be available in the data. But I think I found some bug in the Mapsforge generator, where the tag-value variable is not included in the data if there is another tag with the same value. The value of "osmc_text" is often the same as the value of "ref", and it seems that in such a situation the "osmc_text" is not added to the data. I need to test this with @Menion in more detail and debug the data in the map tiles.


For this reason, I edited one tourist way with "osmc_text" value and set value "03 testtest" (avaialable in attached monaco map). You can test it with your theme...

PathText to display the text "03 testtest"

Code Select Expand

<pathText k="osmc_text" dy="2" font-style="bold" font-size="16" fill="#e67400" stroke="#ffffff" stroke-width="2.5" priority="1000"/>

As you probably know, Locus used a custom implementation of the Mapsforge vector map rendering for LoMaps vector maps. There were several attributes that the original Mapsforge did not support.

As of May 2023, LoMaps is being released as Mapsforge V4 and the old V3 themes cannot be used for the new LoMaps V4. The new theme must be prepared to work with the new LoMaps V4.
 
We have prepared a simple script to help transform an existing Locus V3 theme into a Mapsforge V4 theme 

Script and simple doc are available at https://github.com/asamm/lomaps-mapsforge/tree/main/theme-v3-to-v4-converter

Please note that the script does not convert the entire theme 1:1.
Manual work will still be required, but should save time when editing attributes.

@john_percy

I'm looking at osmc waymarking but I can't see any markings on some routes I am looking at, where OAM maps show osmc markings. For example, one location is N 51.61224°, E 007.57491° (from Locus).

I'm sorry but on given coordinates isn't any osm relation with the specified "osmc:symbol". Could I kindly ask you for some screenshot or a better explanation? Maybe I miss something

Superimposed symbols
Thank you for the report. The definition of "osmc_order" depends on the main color of the route. If multiple routes have the same color, then osmc_order can be the same for those routes. The "osmc_order" was initially used to set a different offset (dy) for parallel routes. But later I decided to use this attribute also for drawing the symbol along the route and it can cause the following problems. More interesting is the easter part where symbols do not overlap. But this is basically an error because 2 blue lines are rendered and it should not happen.
I'll check it and I'll consider consider a custom order tag for symbols...

@Invalid theme - I'll ask @Menion to check it because the theme contains the reported icon and it should be valid

@karlchick - No problem I'll add it.

@TrulloF
We published the python script that can help with the conversion theme from "Custom Locus V3" style to official Mapsforge V4
https://github.com/asamm/lomaps-mapsforge/tree/main/theme-v3-to-v4-converter
The conversion is not 1:1 but it can help to remove not supported attributes or convert DP units to "pixels" in V4