Messages

Great!

When creating a route with navigation commands, each subroute is terminated with a "via point" waypoint.  However it would be nice if it was made with a localized instruction, because while navigating it is spoken out by tss.

This version crashes right at startup. One strange thing was that LocusPro got a strange android icon with "sd" marking on it. I did a fresh install and now it seems okay.

When creating tracks and alternating between "route calculation" and manual adding points, the finnish navigation command wpt stays. It would be nice if adding points would remove it.
One can convert a wpt to a navigation wpt, but I think it should be possible to clear the navigation stuff of a wpt as well.

In Locus I show always show the tracks I've walked/travelled by bike. On some places this can be quite cluttering, but I need to see them stil, because I evaluate new tracks in comparison to them. Have I visited that area before? So when i click on the Locus map at a low zoomlevel I already get a popop with many tracks. To my experience the tracklist isn't sorted on closest to clicked point. This makes it hard to select the right track.
I often use my stylus, and then it should be possible to skip the tracklist more often because of the click accuracy. It would be nice if the Locus did sort the most close tracks and would single click select if the closest track is lets say 2x closer than others without showing the popup. (Make it a config parameter). Otherwise a sorted popuplist could be shown.
If this works more optimal, then a long click could be used to select AND show extra options like edit and statistics.
I guess for real track editing, the track has to be brought in a different state, like how creating a route now is implemented. But that functionality might be improved as well. Now it's very hard to move a routepoint instead of creating a new one.

So to solve my issues I would prefer the following (internal)trackmodes:
Hidden, not shown.
Inactive, this mode could be set in itemlist. The track are visual only and don't react on clicks.
Normal, can be click selected or longclick selected with popup.
Selected this mode is visually different with direction indicators, maybe trackpoints also. With a long click a popup can be shown. One item is track editmode.
Edit mode: trackpoints are shown and can be moved and selected. A selected point is the base for the delete, delete all before/after. For me it would be nice to have a split option, which also connects the previous end and tail and thus opening the track on the splitpoint.

In my house people use the hallway to go to the toilet in 90% of the time. So what I did was I put the toilet in the hallway. And now we climb out of the window to go outside :)The problem here is that the statistics screen is somewhat obstructive, it is an extra UI to visit to come BACK in the UI where one needs to be, but in a different state. I don't like it either. Optimizing software to do someting faster on average isn't always good. User don't count seconds, but irritations.

I don't mind paying for this service, soo no props...

The new Locus has a cool feature of displaying a small minimap for explorered tracks. Is there a way to have them generated for all tracks?

Yesterday I updated my Netherlands map, I had to use my free gift thing again. I think it was less than a year I did "the purchase". Since how long are coins supported in Locus?

In the original route the start and end points aren't connected, thats why after a normal split I end up with two tracks.

Many routes end where they begin. Sometimes it's more convenient to start somewhere in the middle. What I would like is a single function that splits the track on that location and connects the old end/start points to eachother. This means guiding can start and the total distance is correct. I know one can do this by splitting and merging, but these require a lot of actions in the field.

Thanks for your reaction. Maybe GPSBabel can be used, to extrapolate trackpoints, but it isn't the road I would like to travel:). Most of the time i'm hiking with my family, including one 4 year old. I guess the average speed is 1 meter per sec. So 50 meters correspond to 50 secs, almost a minute. That's why I would like the distance to be very short, somewhere between gps accuraracy. Which I believe can get more and more accurate with galileo satelites. I don't know wether these are supported by my phone, but there is where beautiful possibilities ly. Because Locus uses the suboptimal off road calculation, I have to do a check every time I meet a crossroad in real life. This means placing a trolley upright, getting the smartphone out of my waistbag, looking, smartphone back, thumbs up to the family, and pulling the trolley down the road again. I would like to change this behavior into just listening to the voice commands from locus. However this is still better than having to do a route preparation to get it to work the way it should imo .

Bedankt voor alle uitleg, thanks for your reaction. For 20 meters this workaround won't be enough. It is probably best if this is solved fundamentally in Locus. In the field I also sometimes get wrong direction via speech, which shouldn't have to happen if the guiding is implemented completely thought out. This means leaving the idea, that one is "only" traveling from one point to another. From a developer perspective it isn't obvious that a new track has to be created to get navigation commands.

Indeed guiding modus. The out of track setting in meters is, when implemented to tracksections a balance between more false warnings or slow correct warnings. I think 20 meters should be possible. If one gets a false warning on a straight road, i can keep the phone in my pocket and because it happens only in the case the gps is temporarily inaccurate it will only happen sometimes. With a good smoothing algorithm this can be further reduced. Now the off track distance needs to be chosen with the distance between points in mind. Most off the routes I draw are with the use of Brouter, which give great accuracy and sometimes a lot distance between waypoints, when roads are straight. So my wish would be that Locus is mathematically more optimal, without creating more waypoints.

Hmm I thought I had set this option on, but I didn't. Next walk I will check the result. Nethertheless I think the thought of raw data, which can be turned into a definite track with some extra tuning could be fruitfull.