Good plan. If google will allow a police vehicle to be identified as present, then they can't complain about a feature to ensure the information is [still] valid. I could easily write a function that would detect a status change back & forth over a short period of time, but they haven't asked me to code for them.
Another approach is to delay 'not there' as an option for a progressively longer period of time. So the first time it can be cancelled within a minute, but if re-added withing x minutes, then disable the 'not there' status switch for something like 5 minutes. The next meddling, it waits 30 mins, you get the idea. Nobody is going to complain about a warning being old (false positive), but everyone will complain about meddling with the service.
This could be in addition to the above user suggestion, as a stopped vehicle could be at a light, or traffic on road so close waze can't pin-point you.
Good plan. If google will allow a police vehicle to be identified as present, then they can't complain about a feature to ensure the information is [still] valid. I could easily write a function that would detect a status change back & forth over a short period of time, but they haven't asked me to code for them.
Another approach is to delay 'not there' as an option for a progressively longer period of time. So the first time it can be cancelled within a minute, but if re-added withing x minutes, then disable the 'not there' status switch for something like 5 minutes. The next meddling, it waits 30 mins, you get the idea. Nobody is going to complain about a warning being old (false positive), but everyone will complain about meddling with the service.
This could be in addition to the above user suggestion, as a stopped vehicle could be at a light, or traffic on road so close waze can't pin-point you.