On track edit dialog there are currently options simple color, according to speed and according to altitude for color style. Is it possible to add "According to accuracy" ?
This sounds like a debugging feature for GPS.
Is it really useful for users of track logging?
It is useful. It is easy to see what part of recorded track is for example not recorded with enough accuracy and that part isn`t useful for use in OSM for mapping. Setting should exist for manually choose the biggest accuracy that is good enough for use in OSM, and part of track with accuracy worse than that value could be shown in red color.
O.k., I understand.
On the other hand there are settings which control the conditions for points to be recorded:
http://docs.locusmap.eu/doku.php/manu... Max accuracy
Btw. what are the conditions for being good enough for OSM?
I know there is setting for max accuracy, but I don`t want gaps in tracks, I want that all points are recorded on track and after track has been saved, parts of track that are not accurate enough are shown in different color.
Here are few answers regarding OSM accuracy.
I like the idea. I mainly want to use it for the "take me back" use case (=I moved to a point, recorded my track to that point, and want to return on exactly the same track) in difficult conditions (e.g. dense fog & snowfall in the mountains). Then I want to know where the recorded track is reliable / accurate, so I can "just follow it", and where it is very inaccurate and I have to pay special attention. As you can imagine, in such a situation I prefer to have inaccurate points over having no recorded points ;-) but I want to know how accurate a point is - the information is already stored (field acuracy in table locations in tracks.db of Locus / pdop element in GPX export), I just need a way to display it.
For OSM, I don`t need this - I find it much more convenient to see accuracy info in the same editor in which I edit the OSM data. Hence I load the NMEA file that Locs created into JOSM :-)
hmm ... implemented ;)
Thanks :-) Accuracy is working fine in v 2.10.2 :-)
Thank You for excellent app! I knew that this idea will be implemented eventually, and there it is!
Very useful feature. Thanks
Comments have been locked on this page!