Not true.
First, the video doesn’t characterize the system as “hodgepodge,” nor that it was “hacked together.”
Second, the video admits that the “first layer” isn’t used for routing nor FSD, it’s just for display on screen.
But, perhaps more importantly, the video creator doesn’t appear to understand how navigation systems work for just about every car today. That routing happens on a server isn’t unique to Tesla - just about every system does that today. It’s the best way to both account for up to date traffic information as well as to tap the faster processing power of the server versus in car. That this aspect was new to him tells us he has no experience with other systems in other vehicles.
The video creator also doesn’t appear to understand the difference between code and data. A processing engine is quite different than a database, so to say that Valhalla is one layer and the map data that Tesla assembles from OSM, TomTom, and its own data is another layer is not true - they are not separate layers. There is one engine processing one set of data - one layer in total.
And again, this is not unique to Tesla. Almost all OEMs that have their own navigation system have their map data assembled from a variety of sources, including their own data for POIs like OEM service centers, dealerships, and for EVs, their own charging station locations.
In Tesla’s case, we actually don’t know the sources for their map data. It definitely was OSM at one point in time (as an OSM bug about 8 years ago did make to Tesla vehicldes), but just as Apple as moved away from TomTom and Google has moved away from Tele Atlas, it’s not unlikely that Tesla has moved on, too. The OEMs I’m familiar with use different providers for different regions in the world, too.
Here’s an interesting post:
But, back again to the “layers.” Again, there is just one processing engine, and that’s probably still Valhalla running on Tesla’s servers (although when there is no connectivity, the car does create a route internally, as it tells you so). There’s is no “hacking” of different systems together. Google Maps are display only (as video admits, yet still somehow counts), multiple data sources are universally common in the industry, including recent updates since last major version. So, when the video creator tries to characterize updates to maps from Tesla as well as major maps updates each as seperate “layers,” that’s simply incorrect. Again, all navigation systems build their map data from a variety of sources and have an update process and schedule. With Tesla vehicles primarily routing on the server, updates of map data to the car are inconsequential except for when connectivity is unavailable and the car is routing internally on its own, which was specifically excluded from critique in the video.
Heck, the Google Maps used for display purposes are also probably updated regularly.
So, what we have here is simply that no navigation system is perfect, nor can it be perfect due to everything from new roads, new signs, to temporary closures due to accidents and road construction. Humans have to respond to these discrepencies, and so will autonomous driving systems.
That FSD isn’t perfect at handling all potential navigation errors isn’t surprising. As a human driver, I’ve gotten turns and lane guidance instructions that were wrong, and I have sometimes been unable to correct “in time” due to such bugs. The real question is not whether FSD can correct in time, but whether it can recover safely. Missing a turn or even an exit is not that bad, as long as it reroutes safely.
