Hi everyone,
is there a way to apply filter (e.g. fliter.accuracy, filter.skipAttributes) after calculated.Attributes execution.
my problem.
I want to filter non-accurate positions. Unfortunately, my tracer-device always reports accuracy = 0.
idea 1: calculate.attribute accuracy based on gps hdop. calculation works fine, but positions are not filtered.
idea 2: calculate new boolean attribute 'reject'. calculation fine, but filter.skipAttributes does not filter out positions
seems to me that traccar first applies filters, stores to db and only then executes calculated attributes.
is there a way to change this priority ?
tnx
Currently not supported, but this is something we have considered in the past. I recommend creating a feature request on GitHub.
Hi everyone,
is there a way to apply filter (e.g. fliter.accuracy, filter.skipAttributes) after calculated.Attributes execution.
my problem.
I want to filter non-accurate positions. Unfortunately, my tracer-device always reports accuracy = 0.
idea 1: calculate.attribute accuracy based on gps hdop. calculation works fine, but positions are not filtered.
idea 2: calculate new boolean attribute 'reject'. calculation fine, but filter.skipAttributes does not filter out positions
seems to me that traccar first applies filters, stores to db and only then executes calculated attributes.
is there a way to change this priority ?
tnx