Messages

[edit]

I have a different bug with 3.8.2 pro that I don't think anyone else has mentioned yet. In guiding mode the "next waypoint" is one ahead of what should be displayed currently making it useless. You can see below I have created a simple test track, and converted 3 points to coursepoints, and manually changed the text. I have annotated the screen capture with the navigation text - "turn left", "straight" and "stop". The "turn left" text was never displayed, the "straight" text was displayed when I was close to "turn left" but you can see that the 3rd & final point "stop" is displayed in the screen cap & I haven't even reached "straight" let alone "turn left". I first noticed this on a proper cycle trip a few days ago.


edit
I have made a simpler track with 4 navigation waypoints which I named 1 through 4 in Garmin Training Center then re-imported (the labels in the screen capture are added by hand, not in Locus).When I enable guiding the navigation text briefly displayed "2" then skipped even further ahead to "3".

download down

reupload possible?

ZippyShare says this file no longer exists. Can you place in more permanent place?

But it would be great, if the line style might also be set in this context to have a possibilty to indicate the direction (e.g. any arrow style, because is often difficult to read the display of the smartphone in light surroundings quickly.

I also want line style setting for arrow type. If this idea is adopted, please take care to reverse arrow direction for reverse guidance.

+1

It would be nice if Locus just had one "forum" instead of reading duplicate/ parallel discussions in two different "forums" -  http://help.locusmap.eu and http://forum.locusmap.eu. I know forum.locusmap.eu was first. Maybe a phase out of this somehow, with everyone having to move to help.locusmap.eu after certain date? help.locusmap.eu seems better in all functionality respects.

Andrew. No manual, no specialised group ( a moderator ?). In non technical words so mine:
Courses(tracks) and Coursepoints(waypoints) belong to .tcx files. Garmin system and terminology (edit)

Thanks 0709. There is a manual discussing points, tracks - http://docs.locusmap.eu/doku.php?id=manual:data:data_basics. Does it just need improvement? I assume Locus staff are the moderators? Good doco hopefully means less questions, less support, happy knowledgeable users, more sales.

How about a separate forum group for Navigate, Guiding, Routing, TTS, Voice,... aso ?

And in the longer term the online manual could do with a lot more information in this area too, maybe some doco+video in tutorial style in additional to the existing reference manual style. Several terms like coursepoints, waypoints are often discussed here but never fully described that I can find. Then there are the "invisible" points along a track that BRouter creates, what are these called?

4.4. Well ... let's root our devices, which is best possible way how to get rid of this crap feature.

you can't hope or expect an ordinary user to root their device; I don't do that because it voids warranty

Just browsing the GH code, a tremendous amount of effort has gone into the project, so a big bravo to the developers. An amazing effort. I hope they continue to improve GH.

Slightly off topic but after some email discussion with dev Peter from GraphHopper, I find a more important distinction between BRouter and GH - BRouter routing rules/ costs are heavily determined via a profile script which a user (non-programmer) can modify/ tweak or substitute, whereas GH routing rules/ costs are currently determined solely by the Java code within the packaged APK, meaning a non-programmer can't modify/ tweak or substitute other than choosing one of the 5 Locus profiles (fast/ short car, fast/ short bike, walker). I have found GH favors "dirt track" over "primary road" for a Locus "fast bike" profile however I have no control over this. I'd like to stay on the sealed road if possible. There is no current way to alter this logic, so I revert to using BRouter, even if Compute Instructions are not available.

[edit]

Hi,

A few weeks ago I first tried GH. I downloaded Netherlands and Belgium.  Worked well.
Last week I transferred Locus to SD-card.
And this morning I downloaded GH France.
And I tried tot navigate in France. No go!
Back to GH Add-in, to select France. Seems to work. But not the navigation.
Back tot the GH add-in. He, it is still on Belgium. Select France again.
Leave add-in, and start it up again. Hé, Still Belgium is selected.
Try to select Netherlands (worked, a few weeks ago). Leave add-inn and start again. Still Belgium.

Ergo: Selecting an other country does not work anymore. Has it to do with the Locus transfer to SD-card? What can I do?

Thanks!
Paul.

Paul - did you get GH routing working again? I can see no other suggestions or further discussion in this topic. GH routing works for me in my native country - Tasmania/ Australia. But when I swap maps to France, ile-de-france.osm-gh, I get a Locus error displayed, possibly same as you? I am using GN 0.1.3. Routing works fine with BRouter. Both points are on the same map, and only 3km apart. I have tried points further and closer together.





edit
Whoops - I worked it out - I must manually run the "Locus GraphHopper" app & explicitly select one of the GH regions I have copied to the GraphHopper folder. My mistake.

Thanks for that tommi - I was completely unaware of the difference - interesting.

... it is the only offline routing possibility in Locus.

Hu?

How about BRouter - latest update 19th Feb. Latest GraphHopper data 8th Jan.

I have only just come across this forum - http://forum.locusmap.eu.
Up until now I thought all discussion had been at http://help.locusmap.eu. That's where I had created all my topics.
They appear to serve the same purpose.
What is the difference?

Hi Gynta
Please send me an invitation, nickname "AndrewHeard". Where do you send this invitation?
cheers
Andrew