...
- test.bil <- bil file with data
- test.hdr <- header file with geo-referencing and data description
- test.tim <- timestep file
Note: An alternative parser with the ID 'BILBIPBSQ' has become available (in FEWS release 2017.01 and newer), which better adheres to the official (ESRI) specifications for BIL/BIP/BSQ format files. For importing files from external sources it is recommended to use the 'BILBIPBSQ' import type, which is documented here: BIL BIP BSQ Parser
File format
In the above example the test.bil files contains the actual data, the test.hdr describes the bil file and the test.tim file contains the date/time information for the bil file.
...
The first column in the time files contains: YYYYMMDDHHMM, the second column the number of minutes in the timesteps. The second column is presently ignored and may be omitted.
...
To read 32bit float bil files you will need to specify:
No Format |
---|
NRBITS 0
|
...
BIL reader supports keyword PIXELTYPE to read data using float 32 or float 64
Configuration
An example import configuration to import a bil file is shown below:
...
No Format |
---|
<?xml version="1.0" encoding="UTF-8"?> <idMap xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/idMap.xsd" version="1.1"> <!----> <parameter internal="T.fx" external="1"/> <parameter internal="P.fx" external="0"/> <!----> <location internal="BIL" external="BIL"/> </idMap> |
External parameter should be 0, or in case multiple parameters 0, 1, 2 etc.
The bil file doesn't contain any location informations, so location id mapping can be omitted.
If you still use location id mapping, use for external and internal location id the same string.