[ChristianKletzl]

One of the reasons I am frustrated about a long waiting time is wrong expectations set by the map. The map in SOMA typically shows that 5+ cars are within 2 minutes. As soon as I request, the closest is 7 minutes away.

[untog]

AFAIK there isn't a lot they can do about it, because Uber drivers have to manually accept jobs. Those 5+ cars within 2 minutes presumably turned down the job.

[jacalata]

Ok, but can they do something about the car that I do get saying "5 minutes" and actually meaning "9 minutes, including the bit where I watch him drive 2 minutes in the other direction"?

[boulos]

This has always seemed to me as a "doesn't understand one way streets" issue. Uber seems to offer the ride to the geographically closest car first, rather than the driving distance closest. While Uber may (rightfully) want to avoid computing a shortest path between you and the driver, it seems silly that they don't do at least something with one way streets.

[modfodder]

Are you sure that Uber offers the ride to the closest (geographically) car? I've noticed that most of the time when I see close cars, they are not the ones that snag my ride, which can be frustrating when there are multiple cars 2 minutes away and the car that wins my business is 10+ minutes away (this has happened multiple times to me). The map doesn't seem like it understands one way streets, but it also doesn't seem to prioritize by geography either.

[madeofpalk]

Uber will offer your ride to the closest driver, who then has 15 seconds to accept the ride, where it goes to the next closest.