📄 frmt_various.html
字号:
<html><head><title>Various Supported GDAL Raster Formats</title></head><body bgcolor="#ffffff"><h1>Various Support GDAL Raster Formats</h1><h2><a name="AAIGrid">AAIGrid -- Arc/Info ASCII Grid</a></h2>Supported for read and write access, including reading of an affinegeoreferencing 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.<p>The projections support (read if a *.prj file is available) is quitelimited. Additional sample .prj files may be sent to the maintainer,<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>.<p>The NODATA value for the grid read is also preserved when available.<p>If pixels being written are not square (the width and height of a pixel ingeoreferenced units differ) then DX and DY parameters will be output insteadof CELLSIZE. Such files can be used in Golden Surfer, but not most otherascii grid reading programs. For force the X pixel size to be used as CELLSIZEuse the FORCE_CELLSIZE=YES creation option or resample the input to have square pixels.<P>The <a href="#AIG">AIG</a> driver is also availablefor Arc/Info Binary Grid format.<p>NOTE: Implemented as <tt>gdal/frmts/aaigrid/aaigriddataset.cpp</tt>.<p><h2><a name="AIG">AIG -- Arc/Info Binary Grid</a></h2>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 ashdr.adf) from within it.<p>Support includes reading of an affine georeferencing transform, some projections, and a colortable (.clr) if available.<p>This driver is implemented based on a reverse engineering of the format. Seethe <a href="http://home.gdal.org/projects/aigrid/index.html">format description</a> for more details.<p>The projections support (read if a prj.adf file is available) is quitelimited. Additional sample prj.adf files may be sent to the maintainer,<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>.<p>NOTE: Implemented as <tt>gdal/frmts/aigrid/aigdataset.cpp</tt>.<p><h2><a name="BSB">BSB -- Maptech/NOAA BSB Nautical Chart Format</a></h2>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. Versions1.1, 2.0 and 3.0 have been tested successfully.<p>This driver should also support GEO/NOS format as supplied by Softchart.These files normally have the extension .nos with associated .geo filescontaining georeferencing ... the .geo files are currently ignored. <P>This driver is based on work by Mike Higgins. See the frmts/bsb/bsb_read.cfiles for details on patents affecting BSB format.<p>NOTE: Implemented as <tt>gdal/frmts/bsb/bsbdataset.cpp</tt>.<p><h2><a name="BT">BT -- VTP .bt Binary Terrain Format</a></h2>The .bt format is used for elevation data in the VTP software. Thedriver includes support for reading and writing .bt 1.3 format includingsupport for Int16, Int32 and Float32 pixel data types.<p> The driver does<b>not</b> support reading or writting gzipped (.bt.gz) .bt files eventhough this is supported by the VTP software. Please unpack the filesbefore using with GDAL using the "gzip -d file.bt.gz".<p>Projections in external .prj files are read and written, and support formost internally defined coordinate systems is also available.<p>Read/write imagery access with the GDAL .bt driver is terribly slow due toa very inefficient access strategy to this column oriented data. This couldbe corrected, but it would be a fair effort.<p>NOTE: Implemented as <tt>gdal/frmts/raw/btdataset.cpp</tt>.<p>See Also: The <a href="http://www.vterrain.org/Implementation/Formats/BT.html">BT file format</a> is defined on the <a href="http://www.vterrain.org/">VTP</a> web site.<p><h2><a name="CEOS">CEOS -- CEOS Image</a></h2>This is a simple, read-only reader for ceos image files. To use, selectthe main imagery file. This driver reads only the image data, and doesnot capture any metadata, or georeferencing.<p>This driver is known to work with CEOS data produced by Spot Image, butwill have problems with many other data sources. In particular, it willonly work with eight bit unsigned data.<p>See the separate <a href="#SAR_CEOS">SAR_CEOS</a> driver for access to SAR CEOS data products.<p>NOTE: Implemented as <tt>gdal/frmts/ceos/ceosdataset.cpp</tt>.<p><h2><a name="DODS"><a name="OPeNDAP">DODS/OPeNDAP -- Read rasters from DODS/OPeNDAP servers</a></a></h2>Support for read access to DODS/OPeNDAP servers. Pass the DODS/OPeNDAP URL tothe driver as you would when accessing a local file. The URL specifies theremote server, data set and raster within the data set. In addition, you musttell the driver which dimensions are to be interpreted as distinct bands aswell as which correspond to Latitude and Longitude. See the file README.DODSfor more detailed information.<p><h2><a name="DOQ1">DOQ1 -- First Generation USGS DOQ</a></h2>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.<p>NOTE: Implemented as <tt>gdal/frmts/raw/doq1dataset.cpp</tt>.<p><h2><a name="DOQ2">DOQ2 -- New Labelled USGS DOQ</a></h2>Support for read access, including reading of an affine georeferencing transform, capture of the projection string and reading of other auxilaryfields as metadata. This format is the new,labelled DOQ (Digital Ortho Quad) format from the USGS.<p>This driver was implemented by Derrick J Brashear.<p>NOTE: Implemented as <tt>gdal/frmts/raw/doq2dataset.cpp</tt>.<p>See Also: <a href="http://rockyweb.cr.usgs.gov/nmpstds/doqstds.html">USGS DOQ Standards</a><p><h2><a name="EHdr">EHdr -- ESRI .hdr Labelled</h2>GDAL supports reading and writing the ESRI .hdr labelling format,often referred to as ESRI BIL format. Eight, sixteenand thirty-two bit integer raster data types are supported as well as 32bit floating point. Coordinate systems (from a .prj file), and georeferencingare supported. Unrecognised 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.<p>This driver may be sufficient to read GTOPO30, SRTM30 + SRTM90 data and Geospot products.<p>NOTE: Implemented as <tt>gdal/frmts/raw/ehdrdataset.cpp</tt>.<p>See Also: <p><ul> <li> <a href="http://downloads.esri.com/support/whitepapers/other_/eximgav.pdf">ESRI whitepaper: + Extendable Image Formats for ArcView GIS 3.1 and 3.2</a> (BIL, see p. 5)<p> <li> <a href="http://edcdaac.usgs.gov/gtopo30/gtopo30.html">GTOPO30 - Global Topographic Data</a><p> <li> <a href="http://edcdaac.usgs.gov/gtopo30/README.html">GTOPO30 Documentation</a><p></ul><h2><a name="ENVI">ENVI - ENVI .hdr Labelled Raster</h2>GDAL supports some variations of raw raster files with associated ENVIstyle .hdr files describing the format. To select an existing ENVI rasterfile select the binary file containing the data (as opposed to the .hdr file), and GDAL will find the .hdr file by replacing the dataset extensionwith .hdr.<p>GDAL should support reading bil, bip and bsq interleaved formats, andmost pixel types are supported, including 8, 16 and 32bit signed and unsignedintegers, 32bit and 64 bit floating point, and 32bit and 64bit complex floatingpoint. There is limited support for recognising map_info keywords with the coordinate system and georeferencing. In particular, UTM and State Plane should work.<p>Creation Options:<p><ul> <li> <b>INTERLEAVE=BSQ/BIP/BIL</b>: Force the generation specified type of interleaving. <b>BSQ</b> --- band sequental (default), <b>BIP</b> --- data interleaved by pixel, <b>BIL</b> --- data interleaved by line.<p> <li> <b>SUFFIX=REPLACE/ADD</b>: Force adding ".hdr" suffix to supplied filename, e.g. if user selects "file.bin" name for output dataset, "file.bin.hdr" header file will be created. By default header file suffix replaces the binary file suffix, e.g. for "file.bin" name "file.hdr" header file will be created.</ul>NOTE: Implemented as <tt>gdal/frmts/raw/envidataset.cpp</tt>.<p><h2><a name="Envisat">Envisat -- Envisat Image Product</h2>GDAL supports the Envisat product format for read access. All sampletypes are supported. Files with two matching measurement datasets (MDS)are represented as having two bands. Currently all ASAR Level 1 and aboveproducts, and some MERIS and AATSR products are supported.<p>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.<p>Virtually all key/value pairs from the MPH and SPH (primary and secondaryheaders) are copied through as dataset level metadata. <p>NOTE: Implemented as <tt>gdal/frmts/envisat/envisatdataset.cpp</tt>.<p>See Also: <a href="http://envisat.esa.int/dataproducts/">Envisat Data Products</a> at ESA.<p><h2><a name="FITS">FITS -- Flexible Image Transport System</h2><p>FITS is a format used mainly by astronomers, but it is a relativelysimple format that supports arbitrary image types and multi-spectralimages, and so has found its way into GDAL. FITS support isimplemented in terms of the standard <ahref="http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html">CFITSIOlibrary</a>, which you must have on your system in order for FITSsupport to be enabled. Both reading and writing of FITS files issupported. At the current time, no support for a georeferencing systemis implemented, but WCS (World Coordinate System) support is possiblein the future.<p>Non-standard header keywords that are present in the FITS file willbe copied to the dataset's metadata when the file is opened, foraccess via GDAL methods. Similarly, non-standard header keywords thatthe user defines in the dataset's metadata will be written to the FITSfile when the GDAL handle is closed.<p>Note to those familiar with the CFITSIO library: The automaticrescaling of data values, triggered by the presence of the BSCALE andBZERO header keywords in a FITS file, is disabled in GDAL. Thoseheader keywords are accessible and updatable via dataset metadata, inthe same was as any other header keywords, but they do not affectreading/writing of data values from/to the file.<p>NOTE: Implemented as <tt>gdal/frmts/fits/fitsdataset.cpp</tt>.<p><h2><a name="GXF">GXF -- Grid eXchange File</a></h2>This is a raster exchange format propagated by Geosoft, and made a standardin the gravity/magnetics field. The format is supported for read, and writeand includes support for georeferencing information, and projections. <p>Details on the supporting code, and format can be found on the<a href="http://home.gdal.org/projects/gxf/index.html">GXF-3</a> page.<p>NOTE: Implemented as <tt>gdal/frmts/gxf/gxfdataset.cpp</tt>.<p><h2><a name="IDA">IDA -- Image Display and Analysis</h2>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 onlyof 8bit data. IDA files often have the extension .img though that is notrequired.<p>Projection and georeferencing information is read though some projections(ie. Meteosat, and Hammer-Aitoff) are not supported. When writing IDA filesthe 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.<p>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 mustbe used if the data is to be rescaled to original raw values for analysis. <p>NOTE: Implemented as <tt>gdal/frmts/raw/idadataset.cpp</tt>. <p>See Also: <A href="http://www.fao.org/giews/english/windisp/windisp.htm">WinDisp</a><p><h2><a name="ILWIS">ILWIS -- Raster Map</h2>This driver implements reading and writing of ILWIS raster maps and map lists. Select the raster files with the.mpr (for raster map) or .mpl (for maplist) extensions<p>Features:<ul><li>Support for Byte, Int16, Int32 and Float64 pixel data types.</li><li>Supports map lists with an associated set of ILWIS raster maps.</li><li>Read and write geo-reference (.grf). Support for geo-referencing transform is limited to north-oriented GeoRefCorner only. If possible the affine transform is computed from the corner coordinates.</li><li>Read and write coordinate files (.csy). Support is limited to: Projection type of Projection and Lat/Lon type that are defined in .csy file, the rest of pre-defined projection types are ignored.</li></ul>Limitations:<ul><li>Map lists with internal raster map storage (such as produced through Import General Raster) are not supported.</li><li>ILWIS domain (.dom) and representation (.rpr) files are currently ignored.</li></ul><h2><a name="JDEM">JDEM -- Japanese DEM (.mem)</a></h2>GDAL includes read support for Japanese DEM files, normally having theextension .mem. These files are a product of the Japanese Geographic Survey Institute.<p>These files are represented as having one 32bit floating band with elevationdata. The georeferencing of the files is returned as well as the coordinatesystem (always lat/long on the Tokyo datum). <p>There is no update or creation support for this format. <p>NOTE: Implemented as <tt>gdal/frmts/jdem/jdemdataset.cpp</tt>.<p>See Also: <a href="http://www.gsi.go.jp/ENGLISH/">Geographic Survey Institute (GSI) Web Site.</a><p><h2><a name="LAN">LAN -- Erdas 7.x .LAN and .GIS</a></h2>GDAL supports reading Erdas 7.x .LAN and .GIS raster files. Currently 4bit, 8bit and 16bit pixel data types are supported. <p>GDAL does read the map extents (geotransform) from LAN/GIS files, and attempts to read the coordinate system informaton. However, this formatof file does not include complete coordinate system information, so forstate plane and UTM coordinate systems a LOCAL_CS definition is returnedwith valid linear units but no other meaningful information.<p>The .TRL, .PRO and worldfiles are ignored at this time.<p>NOTE: Implemented as <tt>gdal/frmts/raw/landataset.cpp</tt><p>Development of this driver was financially supported by Kevin Flanders of(<a href="http://www.peoplegis.com">PeopleGIS</a>). <p><h2><a name="MFF">MFF -- Vexcel MFF Raster</a></h2>GDAL includes read, update, and creation support for Vexcel'sMFF raster format. MFF dataset consist of a header file (typically withthe extension .hdr) and a set of data files with extensions like .x00, .b00and so on. To open a dataset select the .hdr file.<p>Reading lat/long GCPs (TOP_LEFT_CORNER, ...) is supported but there is nosupport for reading affine georeferencing or projection information.<p>Unrecognised keywords from the .hdr file are preserved as metadata. <p>All data types with GDAL equivelents are supported, including 8, 16, 32 and64 bit data precisions in integer, real and complex data types. In additiontile organized files (as produced by the Vexcel SAR Processor - APP) aresupported for reading. <p>On creation (with a format code of MFF) a simple, ungeoreferenced rasterfile is created.<p>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 ofLSB (Integer -- little endian), and MSB (Motorola -- big endian). This maybe manually added to the .hdr file if required.<p>NOTE: Implemented as <tt>gdal/frmts/raw/mffdataset.cpp</tt>.<p><h2><a name="NDF">NDF -- NLAPS Data Format</a></h2>GDAL has limited support for reading NLAPS Data Format files. This is aformat 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 opena dataset select the header file, often with the extension .H1, .H2 or⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -