Map matching is currently using a radius multiplier of 10 to augment gps_precision. The intention is that gps_precision is assumed to signify one standard deviation of the gps error of the capturing device. The multiplier increases the radius to find outlier as well. Assuming a multiplier of 10 is likely way too aggressive. This should probably be lower, @TheMarex suggested a multiplier of 3 which (following the standard deviation) would capture 99.7% of all cases.

We'd also need to change the default value for gps_precision.

This change will be breaking.