Various Support GDAL Raster Formats

Supported for read and write access, including reading of an affine
georeferencing transform and some projections.
This format is the ASCII interchange format for Arc/Info Grid,
and takes the form of an ASCII file, plus sometimes an associated .prj file.
It is normally produced with the Arc/Info ASCIIGRID command.

The projections support (read if a *.prj file is available) is quite
limited. Additional sample .prj files may be sent to the maintainer,
warmerdam@pobox.com.

The NODATA value for the grid read is also preserved when available in the
same format as the band data.

By default, the datatype returned for AAIGRID datasets by GDAL is autodetected,
and set to Float32 for grid with floating point values or Int32 otherwise. This is
done by analysing the format of the NODATA value and, if needed, the data of the
grid. From GDAL 1.8.0, you can explicitly specify the datatype by setting the
AAIGRID_DATATYPE configuration option (Int32, Float32 and Float64 values are
supported currently)

If pixels being written are not square (the width and height of a pixel in
georeferenced units differ) then DX and DY parameters will be output instead
of CELLSIZE. Such files can be used in Golden Surfer, but not most other
ascii grid reading programs. For force the X pixel size to be used as CELLSIZE
use the FORCE_CELLSIZE=YES creation option or resample the input to have
square pixels.

When writing floating-point values, the driver uses the "%.20g" format
pattern as a default. You can consult a
reference manual for printf to have an idea of the exact behaviour of this ;-).
You can alternatively specify the number of decimal places with the DECIMAL_PRECISION creation
option. For example, DECIMAL_PRECISION=3 will output numbers with 3 decimal
places(using %lf format). Starting with GDAL 1.11, another option is
SIGNIFICANT_DIGITS=3, which will output 3 significant digits (using %g format).

This is a convenience driver to read ACE2 DEMs. Those files contain
raw binary data. The georeferencing is entirely determined by the
filename. Quality, source and confidence layers are of Int16 type,
whereas elevation data is returned as Float32.

Supported by GDAL for read access. Creation is possible, but it must be
considered as experimental and a means of testing read access (although files created
by the driver can be read successfully on another GIS software)

An ADRG dataset is made of several files. The file recognised by GDAL is the
General Information File (.GEN). GDAL will also need the image file (.IMG),
where the actual data is.

The Transmission Header File (.THF) can also be used as an input to GDAL. If the THF references more than one image,
GDAL will report the images it is composed of as subdatasets. If the THF references just one image, GDAL will open it directly.

Overviews, legends and insets are not used. Polar zones (ARC zone 9 and 18) are not supported (due to the lack of test data).

Supported by GDAL for read access.
This format is the internal binary format for Arc/Info Grid,
and takes the form of a coverage level directory in an Arc/Info database.
To open the coverage select the coverage directory, or an .adf file (such as
hdr.adf) from within it. If the directory does not contain file(s) with names
like w001001.adf then it is not a grid coverage.

Support includes reading of an affine
georeferencing transform, some projections, and a color
table (.clr) if available.

This driver is implemented based on a reverse engineering of the format. See
the format
description for more details.

The projections support (read if a prj.adf file is available) is quite
limited. Additional sample prj.adf files may be sent to the maintainer,
warmerdam@pobox.com.

BSB Nautical Chart format is supported for read access, including reading
the colour table and the reference points (as GCPs). Note that the .BSB
files cannot be selected directly. Instead select the .KAP files. Versions
1.1, 2.0 and 3.0 have been tested successfully.

This driver should also support GEO/NOS format as supplied by Softchart.
These files normally have the extension .nos with associated .geo files
containing georeferencing ... the .geo files are currently ignored.

This driver is based on work by Mike Higgins. See the frmts/bsb/bsb_read.c
files for details on patents affecting BSB format.

Starting with GDAL 1.6.0, it is possible to select an alternate color palette
via the BSB_PALETTE configuration option. The default value is RGB.
Other common values that can be found are : DAY, DSK, NGT, NGR, GRY, PRC, PRG...

The .bt format is used for elevation data in the VTP software. The
driver includes support for reading and writing .bt 1.3 format including
support for Int16, Int32 and Float32 pixel data types.

The driver does
not support reading or writing gzipped (.bt.gz) .bt files even
though this is supported by the VTP software. Please unpack the files
before using with GDAL using the "gzip -d file.bt.gz".

Projections in external .prj files are read and written, and support for
most internally defined coordinate systems is also available.

Read/write imagery access with the GDAL .bt driver is terribly slow due to
a very inefficient access strategy to this column oriented data. This could
be corrected, but it would be a fair effort.

This driver can read USGS Land Use and Land Cover (LULC) grids encoded in the
Character Composite Theme Grid (CTG) format. Each file is reported as a 6-band
dataset of type Int32. The meaning of each band is the following one :

Land Use and Land Cover Code

Political units Code

Census county subdivisions and SMSA tracts Code

Hydrologic units Code

Federal land ownership Code

State land ownership Code

Those files are typically named grid_cell.gz, grid_cell1.gz or grid_cell2.gz
on the USGS site.

Supported for writing and creation. The DirectDraw Surface file format (uses
the filename extension DDS), from Microsoft, is a standard for storing data
compressed with the lossy S3 Texture Compression (S3TC) algorithm. The DDS
format and compression are provided by the crunch library.

The driver supports the following texture formats: DXT1. DXT1A, DXT3 (default) and
DXT5. You can set the texture format using the creation option FORMAT.

The driver supports the following compression quality: SUPERFAST, FAST, NORMAL
(default), BETTER and UBER. You can set the compression quality using the
creation option QUALITY.

This is a read-only read for Spot DIMAP described images. To use, select
the METADATA.DIM file in a product directory, or the product directory
itself.

The imagery is in a distinct imagery file, often a TIFF file, but the
DIMAP dataset handles accessing that file, and attaches geolocation and
other metadata to the dataset from the metadata xml file.

From GDAL 1.6.0, the content of the <Spectral_Band_Info> node is reported as metadata
at the level of the raster band. Note that the content of the Spectral_Band_Info
of the first band is still reported as metadata of the dataset, but this should
be considered as a deprecated way of getting this information.

Support for read access to DODS/OPeNDAP servers. Pass the DODS/OPeNDAP URL to
the driver as you would when accessing a local file. The URL specifies the
remote server, data set and raster within the data set. In addition, you must
tell the driver which dimensions are to be interpreted as distinct bands as
well as which correspond to Latitude and Longitude. See the file README.DODS
for more detailed information.

Support for read access, including reading of an affine georeferencing
transform, and capture of the projection string. This format is the old,
unlabelled DOQ (Digital Ortho Quad) format from the USGS.

Support for read access, including reading of an affine georeferencing
transform, capture of the projection string and reading of other auxiliary
fields as metadata. This format is the new,
labelled DOQ (Digital Ortho Quad) format from the USGS.

GDAL supports reading and writing the ESRI .hdr labeling format,
often referred to as ESRI BIL format. Eight, sixteen
and thirty-two bit integer raster data types are supported as well as 32
bit floating point. Coordinate systems (from a .prj file), and georeferencing
are supported. Unrecognized options in the .hdr file are ignored. To
open a dataset select the file with the image file (often with the extension
.bil). If present .clr color table files are read, but not written. If present,
image.rep file will be read to extract the projection system of SpatioCarte Defense 1.0 raster products.

This driver does not always do well differentiating between floating point and
integer data. The GDAL extension to the .hdr format to differentiate is to add
a field named PIXELTYPE with values of either FLOAT, SIGNEDINT or UNSIGNEDINT.
In combination with the NBITS field it is possible to described all variations
of pixel types.

This is a read-only reader for ECRG (Enhanced Compressed Raster Graphic) products,
that uses the table of content file, TOC.xml, and exposes it as a virtual dataset whose
coverage is the set of ECRG frames contained in the table of content.

The driver will report a different subdataset for each subdataset found in the TOC.xml
file. Each subdataset consists of the frames of same product id, disk id, and starting
with GDAL 1.11.3, with same scale.

To open a dataset select the file with the header information. The driver finds
the image file from the header information. Erdas documents call the header
file the "raw" file and it may have the extension .raw while the image file that
contains the actual raw data may have the extension .bl.

GDAL supports some variations of raw raster files with associated ENVI
style .hdr files describing the format. To select an existing ENVI raster
file select the binary file containing the data (as opposed to the .hdr
file), and GDAL will find the .hdr file by replacing the dataset extension
with .hdr.

GDAL should support reading bil, bip and bsq interleaved formats, and
most pixel types are supported, including 8bit unsigned, 16 and 32bit
signed and unsigned integers, 32bit and 64 bit floating point, and
32bit and 64bit complex floating point. There is limited support for
recognising map_info keywords with the
coordinate system and georeferencing. In particular, UTM and State Plane
should work.

Starting with GDAL 1.10, all ENVI header fields will be stored in the
ENVI metadata domain, and all of these can then be written out to the header file.

GDAL supports the Envisat product format for read access. All sample
types are supported. Files with two matching measurement datasets (MDS)
are represented as having two bands. Currently all ASAR Level 1 and above
products, and some MERIS and AATSR products are supported.

The control points of the GEOLOCATION GRID ADS dataset are read if available,
generally giving a good coverage of the dataset. The GCPs are in WGS84.

Virtually all key/value pairs from the MPH and SPH (primary and secondary
headers) are copied through as dataset level metadata.

ASAR and MERIS parameters contained in the ADS and GADS records (excluded
geolocation ones) can be retrieved as key/value pairs using the "RECORDS"
metadata domain.

FITS is a format used mainly by astronomers, but it is a relatively
simple format that supports arbitrary image types and multi-spectral
images, and so has found its way into GDAL. FITS support is
implemented in terms of the standard CFITSIO
library, which you must have on your system in order for FITS
support to be enabled. Both reading and writing of FITS files is
supported. At the current time, no support for a georeferencing system
is implemented, but WCS (World Coordinate System) support is possible
in the future.

Non-standard header keywords that are present in the FITS file will
be copied to the dataset's metadata when the file is opened, for
access via GDAL methods. Similarly, non-standard header keywords that
the user defines in the dataset's metadata will be written to the FITS
file when the GDAL handle is closed.

Note to those familiar with the CFITSIO library: The automatic
rescaling of data values, triggered by the presence of the BSCALE and
BZERO header keywords in a FITS file, is disabled in GDAL. Those
header keywords are accessible and updatable via dataset metadata, in
the same was as any other header keywords, but they do not affect
reading/writing of data values from/to the file.

This driver supporting reading "Generic Binary" files labelled with a .hdr
file, but distinct from the more common ESRI labelled .hdr format (EHdr driver).
The origin of this format is not entirely clear. The .hdr
files supported by this driver are look something like this:

{{{
BANDS: 1
ROWS: 6542
COLS: 9340
...
}}}

Pixel data types of U8, U16, S16, F32, F64, and U1 (bit) are supported.
Georeferencing and coordinate system information should be supported
when provided.

By default, the datatype returned for GRASS ASCII grid datasets by GDAL is autodetected,
and set to Float32 for grid with floating point values or Int32 otherwise. This is
done by analysing the format of the null value and the first 100k bytes of data of the
grid. You can also explicitly specify the datatype by setting the
GRASSASCIIGRID_DATATYPE configuration option (Int32, Float32 and Float64 values are
supported currently)

This is the ASCII-based (human-readable) version of one of the raster formats
used by Golden Software products (such as the Surfer series). This format is
supported for both reading and writing (including create, delete, and copy).
Currently the associated formats for color, metadata, and shapes are not
supported.

This is the binary (non-human-readable) version of one of the raster formats
used by Golden Software products (such as the Surfer series). Like the ASCII
version, this format is supported for both reading and writing (including
create, delete, and copy). Currently the associated formats for color,
metadata, and shapes are not supported.

