Topics

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.

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?

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.

I find that when we pause our walks for few longer moment to sit on a bench, the measured track length is getting a lot lengthier than the actual one (+10%). I guess this is because gps noise is recorded as well. I suppose by using a good noise canceling method, the 2 will be close together. My wish would be that this method would be more advanced. I know there are parameters by which to tune the recording like time and distance. But a stronger method, would also take different parameters or could be self learning. I know Oziexplorer works internally by taking angle, velocity changes etc into acount. For the user, only one "smoothing factor" parameter could be enough. Which even could be chosen with some preview/feedback when saving the current track and then controlling the post processing of raw data.
In short:
More advanced realtime smoothing for track display
Recording of gps raw data and controllable advanced smoothing with feedback when saving the track.

When walking along a route I found that Locus incorrectly warns about being off track. I guess Locus computes how one is off track by calculating the distance to the active waypoint. But on many routes, with long straight lines this waypoint can be quite far away. I would like it better if the distance to the active route section (the line to the active waypoint, from the previous) would be taken. In the case of going off track, I would like locus to talk (tts) me to the closest point on that section instead of to the active waypoint. I find it important that I can take the right roads, even if the wrong road is also close to the active waypoint. By measuring the distance to the active section, the max off track distance can be tighter, and the distances from tts will be smaller and more usefull. Now I get false messages like route is 100 m on 0 o clock. I would like correct messages like: route is 20 meters 10 o clock.  This is good info on which to decide wether to take another road in real life or wether its a false message coming from gps inaccuracy.

Today I found a new version of Galileo on my iPad 3. I never came to to use this app in the field. It's incredibly limited in functionality. That said, here comes the point: in respect of render speed of vector maps it just much faster than what I used to on my Note 3. Uch locus uch... I know Locus depends on opensource renderer of vector maps, but I guess this still has a lot of room for improvement. In Galileo it's so fast that it even hard to see individual tiles are beeing rendered. But I guess the difference isn't explained by hardware vs software rendering. Another speed difference is in the drawing of tracks, this Is also much faster in Galileo. They also have an instant search and display of offline pois.
B.t.w. this is not an attack on Locus, but one sometimes needs some reference to set a feasible target.

From what i understand it is possible to generate a sqllite db from the kadaster maps. Somewhere here there is also a howto. Has anyone succeeded in creating such a map? I think vectormaps are the way to go, but these kadaster tile maps can be of help in some situations.

Guidelines shrink while rotating the map.

In multicaches some waypoints usually contain variables, which should be replaced by some answers. For example: N°(G*H+I).(E/G).(A-(D*C)) E°(J-H).(J/2+I).(K*B+F)
What i would like is that these waypoint can be added to the cache in that form.
After that Locus extracts the variables, and makes a nice variable list.
For each variable in this list the user can enter the value / answer,
After that Locus automatically calculates the right coordinates for the parameterized waypoints.

I know quite hard to devellop, but this would be really cool feature. In the whole android store I couldn't find such an app.

At my Note 3, this new version directly crashes with a java.util.FormatFlagsConversionMismatchException
% does not support.

I did send a report. Is there a quick workaround?


Verzonden vanaf mijn iPad met behulp van Tapatalk