Comment by sd9
16 hours ago
This is a really good proof of concept. I would use this.
Something about the moment of the turn itself isn’t working for me though. Just before the turn you have essentially no information about the route ahead, until after the turn is completed. This would make a sequence of consecutive turns difficult to navigate.
This is exactly why on traditional gps maps I prefer it to be very very zoomed out. It's far too common that mapping tools make something like a sudden second turn invisible to you until it is too late to switch lanes.
I find that Apple Maps is typically pretty smart with its automatic zoom. For a typical intersection with just one turn to navigate, it will zoom in to give you a good sense of the lanes, stop signs/lights, etc. But when there are consecutive turns to navigate, or a heavily curved section of road (like highway on-ramps) it will zoom out and even rotate the map to show that upcoming context.
Apple Maps got really good at some point! I once pick it by accident for navigation, and never went back to Google Maps.
5 replies →
I have had an occasional problem where a large building ends up blocking my view, but in general it’s very good.
I remember for at least a while people would complain about how GPS navigation ruined their sense of the local area. Probably stopped hearing about it because people have just surrendered to the apps, but I think part of the reason is also that by default they were just zoomed in way too close. If you forced them back out a ways, I was actually learning a lot about my local area. Like, there's all these subdivisions around, you know, and from the outside who knows what connects to what, I'm not going to just duck in to a subdivision and physically navigate the streets to see how they're all connected, but driving around with the navigation made it much more clear... when it was zoomed out somewhat.
I had similar thoughts, but this is a largely solved problem: even headlights in my Volvo turn as I turn the wheel, and it should be easy to change rendering direction to an "average" of road tangents for the next say 50m (would depend on the speed and would need experimenting to know the best value).
This is also a problem with Google Maps navigation. It is always showing the perspective looking straight ahead of your current direction, even when you're approaching a sharp turn. Instead, the perspective should be along a vector connecting your current location with the point where the navigation's path crosses the edge of the display, pointing straight up.
Took me a while to figure out what you're saying, now I assume you're using the "up is direction of motion"?
I use map view / north is up, which makes it reasonably easy to get he big picture - I encourage everybody to try it :).
That seems very wrong and unintuitive for U-turns.
It does.
Let us embrace this minor imperfection by simply excluding U-turns from this presentation method.
So why not use 2D maps, have people lost the ability to read North up maps? I swear ever since paper maps have not been used in cars, people have gotten spatially dumber.
I love north-up maps because I find they give me way better spatial context. My truck’s nav system gives north-up as an option but my phone and my truck map both suffer from the same problem on different axes. My phone sits in its holder vertically, so I have way more north-south context than east-west. The truck screen is landscape, same problem north-south! A square map north-up would be amazing!