This is the binary (non-human-readable) version of one of the raster formats
used by Golden Software products (such as the Surfer series). This format
differs from the GSBG format (also known as Surfer 6
binary grid format), it is more complicated and flexible.

This is a raster exchange format propagated by Geosoft, and made a standard
in the gravity/magnetics field. GDAL supports reading (but not writing)
GXF-3 files, including support for georeferencing information, and projections.

By default, the datatype returned for GXF datasets by GDAL is Float32.
From GDAL 1.8.0, you can specify the datatype by setting the GXF_DATATYPE
configuration option (Float64 supported currently)

Details on the supporting code, and format can be found on the
GXF-3 page.

GDAL supports reading and writing IDA images with some limitations. IDA
images are the image format of WinDisp 4. The files are always one band only
of 8bit data. IDA files often have the extension .img though that is not
required.

Projection and georeferencing information is read though some projections
(i.e. Meteosat, and Hammer-Aitoff) are not supported. When writing IDA files
the projection must have a false easting and false northing of zero. The
support coordinate systems in IDA are Geographic, Lambert Conformal Conic,
Lambert Azimuth Equal Area, Albers Equal-Area Conic and Goodes Homolosine.

IDA files typically contain values scaled to 8bit via a slope and offset.
These are returned as the slope and offset values of the bands and they must
be used if the data is to be rescaled to original raw values for analysis.

Driver for the image formats used in the JPL's Interferometric synthetic
aperture radar Scientific Computing Environment (ISCE). Only images with
data types mappable to GDAL data types are supported.

Image properties are stored under the ISCE metadata domain, but there is
currently no support to access underlying components elements and their
properties. Likewise, ISCE domain metadata will be saved as properties
in the image XML file.

Georeferencing is not yet implemented.

The ACCESS_MODE property is not currently honored.

The only creation option currently is SCHEME, which value (BIL, BIP, BSQ)
determine the interleaving (default is BIP).

Supported for read access, update and creation.
This format is a binary raw format, that supports data of several depths (
8 bit, unsigned integer 16 bit and floating point 32 bit) and with several band
number (3 or 4 typically, for RGB and RGBA). There is no file size limit,
except the limitation of the file system.

GDAL supports reading and writing
Erdas 7.x .LAN and .GIS raster files. Currently
4bit, 8bit and 16bit pixel data types are supported for reading
and 8bit and 16bit for writing.

GDAL does read the map extents (geotransform) from LAN/GIS files, and
attempts to read the coordinate system information. However, this format
of file does not include complete coordinate system information, so for
state plane and UTM coordinate systems a LOCAL_CS definition is returned
with valid linear units but no other meaningful information.

The .TRL, .PRO and worldfiles are ignored at this time.

NOTE: Implemented as gdal/frmts/raw/landataset.cpp

Development of this driver was financially supported by Kevin Flanders of
(PeopleGIS).

GDAL includes read, update, and creation support for Vexcel's
MFF raster format. MFF dataset consist of a header file (typically with
the extension .hdr) and a set of data files with extensions like .x00, .b00
and so on. To open a dataset select the .hdr file.

Reading lat/long GCPs (TOP_LEFT_CORNER, ...) is supported but there is no
support for reading affine georeferencing or projection information.

Unrecognized keywords from the .hdr file are preserved as metadata.

All data types with GDAL equivalents are supported, including 8, 16, 32 and
64 bit data precisions in integer, real and complex data types. In addition
tile organized files (as produced by the Vexcel SAR Processor - APP) are
supported for reading.

On creation (with a format code of MFF) a simple, ungeoreferenced raster
file is created.

MFF files are not normally portable between systems with different byte orders.
However GDAL honours the new BYTE_ORDER keyword which can take a value of
LSB (Integer -- little endian), and MSB (Motorola -- big endian). This may
be manually added to the .hdr file if required.

GDAL has limited support for reading NLAPS Data Format files. This is a
format primarily used by the Eros Data Center for distribution of Landsat
data. NDF datasets consist of a header file (often with the extension .H1)
and one or more associated raw data files (often .I1, .I2, ...). To open
a dataset select the header file, often with the extension .H1, .H2 or
.HD.

The NDF driver only supports 8bit data. The only supported projection is
UTM. NDF version 1 (NDF_VERSION=0.00) and NDF version 2 are both supported.

GDAL has limited support for reading and writing netCDF grid files.
NetCDF files that are not recognised as grids (they lack variables called
dimension, and z) will be silently ignored by this driver. This driver is
primarily intended to provide a mechanism for grid interchange with the
GMT package. The
netCDF driver should be used for more general netCDF datasets.

The units information in the file will be ignored, but x_range, and
y_range information will be read to get georeferenced extents of the raster.
All netCDF data types should be supported for reading.

Newly created files (with a type of GMT) will always have
units of "meters" for x, y and z but the x_range, y_range and z_range should
be correct. Note that netCDF does not have an unsigned byte data type, so
8bit rasters will generally need to be converted to Int16 for export to
GMT.

GDAL includes a partial implementation of the PCI .aux labelled raw raster
file for read, write and creation. To open a PCI labelled file, select the
raw data file itself. The .aux file (which must have a common base name) will
be checked for automatically.

The format type for creating new files is PAux. All PCI data types
(8U, 16U, 16S, and 32R) are supported. Currently georeferencing, projections,
and other metadata is ignored.

GDAL includes support for reading and writing PCRaster raster files. PCRaster is a dynamic modeling system for distributed simulation models. The main applications of PCRaster are found in environmental modeling: geography, hydrology, ecology to name a few. Examples include models for research on global hydrology, vegetation competition models, slope stability models and land use change models.

The driver reads all types of PCRaster maps: booleans, nominal, ordinals, scalar, directional and ldd. The same cell representation used to store values in the file is used to store the values in memory.

The driver detects whether the source of the GDAL raster is a PCRaster file. When such a raster is written to a file the value scale of the original raster will be used. The driver always writes values using UINT1, INT4 or REAL4 cell representations, depending on the value scale:

Value scale

Cell representation

VS_BOOLEAN

CR_UINT1

VS_NOMINAL

CR_INT4

VS_ORDINAL

CR_INT4

VS_SCALAR

CR_REAL4

VS_DIRECTION

CR_REAL4

VS_LDD

CR_UINT1

For rasters from other sources than a PCRaster raster file a value scale and cell representation is determined according to the following rules:

Source type

Target value scale

Target cell representation

GDT_Byte

VS_BOOLEAN

CR_UINT1

GDT_Int32

VS_NOMINAL

CR_INT4

GDT_Float32

VS_SCALAR

CR_REAL4

GDT_Float64

VS_SCALAR

CR_REAL4

The driver can convert values from one supported cell representation to another. It cannot convert to unsupported cell representations. For example, it is not possible to write a PCRaster raster file from values which are used as CR_INT2 (GDT_Int16).

Although the de-facto file extension of a PCRaster raster file is .map, the PCRaster software does not require a standardized file extension.

GDAL includes support for reading, and creating .png files. Greyscale,
pseudo-colored, Paletted, RGB and RGBA PNG files are supported as well as
precisions of eight and sixteen bits per sample.

PNG files are linearly compressed, so random reading of large PNG files can
be very inefficient (resulting in many restarts of decompression from the
start of the file).

Text chunks are translated into metadata, typically with multiple lines per
item. World files with the extensions of .pgw, .pngw or .wld
will be read. Single transparency values in greyscale files will be
recognised as a nodata value in GDAL. Transparent index in paletted images
are preserved when the color table is read.

PNG files can be created with a type of PNG, using the CreateCopy() method,
requiring a prototype to read from. Writing includes support for the
various image types, and will preserve transparency/nodata values.
Georeferencing .wld files are written if option WORLDFILE is set. All
pixel types other than 16bit unsigned will be written as eight bit.

Starting with GDAL 1.9.0, XMP metadata can be extracted from the file, and will be
stored as XML raw content in the xml:XMP metadata domain.

Color Profile Metadata

