|
|
|
|
|
by bri3d
1115 days ago
|
|
Using anything that could cause incorrect directions as a trap location / trap street would be a ridiculously bad idea. I strongly suspect the reason is a more standard corporate one; the volume of corrections and signal to noise ratio is probably quite poor. In the case of my repeated Uber map correction attempt, I suspect that my correction isn't prioritized because of two factors: first, the turn which Uber Maps suggests, while both illegal and very dangerous, is not impossible (it's an illegal left turn accomplished by making a U-Turn around an island designed to prevent left turns). So, they probably see enough volume of "driver completed route as suggested" data signals to ignore any "but it's illegal and dangerous" complaints, a classic problem with "data driven" systems. And, Uber don't seem to have a real process for riders to submit mapping corrections, only drivers, so my request is unlikely to ever be routed to the correct queue to begin with. |
|