Thus it is going to be hard to avoid a network connected car and it seems likely that network will be the Internet.
Well, I agree that maps as a second source of information can be important for autonomous vehicles. However, I don't understand why "map" would imply "network connected". Offline navigation systems with detailed maps have existed and still exist for more than twenty years now. I fear that the "offline autonomous vehicle" will solely fail to manifest because of business decisions (online being "more convenient" for both the end-user and the company), not because of technical limitations.
Edit: which is to say, maps aren't really secondary parts of current systems but more like "co-primary" parts. The cars aren't planning identify traffic lights where they don't expect them.
"Almost all of the fully autonomous vehicles currently allowed on public roads are still under the direct supervision of human pilots, and they’re only driving on roads that have been heavily studied and mapped in three dimensions."
See:
https://www.consumerreports.org/autonomous-driving/self-driv...
or "Cars will only be able to drive themselves if they have access to high-precision maps. The digital material contained in today’s navigation systems is not enough. To be able to drive itself safely, a car needs to know its position on the road down to the centimetre. "
https://www.mercedes-benz.com/en/mercedes-benz/next/connecti...
Comma.ai, on the other hand, feeds their AI the camera feed and the sensor signals from the car, and it responds, as far as I know, almost entirely based on that stimulus. Of course, Comma.ai's car is presumably less predictable, it relies on a black box to "think", but you could feed it the general concept of what path to take from A to B, even a set of waypoint GPS coordinates of where to turn, and hypothetically, such a car could navigate to that destination otherwise offline, or with the grade of maps reasonably available offline. It's intended to drive like a human drives: Based on the information it perceives in the world around it.
When a dashboard GPS is out of date, it's irritating. When your car's autonav system is out of date, your car is useless.
For the purposes of outside knowledge queries you might not be able to come up with in advance, there's good cause to outsource those rare requests out to the Internet: Just do it intelligently. Require a prefix instruction for an outside request.
For instance, I went ahead and implement Wolfram's API for knowledge queries. They have a great "spoken answer" endpoint, which replies with a string meant to be piped straight to speech output. So I "ask wolfram how tall abraham lincoln was", my program hands everything AFTER "ask wolfram" to the Wolfram API, and Wolfram's API gives me a string back with exactly what I asked.
Now sure, I'm not entirely offline at that point, but everything regarding my personal data, home automation devices, etc. is under my control, and any time I reach out, it's specifically using a command authorizing it to do so.
Of course, caveats before you think my project sounds impressive: A. It's written in Visual Basic. B. Speech recognition isn't working (yet).
Visual Basic is a fine programming language with very weird syntax. Hell, Microsoft has put out .NET bindings for CNTK so you could even use that.
Specifically, look in the article:
>First allow me to address what I think won't work:
>Trying to air gap autonomous devices.
This trend of doing everything over the Internet for no good reason other than business model is growing from just ridiculous and user-hostile into something that's actually dangerous to people's lives.