Starting with GDAL 1.11, GDAL can deal with the following color profile metadata in the COLOR_PROFILE domain:

This is a read-only reader for RPF products, like CADRG or CIB, that uses the table of
content file - A.TOC - from a RPF exchange, and exposes it as a virtual dataset whose
coverage is the set of frames contained in the table of content.

The driver will report a different subdataset for each subdataset found in the A.TOC
file.

In some situations, NITF tiles inside a
subdataset don't share the same palettes. The RPFTOC driver will do its best
to remap palettes to the reported palette by gdalinfo (which is the palette of
the first tile of the subdataset). In situations where it would not give a
good result, you can try to set the RPFTOC_FORCE_RGBA environment variable to
TRUE before opening the subdataset. This will cause the driver to expose the
subdataset as a RGBA dataset, instead of a paletted one.

It is possible to build external overviews for a subdataset. The overview for the first subdataset
will be named A.TOC.1.ovr for example, for the second dataset it will be A.TOC.2.ovr, etc.
Note that you must re-open the subdataset with the same setting of RPFTOC_FORCE_RGBA as the one you
have used when you have created it. Do not use any method other than NEAREST resampling when building
overviews on a paletted subdataset (RPFTOC_FORCE_RGBA unset)

A gdalinfo on one of this subdataset will return the various NITF metadata, as well
as the list of the NITF tiles of the subdataset.

This is a read-only reader for the datasets handled by the
R Raster package.
Those datasets are made of a .grd file, which is a text header file, and a .gri
binary file containing the raster data itself. The .grd is the file opened by
GDAL.
Starting with GDAL 2.3, the driver will read ratvalues as RAT or color tables.
Layer names will be assigned to GDAL band description. The 'creator' and 'created'
attributes of the '[general]' section will be assigned to the GDAL 'CREATOR'
and 'CREATED' dataset metadata items.

Starting with GDAL 2.3, the driver has write capabilities.
Color tables or RAT will be written.
The 'CREATOR' and 'CREATED' dataset metadata items will be written as the
'creator' and 'created' attributes of the '[general]' section.
Band description will be written as the 'layername' attribute of the
'[description]' section.

The following creation options are supported:

INTERLEAVE=BIP/BIL/BSQ. Respectively band interleaved by pixel, band
interleaved by line, band sequential. Default to BIL

PIXELTYPE=SIGNEDBYTE. To write Byte bands as signed byte instead of
unsigned byte.

This is a read-only reader for CEOS SAR image files. To use, select
the main imagery file.

This driver works with most Radarsat and ERS data
products, including single look complex products; however, it is unlikely
to work for non-Radar CEOS products. The simpler CEOS
driver is often appropriate for these.

This driver will attempt to read 15 lat/long GCPS by sampling the per-scanline
CEOS superstructure information. It also captures various pieces of metadata
from various header files, including:

The SAR_CEOS driver also includes some support for SIR-C and PALSAR
polarimetric data. The SIR-C format contains an image in compressed
scattering matrix form, described
here.
GDAL decompresses the data as it is read in. The PALSAR format
contains bands that correspond almost exactly to elements of the 3x3
Hermitian covariance matrix-
see the
ERSDAC-VX-CEOS-004A.pdf document for a complete description (pixel
storage is described on page 193). GDAL converts these to complex floating
point covariance matrix bands as they are read in. The convention used
to represent the covariance matrix in terms of the scattering matrix
elements HH, HV (=VH), and VV is indicated below. Note that the
non-diagonal elements of the matrix are complex values, while the diagonal
values are real (though represented as complex bands).

The driver supports both reading and writing (including create, delete,
and copy) SAGA GIS binary grids. SAGA binary grid datasets are made of
an ASCII header (.SGRD) and a binary data (.SDAT) file with a common
basename. The .SDAT file should be selected to access the dataset.
Starting with GDAL 2.3, the driver can read compressed .sg-grd-z files that
are ZIP archives with .sgrd, .sdat and .prj files.

