JPEG – JPEG JFIF File Format¶
Driver short name
(internal libjpeg provided)
The JPEG JFIF format is supported for reading, and batch writing, but not update in place. JPEG files are represented as one band (greyscale) or three band (RGB) datasets with Byte valued bands.
The driver will automatically convert images whose color space is YCbCr, CMYK or YCbCrK to RGB, unless GDAL_JPEG_TO_RGB is set to NO (YES is the default). When color space translation to RGB is done, the source color space is indicated in the SOURCE_COLOR_SPACE metadata of the IMAGE_STRUCTURE domain.
EXIF metadata can be read from JPEG files (but this will not result in a georeferenced image even if the EXIF_GPSLatitude and EXIF_GPSLongitude tags are set). But if an ESRI world file exists with the .jgw, .jpgw/.jpegw or .wld suffixes, it will be read and used to establish the geotransform for the image. If available a MapInfo .tab file will also be used for georeferencing. Overviews can be built for JPEG files as an external .ovr file.
The driver also supports the “zlib compressed mask appended to the file” approach used by a few data providers to add a bitmask to identify pixels that are not valid data. See RFC 15: Band Masks for further details.
The driver can deal with bitmask where the bits are ordered with most significant bit first (whereas the usual convention is least significant bit first). The driver will try to autodetect that situation, but the heuristics may fail. In that circumstance, you can set the JPEG_MASK_BIT_ORDER configuration option to MSB. Bitmask can also be completely ignored by specifying JPEG_READ_MASK to NO.
The GDAL JPEG Driver is built using the Independent JPEG Group’s jpeg library. Also note that the GeoTIFF driver supports tiled TIFF with JPEG compressed tiles.
To be able to read and write JPEG images with 12-bit sample, you can build GDAL with its internal libjpeg (based on IJG libjpeg-6b, with additional changes for 12-bit sample support), or explicitly pass –with-jpeg12=yes to configure script when building with external libjpeg. See “8 and 12 bit JPEG in TIFF” wiki page for more details.
It is also possible to use the JPEG driver with the libjpeg-turbo, a version of libjpeg, API and ABI compatible with IJG libjpeg-6b, which uses MMX, SSE, and SSE2 SIMD instructions to accelerate baseline JPEG compression/decompression.
XMP metadata can be extracted from the file, and will be stored as XML raw content in the xml:XMP metadata domain.
Embedded EXIF thumbnails (with JPEG compression) can be used as overviews, and generated by GDAL.
This driver supports the
This driver supports georeferencing
This driver supports virtual I/O operations (/vsimem/, etc.)
Color Profile Metadata¶
GDAL can deal with the following color profile metadata in the COLOR_PROFILE domain:
SOURCE_ICC_PROFILE (Base64 encoded ICC profile embedded in file.)
Note that this metadata property can only be used on the original raw pixel data. If automatic conversion to RGB has been done, the color profile information cannot be used.
This metadata tag can be used as creation options.
While decoding, libjpeg has resiliency towards some errors in the JPEG datastream and will try to recover from them as much of possible. Such errors will be reported as GDAL Warnings, but can optionally be considered as true Errors by setting the GDAL_ERROR_ON_LIBJPEG_WARNING configuration option to TRUE.
JPEG files are created using the “JPEG” driver code. Only Byte band types are supported.
Only 1 (greyscale), 3 band (input should be in RGB colorspace.
the driver will convert it automatically to YCbCr colorspace for storage, and
will expose it back as RGB on reading) or 4 band
(input should already by in CMYK colorspace. It will be exposed as RGB on reading
by default, unless the
GDAL_JPEG_TO_RGB configuration option
is set to NO) configurations.
JPEG file creation is implemented by the batch (CreateCopy) method. YCbCrK colorspace is not supported in creation. If the source dataset has a nodata mask, it will be appended as a zlib compressed mask to the JPEG file.
WORLDFILE=YES: Force the generation of an associated ESRI world file (with the extension .wld).
QUALITY=n: By default the quality flag is set to 75, but this option can be used to select other values. Values must be in the range 10-100. Low values result in higher compression ratios, but poorer image quality. Values above 95 are not meaningfully better quality but can but substantially larger.
PROGRESSIVE=ON: Enabled generation of progressive JPEGs. In some cases these will display a reduced resolution image in viewers such as Netscape, and Internet Explorer, before the full file has been downloaded. However, some applications cannot read progressive JPEGs at all. GDAL can read progressive JPEGs, but takes no advantage of their progressive nature.
INTERNAL_MASK=YES/NO: By default, if needed, an internal mask in the “zlib compressed mask appended to the file” approach is written to identify pixels that are not valid data. This can be disabled by setting this option to NO.
ARITHMETIC=YES/NO: To enable arithmetic coding. Not enabled in all libjpeg builds, because of possible legal restrictions.
BLOCK=1…16: (libjpeg >= 8c) DCT block size. All values from 1 to 16 are possible. Default is 8 (baseline format). A value other than 8 will produce files incompatible with versions prior to libjpeg 8c.
COLOR_TRANSFORM=RGB or RGB1: (libjpeg >= 9). Set to RGB1 for lossless RGB. Note: this will produce files incompatible with versions prior to libjpeg 9.
SOURCE_ICC_PROFILE=value: ICC profile encoded in Base64.
COMMENT=string: String to embed in a comment JPEG marker. When reading, such strings are exposed in the COMMENT metadata item.
EXIF_THUMBNAIL=YES/NO: Whether to generate an EXIF thumbnail(overview), itself JPEG compressed. Defaults to NO. If enabled, the maximum dimension of the thumbnail will be 128, if neither THUMBNAIL_WIDTH nor THUMBNAIL_HEIGHT are specified.
THUMBNAIL_WIDTH=n: Width of thumbnail. Only taken into account if EXIF_THUMBNAIL=YES.
THUMBNAIL_HEIGHT=n: Height of thumbnail. Only taken into account if EXIF_THUMBNAIL=YES.
WRITE_EXIF_METADATA=YES/NO: (Starting with GDAL 2.3). Whether to write EXIF_xxxx metadata items in a EXIF segment. Default to YES.
New in version 3.3.
Metadata encoded according to the FLIR convention (infrared images) is available
FLIR metadata domain.
Metadata from the following sections is supported:
Consult https://exiftool.org/TagNames/FLIR.html for details.
The thermal image data, stored either as raw data or in PNG, is exposed as a
GDAL subdataset whose name is