Messages

Hello Christian,

main key parameter for guidance that influence "when" Locus switch to next trackpoint is "Set next trackpoint" (in Guidance settings).

About rotation ... good observation. Locus filtered values from "before" screen turned off. I've fixed it now. Result is quite visible jump in rotation right after you turn screen on, but positive is, that you see it almost immediately. So "fixed", thanks.

Hello Petr
We talk about "house number sorting" in march 2016. do you remember?
I think alphabetical sorting arrays will be work. Let's try
Currently we have a wild mixed list.

done

@Andrew Heard
My description were quite simplified. There are more values that influence if road / street has record in DB. Num of segments (number of OSM Way with the same name), the distance from the city (if any exist around), houses along the road...

The handling of long roads is not ideal and the address database does not expect that there could be long roads outside the towns. The generator process them but there are some weakness.
More over is complicated to recognize if Osm Way  is part of street inside any town if it is only some named road outside.  For example almost every forest track in Germany has defined the name. For example https://www.openstreetmap.org/way/37641016

And the question is how handle such way? Is it street? Should we use this road in address search? This is probably the question for every body..

However you can send me some mistakes and I'll check them.

@Andrew: hmm I'm almost sure that my small change should have no influence on this. I may disable it, as it's just one line of code, but it really should work without a problem.

Do you have exact steps I may follow to get exactly same problem?

I'm trying to play with it little bit, but GPS is always turned of correctly in Locus, hmm :/.

EDIT: maybe I've found some weird combination, so next version probably during weekend, thanks

Hehe, oki guys, you are welcome. To make it more "fast", after save of changes, screen will be closed back to map. Hope it will be ok. And btw. do not forget to enable this button in settings, because I left it disabled by default.

Hmm, this isn't what I wanted to hear . Implemented.

Ich hab' heute ein neues Release (1.4) hochgeladen, was die Abbiegehinweise enthält:

http://brouter.de/brouter/revisions.html

Gegenüber dem letzten Patch, den ich hier vorgestellt hatte, ist das schon deutlich anders.

Es gibt "keep left/keep right" Hinweise und explizite Kreisel-Ansagen. Aber auch, wenn man mit dem "trekking" Profil entlang der Radwege über eine komplexe (Kreisel-)Kreuzung fährt, wird das in der Regel zu einer einzigen Winkel-Anweisung vereint, die dann nur noch sagt, dass man (alles-in allem) nach links fahren soll.

Ist also bisschen das andere Extrem zu dem vorherigen Zustand mit zuvielen Hinweisen, und kann auch irritierend sein, wenn man für eine links-rechts Kombination mit weniger als 40m dazwischen einen "geradeaus" Hinweis bekommt.

Aber nach meiner bisherigen Erfahrung ist eigentlich nur wichtig, dass man einen Trigger bekommt, was er dann sagt ist eher zweitrangig.

Ich hab' das im dev-forum alles auch Menion erklärt, und hoffe, dass es bald eine Locus Version gibt, die auch für Berechnungen über die Servive-Schnittstelle diese Hinweise verarbeitet.

Bisher geht's it Locus nur über den manuellen Import von GPX-Tracks. Werden die mit der BRouter-App berechnet, sollten die die Locus Hinweise enthalten (wegen turnInstructionMode = 1 = auto in den Profilen). Will man sie in brouter-web berechnen, muss man turnInstructionMode = 2 setzen.

Die zweite Neuerung in dem neuen Release ist ein "erweiterter Scan" nach Wegpunkt-Datenbanken, weil ich mitbekommen hatte, dass das öfter zum Showstopper wird, wenn die Installationsorte der Maptools nicht automatisch gefunden werden. Hab' noch keine Erfahrung, wie gut das mit Android 5, 6,, (7) .. funktioniert.

Gruss, Arndt

Anyway if you will wants to use format I use in Locus, less work for me, anyway it's not clear solution I think.

Hi Menion,

sorry for the long delay, but here's what I came up with.

You can use the latest version (1.4.) of BRouter from it's homepage (not yet on Google Play):

http://brouter.de/brouter/revisions.html

use the apk there'in, and also update the routing profiles (they are not automatically overwritten by an APK update. Simplest way is to just delete the "profiles2" directory, it will be re-created on next brouter app start)

After careful consideration, I decided to go with the native turn-instruction formats used by Locus and OsmAnd.

3 ways to generate an GPX, so 3 ways to make sure that Locus format is used:

- when creating a GPX via the BRouter app, nothing special to do. The profiles are configured to "turnInstructionMode = 1 = auto, which means it generates Locus format when using a Locus waypoint-database.

- when creating the GPX by requesting it via the AIDL interface, you must send an additional parameter
  "turnInstructionFormat" with value "locus".(Just the same way you are sending "lons" and "lats", but with a String value)

