4 ms·
I've noticed some of the "Waze shortcuts' making their way into Google maps. Some of these are pretty hairy. For anyone familiar with SF, here's an example: To
by scurvy 11y ago
I've noticed some of the "Waze shortcuts' making their way into Google maps. Some of these are pretty hairy. For anyone familiar with SF, here's an example:
To get from 8th & Bryant to 3rd & Bryant, Google Maps/Waze wants you to get on I-80 at 8th and exit at 4th. That would be OK but you enter 80 from the left side of the interstate and must exit within a quarter mile to the right side of the interstate. This means crossing 4 lanes to get there. It's actually do-able in bumper-to-bumper gridlock but when traffic is moving it's pretty dangerous. Why not just go down Bryant Street? The "shortcut" can't save more 2 minutes at best and at worst costs 10+ minutes.
Waze used to be good for spotting cops and speed traps. Now it's just a collection of bad "short cuts".
- jonchang 11y agoOne of my favorite Waze "shortcuts" in Los Angeles has me crossing all 8 lanes of Wilshire Boulevard at an uncontrolled intersection. I always avoid this route in the hope that Google will figure out this is a dangerous intersection but so far it keeps popping up.
- mg1982 11y agoA shortcut is supposed to be difficult; if it was easy, it would just be 'the way'.
- scurvy 11y agoDangerously so?
- zo1 11y agoA few weeks back, after heading back home from a conference during "rush-hour", the Google maps app sent me through a very very dodgy area. It was run-down, semi-shanty town. Generally that wouldn't be a bad thing, but this being South Africa, with one of the highest crime-rates in the world, it was quite disturbing. You don't want to go through "bad parts" of town unless you really have to, especially if you look out of place as either a different skincolor, or nationality. Of which I am both.