Exchangeable image file format

From Infogalactic: the planetary knowledge core
(Redirected from Exif)
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

This article is about a format for storing metadata in image and audio files. For information about filename and directory structures of digital cameras, see Design rule for Camera File system.
Exchangeable image file format
Filename extension .JPG, .TIF, .WAV
Developed by JEIDA, now JEITA, CIPA
Initial release 1995 (1995)
Latest release
2.3
(26 April 2010; 14 years ago (2010-04-26), revised 20 December 2012; 11 years ago (2012-12-20))
Extended from TIFF, JPEG, WAV
Extended to DCF

Exchangeable image file format (officially Exif, according to JEIDA/JEITA/CIPA specifications) is a standard that specifies the formats for images, sound, and ancillary tags used by digital cameras (including smartphones), scanners and other systems handling image and sound files recorded by digital cameras. The specification uses the following existing file formats with the addition of specific metadata tags: JPEG discrete cosine transform (DCT)[1] for compressed image files, TIFF Rev. 6.0 (RGB or YCbCr) for uncompressed image files, and RIFF WAV for audio files (Linear PCM or ITU-T G.711 μ-Law PCM for uncompressed audio data, and IMA-ADPCM for compressed audio data).[2] It is not supported in JPEG 2000, PNG, or GIF.

This standard consists of the Exif image file specification and the Exif audio file specification.

Background

The Japan Electronic Industries Development Association (JEIDA) produced the initial definition of Exif. Version 2.1 of the specification is dated 12 June 1998. JEITA established Exif version 2.2 (aka "Exif Print"), dated 20 February 2002 and released in April 2002.[3] Version 2.21 (with Adobe RGB support) is dated 11 July 2003, but was released in September 2003 following the release of DCF 2.0. The latest, version 2.3, released on 26 April 2010 and revised in May 2013, was jointly formulated by JEITA and CIPA. Exif is supported by almost all camera manufacturers.

The metadata tags defined in the Exif standard cover a broad spectrum:

  • Date and time information. Digital cameras will record the current date and time and save this in the metadata.
  • Camera settings. This includes static information such as the camera model and make, and information that varies with each image such as orientation (rotation), aperture, shutter speed, focal length, metering mode, and ISO speed information.
  • A thumbnail for previewing the picture on the camera's LCD screen, in file managers, or in photo manipulation software.
  • Descriptions
  • Copyright information.

Technical

The Exif tag structure is borrowed from TIFF files. On several image specific properties, there is a large overlap between the tags defined in the TIFF, Exif, TIFF/EP, and DCF standards. For descriptive metadata, there is an overlap between Exif, IPTC Information Interchange Model and XMP info, which also can be embedded in a JPEG file. The Metadata Working Group has guidelines on mapping tags between these standards.[4]

When Exif is employed for JPEG files, the Exif data are stored in one of JPEG's defined utility Application Segments, the APP1 (segment marker 0xFFE1), which in effect holds an entire TIFF file within. When Exif is employed in TIFF files (also when used as "an embedded TIFF file" mentioned earlier), the TIFF Private Tag 0x8769 defines a sub-Image File Directory (IFD) that holds the Exif specified TIFF Tags. In addition, Exif also defines a Global Positioning System sub-IFD using the TIFF Private Tag 0x8825, holding location information, and an "Interoperability IFD" specified within the Exif sub-IFD, using the Exif tag 0xA005.

Formats specified in Exif standard are defined as folder structures that are based on Exif-JPEG and recording formats for memory. When these formats are used as Exif/DCF files together with the DCF specification (for better interoperability among devices of different types), their scope shall cover devices, recording media, and application software that handle them.

Geolocation

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: Geotagging

The Exif format has standard tags for location information. As of 2014 many cameras and most mobile phones have a built-in GPS receiver that stores the location information in the Exif header when a picture is taken. Some other cameras have a separate GPS receiver that fits into the flash connector or hot shoe. Recorded GPS data can also be added to any digital photograph on a computer, either by correlating the time stamps of the photographs with a GPS record from a hand-held GPS receiver or manually by using a map or mapping software. The process of adding geographic information to a photograph is known as geotagging. Photo-sharing communities like Panoramio, locr or Flickr equally allow their users to upload geocoded pictures or to add geolocation information online.

Program support

Exif data are embedded within the image file itself. While many recent image manipulation programs recognize and preserve Exif data when writing to a modified image, this is not the case for most older programs. Many image gallery programs also recognise Exif data and optionally display it alongside the images.

Software libraries, such as libexif[5] for C and Adobe XMP Toolkit[6] or Exiv2[7] for C++, Metadata Extractor[8] for Java, or Image::ExifTool[9] for Perl, parse Exif data from files and read/write Exif tag values.

Problems

Technical

