You didn't get it again. You have to imagine it, man. Normally, imagine both situations that you want to travel somewhere. And that you are looking for the appropriate thing on the map... just for info... to know... where you will go with your off-road SUV :).
In small villages, there are actually no intersecting streets, but only 1 very long street. There is no need for street names at all - on the navigation map. However... when I want to find a particular small village, of which there are always several next to each other (see my screenshots), I need to see which of them is the village I want to visit. I need to possibly see a view from the top to see which other villages I have to pass through - on the way to my destination.
The second case is the one you mentioned. But it concerns the big city. And there's the problem with intersecting streets. I don't know if you've ever seen Beverly Hills, California, for example, but I'm guessing you have. It is several long streets with different names that cross each other. If you get into another street by mistake, then you have to turn around or go through the one-way street for a long time and return to the original place again. However, if you know exactly which streets cross your path with your car in order, then you will get a good overview of the destination and know exactly when to turn into the street (between which streets - according to their visible names).
Sorry, I'm an apps developer :). I need to know exactly where to go and how to get there :). Such navigation as, for example, "go straight with the car... then after the second big green tree, turn right" is not enough for me.
Bookmarks