Google Maps is, often, on crack

[jducoeur]

[First of several little posts about Coronation and reflections on the reign.]

The travel to Coronation was generally fun and stress-free, at least insofar as Friday rush-hour driving ever is. But it was a good reminder that Google Maps is an automated program, and sometimes shows poor judgement. To wit: regardless of the traffic on the Garden State Parkway and New Jersey Turnpike, taking us through the middle of downtown Newark is probably *never* the right answer. This will remind me to look at the route it has laid out, and see what that actually *means*, before uncritically following it.

(On Sunday, we did the more sensible thing: msmemory figured out the route herself, and we just used Google to keep an eye on the traffic...)

Comments

I feel your pain...

[anu3bis.livejournal.com]

for long distance travel, I use it as a map rather than a set of directions, mainly because it always wants me to take the GWB, instead of the more sensible Tappan Zee.

[eclecticmagpie.livejournal.com]

Yesterday I asked Google to show me the route from Waltham (Prospect Hill Forge in particular) to the Weekes Memorial Footbridge in Cambridge. It had no trouble showing me where the footbridge is, about which I was a little surprised (in a pleasant way) but insisted that there was no way to get from one to the other!