You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way we are checking for intersection is based on storing data and checking it periodically and sending a notification if an intersection is found. Now the issue here is that the intersection which happened 5 days ago will get flagged again when it is found on the next day as an intersection which happened 6 days ago.
We need to find a way to get rid of the duplicate notifications in the time domain. This, in general, also brings the point that right now we check for whole intersection every 12 hours which might not be a good idea, especially when the public json files would be larger.
The text was updated successfully, but these errors were encountered:
The way we are checking for intersection is based on storing data and checking it periodically and sending a notification if an intersection is found. Now the issue here is that the intersection which happened 5 days ago will get flagged again when it is found on the next day as an intersection which happened 6 days ago.
We need to find a way to get rid of the duplicate notifications in the time domain. This, in general, also brings the point that right now we check for whole intersection every 12 hours which might not be a good idea, especially when the public json files would be larger.
The text was updated successfully, but these errors were encountered: