Hacker News Reader

Comment by lqr | Hacker News Reader

If by "unprotected" you mean "no green arrow", in what part of the LA area is it feasible to avoid unprotected lefts? They are all over the place in my neighborhood.

If by "unprotected" you mean a left from a stop sign onto a street that does not stop, then I agree. They can be almost impossible. Waze was especially notorious for them a few years ago.

View on HN

The latter I mean. "Take a left on pico from this stop sign, hold your breath and good luck, no one will let you in." Somehow google maps ignores these and prefers me to make a right out of a parking lot or a stop signed street and take my lefts at lights (or off the major arterial) seems like its just a simple set of rules you can apply to your navigation algorithm to avoid these entirely, but the fact that they are still there years later tells me the Apple maps designers really don't care too much.

It does seem like it should be simple to avoid those. I can imagine it might be complicated if the model treats turns as instantaneous and only considers edges in the road graph as taking time.

I would love a road navigation tool that gives more options to modify the cost of various route features other than pure distance/traffic. To me, Google is too willing to give a complicated route to save a tiny amount of time. It makes the driving more mentally draining. I would raise the cost of all turns, stop signs, and intersections where I don't have priority.

Apple could farm their data to see how long people wait to make turns it recommends and adjust the edge weight accordingly. I'm guessing that's what Google does.

Reply on news.ycombinator.com