missing accuracy filter

[PontiacCZ]

Recently I was using OSMTracker for collecting railway tracklogs with direct upload to OSM. Always when I turn the logging on, I watch decreasing GNSS accuracy value - "19 m"... "11 m".... "8 m".... and after a couple of seconds I am on stable 1 - 2 m accuracy with about 30 satelites in view.

When loooking at those inaccurate initial seconds I was thinking "I believe these points don't get saved, they would not be useful for anyone".

Well, they do get saved. The question is why? See these screenshots from JOSM:

What is the point in saving this initial clutter?

How about to create an option in settings:
"Save only trackpoints with accuracy better than ___"

Or at least time-delayed start of capture:
"Start logging after ___ seconds."

[Binnette]

Close as duplicate of #444