EVOLUTION-MANAGER

Edit File: frmt_ers.html

<html>
<head>
<title>ERS -- ERMapper .ERS</title>
</head>

<h1>ERS -- ERMapper .ERS</h1>

GDAL supports reading and writing raster files with .ers header files, with some
limitations.  The .ers ascii format is used by ERMapper for labeling raw
data files, as well as for providing extended metadata, and georeferencing
for some other file formats.  The .ERS format, or variants are also used to
hold descriptions of ERMapper algorithms, but these are not supported by GDAL.<p>

Starting with GDAL 1.9.0, the PROJ, DATUM and UNITS values found in the ERS header are reported
in the ERS metadata domain.<p>

<h2>Creation Issues</h2>

Creation Options:<p>

<ul>

<li> <b>PIXELTYPE=value</b>:.By setting this to SIGNEDBYTE, a new Byte file can be forced to be written as signed byte<p>

<li> <b>PROJ=name</b>: (GDAL >= 1.9.0) Name of the ERS projection string to use.
Common examples are NUTM11, or GEODETIC. If defined, this will override the value computed by SetProjection() or SetGCPs().<p>

<li> <b>DATUM=name</b>: (GDAL >= 1.9.0) Name of the ERS datum string to use.
Common examples are WGS84 or NAD83. If defined, this will override the value computed by SetProjection() or SetGCPs().<p>

<li> <b>UNITS=name</b>: (GDAL >= 1.9.0) Name of the ERS projection units to use :
METERS (default) or FEET (us-foot). If defined, this will override the value computed by SetProjection() or SetGCPs().<p>

</ul>

<ul>
<li> Implemented as <tt>gdal/frmts/ers/ersdataset.cpp</tt>.<p>
</ul>

</body>
</html>