A gigapanorama taken in London recently has broken all records with its 320 gigapixels. Gigapixel-count is a type of competition that seemed to have gone off the boil recently after years of one large resolution photo beating the previous recordholder from the week before.
Not so long ago, a new gigapanorama photo raised the bar almost every week in terms of resolution, detail and other gigapan specs. In recent years, the race has slowed down almost to a halt. Of course, resolutions have drastically increased. From the level of tens of gigapixels levels to hundreds of gigapixels. This increases the time necessary for creating these types of photos. The increase in time needed can also affect the light, weather and other circumstances of the shooting. Another, more significant effect of the the increase in resolution is the increase in time required for developing and stitching the photos.
The newest 320 gigapixel city panorama was taken in London. You can see it in full detail on the BT London website. The photo is constructed from 48,600 individual photos taken over three days. Developing and stitching them together into this monumental gigapanorama took three months. More of the technical details can be found over on PetaPixel in English.
Update: Article of PictureCorrect has some more technical details of the shooting and stiching and they also included a video of the production, see it below.
- There were six attempts before an acceptable set of photos were captured
- Four Canon 7D cameras were used, each equipped with 400mm telephoto lens and 2x teleconverter, resulting in a 1 degree angle of view
- The cameras captured nearly three terabytes of data in JPG format. RAW would have been too much data too handle.
- A 32 core computer with 256 GB of RAM was used and took 200 hours to render the photo
- Due to the heavy winds, each photo had about a 30% overlap to compensate in case the rig was shifted too much
- The completed pano equaled 320 gigapixels, about 30,000 times more resolution than a regular photo
Cannot unset string offsets