Indeed, imagine how much space you'd need to have something like google streetview, at a resolution that not only is 4K for any given viewport, but allows zooming in and maintaining that 4K resolution for a significant magnification.
Then multiply it by 3 orders of magnitude to bring in temporal detail.
And you're still after a format that records the depth of each pixel, allowing recreation of a true 3d environment.
The numbers would be astronomical. Lets say a single 360 degree picture, using 30 bits per pixel (R,G,B,Depth at 10 bits each), allowing 100x zoom, so 40gpixels, 50 bits per pixel, that's 200GBytes per image.
One image every metre, or 1600 every mile, 4 million miles of roads in the U.S. alone. That's a billion terrabytes.
1Exabyte is 10% of what Randall Munroe estimated google had in 2013. Not that much. Wow.
Indeed, imagine how much space you'd need to have something like google streetview, at a resolution that not only is 4K for any given viewport, but allows zooming in and maintaining that 4K resolution for a significant magnification.
Then multiply it by 3 orders of magnitude to bring in temporal detail.
And you're still after a format that records the depth of each pixel, allowing recreation of a true 3d environment.
The numbers would be astronomical. Lets say a single 360 degree picture, using 30 bits per pixel (R,G,B,Depth at 10 bits each), allowing 100x zoom, so 40gpixels, 50 bits per pixel, that's 200GBytes per image.
One image every metre, or 1600 every mile, 4 million miles of roads in the U.S. alone. That's a billion terrabytes.
1Exabyte is 10% of what Randall Munroe estimated google had in 2013. Not that much. Wow.