This object is in archive! 

Real track width : define a track width as it is actually but corrected with GPS accuracy

Fifi shared this idea 7 years ago
Declined

Track style width is very useful when you have to do a search (and rescue for example). You can define the default width to correspond to your field of view.

For example 5 meters on each side in a forest, 10 meters in a field, 20 meters on the water, etc ...

With this, you can have a live view (or also a recorded view later) of the search total covered area and the holes in the search.


But, it doesn't take in consideration the GPS accuracy at the moment of the point is added to the track.


So, could we imagine to have an option for that where the result of the track width will be something like that :


path_witdh_settings = 20 m

real_path_width = if(accuracy>path_width_settings;0;int(path_width_settings - (accuracy*2)))


Idiot idea or good idea ?


Cheers,


Fifi

Replies (3)

photo
1

Good day Fifi,

I understand your point. It's absolutely correct that accuracy has no effect on this "width" parameter now.


I see here one main problem and it is "accuracy" value itself. This value is from my experience usually a lot worst then real accuracy and value do guarantee nothing. So from my point of view, using received "accuracy" parameter for some precise compute of width, will cause only wavy line without an usage.


If you anyway care about this, what about using current width of line and colorize line by "accuracy"? Then you should see where values are less precise just thanks to color.


I'm trying to find some alternative also because I believe that this "width in metres" is really rarely used. And adding some more parameters is really far far beyond usage in hike & bike app. Thanks for understanding.

photo
1

@ Menion


Advise. Best not remove trackwidth setting in meters. Rarely used but nice to have and usefull.


See: http://help.locusmap.eu/topic/visible-navigation-help-corridor-possible

photo
1

Thank you Willy, no worry, I also know few users that use this feature, so removing is definitely not planned.

photo
2

Good Day Menion,


Thank you for your answer. Good to know your own experience. What you suggest about using the accuracy colours (i have completely forgotten that it was available) for the track line is interesting, and could be a good +.


It's a shame that people don't know what they can do with something like this option in Locus.

3 weeks ago, two young guys (one was a recent father) were lost in our lagoon. Rescue teams and hundreds of volunteers tried to find them during days and days by feet on islands, by planes, helicopters, boats, unfortunately ... unsuccessfully. After this painful event, lots of peoples realised how important it is to have a way to call the rescues. Families of the two young guys asked to the volunteers if they could walk and search every where they could. That's were Locus can be a very useful tool with its very unique feature that you can't find anywhere else.


I hope some users will realise that and it will be known more then it is actually. It richly deserve.


Thanks again for that Menion,


Cheers,

photo
1

Thank you Fifi. You know, it is sometimes small "fight" if > this is close to hike/bike, this may be useful, ah sorry, this is too complicated for basic user, etc etc. Anyway still the usefulness of features for most of users is important here and this one is really too specialized.


You are welcome and have a nice, searching-free, day.

photo
1

>colorize line by "accuracy"<

where can i find the legend of color??

ok, red is low accuracy

photo
1

Good day balloni,

it is same with all other parameters ... color is based on full range in your track, so on relative values, not on absolute values. So blue color will be at lowest accuracy value (highest accuracy) and and red on opposite.


Agree it's then little cumberstone for this task, anyway : http://help.locusmap.eu/topic/ability-to-view-somehow-small-legend-for-coloured-tracks

photo
2

for better understanding i´ve done some tests and created a legend

860ea98eccedb0ec99d3bdaa50c4568b13a41172ad997cec89fb88069a5b9ece

Replies have been locked on this page!