3 ms·

> with Waze and most driving apps - they optimize for "least time," not "least anguish" It's my impression that Google Maps does the latter; Waze is known for

> with Waze and most driving apps - they optimize for "least time," not "least anguish" It's my impression that Google Maps does the latter; Waze is known for taking wild routes that are nominally faster. I'm not sure that I see a basis for complaint, as they're just offering a choice of different route objectives to optimize for (I know people who explicitly use Waze because they prefer its aggressive optimization to Maps). I suppose a toggle would be nice though.

eigenvector 7y ago
I travel to new cities often and usually rent a car from the airport. In most cities around the world, there is dedicated signage pointing out the access to the airport on every major approach it. I would say half the time Google wants to take me on a different route on some back road that is not meant to be the public access to the airport, which creates the extra mental overhead of having to ignore the gigantic "AIRPORT - EXIT HERE" signs all along the way. It even does this at SFO, presumably an airport that the very people who work on Google Maps use, where it always wants to exit the interstate one exit before the sign for the airport and take city streets instead. The worst experience I've had of this was in Denver, where it directed me onto a country road that circled the airport property and then ended at a temporary road closure. That is, Google's "5 seconds faster than the main, signed route" optimization wasn't even an actual route to the airport!
- Spooky23 7y ago
  My favorite example of this was in NYC heading to Citi Field for a Mets game. Google Maps guides you past the exit, has you make a u-turn by getting off at the next exit (which is really unusual) and get you trapped on some ramp for an extra 20m.
  - InitialLastName 7y ago
    I'm really glad they aren't optimizing for people to drive to a major gathering point with 4+ good non-driving alternatives.

eigenvector 7y ago

I travel to new cities often and usually rent a car from the airport. In most cities around the world, there is dedicated signage pointing out the access to the airport on every major approach it. I would say half the time Google wants to take me on a different route on some back road that is not meant to be the public access to the airport, which creates the extra mental overhead of having to ignore the gigantic "AIRPORT - EXIT HERE" signs all along the way. It even does this at SFO, presumably an airport that the very people who work on Google Maps use, where it always wants to exit the interstate one exit before the sign for the airport and take city streets instead. The worst experience I've had of this was in Denver, where it directed me onto a country road that circled the airport property and then ended at a temporary road closure. That is, Google's "5 seconds faster than the main, signed route" optimization wasn't even an actual route to the airport!

Spooky23 7y ago
My favorite example of this was in NYC heading to Citi Field for a Mets game. Google Maps guides you past the exit, has you make a u-turn by getting off at the next exit (which is really unusual) and get you trapped on some ramp for an extra 20m.
- InitialLastName 7y ago
  I'm really glad they aren't optimizing for people to drive to a major gathering point with 4+ good non-driving alternatives.