HankLloydRight
No Roads
My wild-ass guess with no inside information is this: The touchscreen takes the google-searched for location/destination address, and passes that back to the Navigon module. Navigon calculates the route, and then passes back to the touchscreen(Google) maps a set of waypoints to display the route on the touchscreen. I've never seen them differ, and if they do differ, I'd guess that that happens during a route re-calculation in Navigon before it has passed the waypoints to Google maps to draw. It does seem like a Rube Goldberg device patched together that just seems to work "good enough".
What really gets my goat is that NONE of the google maps are cached, and even when navigating the same area, or zooming in or out, it has to re-draw the map from the network. Come on Tesla, how about caching the maps for just ONE DAY? I know Google might have some TOS prohibiting that, but do something to fix it. Over 3G, it's painfully slow to watch the redraw for a map IT JUST DREW 30 seconds ago.
What really gets my goat is that NONE of the google maps are cached, and even when navigating the same area, or zooming in or out, it has to re-draw the map from the network. Come on Tesla, how about caching the maps for just ONE DAY? I know Google might have some TOS prohibiting that, but do something to fix it. Over 3G, it's painfully slow to watch the redraw for a map IT JUST DREW 30 seconds ago.