Messages

Hello,
In navigation, the blue labels with km and time are not full visible.

Inviato dal mio SM-A520F utilizzando Tapatalk

Good day John,
you are right. World vector map from Locus Store is built-in into improved MapsForge V3 system and is rendered little bit different than system suggested by Michael (with automatically selected optimized theme and some other minor improvements).

Anyway, I will have to ask for little patience. For some time, I work on improved system how will Locus Map handle maps and one of the changes will be united system how world map will be handled. And correct (and only) behavior will be as suggested Michael. But you will definitely notice this change (hopefully somewhere in February). Thanks for understanding.

Settings - Offline Maps - Preload global map ...

works for me, but I do not use the Locus world map, as you may guess :-)

@michaelbechtold
you mean around the rendering of maps?

I believe we all will agree that best from long-term will be adapt to latest MapsForge version. This on one side will be a lot of work mainly for @voldapet who work years on themes for LoMaps, on the second side, it simplifies life to all of you, who suffer from divided themes for Locus Map and other apps.

Currently, latest version 0.10.0 of MapsForge library is already in app so V4 maps (and in next version V5 also) are supported. Auto-loading most probably does not work, MapsForge POI's are another, currently not so important, story.

Anyway, support for external V4 maps is not problem for LoMaps (they may still use old renderer).

Issue reported by John is probably little more complicated.
MapsForge is based on the same system as Google Maps or other map frameworks. They have own "map view" component which has logic how to draw map tiles. Anyway here is a problem. Locus Map has also own component. For using maps from MapsForge V4+, I use own hack how to prepare map tiles, which most probably cause a new issue with labels. But seems, there is one active use who may save us for now: https://github.com/mapsforge/mapsforge/issues/1085 . So let's wait on 0.11 version of MapsForge, I'll then use this method and we will see .

Hello John
"Exit" is only available if "FullScreen" is enabled
with PRO and BETA

1. have to check it in "free" time. It's still available only after editing of config.cfg so I do not worry about malfunction too much .
2. nono, there is the difference. App analyze your movement based on type of navigation and also based on activity in track recording profile. So walking should not mess computed speed for driving etc. Anyway, more inner logic is definitely needed, I'm aware of it.
3. currently it is : below 1000 years: xxxx yards, and above x.x miles . Oki, I've changed it to keep yeards below one mile, thanks.

The theme used is a pretty current version of Elevate, not Andromaps, and the map is also one of OpenAndroMaps, as surface is rendered.
But the symbols/text size shouldn't be reduced by zooming, and also aren't in all but one example - that's just an optical illusion. As everything around is enlarged it seems that they are smaller, but they aren't. In the first example it seems like the text size is reduced via a Locus setting (or some bug), because in the theme code the size is constant.

@john_percy Car routing with turn restrictions is not possible at the moment — https://github.com/graphhopper/graphhopper/issues/1401

Without discussion with GraphHopper developers I don't want to publish car routing using CH because I think that turn restrictions (https://github.com/graphhopper/graphhopper/blob/master/docs/core/turn-restrictions.md) is very important. If will be confirmed that landmarks algo is very slow and it is not possible to speed up on mobile, CH will be published with a warning that  turn restrictions not supported (well, you have to always follow actual road signs, but people are people).

@john_percy I will add CH data to support car mode, it seems as separate graph routing data because of https://github.com/graphhopper/graphhopper/issues/1398

There's a mistake in your theme xml. bicycle_rental.png should be bicycle_rental.svg. Just check any bigger city (e. g. in Germany Berlin, Leipzig starting with zoom level 16).

John, this one was really bad . Problem was in incorrect naming of cached tiles, where rarely happen, that for some tile was took incorrect cached tile. I remember few times some people reported me about some incorrect shading and it was definitely this issue.
Perfect, I was able to simulate it on different place and finally fix!!
Thank you very much, should be work correctly in next (beta) version.

I would LOVE for major labels (eg a city) to not disappear at certain zooms, especially when I'm lost over the map and trying to *find* that city.

+1

Mapsforge, however, has solved the problem

I don't know where the rest of this conversation is, but it gives me hope.  I would LOVE for major labels (eg a city) to not disappear at certain zooms, especially when I'm lost over the map and trying to *find* that city.

Thanks, and Merry Christmas to all

Hi.
They changed their tiling scheme some time ago, so you can easily integrate it into Locus.
Just create a new xml file (e. g.  michelin.xml) in the \Locus\mapsOnline\custom\ folder with the following content:

<?xml version="1.0" encoding="UTF-8" ?>
<!-- ViaMichelin maps -->
<providers>
<provider id="80118" type="0" visible="true" background="-1">
      <name>ViaMichelin</name>
      <mode>Michelin</mode>
      <countries>Europe</countries>
      <url><![CDATA[http://map{s}.viamichelin.com/map/mapdirect?map=viamichelin&z={z}&x={x}&y={y}&format=png&version=201503191157&layer=background&locale=default&debug_pattern=.*]]></url>
      <serverPart>1;2;3</serverPart>
      <zoomPart>{z}-8</zoomPart>
      <zoomMin>16</zoomMin>
      <zoomMax>28</zoomMax>
      <tileSize>256</tileSize>
      <attribution><![CDATA[Map data ©Michelin TomTom Natural Earth<a href="http://www.viamichelin.de/">© viamichelin.de</a>]]></attribution>
      <extraHeader><![CDATA[Referer#http://www.viamichelin.de/]]></extraHeader>
      <extraHeader><![CDATA[User-Agent#Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/21]]></extraHeader>
   </provider>
</providers>