- when creating a GPX via the Web-Interface ( http://brouter.de/brouter-web/ ) you have to modify the profile to contain turnInstructionMode = 2 (use the "upload" button the upload the modified profile)

I tested the voice hints by manuelly importing them into Locus, and that works fine. So I really wold like to be able to use them also when using BRourer via the AIDL-Interface...

What you have to change for that is:

- send turnInstructionFormat = locus as secribed above

- evaluate the locus extensions containing the turn-instructions the same way you do it when importing with "merge waypoints into track"

What you should also do is look at a bug I encountered when using the "roundabout" hints:
the first instruction after a roundabout that is not a roundabout is announced as the last roundabouts exit count ("third exit") instead of the actual next instruction ("turn left").

Thanks in advance for looking into this,

regards, Arndt

@Andrew Heard
1) North Street and Slovenia Ljubljana - this should be fixed in the next address database that is in generation process

2) Inconsistent suburbs - Well it's similar to previous problem - to find the best city / district / suburb for street. If no suburb is found for street then no suburb is shown in dialog. However especially mentioned Grenfell St should be displayed with Suburb - I'll check it in the next DB (probably in the end of this week)

5) @menion I can confirm issues with Swiftkey keyboard

[previously]

yep. It really just preselect tha ONE item you long clicked. Nothing more and it won't have effect on visibility/selection of other items. So in case, you have visible a lot of points/tracks on a map, but wants just select two of them, you had:

previously: tap on bottom button, in top toolbar tap "selection button" > deselect all and then tap on wanted two items
now: long click on first item, then select also second item

Hmm sounds good. Thanks for help.

Hmm good point. So to make it "different then bottom button" and more useful ... just long-tapped item will be pre-selected. Not all currently visible + long-tapped. Agree, done, thanks.

[The Voluntary themes support OAM maps and both new and old LoMaps.]

Theme last updated 22 January 2024. Download and install from https://voluntary.nichesite.org

The Voluntary themes support OAM maps and both new and old LoMaps.


The Voluntary theme is designed for clarity of display. Its colours are based on UK Ordnance Survey conventions and will be fairly familiar to British users. Even if you are not British, the colours and styles will probably work well for you. It automatically scales for devices with displays of different resolutions and symbols enlarge smoothly for higher zoom levels. The zoom levels at which various features appear has been adjusted to provide optimal information and reduce unwanted clutter.



You can choose Hiking, Cycle, City, Multi, Yellow or Transparent style when you select the Voluntary UK theme.

The styles take advantage of switchable options. Display of hiking, cycle and mountain bike routes can now be switched on or off, as can highlighting for each of them. The number of options shown is relatively limited to aid ease of use. Cycling, Hiking, City and Road styles function almost as presets with a limited range of tailored options. Within these particular styles the display is subtly tailored to its purpose: for example, Road displays junction and road numbers better; Cycling has a better display of cycle routes. Multi, Transparent and Yellow have a fuller (but manageable) range of options. Locus remembers the settings of the options for each style.

The City style is aimed at use in large cities such as London and has a less cluttered (and slightly faster) display at low zoom levels. Colours in the Yellow theme are more muted and are aimed at use with overlays.

A "Transparent" style turns off the map background and enables use of a vector map as an overlay on top of a satellite image in Locus. Similarly the "background" checkbox in the Yellow style can be used to achieve the same effect.

Generally, blue dashes are cycle ways, green dashes represent dual use both on bike and on foot (bridle paths in the UK), and brown shorter dashes use on foot only. Blue blobs are cycle routes, green blobs are hiking routes. Mountainbike trails are shown by violet blobs. Cycle routes are also indicated by blue dashes on the roads. Hiking, cycle and mountainbike routes can be emphasised by selectable overlays.

The theme is designed to work well with both LoMaps from Locus Store and maps from OpenAndroMaps. Footpaths, bridleways and cycleways are indicated on the map by dashed lines where they follow the path of a mapped track or pedestrian way if the map supports it. On maps from OpenAndroMaps, blue dashes on roads are either cycle routes or roads with cycle tracks alongside, while shorter blue dashes on roads show cycle lanes in the road.

The Locus package includes two flavours: one that works with older LoMaps (LE) and one that works with the newer LoMaps as well as Mapsforge maps, such as from OpenAndroMaps (V5 LE). The appropriate theme appears according to the map selected.



Also included is the visually-similar Velocity theme for a simpler display with much faster drawing.   

The package is also available in  versions for other apps such as Cruiser, Orux Maps, etc.

o V5 for latest versions of Cruiser, Orux etc
o V5- for apps that cannot display text on curved paths
o V4 for apps that cannot scale dotted and dashed lines.

Voluntary and Velocity themes can be downloaded and installed from https://voluntary.nichesite.org

[EDIT:]

version for testing before release on Android Market

[attachment=0:lkzq65mw]0.3.0 RC1.apk[/attachment:lkzq65mw]

EDIT: topic closed, application in version 0.3.0 is on market now