[artoonie]

Most spot on (within 0.5 mi), some overpayments.

Overpayments are much less frequent than underpayments, and regardless: when someone accepts a trip, who knows if they did it because they thought "that amount sounds fair" or thought "that amount given the distance shown sounds fair." The only fair thing for Uber to do here is to rectify all underpayments, and let the overpayments stand.

Further: just because Uber couldn't find a route as efficiently as the extension could doesn't mean it was an overpayment. The extension uses Google Maps. If the driver used Uber Navigation to navigate, and Uber navigation was twice as long as Google's - is that really an overpayment?

[bagacrap]

I'm not sure how ubereats works for drivers, but based on what you just said, wouldn't the reverse hold true as well? If someone accepts an under-paying trip it must be because they thought the amount sounded fair.

[bluesign]

Can you share one route uber underpaid by big margin?

For the second part I agree, but without seeing outlier, maybe in some cases google couldn’t find the best route, compared to the app.

PS: all this stats used Google Maps shortest path or best path?

[artoonie]

https://imgur.com/v4bSD5S

I was paid 1 mile, actual distance 3.5-4.0 miles.

Previous versions of the app would use the first result returned by Google Directions API, which could have been best not shortest (I'm not sure, anyone know?). Newer version (pending app store review) does shortest always.

[bluesign]

This looks like an obvious bug if it is straight line.

Yeah google can show longer but faster route depending on traffic etc.

Also one more thing can be, gps location point and address can point to different locations. Not sure how Uber is showing, or calculating from which one.

[WrtCdEvrydy]

The problem is you used Uber Car, instead of Uber Airplane (please don't)

[artoonie]

I just got a lease on an UberCopter. Runways are too far from restaurants. Hope it works out for me!