The Exif format has a number of drawbacks, mostly relating to its use of legacy file structures.

  • The derivation of Exif from the TIFF file structure using offset pointers in the files means that data can be spread anywhere within a file, which means that software is likely to corrupt any pointers or corresponding data that it doesn't decode/encode. For this reason most image editors damage or remove the Exif metadata to some extent upon saving.[10]
  • The standard defines a MakerNote tag, which allows camera manufacturers to place any custom format metadata in the file. This is used increasingly by camera manufacturers to store camera settings not listed in the Exif standard, such as shooting modes, post-processing settings, serial number, focusing modes, etc. As the tag contents are proprietary and manufacturer-specific, it can be difficult to retrieve this information from an image or to properly preserve it when rewriting an image. Manufacturers can encrypt portions of the information; for example, some Nikon cameras encrypts the detailed lens data in the MakerNote data.[11]
  • The standard only allows TIFF or JPEG files — there is no provision for a "raw" file type which would be a direct data dump from the sensor device. This has caused camera manufacturers to invent many proprietary, incompatible "raw" file formats. To solve this problem, Adobe developed the DNG format (a TIFF-based raw file format), in hopes that manufacturers would standardize on a single, raw file format.
  • The Exif standard specifically states that color depth is always 24 bits.[12] However, some modern cameras can capture more data such as the Nikon D70 which captures 36 bits of color per pixel. Since Exif/DCF files cannot represent this color depth, manufacturers have developed proprietary, non-compatible raw image formats.
  • Exif is very often used in images created by scanners, but the standard makes no provisions for any scanner-specific information.[citation needed]
  • Photo manipulation software sometimes fails to update the embedded thumbnail after an editing operation, possibly causing the user to inadvertently publish[how?] compromising information.[13]
  • Exif metadata are restricted in size to 64 kB in JPEG images because according to the specification this information must be contained within a single JPEG APP1 segment. Although the FlashPix extensions allow information to span multiple JPEG APP2 segments, these extensions are not commonly used. This has prompted some camera manufacturers to develop non-standard techniques for storing the large preview images used by some digital cameras for LCD review. These non-standard extensions are commonly lost if a user re-saves the image using image editor software, possibly rendering the image incompatible with the original camera that created it. (In 2009, CIPA released the Multi-Picture Format specification which addresses this deficiency and provides a standard way to store large previews in JPEG images.[14])
  • There is no way to record time-zone information along with the time[citation needed], thus rendering the stored time ambiguous.
  • There is no field to record readouts of a camera's accelerometers or inertial navigation system. Such data could help to establish the relationship between the image sensor’s XYZ coordinate system and the gravity vector (i.e., which way is down in this image). It could also establish relative camera positions or orientations in a sequence of photos.
  • The DPI-value of photos is meaningless, a fictitious number, but it is required[citation needed]. The inclusion of this made up tag confuses both people and software. The format has not yet been updated to remove this requirement.[15]

Privacy and security

Since the Exif tag contains metadata about the photo, it can pose a privacy problem. For example, a photo taken with a GPS-enabled camera can reveal the exact location and time it was taken, and the unique ID number of the device - this is all done by default - often without the user's knowledge. Many users may be unaware that their photos are tagged by default in this manner, or that specialist software may be required to remove the Exif tag before publishing. For example, a whistleblower, journalist or political dissident relying on the protection of anonymity to allow them to report malfeasance by a corporate entity, criminal, or government may therefore find their safety compromised by this default data collection.

In December 2012, anti-virus programmer John McAfee was arrested in Guatemala while fleeing from alleged persecution[16] in Belize, which shares a border. Vice magazine had published an exclusive interview on their website with McAfee "on the run"[17] that included a photo of McAfee with a Vice reporter taken with a phone that had geotagged the image.[18] The photo's metadata included GPS coordinates locating McAfee in Guatemala, and he was captured two days later.[19]

According to documents leaked by Edward Snowden, the NSA is targeting Exif information under the XKeyscore program.[20]

The privacy problem of Exif data can be avoided by removing the Exif data using a metadata removal tool.

Related standards

Metadata Working Group was formed by a consortium of companies in 2006 (according to their web page) or 2007 (as stated in their own press release). Version 2.0 of the specification was released in November 2010,[4] giving recommendations concerning the use of Exif, IPTC and XMP metadata in images.

Extensible Metadata Platform (XMP) is an ISO standard, originally created by Adobe Systems Inc., for the creation, processing and interchange of standardized and custom metadata for digital documents and data sets. IPTC was developed in the early 1990s by the International Press Telecommunications Council (IPTC) to expedite the international exchange of news among newspapers and news agencies.

Example

Konqueror screenshot showing Exif data

