Messages

The used tags in OAM and LoMaps are different. LoMaps use almost the same key|value as original OSM tags but as I know OAM uses lots of custom keys|values.

Anyway, the mentioned residential areas are available in LoMaps as `lm_landuse=residential_city` https://github.com/asamm/lomaps-mapsforge/blob/main/various/tag-mapping-xml/tag-mapping-tourist.xml#L946

The original `landuse=residential` will be available in the map in the next version of LoMaps

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

Hi,
it seems that the script is not able to work with XML file if isn't in UTF8 encoding. Would you please share your theme file and I'll check it.
Thansk Petr

Hi,
I'm sorry but could I ask you for more info? What does exactly mean "doesn't work perfect with Lomaps."?
Anyway, some info about conversion can be found in topic https://forum.locusmap.eu/index.php?topic=8427.0


I'm sorry but I'm not sure I can understand the sentence. Could I ask you to describe it more detailed?
>Very general: are different assets included into lomaps? Maybe even renamed ones?

@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

Hi,
the number in the red badge represents the discount on that item. A -100% means the item is for free.

@wkin
It's still in progress because communication with KOMPASS is quite slow. I can't give a clear result at the moment, but I think our negotiations are on the right track.

@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
ahh thank you. I missed it.

The "osmc:symbol" for this way is extracted into these values:

Code Select Expand

  <tag k="osmc" v="yes"/>
  <tag k="osmc_color" v="red"/>
  <tag k="osmc_background" v="black"/>
  <tag k="osmc_foreground" v=""/>
  <tag k="osmc_text" v="XE"/>
  <tag k="osmc_text_length" v="2"/>
  <tag k="osmc_text_color" v="white"/>

Please note especially the "osmc_foreground" that's empty but it should be "black_rectangle". This is my ugly workaround when the color of the foreground symbol is the same as the color of the background. The pseudo-code should look like:

Code Select Expand

if osmc_foreground.hasTheSameColor(osmc_background):
  set_value_empty_for(osmc_foreground)

The reason for this hack is a problematic rendering of text symbols that are not rendered by LoMaps theme. In the theme is a rule that requires defined osmc_foreground - I mean symbols are rendered only when osmc_foreground is defined (to avoid empty black rectangles).

Anyway the text and text color values are available in the data and you can use them

@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

@Gerhard57
I see thank you for the info. Well the width of the text is increased when changing the scale for text. I'll discuss it with @Menion but I'm not sure if we can improve it.

@john_percy Honestly, the position for captions remains in the theme very likely from my testing of this attribute. As I recall, "position" without an ID has minimal effect. It basically changes the defining point for the text box (the minimum rectangle around the text).