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. Grids are treated as signed 16bit integer unless the first scanline contains decimal values in which case the image is treated as 32bit floating point.
The AIG GIO drivers are also available for Arc/Info Binary Grid format.
NOTE: Implemented as gdal/frmts/aaigrid/aaigriddataset.cpp.
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.
Note that another driver (GIO) is available for Windows platforms with ArcView installed.
NOTE: Implemented as gdal/frmts/aigrid/aigdataset.cpp.
This driver is known to work with CEOS data produced by Spot Image, but will have problems with many other data sources. In particular, it will only work with eight bit unsigned data.
See the separate SAR_CEOS driver for access to SAR CEOS data products.
NOTE: Implemented as gdal/frmts/ceos/ceosdataset.cpp.
NOTE: Implemented as gdal/frmts/raw/doq1dataset.cpp.
This driver was implemented by Derrick J Brashear.
NOTE: Implemented as gdal/frmts/raw/doq2dataset.cpp.
NOTE: Implemented as gdal/frmts/dted/dteddataset.cpp.
Currently only the raster data is accessed. Georeferencing, and other meta data is ignored.
NOTE: Implemented as gdal/frmts/raw/effdataset.cpp.
This driver may be sufficient to read GTopo 30 data, and Geospot products.
NOTE: Implemented as gdal/frmts/raw/ehdrdataset.cpp.
NOTE: Implemented as gdal/frmts/envisat/envisatdataset.cpp.
NOTE: Implemented as gdal/frmts/fits/fitsdataset.cpp.
This driver supports georeferencing bounds, but no projection definition. New coverages can be created with a code of GIO.
Also see the AIG read-only driver available on all platforms.
NOTE: Implemented as gdal/frmts/aigrid/giodataset.cpp.
Details on the supporting code, and format can be found on the GXF-3 page.
NOTE: Implemented as gdal/frmts/gxf/gxfdataset.cpp.
Reading lat/long GCPs (TOP_LEFT_CORNER, ...) is supported but there is no support for reading affine georeferencing or projection information.
Unrecognised keywords from the .hdr file are preserved as metadata.
All data types with GDAL equivelents 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 Atlantis 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.
NOTE: Implemented as gdal/frmts/raw/mffdataset.cpp.
To select an MFF2 dataset select the directory containing the attrib, and image_data files for the dataset.
Currently only the UTM projection is supported (georef.projection.name = utm), with the affine transform computed from the lat/long control points. In any event, if GCPs are available in a georef file, they are returned with the dataset.
Newly created files (with a type of MFF2) are always just raw rasters with no georeferencing information. For read, and creation all data types (real, integer and complex in bit depths of 8, 16, 32) should be supported.
NOTE: Implemented as gdal/frmts/raw/hkvdataset.cpp.
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.
NOTE: Implemented as gdal/frmts/raw/pauxdataset.cpp.
See Also: PCI's .aux Format Description
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 extension of .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. However, georeferencing .wld files are not current written. All pixel types other than 16bit unsigned will be written as eight bit.
NOTE: Implemented as gdal/frmts/png/pngdataset.cpp. PNG support is implemented based on the libpng reference library. More information is available at http://www.libpng.org/pub/png.
Netpbm files can be created with a type of PNM.
NOTE: Implemented as gdal/frmts/raw/pnmdataset.cpp.
This driver works with most Radarsat and ERS data products, including simple look complex products; however, it is unlikely to work for non-Radar CEOS products. The simplier 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:
CEOS_LOGICAL_VOLUME_ID=EERS-1-SAR-MLD CEOS_PROCESSING_FACILITY=APP CEOS_PROCESSING_AGENCY=CCRS CEOS_PROCESSING_COUNTRY=CANADA CEOS_SOFTWARE_ID=APP 1.62 CEOS_ACQUISITION_TIME=19911029162818919 CEOS_SENSOR_CLOCK_ANGLE= 90.000 CEOS_ELLIPSOID=IUGG_75 CEOS_SEMI_MAJOR= 6378.1400000 CEOS_SEMI_MINOR= 6356.7550000NOTE: Implemented as gdal/frmts/ceos2/sar_ceosdataset.cpp.
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.
BUGS: