Granted, we didn't log all that data all the time, but TL;DR: I wouldn't nitpick over a factor of 8 based on your own calculations.
I have worked on several fully autonomous vehicle projects based on Velodynes and their processing and logging rates are around of 5-20MB/ (as you would expect) so seeing someone quote "1 GB/s" is pretty awful.
1 - http://velodynelidar.com/lidar/products/manual/63-HDL64ES2h%...
[1] http://imgur.com/IfxYZL2 – the bottom image is from this presentation: http://youtu.be/YXylqtEQ0tk
That said, this guy may be more than an order of magnitude off (confused MB and GB?). If 1GB/sec figure is correct, then they'd fill up a 10TB NAS in 3 hours. Forget about network throughput, how much storage do they carry in the back of that vehicle?
Meaning, it can look at a lot more data than just its raw sensors, every second.
Also, why do you assume the front-facing camera is the only one?
I saw the tech lead of the project talk about 1.5 years ago. He said the primary sensor was the Velodyne, followed by radars. The only use for the camera mentioned is detecting stop light colors. At that time their main computer was a quad core machine, processing that much data sounds beyond it's limits as well.
Doing the math: 100 + 10*1 + 1000 = 1100MBit != 8192Mbit (1 GB)
1. http://velodynelidar.com/lidar/products/brochure/HDL-64E%20S...
2. http://www.kvaser.com/zh/about-can/the-can-protocol/19.html