john@ostrowick.com
Your algorithm that reports duplicate reports is wrong. It assumes that the LAST located report is the real thing and prior nearby reports are duplicates. This is incorrect. You should assume that reports are NOT duplicates at all. Let me give an exact case. On the highway n12/n3 intersection on the corner of woodmead (suburb) in Johannesburg RSA, starting at -26.047675193550557, 28.093193441959258 and ending at -26.03960699164605, 28.067755371505946, on the date 31 Nov 2021 at around 4pm, there were THREE stopped vehicles at the roadside. Your system recorded them as THREE REPORTS at the LAST location, rather than three separate reports. In actual fact, there were THREE stopped vehicles. The first one was roughly at -26.047675193550557, 28.093193441959258 and the last one at -26.03960699164605, 28.067755371505946. The middle one in between was IN THE ROAD at 120kmh. It was NOT visible around the curve. HIGHLY dangerous. I tried to report it but it was assimilated into the last vehicle which was about ½ km FURTHER. I suggest you assume that reports are duplicates within a 50-100m difference max. My reporting accuracy is VERY accurate, I report precisely where the incident is. We have BAD drivers, and LOTS of accidents and incidents. DO NOT assume it is a duplicate.
Thanks for reaching out. Please note this platform is dedicated to ideas and suggestions for the Waze app. If your idea is for a Community platform like the Waze Map Editor, please submit it through the Community forum. If you need help using Waze, please click here to reach the "Waze support" page.
-
John Ostrowick commented
Please take the above seriously. It was VERY dangerous. The stopped vehicle was stopped IN THE ROAD but the other TWO were stopped on the shoulder. The middle one was NOT the same as the others but Waze assumed it was, and merged it with the LAST one, which made it especially dangerous because you'd not anticipate it due to the road curve.