Fine granular Intersection calculation required

[ariellev]

At the current release, the criterion for finding an intersection between a corona carrier to a given user on the production environment is "500 meter for 1 millisecond", which obviously does not make any sense.

./config/config.ts

Is:

{
..
   meterRadius: 500,
    intersectMilliseconds: 1, // 1 milli
}

Should:

{
..
   meterRadius: 10,
    intersectMilliseconds: 1000 * 60 * 15, // e.g. 15 minutes 
}

[ItayElgazar]

why 10? meterRadius should be 2

[ariellev]

Of course GPS signals tend to hope, so we need to account for that

[ItayElgazar]

Still don't get why 10 :) from where did you get this number?

[ariellev]

intuition, like 2 meters would be the ideal case, I agree, but I am not sure it's realistic taking into account GPS hoping. So I would recommend to drop the radius to the 10-20 meters area, and keep on optimizing from there.

[henry-hz]

ops, just sent a PR for 200m, because we walk 100m in 1 min, and it's feasible to think that people leave the celular in the car, or near him. 10m doesn't cover the GPS lack of accuracy... see here and here

[yehudit-vizel-Moh]

Thanks @ariellev, @ItayElgazar and @henry-hz !

See more details here:
#32