Messages

@den def you're right it could be better. We'll check it and try to improve it
Thanks, Petr

Ich finde das auch nicht ganz glücklich. Oft wird halt vergessen weitere Informationen anzugeben. Ich würde alle Parkplätze nehmen außer Privat usw.
Aber du kannst es verbessern in dem du solche Parkplätze in OSM mit Informationen füllst. Kostenlos, Anzahl Plätze, begrenzte Parkzeit (sehr wichtig)öffentlich oder Kunden, Privat usw. Ganz gut geht das vor ort mit OSMgo App.

Unfortunately, there are lots of parking lots that are private but this information isn't available in OSM. For this reason, we display only parking lots with defined "access"

Hallo,
vielen Dank für Ihre Nachricht. Locus POIs sind streng bei der Anzeige von Parkplätzen und es werden nur Parkplätze mit access=yes|public|customers angezeigt.

Vielen Dank
Petr

-- EN --
Hello,
thank you for your message. Locus POIs are strict when displaying parking lots and only parking lots with access=yes|public|customers are displayed.

Thank you
Petr

Well, amenity=bicycle_park is included in the online/offline POI, but I understand and added it to the tag-mapping file.

@karlchick
- building will be from ZL 14 and the importatnt ones from ZL13
- landuse=retail from ZL 13

@karlchick
place=locality from z15 - changed
buildings - which buildings are important?
landuse=retail - does it have any effect for zl=10?  I mean - these areas are often quite small and the user cannot recognize them in zl=10

OK, it's changed...

this is more question on Mapsforge team https://github.com/mapsforge/mapsforge. Anyway, as I know, it's impossible to write a rule the way you intend. The wildcard '*' can be used to "replace" an entire key or value. It cannot be used as a wildcard for part of a key or value

Thanks,
Petr

as @Menion mentioned we've already created some improvements in the official MapsForge render and adopted "cubic" or text and symbol orientation. 
I also like the scale-font or scale-symbol directives but I think it doesn't fit the conception of theme when only the "rule" should specify the appearance of a particular element.

bg-rect-* are also a little bit strange and were created especially for our use-cases. Anyway, I've already thought about adopting of the "Shield" system used by Mapnik https://github.com/mapnik/mapnik/wiki/ShieldSymbolizer
It's basically a combination of image and text - especially used for highway number shields. 

@karlchick yes, 'lm_highway' is a copy of the original 'highway' tag. So every value of the 'highway' tag is available in 'lm_highway' tag. Of course, you need to take into account the set of tags of the tag mapping file https://github.com/asamm/lomaps-mapsforge/blob/main/various/tag-mapping-xml/tag-mapping-tourist.xml#L1328

The following tags are copied from the original way to "marked trail" way:
- highway (as lm_highway)
- sac_scale
- tunnel
- bridge
- layer
and ferry=route is mapped to custom lm_highway=ferry

@karlchick
I understand that in this situation the "layer" tag is probably misapplied (as per the instructions). However, I have always tried to avoid manipulating OSM data "from the table" (unless it's necessary)

I really think the best solution is to add a "layer" tag for hike & vike way as well. Please try the following map (not posted in the store). I think it should solve your problems.  https://gofile.me/7ecf2/CVYghVabB

In any case, this is very likely to cause further complications. Mapsforge has an internal limit where a node/path can have a maximum of 15 tags. I know there are already paths with 15 tags and I'm afraid that using a layer tag will exceed this limit. Well, we'll see during the next generation

@karlchick the updated England map is available in the Locus Store. (the map version remains the same - please delete the map and download it again)

@karlchick
thank you - problem was more complicated. All ways in relation were ignored in case that the relation has another child relation. And only members of such child relation were marked as bicycle route.
I'll inform you when map is fixed (re-generated)

Hi,

all themes were removed because were created for LoMaps gen 3 and weren't compatible with gen 4. But some authors were preparing new version compatible with LoMaps gen 4. @john_percy @karlchick do you think is it possible to publish your themes in Locus Store?

@alick
...good question. To be honest we aren't very familiar with Google Play Credit but according to https://support.google.com/googleplay/answer/6080850 it may be possible to buy also subscription with Google Play Credit

Check if your country allows you to pay for your subscription using your Google Play balance/credit. Google Play should prioritize your GP balance on your next renewal. This means you don't need to take any additional steps, you can keep your subscription active and Google Play will use the balance for your next renewal.

I would rather suggest setting the Google Play balance as the default payment method (Google Play > Menu > Tap Payments & subscriptions and then Payment methods and then Google Play balance.)

Anyway, you can contact us in November and we can refund your payment if the GP balance is not used, and we would focus on dealing with locoins...