Messages

What happens with a scalable theme like my Voluntary UK, where everything is defined in terms of dp?

Surely you should zoom in or out accordingly? What happens with your column B images if you zoom in at higher resolution, so the same area of real life is shown on the screen?

@fingret
1. What method are you using to generate navigation routes with BRouter?
2. Have you got "from" and "to" Quick Points working with BRouter? If not, the most likely error is in not setting the additional maptools directory correctly in storageconfig.txt and not creating a brouter.redirect file. See my comments a few posts previously.
3. If you have "from" and "to" Quick Points working, I can only guess that you have set the nogo Quick Point up incorrectly. Could you attach a screenshot of the details of the nogo Quick Point?

valid syntax of nogo area is
nogo[km] i.e. nogo100

Actually correct syntax is
nogo[m] [comment]
where [m] is distance in metres (default 20m) and [comment] is any free text. Both [m] and [comment] are optional.

I actually constructed mine using the function built into Emux's Atlas, but using a Java console window to get more memory when launching Atlas.
Command line from windows: java -Xmx1024M -jar Atlas.jar (make sure java is on the path, and launch from the Atlas directory)
Atlas is at: http://www.talent.gr/public/atlas/
osm.pbf files from: http://download.geofabrik.de/ (I used a Special Subregion from teh bottom of the page to get data for the entire British Isles)

Actually the syntax ought to be correct according to the BRouter readme:

So "nogo", "nogo1000", "nogo roadblock", "nogo200 badferry" are all validnames for nogo-waypoints.

Edit: I can confirm this syntax works for me with BRouter and Locus.
I have a Quick Point defined as "nogo50 point{c}" to generate numbered nogo points like "nogo50 point2" for the second 50m exclusion area (and also "via{c}" to produce points like "via2" for the second via point) and it works fine in all the various routing methods available in Locus with BRouter.

I have Locus in main memory, that is, not moved to external SD. That allows me to use the Locus widget.
I set the Locus root directory to be on the external SD. That has drawbacks, not least that all the data is deleted if I ever uninstall Locus but I can live with that. You don't have to do that.
I created a directory on the external SD named LocusMaps and set custom directories for vector maps etc as subdirectories of that, using settings>miscellaneous>default directories
I moved relevant data to those directories including the GraphHopper routing folder. So I have a directory mapsVector/british-isles-gh
And it works.

Lollipop, actually.
Yes, finally got it working (well, still to ensure via and nogo works - tomorrow)
Many thanks for your help.
I really like the BRouter hiking routes which seem much better than GraphHopper. Doing it this way allows me to choose between different profiles, as well as having no go areas.

Edit: Now via and nogo Quick Add points work with the BRouter app method. And nogo works in both the Quick Navigation and the Add new route and measure methods, which I hadn't expected until I read right through the readme!.

OK, this is where it was getting complicated but re-re-re-reading the two readmes has finally got me there!
For the sake of anyone else who might want to try this, these are the two extra steps I had to do.
Having set custom directories for Locus and having set Locus root to my secondary SD card, I had to
1. Edit storageconfig.txt in the brouter/segment3 folder to have the line:
additional_maptool_dir=/storage/sdcard1/Android/data/menion.android.locus.pro/files
(And then remember to remove the # at the start of that line). That's the value I had chosen for the Locus root directory

2. In /storage/sdcard1/Android/data/menion.android.locus.pro/files/Locus/mapItems, where BRouter attempts and fails to write a track (construct that location from the result in step 1) I had to create a text file named brouter.redirect with a single line that is the location where I wanted the track to be written, such as /storage/sdcard1/brouter (or in my case, /storage/sdcard1/LocusMaps/mapItems, which was the value I had set for my my custom writeable mapItems folder)

Yes, that's right. And also if you leave Locus in main memory and set custom folder locations on the SD.

i really hope you have patience on my pitiful attempts to help.
I'm sure it's easy - but not yet.

please try only a from - to (no "via" and "no "nogo")
with add quick point.

I am very grateful for your help.
I have tried a simple from and to using Quick Add Points and the BRouter app. It doesn't work for me. No points found.

I'm getting confused now.

resume:
Route & measure
Quick point "from -> to"  with Brouter works

Using the add a point button in the bottom toolbar and using BRouter within Locus, yes. Not the "Quick point" (from/to) from the screenshots that we were discussing earlier and using BRouter app.

Route & measure - Quick point  - "from -> via -> to" also?

Using the add a point button from the bottom toolbar to produce a route and using BRouter within Locus, yes. But not the "Quick point" from the side bar. However that does mean I can define a series of any number of via points - good. BRouter produces good routes for walking or hiking.

and only Route & measure - Quick point  - "from -> via -> nogo50 (eg) -> to" make troubles??

Correct. I have no way of doing "nogo". BRouter doesn't seem to look in the right place for these

Route & measure works fine also (first time I ventured there).

Android version 5.1 on MotoG

From -> to works with BRouter using Locus navigation
From/to BRouter Quick points method does not work at all.

a) yes
b) yes
When I get to 4:27 in the second video, after selecting the profile I get: