- About Us
D'Angelo proposed the database project during the Libre Graphics Meeting earlier this month. D'Angelo's presentation, "Panoramic imaging - State of the art and future challenges," outlined a collaborative scheme that would create a database that could be integrated into image processing applications such as the GIMP, digiKam, and Krita to automatically correct distortion for known cameras. D'Angelo's presentation includes several illustrations of the improvement distortion correction can provide to typical images. Continued discussion of the proposal has since taken place between d'Angelo and other developers via email.
Given a centralized repository of calibration data for popular cameras, users of photo management tools could make dramatic corrections to a batch of images with a single click. EXIF data on the photographs under operation could be used to select an appropriate calibration set from the database. The database would require server-side management software and a Web submission system in addition to the "lightweight C library" d'Angelo plans to write for applications to access the database and apply corrections.
Methods against madness: fixing distortion
The Hugin software will be used to collect calibration data from sample photographs of individual cameras. While stitching panoramas, combining individual photographs taken in spatial sequence into a single large image, Hugin employs techniques for correcting image distortion courtesy of the panotools project. These distortions worsen the appearance of seams between constituent photographs present in the final stitched image, so correcting for them is especially important for panoramic imaging. The primary forms of distortion addressed are:
Even in the relatively mild example of distortion correction shown here, from the memorial of Marie Christine of Austria in Augustinerkirche, Vienna, you can clearly see the effects of vignetting and radial distortion. Notice how the corners are darker and the large triangular shape bulges slightly in the uncorrected sample. Click the image for a larger animated GIF.
Because these parameters all depend on the focal length of the camera, it will be important to gather samples at varying focuses. D'Angelo suggests that the database concentrate on gathering data for relatively large focal lengths, where the majority of photographs are taken. Users operating on macroscopic, close-up photographs may be less accommodated by the lens database.
Just days after it was proposed, d'Angelo's project has attracted encouraging attention. KDE developer Boudewijn Rempt has already expressed interest in integrating the database into the image editing application Krita as an "adjustment layer or effect mask." Venerable panoramic photographer and software developer Yuval Levy has stepped forward to "build the online tools to enter and manage the database," hoping to complete a preliminary version by June. Others on the FreeDesktop.org CREATE mailing list have also participated in the planning of the project.
While a committed development community seems to have emerged, consensus on project specifics has yet to be reached. Of particular interest will be the licensing of both database content and the software infrastructure to be built for its management. A strong proposal from Levy suggests a GPL license for the database management and Web submission software to ensure that it is maintained as Free Software, while distributing the code for application integration as LGPL so that it may be used within proprietary applications.
For the database content, clearly the most valuable aspect of the project, Levy suggests a different scheme. He stresses the importance of assigning ownership of the content to a single body to avoid copyright disputes. A warning on the Web submission system would make users aware that they must cede control of their submission to the database operator. Once assimilated, the content would be freely provided to open source applications for non-commercial use, while commercial users of the database would have to pay. Levy suggests a small flat fee for commercial open source software and a "negotiable" payment structure for proprietary users. Levy assures that any money collected would be used for project expenses and to encourage development through bounties.
The format for storing lens-specific calibration sets in the database has been extensively discussed. D'Angelo has proposed an XML format for calibration parameters, identifying the calibration set by camera/lens model and mount type. Each calibration set would be attributable to a specific contributor, complete with contact information. Levy suggests that this contact information will be stored internally in the database and provided upon request, but not distributed during typical correction operations. The contributor would be asked to submit source images (probably a minimum of three), the Hugin .pto project file used in collecting the calibration set, and as much extraneous information about the source photographs as possible.
Submitter commentary will play a large role in the lens calibration database. As with Wi-Fi adapters or TV tuner card chipsets, individual camera models that are expected to share a common lens may actually house one of many, depending upon manufacturing period. D'Angelo suggests trying to identify which lens a specific camera uses by associating serial number ranges with each possible lens. Serial numbers are an optional component of EXIF data that some manufacturers choose to include in photographs. Levy contends that such ranges would not be reliable and the system would have to default to user judgment.
Current plans are to host and distribute the database and appropriate software through the Hugin page on SourceForge.net. Recent suggestions have posed the idea of integrating submission forms into Hugin itself and automating the calibration process. D'Angelo has raised concerns that users stitching panoramas with Hugin may not necessarily be dealing with samples appropriate for determining lens correction parameters. He suggests that the manual Web upload system be implemented first and the automatic system be considered later.
D'Angelo describes his project as a "free alternative to the PTLens database." PTLens began as an open database, but is now closed, encrypted, Windows-only software sold for $15. D'Angelo has some familiarity with the old, open version. When the author of PTLens, Thomas Niemann, opted to transform his work into a closed project about a year ago, d'Angelo built the fulla tool to apply batch corrections to photographs in Hugin using the older PTLens version, which is still made available. Now Niemann has granted d'Angelo the ability to integrate the older PTLens content into his new lens correction database.
The PTLens content will give d'Angelo's database an excellent starting point, but it has several limitations. Because PTLens was closed over a year ago, the content only covers cameras made before that point -- although it does have fairly comprehensive coverage of older cameras. Moreover, the PTLens content only provides data on radial distortion and cannot be used to correct vignetting or chromatic aberration.
DxO also operates a proprietary database that goes beyond the scope of either the PTLens or d'Angelo's project. It includes calibration data for lens softness and perspective, in addition to features that go beyond systematic distortion correction. DxO's Optics Pro 4 product is only available for Windows and Mac OS X and costs between $79 and $299.
D'Angelo's project already has strong direction, developer commitment, and even some data to start out with. Nonetheless, it could take years to amass a comprehensive database applicable to the hundreds of camera models in popular use around the world, even with substantial user contribution. Before that time, expect many Free Software image editing applications to begin incorporating d'Angelo's work.
Those interested in learning more about the database project or contributing are encouraged to join the FreeDesktop.org CREATE mailing list.