ERDAS RAW Reader/Writer
FME Format Type Identifier |
ERDASRAW |
Reader/Writer |
Both |
Typical File Extensions |
.raw, .bqw, .blw, .bpw |
An ERDAS® .raw file is a header file that stores the properties of an associated raw raster file.
ERDAS RAW Product and System Requirements
Format |
FME Platform |
Operating System |
||||
---|---|---|---|---|---|---|
Reader/Writer |
FME Form |
FME Flow |
FME Flow Hosted |
Windows 64-bit |
Linux |
Mac |
Reader |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Writer |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Overview
The georeferencing information is read from or written to an Esri world file and some properties are stored in the .raw file with the following keywords.
Keyword |
Value |
---|---|
BYTE_ORDER |
The byte order in which image pixel values are stored. The byte order is important for 16-bit images, with 2 bytes per pixel. Acceptable values are LSB, which is Intel byte order (Silicon Graphics, DEC Alpha, PC) or little-endian, and MSB, which is Motorola byte order (Sun, HP, etc.) or big-endian. Required for DATA_TYPE values of U16, S16, U32, S32, F32 and F64. It is ignored otherwise. |
DATA_OFFSET |
The number of bytes of data in the image file to skip in order to reach the start of the image data. This keyword allows you to bypass any existing image header information in the file. Default: 0 bytes |
DATA_TYPE |
The data type used for each pixel in each band. Acceptable values are U1, U2, U4, U8, U16, U32, S16, S32, F32, and F64. For a true color image with three bands (R, G, B) stored using 8 bits for each pixel in each band, DATA_TYPE equals U8 and NUM_LAYERS equals 3, for a total of 24 bits per pixel. Default: U8 |
END_RAW_FILE |
Indicates the end of the raw file. The reader will ignore any keywords after it reads this keyword. |
FORMAT |
The organization of the bands in the image file. Acceptable values are BIL, which is band interleaved by line, BIP, which is band interleaved by pixel, and BSQ, which is band sequential. Default: BIL |
HEIGHT |
The number of rows in the image. Rows are parallel to the x-axis of the map coordinate system. There is no default. |
IMAGINE_RAW_FILE |
This keyword must be at the very beginning of the file, on a line by itself. |
NUM_LAYERS |
The number of spectral bands in the image. Default: 1 |
PIXEL_FILES |
The name of the file in which raster data resides. The reader currently ignores this keyword and assumes the name of the raw file is the name of the header without an extension. Default: The name of the raw file without an extension |
WIDTH |
The number of columns in the image. Columns are parallel to the y-axis of the map coordinate system. There is no default. |
Usage Notes
Since the reader does not read the PIXEL_FILES directive, the reader always assumes that the raw binary file is the dataset, and the name of this file is the name of the header without the extension.
Currently, the reader does not support multiple raw binary files in one dataset or a single file with both the header and the raw binary data at the same time.
Reader Overview
FME can read a binary raw raster file with an associated ERDAS .raw header file, with or without an Esri world file.
FME considers a single binary ERDAS RAW file associated with a header file to be a dataset. The ERDAS RAW file contains pixel data, and each pixel in the file is a point in a single FME raster feature. The header file contains the raster properties.
Writer Overview
FME can output a binary raw raster file and an associated ERDAS .raw header file, along with an Esri World file, into a single folder specified by the Dataset parameter.
The ERDAS RAW file contains pixel data: each pixel in the file is a point in a single FME raster feature. The ERDAS RAW writer distinguishes duplicate output files by appending numbers to the filenames.
FME Raster Features
FME raster features represent raster data and use several concepts that are unlike those used in the handling of vector data.
For comprehensive information about how FME processes raster data, see Rasters.
ERDAS Raw supports rasters with an arbitrary number of bands, provided all bands are the same data type and no band has a palette.
For each raster, there is only a single feature returned, since this feature will contain the entire raster.