The following table shows Exif data for a photo made with a typical digital camera. Notice that authorship and copyright information is generally not provided in the camera's output, so it must be filled in during later stages of processing. Some programs, such as Canon's Digital Photo Professional, allow the name of the owner to be added to the camera itself.

Tag Value
Manufacturer CASIO
Model QV-4000
Orientation (rotation) top - left [8 possible values[21]]
Software Ver1.01
Date and Time 2003:08:11 16:45:32
YCbCr Positioning centered
Compression JPEG compression
x-Resolution 72.00
y-Resolution 72.00
Resolution Unit Inch
Exposure Time 1/659 sec.
FNumber f/4.0
ExposureProgram Normal program
Exif Version Exif Version 2.1
Date and Time (original) 2003:08:11 16:45:32
Date and Time (digitized) 2003:08:11 16:45:32
ComponentsConfiguration Y Cb Cr -
Compressed Bits per Pixel 4.01
Exposure Bias 0.0
MaxApertureValue 2.00
Metering Mode Pattern
Flash Flash did not fire.
Focal Length 20.1 mm
MakerNote 432 bytes unknown data
FlashPixVersion FlashPix Version 1.0
Color Space sRGB
PixelXDimension 2240
PixelYDimension 1680
File Source DSC
InteroperabilityIndex R98
InteroperabilityVersion (null)

FlashPix extensions

The Exif specification also includes a description of FPXR (FlashPix-Ready) information which may be stored in APP2 of JPEG images using a structure similar to that of a FlashPix file.[22] These FlashPix extensions allow meta information to be preserved when converting between FPXR JPEG images and FlashPix images. FPXR information may be found in images from some models of digital cameras by Kodak and Hewlett-Packard.[23] Below is an example of the FPXR information found in a JPEG image from a Kodak EasyShare V570 digital camera:

Tag Value
Code Page 1200
Used Extension Numbers 1
Extension Name Screen nail
Extension Class ID 10000230-6FC0-11D0-BD01-00609719A180
Extension Persistence Invalidated By Modification
Extension Create Date 2003:03:29 17:47:50
Extension Modify Date 2003:03:29 17:47:50
Creating Application Picoss
Extension Description Presized image for LCD display
Storage-Stream Pathname /.Screen Nail_bd0100609719a180
Screen Nail (124498 bytes of data containing 640x480 JPEG preview image)

Exif audio files

The Exif specification describes the RIFF file format used for WAV audio files, and defines a number of tags for storing meta information such as artist, copyright, creation date, and more in these files.[24] The following table gives an example of Exif information found in a WAV file written by the Pentax Optio WP digital camera:

Tag Value
Encoding Microsoft PCM
Num Channels 1
Sample Rate 7872
Avg Bytes Per Sec 7872
Bits Per Sample 8
Date Created 2005:08:08
Exif Version 0220
Related Image File IMGP1149.JPG
Time Created 16:23:35
Make PENTAX Corporation
Model PENTAX Optio WP
MakerNote (2064 bytes of data)

MakerNote data

The 'MakerNote' tag contains image information normally in a proprietary binary format. Some of these manufacturer-specific formats have been decoded:

  • OZHiker (not updated since 2008): Agfa, Canon, Casio, Epson, Fujifilm, Konica/Minolta, Kyocera/Contax, Nikon, Olympus, Panasonic, Pentax/Asahi, Ricoh, Sony[25]
  • Kamisaka (not updated since 2007): Canon, Casio, FujiFilm, ISL, KDDI, Konica/Minolta, Mamiya, Nikon, Panasonic, Pentax, Ricoh, Sigma, Sony, WWL[26]
  • X3F Info: Sigma/Foveon[27]
  • ExifTool: Canon, Casio, FujiFilm, GE, HP, JVC/Victor, Kodak, Leaf, Minolta/Konica-Minolta, Nikon, Olympus/Epson, Panasonic/Leica, Pentax/Asahi, Reconyx, Ricoh, Samsung, Sanyo, Sigma/Foveon, Sony[28]
  • Olypedia: Olympus[29]

Unfortunately, the proprietary formats used by many manufacturers break if the MakerNote tag is moved - i.e. by inserting or editing a tag which precedes it. The reason to edit to the Exif data could be as simple as to add copyright information, an Exif comment, etc. In some cases, camera vendors also store important information only in proprietary makernote fields, instead of using available Exif standard tags. An example for this is Nikon's ISO settings tag.[30]

See also

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ (JEITA CP-3451) Section 4.4.3: Pixel Composition and Sampling
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Dpi, misunderstandings and explanation, what is dpi
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ (JEITA CP-3451) Section 4.7.2: Interoperability Structure of APP2 in Compressed Data
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ (JEITA CP-3451) Section 5: Exif Audio File Specification
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Exchangeable_image_file_format&oldid=216638"