Messages

Is this the suggestion that you refer to: http://help.locusmap.eu/topic/independent-configuration-of-navigation-services-for-carbikefoot ?
I found the suggestion hard to track down on the help desk!

Would it make sense to ask menion to allow Locus to choose different routing engines according to travel mode?
I would like to choose GraphHopper for car travel and BRouter for travel by foot.

Each product has its customers, none is intended to serve all , whatever product domain is considered.

For off-line car navigation, GH is definitely a good choice.

For bicycle and foot navigation, one can have with GH any ice cream flavour whatever one wants, if it is vanilla. Nothing bad with vanilla. For other flavours, there is the Brouter.

Ok for me.

[no|yes]

When the "Autorecalculation" options changed from no|yes to no|point|track, it appears that if the setting was "yes" it was lost and changed to "no". That was my experience and is kind of logical.
I guess that ideally the update screen ought to flag up changes in settings like that.

The following two snippets control the outline and fill of unclassified roads at zoom=13 and above:

Code Select Expand

<rule e="way" k="highway" v="road|unclassified|residential|living_street|ford" zoom-min="13">
<line stroke="#222222" stroke-width="3.20" />
</rule>


Code Select Expand

<rule e="way" k="highway" v="unclassified|residential|living_street|road|ford" zoom-min="13">
<line stroke="#FFFFFF" stroke-width="2.20" />
</rule>


The following snippet controls the appearance of unclassified roads at zoom=12 and below. They are shown as a single grey stroke:

Code Select Expand

<rule e="way" k="highway" v="unclassified|residential|living_street|road|ford" zoom-max="12">
<line stroke="#CCCCCC" stroke-width="2.20" />
</rule>

There is no zoom-min here, so if the road does not appear at low zooms, it is because the map itself hides it. You may find that the relevant map from OpenAndroMaps shows unclassified roads at a lower zoom in your region but I don't know.

@gynta: I don't think that helps as Genymotion runs on Oracle Virtualbox and and is required to provide the Android environment that is needed.
@Andrew: Can you create tracks on Locus Free/Beta on Genymotion?

So Locus free or beta works on Genymotion with Windows 10? And I can confirm both Locus pro and free (and beta) work with Genymotion on Windows 7.

Hi,

you're right. However - firstly, we are planning to reduce their number, select only the most used, and change their naming in order to improve their comprehensiveness.

What a good idea

Me too

On an earlier version of Locus I could not log on to GPSies from Locus and had to first log on to GPSies from the GPSies app on Android itself. After that it was OK. I had previously registered from the web.

BRouter 1.3 has been announced in the German language version of this forum: http://forum.locusmap.eu/index.php?topic=4064.msg39621#msg39621

I've uploaded the version 1.3 (only distribution-Zip, not on Google Play yet):

http://brouter.de/brouter/revisions.html [in English]

This is a purely technological update, it makes the data files considerably smaller, making the carsubset files unnecessary and improves memory footprint, thus preventing out-of-memory error.

This is only intended as an interim release, and version 1.4 will (hopefully) bring new functionally (voice hints?) and reappear on Google Play. But I will now first experience problems with the file format update in "friendly fire"

Gruss, Arndt

The data files are considerably smaller, with no need for a carsubset. They are stored in a directory "segments4" which is automatically created with a file "storageconfig.txt" that includes a value for "secondary_segment_dir" pointing to the old directory (segments3), so that is also found and the old data can be used. If you have customised the file locations, you will need to edit the new storageconfig.txt after running BRouter once.

My advice is to use the BRouter download manager to download new data files and then delete the old ones in segments3. Data files can be updated from the BRouter download manager when a new version is available.

It's working for me.

PS. I've made use of walking and cycling profiles from https://github.com/poutnikl/Brouter-profiles/wiki/Brouter-profiles-collection to select the profiles most close to my preferences and altered serviceconfig.dat accordingly.

When a vector map redraws on changing themes it sometimes results in one of the squares displaying black areas. Scrolling the map so that part goes off the screen and bringing it back on forces a correct redraw. It's not terribly reproducible but it does keep happening.

The version I uploaded yesterday required further tweaking of sea, coastline and riverbanks, particularly in the Velocity theme. Sorry.
Revised version in the first post and available in Locus Store (free).

Because there is no beta version at present. The Store version of the app is fully up to date.
Once Menion releases a new beta, your Locus Free will update to a beta version of locus pro (more or less)

Revised version in the first post.
Recent Changes:
Forest, wood, orchard, desert, glacier, desert, nature reserve captions now appear at varying zoom levels according to their size when using recent OAM maps
Debugged military airports, woods and forests, widened paths slightly, tweaked rendering of service roads and living streets.
Bugfix for access on footpaths in tunnels and private highways