GDAL includes support for reading USGS SDTS formatted DEMs. USGS DEMs are
always returned with a data type of signed sixteen bit integer, or 32bit float.
Projection and georeferencing information is also returned.

SDTS datasets consist of a number of files. Each DEM should have one file
with a name like XXXCATD.DDF. This should be selected to open
the dataset.

The elevation units of DEMs may be feet or meters. The GetType() method on a
band will attempt to return if the units are Feet ("ft") or Meters ("m").

The SGI driver currently supports the reading and writing of SGI Image files.

The driver currently supports 1, 2, 3, and 4 band images. The driver
currently supports "8 bit per channel value" images. The driver supports
both uncompressed and run-length encoded (RLE) images for reading, but
created files are always RLE compressed..

The ASRP and USRP raster products (as defined by DGIWG) are variations on a
common standard product format and are supported for reading by GDAL. ASRP and
USRP datasets are made of several files - typically a .GEN, .IMG, .SOU and .QAL
file with a common basename. The .IMG file should be selected to access the dataset.

ASRP (in a geographic coordinate system) and USRP (in a UTM/UPS coordinate
system) products are single band images with a palette and georeferencing.

Starting with GDAL 1.11, the Transmission Header File (.THF) can also be used as an input to GDAL. If the THF references more than one image,
GDAL will report the images it is composed of as subdatasets. If the THF references just one image, GDAL will open it directly.

The SRTM HGT driver currently supports the reading of SRTM-3 and SRTM-1 V2 (HGT) files.
The files must be named like NXXEYYY.hgt, or starting with GDAL 2.1.2,
NXXEYYY[.something].hgt

Starting with GDAL 2.2, the driver can directly read .hgt.zip files provided
that they are named like NXXEYYY[.something].hgt.zip and contain a NXXEYYY.hgt
file. For previous versions, use /vsizip//path/to/NXXEYYY[.something].hgt.zip/NXXEYYY.hgt
syntax

The driver does support creating new files, but the input data
must be exactly formatted as a SRTM-3 or SRTM-1 cell. That is the size,
and bounds must be appropriate for a cell.

GDAL includes support for reading and writing XPM (X11 Pixmap Format)
image files. These are colormapped one band images primarily used for
simple graphics purposes in X11 applications. It has been incorporated in
GDAL primarily to ease translation of GDAL images into a form usable with
the GTK toolkit.

The XPM support does not support georeferencing (not available from XPM files)
nor does it support XPM files with more than one character per pixel. New
XPM files must be colormapped or greyscale, and colortables will be reduced
to about 70 colors automatically.

This read-only GDAL driver is designed to provide access to processed data from Sandia National Laboratories' various experimental sensors. The format is essentially an arbitrary length header containing instrument configuration and performance parameters along with a binary matrix of 16- or 32-bit complex or byte real data.

The GFF format was implemented based on the Matlab code provided by Sandia to read the data. The driver supports all types of data (16-bit or 32-bit complex, real bytes) theoretically, however due to a lack of data only 32-bit complex data has been tested.

Supported for read access and creation.
This format is an ASCII interchange format for gridded data
in an ASCII line format for transport and storage. It is commonly used
in applications in the Oil and Gas Exploration field.

By default, files are interpreted and written according to the
PIXEL_IS_AREA convention. If you define the ZMAP_PIXEL_IS_POINT
configuration option to TRUE, the PIXEL_IS_POINT convention will be
followed to interpret/write the file (the georeferenced values in the
header of the file will then be considered as the coordinate of the
center of the pixels). Note that in that case, GDAL will report the
extent with its usual PIXEL_IS_AREA convention (the coordinates of the
topleft corner as reported by GDAL will be a half-pixel at the top and
left of the values that appear in the file).

OGR DWG support is based on libopencad, so the list of supported DWG (DXF)
versions can be seen in libopencad documentation. All drawing entities are
separated into layers as they are in DWG file. The rasters are usually a separate
georeferenced files (GeoTiff, Jpeg, Png etc.) which exist in DWG file as separate
layers. The driver try to get spatial reference and other methadata from DWG
Image description and set it to GDALDataset.