Difference between revisions of "How to convert data for Geogrid"

Revision as of 14:14, 9 October 2013

Back to the WRF-SFIRE user guide.

See the github repository for convert_geotiff for the latest documentation and source code.

@@ Line 1: / Line 1: @@
 {{users guide}}
-Running WRF-Fire using real data requires additional datasets not included in the standard
-WPS input data [http://www.mmm.ucar.edu/wrf/src/wps_files/geog_v3.1.tar.gz tarball].  For these,
-it is necessary to convert your source data into the
-[http://www.mmm.ucar.edu/wrf/users/docs/user_guide_V3.1/users_guide_chap3.htm#_Writing_Static_Data geogrid data format].
-The geogrid data format consists of a directory of tiled binary files with names indicating the index range contained in each tile.
-For instance, a file name of <tt>00101-00200.00051-00100</tt> would consist of columns 101 through 200 and rows 51 through 100.
-The files themselves contain only an array integers, with no associated metadata.
-The metadata for the dataset is contained in a file called <tt>index</tt>, which contains a series ''keyword=value'' statements
-telling geogrid the details of the data tiles, such as width, height, the number of bytes per integer, etc.  The index file also contains metadata
-for the data set itself, such as the projection information and physical units.
-We have made available a series of scripts and utilities ([http://github.com/jbeezley/autoWPS autoWPS]) intended to automate many of the steps
+See the github repository for [https://github.com/jbeezley/convert_geotiff.git convert_geotiff] for the latest documentation and source code.
-required to create a dataset for a WRF real run.  A utility program included in this repository, WPSGeoTiff, is a simple command line utility that
-takes a GeoTiff file and writes converts the data into geogrid binary format.  The GeoTiff format was chosen because it is a highly ubiquitous format
-for geotagged data and it has a cross-platform and open source c library called [http://trac.osgeo.org/geotiff/ libGeoTIFF].  Most, if not all, GIS application
-software is capable of converting or exporting a dataset as a GeoTiff file.
-=Prerequisites=
-The WPSGeoTiff utility requires two external libraries in order to compile.  You should pick a location to install the libraries, for instance <tt>PREFIX=${HOME}/opt</tt>.
-* Optional: [http://trac.osgeo.org/proj/ Proj.4]  This library is required in order to process projected GeoTIFF files.  It must be installed before GeoTIFF for the projection support to be added.
- <code>./configure --prefix=$PREFIX
- make
- make install</code>
-* [http://www.libtiff.org/ libTIFF] The following commands are sufficient to install libTIFF for most systems.
- <code>./configure --prefix=$PREFIX
- make
- make install</code>
-* [http://trac.osgeo.org/geotiff/ libGeoTIFF] A similar set of commands install libGeoTIFF, but we must tell the configure script were we put libTIFF.
- <code>./configure --prefix=$PREFIX --with-libtiff=$PREFIX
- make
- make install</code>
-If you are compiling in Proj.4 support it may be necessary to tell GeoTIFF where that library is installed.  You can do this by adding the flag <tt>--with-proj=$PREFIX</tt>.
- <code>./configure --prefix=$PREFIX --with-libtiff=$PREFIX --with-proj=$PREFIX
- make
- make install</code>
-After doing this, the configuration summary that prints after running configure will have a line saying <tt>PROJ support......: yes</tt>.
-=Obtaining the WPSGeoTiff source=
-The autoWPS package is available as a git repository hosted at [http://github.com/jbeezley/autoWPS github].  The repository can be cloned with the
-[http://git-scm.com/ git] command:
- <code>git clone git://github.com/jbeezley/autoWPS.git</code>
-A tarball of the latest release can also be obtained
-at [http://github.com/jbeezley/autoWPS/tarball/master http://github.com/jbeezley/autoWPS/tarball/master].
-=Compiling WPSGeoTiff=
-Inside the main directory of the autoWPS release is a subdirectory called WPSGeoTiff.  This utility is written in pure c and creates a standalone binary.
-In most cases it can be compiled by issuing the following command.
- <code>LIBTIFF=$PREFIX GEOTIFF=$PREFIX make</code>
-The main binary <tt>convert_geotiff.x</tt>, should now reside in the current directory.
-=Running WPSGeoTiff=
-Running <tt>convert_geotiff.x</tt> with no arguments will produce a usage description.
-<code><pre>Usage: ./convert_geotiff.x [OPTIONS] FileName
-Converts geotiff file `FileName' into geogrid binary format
-into the current directory.
-Options:
--h         : Show this help message and exit
--c NUM     : Indicates categorical data (NUM = number of categories)
--b NUM     : Tile border width (default 3)
--w [1,2,4] : Word size in output in bytes (default 2)
--z         : Indicates unsigned data (default FALSE)
--t NUM     : Output tile size (default 100)
--s SCALE   : Scale factor in output (default 1.)
--m MISSING : Missing value in output (default 0., ignored for categorical data)
--u UNITS   : Units of the data (default "NO UNITS")
--d DESC    : Description of data set (default "NO DESCRIPTION")
-</pre></code>
-All of the files will be created in the current directory, so it is best to run the program from an empty directory.  A more detailed description of the
-arguments to this program follows.
-*; <tt>-b</tt>
-:<p>The data tiles in the geogrid binary format are allowed to overlap by a fixed number of grid points.  The extra border around the tile is called the halo, and this argument sets the width of the halo.  For instance with a halo of size three, the file named <tt>00101-00200.00051-00100</tt> would actually contain columns 98-203 and rows 48-103 of the full dataset.  This halo is necessary for the interpolation scheme inside of WPS.  The default should be acceptable for most situations.</p>
-*; <tt>-w</tt>
-:<p>The number of bytes to represent each data point as an integer.  These integers are scaled by the scaling parameter before being truncated to an integer. scaledA lower value will make the output data smaller, at the cost of accuracy or the dynamic range of the input.</p>
-*; <tt> -m</tt>
-:<p>Any grid point that is missing data, such as the outer border of the edge tiles, or grid points that the GeoTIFF file indicates as missing will be set to this value.  This argument is currently ignored when the categorical flag is set, instead missing data will be set to the maximum category + 1.</p>
-*;<tt>-s</tt>
-:<p>Because the data is always stored as an integer, a scaling parameter is needed to represent fractional numbers or large values.  The data set will be divided by this number prior to being truncated to an integer.  If the data set has an accuracy of 2 decimal places, a reasonable scale to use would be 0.01.</p>
-*;<tt>-u, -d</tt>
-:<p>The units and a small description of the data set should be included as arguments.  Multi-word arguments should be quoted as follows. <code><pre>-u meters -d "elevation above sea level"</pre></code></p>
-*; <tt>FileName</tt>
-:<p>The final argument must always be present.  This is the (absolute or relative) path to the GeoTIFF file to be converted.</p>
-If you get an error that says something like "<tt>error while loading shared libraries: libgeotiff.so</tt>...", this means that GeoTIFF was compiled in as a shared library.  You just need to tell the system where to find this library.  This can be done by adding the path to the GeoTIFF library to the environment variable <tt>LD_LIBRARY_PATH</tt>.  For example,
-<code>export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PREFIX}/lib</code>
-where $PREFIX is the location where you installed GeoTIFF.
-=Limitations=
-The current code has several limitations which are listed here.
-* Datasets must not contain more than 99,999 grid points in each axis.  This is a limitation of the geogrid format itself, due to the naming convention of the tiles.  However, it is possible (but inefficient) to split a single dataset into multiple directories for this purpose.  A better solution would be to resample the data to a lower spatial resolution prior to converting.
-* This program cannot convert between geographic projections, so the input data must be in a projection supported by WPS.  All of the projections [http://www.mmm.ucar.edu/wrf/users/docs/user_guide_V3.1/users_guide_chap3.htm#_Description_of_index supported by WPS] should work for this conversion program; however, only UTM, Albers equal area, and lat-lon have been tested.  In addition, data sources may not conform to [http://www.spatialreference.org/ EPSG standards] in their projection tags; the output should always be checked before use.
 [[Category:WRF-Fire]]
 [[Category:Howtos|Convert data for Geogrid]]
 [[Category:Data]]

Difference between revisions of "How to convert data for Geogrid"

Revision as of 14:14, 9 October 2013

Navigation menu

Search