I expect <entry key='coordinates.maxError'>200</entry> to make traccar ignore points with accuracy over 200m, but still I get log entries with an accuracy of 2.4km and a height of 0m, indicating it is a celltower or wifi-fix, not gps.
Is it possible simply not to have the client send if gps fix is not obtained?
I don't want entries that are not accurate within 50m or so, I use traccar for sports training.
If I can't plot the position fairly accurate, I don't want the participiant teleporting back and forth to cell towers
I think you misunderstood the configuration parameter that you are using. It has nothing to do with accuracy.
So can I filter on accuracy?
Yes, you can. Use filter.accuracy parameter. Value is in meters.
I expect
<entry key='coordinates.maxError'>200</entry>to make traccar ignore points with accuracy over 200m, but still I get log entries with an accuracy of 2.4km and a height of 0m, indicating it is a celltower or wifi-fix, not gps.Is it possible simply not to have the client send if gps fix is not obtained?
I don't want entries that are not accurate within 50m or so, I use traccar for sports training.
If I can't plot the position fairly accurate, I don't want the participiant teleporting back and forth to cell towers