root/MGET/Branches/Jason/PythonPackage/dist/TracOnlineDocumentation/Documentation/ArcGISReference/BinaryRaster.ToArcInfoASCIIGridArcGISTable.html @ 842

Revision 842, 26.7 KB (checked in by jjr8, 19 months ago)

Rebuilt installation packages again. This will be merged with the Trunk and released as MGET 0.8a28.
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml"><head><link rel="stylesheet" type="text/css" href="81help.css?format=raw" /><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Convert Binary Rasters Listed in Table To ArcInfo ASCII Grids</title></head><body><table style="margin-top:-1em; margin-bottom:0; padding:0; margin-left:-1em"><tr><td style="background:white"><img width="875" height="70" alt="ArcToolbox banner" src="AHBanner_ArcToolbox.gif?format=raw" /></td></tr></table><h1>Convert Binary Rasters Listed in Table To ArcInfo ASCII Grids</h1><p></p><p>Converts each two-dimensional binary raster in a table to a text file in ArcInfo ASCII Grid format.</p><br /><p><h2><img width="11" height="11" border="0" src="sm_arrow_down.gif?format=raw" /> Command line syntax</h2></p><div Class="expand" id="id103142">BinaryRasterToArcInfoASCIIGridArcGISTable_GeoEco &lt;table&gt; &lt;inputFileField&gt; &lt;outputFileField&gt; &lt;int8 | uint8 | int16 | uint16 | int32 | uint32 | float | double&gt; &lt;columnCount&gt; &lt;rowCount&gt; &lt;xLowerLeftCorner&gt; &lt;yLowerLeftCorner&gt; &lt;cellSize&gt; {nodataValue} {offset} {swapBytes} {transpose} {mirror} {flip} {swapHemispheres} {where} {orderBy;orderBy...} {directions;directions...} {skipExisting} {basePath} <br /><br /><b>Parameters</b><br /><table width="100%" border="0" cellpadding="5"><tbody><tr><th width="40%"><b>Expression</b></th><th width="60%"><b>Explanation</b></th></tr><tr><td class="info">&lt;table&gt;</td><td class="info" align="left"><p>Table to query.</p></td></tr><tr><td class="info">&lt;inputFileField&gt;</td><td class="info" align="left"><p>Field containing the paths of the input binary rasters.</p><p>A binary raster is a file that contains a raw array of numbers stored
4in binary format, as if a snapshot of in-memory data had been written
5directly to disk. In ArcGIS, this is the type of file output by the
6Raster to Float tool, although that tool can only output binary
7rasters that use a 32-bit floating point data type. This tool can use
8any standard numeric data type.</p><p>The data must have two dimensions. By default, it is assumed that the
9data are in "row-major order", the approach used by the C programming
10language: the cells are ordered left-to-right, top-to-bottom, with
11columns increasing before rows. The upper-left cell is the first cell,
12followed by the cell to its right, and so on to the end of the first
13row. The second row comes next, and so on to the end. The lower-right
14cell is the last one. If the data are in "column-major order", the
15approach used by Fortran and MATLAB, use the Transpose option to flip
16the data about the diagonal axis.</p><p>By default, it is assumed that the data should be read starting with
17the first byte of the file. If the file contains a header of a known
18length, use the Offset parameter to skip over it.</p><p>If the file contains extra bytes that occur after the data, they will
19be ignored.</p><p>If you provide compressed files in a supported compression format,
20they will be automatically decompressed. If files are compressed in an
21archive format (e.g. .zip or .tar), each archive must contain exactly
22one file, which must not be in a subdirectory.</p></td></tr><tr><td class="info">&lt;outputFileField&gt;</td><td class="info" align="left"><p>Field containing the paths of the ArcInfo ASCII Grid files to write.</p><p>ArcInfo ASCII Grid format is not formally specified by ESRI but you
23can find informal specifications by searching the Internet. The format
24is well-known, stable and very simple. A short example:</p><dl><dt></dt><dd><pre>ncols 4
25nrows 6
26xllcorner 0
27yllcorner 0
28cellsize 50
29NODATA_value -9999
30-9999 -9999 5 2
31-9999 20 100 36
323 8 35 10
3332 42 50 6
3488 75 27 9
3513 5 1 -9999</pre></dd></dl></td></tr><tr><td class="info">&lt;int8 | uint8 | int16 | uint16 | int32 | uint32 | float | double&gt;</td><td class="info" align="left"><p>Data type of the binary raster.</p><p>This may be one of the following values:</p><ul><li><p>int8 - 8-bit signed integer, range -128 to 127</p></li></ul><ul><li><p>uint8 - 8-bit unsigned integer, range 0 to 255</p></li></ul><ul><li><p>int16 - 16-bit signed integer, range -32768 to 32767</p></li></ul><ul><li><p>uint16 - 16-bit unsigned integer, range 0 to 65535</p></li></ul><ul><li><p>int32 - 32-bit signed integer, range -2147483648 to 2147483647</p></li></ul><ul><li><p>uint32 - 32-bit unsigned integer, range 0 to 4294967295</p></li></ul><ul><li><p>float - 32-bit single-precision floating point</p></li></ul><ul><li><p>double - 64-bit double-precision floating point</p></li></ul><p>Binary rasters with other data types cannot be converted because the
36ArcInfo ASCII Grid format does not support them.</p><p>The exact format, precision and range of the floating types depend on the
37processor architecture of your computer. Most processors implement the IEEE
38Standard for Binary Floating-Point Arithmetic (IEEE 754).</p><p>Binary rasters that use the float or double data type must not contain
39"infinity" (INF) or "not a number" (NAN) values. A ValueError will be raised if
40these values are discovered.</p><p>The ArcGIS raster format supports the 32-bit float data type but not the 64-bit
41double data type. You may still run the ArcGIS ASCII to Raster geoprocessing
42tool to convert ASCII files created from double-precision binary rasters. The
43tool's behavior in this situation is not documented. In ArcGIS 9.1 it appears to
44be:</p><ul><li><p>Values where the exponent ranges from -38 to +38 are properly represented in
45the resulting 32-bit float raster.</p></li></ul><ul><li><p>Values where the exponent is less than -38 (e.g. -39, -40, and so on) are
46converted to 0.</p></li></ul><ul><li><p>Values where the exponent is greater than +38 are converted to -INF or +INF,
47depending on the sign of the value (e.g. -5.3083635279597874e-212 appears as
48-1.#INF in the ArcCatalog GUI, while 2.5502286890301497e+084 appears as
491.#INF).</p></li></ul><p>The ArcGIS 9.1 ASCII to Raster tool also exhibits some quirks when converting
50integer rasters:</p><ul><li><p>For an ASCII file created from an int8 binary file, the tool will create an
51int16 raster if the value -128 appears in the ASCII file, unless -128 is
52designated the NODATA value. Specifying a different NODATA value, such as 0,
53still yields an int16 raster if -128 appears.</p></li></ul><ul><li><p>Similarly, for an ASCII file created from an int16 binary file, the tool will
54create an int32 raster if the value -32768 appears in the ASCII file, unless
55it is designated the NODATA value.</p></li></ul><ul><li><p>Worse, for an ASCII file created from an int32 binary file, the tool will
56report an error if the value -2147483648 appears in the ASCII file unless it
57is designated the NODATA value. Even stranger, the value -2147483647 is
58always translated to NODATA, no matter what.</p></li></ul><ul><li><p>For all types of integer rasters, the tool produces strange behavior when you
59specify a NODATA value that is not the smallest possible value for the data
60type. For example, if the ASCII file contains values from 0 to 255 and 0 is
61designated the NODATA value, the tool produces a uint8 output raster. But if
621 is designated the NODATA value, it produces an int16 output raster, and
63ArcCatalog shows under Raster Dataset Properties that the NoData Value is
64-32768, although the Identify tool shows cells that had value 1 are actually
65NODATA. Similar strange results can be obtained for integer rasters of other
66data types, when you designate a NODATA that is not the smallest possible
67value.</p></li></ul></td></tr><tr><td class="info">&lt;columnCount&gt;</td><td class="info" align="left"><p>Number of columns in the binary raster.</p></td></tr><tr><td class="info">&lt;rowCount&gt;</td><td class="info" align="left"><p>Number of rows in the binary raster.</p></td></tr><tr><td class="info">&lt;xLowerLeftCorner&gt;</td><td class="info" align="left"><p>X coordinate of the lower-left corner of the raster.</p><p>The coordinate is for the corner of the lower-left cell, not the center of that
68cell. For example, if the raster is a geographic projection of the entire Earth,
69the coordinate of the lower left corner would be -180.0, corresponding to a
70longitude of 180 degrees West.</p></td></tr><tr><td class="info">&lt;yLowerLeftCorner&gt;</td><td class="info" align="left"><p>Y coordinate of the lower-left corner of the raster.</p><p>The coordinate is for the corner of the lower-left cell, not the center of that
71cell. For example, if the raster is a geographic projection of the entire Earth,
72the coordinate of the lower left corner would be -90.0, corresponding to a
73latitude of 90 degrees South.</p></td></tr><tr><td class="info">&lt;cellSize&gt;</td><td class="info" align="left"><p>Size of each raster cell.</p><p>For example, if the raster is a geographic projection of the entire Earth, with
74720 columns and 360 rows, it would have a cell size of 0.5, corresponding to
751/2 of a geographic degree.</p><p>The underlying data format requires the cells be square. It is not possible to
76specify a cell size for each dimension.</p></td></tr><tr><td class="info">{nodataValue}</td><td class="info" align="left"><p>Value that indicates a cell has no data.</p></td></tr><tr><td class="info">{offset}</td><td class="info" align="left"><p>Number of bytes of the file to skip before reading the data.</p><p>This option is useful for skipping a headers or other metadata that
77occur before the data. For example, if the file contains a 512 byte
78header, set this parameter to 512 to skip over the header. If this
79parameter is not specified, the data will be read starting at the
80first byte of the file.</p></td></tr><tr><td class="info">{swapBytes}</td><td class="info" align="left"><p>If True, the byte ordering of the binary raster will be reversed
81prior to conversion.</p><p>This option is ignored if the raster data type is int8 or uint8.</p><p>This option is useful if the input file was produced on computer with a
82processor architecture that uses a different byte ordering than your computer.
83For example, if you are running on an Intel x86 processor, which uses "little
84endian" byte ordering, you might use this option to process data produced by a
85Sun SPARC processor, which uses "big endian" byte ordering.</p></td></tr><tr><td class="info">{transpose}</td><td class="info" align="left"><p>If True, the image will be transposed (flipped about the diagonal
86axis) prior to conversion. Use this option to fix an image that has
87the east/west axis going up and down instead of left and right.</p></td></tr><tr><td class="info">{mirror}</td><td class="info" align="left"><p>If True, the image will be flipped about the vertical axis prior
88to conversion. Use this option to fix an image that is the "mirror
89image" of what it is supposed to be.</p></td></tr><tr><td class="info">{flip}</td><td class="info" align="left"><p>If True, the image will be flipped about the horizontal axis prior
90to conversion. Use this option to fix an image that is
91upside-down.</p></td></tr><tr><td class="info">{swapHemispheres}</td><td class="info" align="left"><p>If True, the east and west hemispheres of the image will be
92swapped. Use this option to change the orientation of a global image
93from a 0 to 360 orientation centered on the Pacific ocean to a -180 to
94+180 orientation centered on the Atlantic ocean, or visa versa.</p></td></tr><tr><td class="info">{where}</td><td class="info" align="left"><p>SQL WHERE clause expression that specifies the subset of rows to
95process. If this parameter is not provided, all of the rows will be
96processed. If this parameter is provided but the underlying database
97does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying
98database. ESRI recommends you reference fields using the following
99syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or
100dBASE tables (.dbf files), enclose field names in double quotes in
101the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal
102geodatabase tables, enclose field names in square brackets:
103[MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
104class, or an ArcIMS image service sublayer, don't enclose field
105names: MY_FIELD.</p></li></ul></td></tr><tr><td class="info">{orderBy;orderBy...}</td><td class="info" align="left"><p>Fields that will be used to sort the rows (i.e., the columns
106specified in the ORDER BY clause of a SQL SELECT statement). If no
107fields are provided, the rows will be sorted in the default order
108determined by the underlying database. If this parameter is provided
109but this computer is not running ArcGIS 9.2 or later or the underlying
110database does not support ORDER BY clauses, an error will be raised.</p><p>In addition to specifying the ORDER BY fields, you must also specify
111the sort direction for each field.</p></td></tr><tr><td class="info">{directions;directions...}</td><td class="info" align="left"><p>List of strings, either 'Ascending' or 'Descending', that specify
112the sort directions for the ORDER BY fields. If this parameter is
113provided but this computer is not running ArcGIS 9.2 or later or the
114underlying database does not support ORDER BY clauses, an error will
115be raised.</p></td></tr><tr><td class="info">{skipExisting}</td><td class="info" align="left"><p>If True, processing will be skipped for output files that already exist.</p></td></tr><tr><td class="info">{basePath}</td><td class="info" align="left"><p>Base path to prepend to relative paths.</p><p>If a base path is provided, it will be prepended to any relative paths
116that are obtained from the fields that list the inputs (and outputs,
117if this tool has outputs). If a base path is not provided, the
118workspace containing the table will be prepended instead.</p></td></tr></tbody></table></div><p><h2><img width="11" height="11" border="0" src="sm_arrow_down.gif?format=raw" /> Scripting syntax</h2></p><div Class="expand" id="TEST">BinaryRasterToArcInfoASCIIGridArcGISTable_GeoEco (table, inputFileField, outputFileField, dataType, columnCount, rowCount, xLowerLeftCorner, yLowerLeftCorner, cellSize, nodataValue, offset, swapBytes, transpose, mirror, flip, swapHemispheres, where, orderBy, directions, skipExisting, basePath) <br /><br /><b>Parameters</b><br /><table width="100%" border="0" cellpadding="5"><tbody><tr><th width="40%"><b>Expression</b></th><th width="60%"><b>Explanation</b></th></tr><tr><td class="info">Table (Required) </td><td class="info" align="left"><p>Table to query.</p></td></tr><tr><td class="info">Input binary raster field (Required) </td><td class="info" align="left"><p>Field containing the paths of the input binary rasters.</p><p>A binary raster is a file that contains a raw array of numbers stored
119in binary format, as if a snapshot of in-memory data had been written
120directly to disk. In ArcGIS, this is the type of file output by the
121Raster to Float tool, although that tool can only output binary
122rasters that use a 32-bit floating point data type. This tool can use
123any standard numeric data type.</p><p>The data must have two dimensions. By default, it is assumed that the
124data are in "row-major order", the approach used by the C programming
125language: the cells are ordered left-to-right, top-to-bottom, with
126columns increasing before rows. The upper-left cell is the first cell,
127followed by the cell to its right, and so on to the end of the first
128row. The second row comes next, and so on to the end. The lower-right
129cell is the last one. If the data are in "column-major order", the
130approach used by Fortran and MATLAB, use the Transpose option to flip
131the data about the diagonal axis.</p><p>By default, it is assumed that the data should be read starting with
132the first byte of the file. If the file contains a header of a known
133length, use the Offset parameter to skip over it.</p><p>If the file contains extra bytes that occur after the data, they will
134be ignored.</p><p>If you provide compressed files in a supported compression format,
135they will be automatically decompressed. If files are compressed in an
136archive format (e.g. .zip or .tar), each archive must contain exactly
137one file, which must not be in a subdirectory.</p></td></tr><tr><td class="info">Output ArcInfo ASCII Grid file field (Required) </td><td class="info" align="left"><p>Field containing the paths of the ArcInfo ASCII Grid files to write.</p><p>ArcInfo ASCII Grid format is not formally specified by ESRI but you
138can find informal specifications by searching the Internet. The format
139is well-known, stable and very simple. A short example:</p><dl><dt></dt><dd><pre>ncols 4
140nrows 6
141xllcorner 0
142yllcorner 0
143cellsize 50
144NODATA_value -9999
145-9999 -9999 5 2
146-9999 20 100 36
1473 8 35 10
14832 42 50 6
14988 75 27 9
15013 5 1 -9999</pre></dd></dl></td></tr><tr><td class="info">Data type (Required) </td><td class="info" align="left"><p>Data type of the binary raster.</p><p>This may be one of the following values:</p><ul><li><p>int8 - 8-bit signed integer, range -128 to 127</p></li></ul><ul><li><p>uint8 - 8-bit unsigned integer, range 0 to 255</p></li></ul><ul><li><p>int16 - 16-bit signed integer, range -32768 to 32767</p></li></ul><ul><li><p>uint16 - 16-bit unsigned integer, range 0 to 65535</p></li></ul><ul><li><p>int32 - 32-bit signed integer, range -2147483648 to 2147483647</p></li></ul><ul><li><p>uint32 - 32-bit unsigned integer, range 0 to 4294967295</p></li></ul><ul><li><p>float - 32-bit single-precision floating point</p></li></ul><ul><li><p>double - 64-bit double-precision floating point</p></li></ul><p>Binary rasters with other data types cannot be converted because the
151ArcInfo ASCII Grid format does not support them.</p><p>The exact format, precision and range of the floating types depend on the
152processor architecture of your computer. Most processors implement the IEEE
153Standard for Binary Floating-Point Arithmetic (IEEE 754).</p><p>Binary rasters that use the float or double data type must not contain
154"infinity" (INF) or "not a number" (NAN) values. A ValueError will be raised if
155these values are discovered.</p><p>The ArcGIS raster format supports the 32-bit float data type but not the 64-bit
156double data type. You may still run the ArcGIS ASCII to Raster geoprocessing
157tool to convert ASCII files created from double-precision binary rasters. The
158tool's behavior in this situation is not documented. In ArcGIS 9.1 it appears to
159be:</p><ul><li><p>Values where the exponent ranges from -38 to +38 are properly represented in
160the resulting 32-bit float raster.</p></li></ul><ul><li><p>Values where the exponent is less than -38 (e.g. -39, -40, and so on) are
161converted to 0.</p></li></ul><ul><li><p>Values where the exponent is greater than +38 are converted to -INF or +INF,
162depending on the sign of the value (e.g. -5.3083635279597874e-212 appears as
163-1.#INF in the ArcCatalog GUI, while 2.5502286890301497e+084 appears as
1641.#INF).</p></li></ul><p>The ArcGIS 9.1 ASCII to Raster tool also exhibits some quirks when converting
165integer rasters:</p><ul><li><p>For an ASCII file created from an int8 binary file, the tool will create an
166int16 raster if the value -128 appears in the ASCII file, unless -128 is
167designated the NODATA value. Specifying a different NODATA value, such as 0,
168still yields an int16 raster if -128 appears.</p></li></ul><ul><li><p>Similarly, for an ASCII file created from an int16 binary file, the tool will
169create an int32 raster if the value -32768 appears in the ASCII file, unless
170it is designated the NODATA value.</p></li></ul><ul><li><p>Worse, for an ASCII file created from an int32 binary file, the tool will
171report an error if the value -2147483648 appears in the ASCII file unless it
172is designated the NODATA value. Even stranger, the value -2147483647 is
173always translated to NODATA, no matter what.</p></li></ul><ul><li><p>For all types of integer rasters, the tool produces strange behavior when you
174specify a NODATA value that is not the smallest possible value for the data
175type. For example, if the ASCII file contains values from 0 to 255 and 0 is
176designated the NODATA value, the tool produces a uint8 output raster. But if
1771 is designated the NODATA value, it produces an int16 output raster, and
178ArcCatalog shows under Raster Dataset Properties that the NoData Value is
179-32768, although the Identify tool shows cells that had value 1 are actually
180NODATA. Similar strange results can be obtained for integer rasters of other
181data types, when you designate a NODATA that is not the smallest possible
182value.</p></li></ul></td></tr><tr><td class="info">Columns (Required) </td><td class="info" align="left"><p>Number of columns in the binary raster.</p></td></tr><tr><td class="info">Rows (Required) </td><td class="info" align="left"><p>Number of rows in the binary raster.</p></td></tr><tr><td class="info">X coordinate of lower-left corner (Required) </td><td class="info" align="left"><p>X coordinate of the lower-left corner of the raster.</p><p>The coordinate is for the corner of the lower-left cell, not the center of that
183cell. For example, if the raster is a geographic projection of the entire Earth,
184the coordinate of the lower left corner would be -180.0, corresponding to a
185longitude of 180 degrees West.</p></td></tr><tr><td class="info">Y coordinate of lower-left corner (Required) </td><td class="info" align="left"><p>Y coordinate of the lower-left corner of the raster.</p><p>The coordinate is for the corner of the lower-left cell, not the center of that
186cell. For example, if the raster is a geographic projection of the entire Earth,
187the coordinate of the lower left corner would be -90.0, corresponding to a
188latitude of 90 degrees South.</p></td></tr><tr><td class="info">Cell size (Required) </td><td class="info" align="left"><p>Size of each raster cell.</p><p>For example, if the raster is a geographic projection of the entire Earth, with
189720 columns and 360 rows, it would have a cell size of 0.5, corresponding to
1901/2 of a geographic degree.</p><p>The underlying data format requires the cells be square. It is not possible to
191specify a cell size for each dimension.</p></td></tr><tr><td class="info">NODATA value (Optional) </td><td class="info" align="left"><p>Value that indicates a cell has no data.</p></td></tr><tr><td class="info">Offset (Optional) </td><td class="info" align="left"><p>Number of bytes of the file to skip before reading the data.</p><p>This option is useful for skipping a headers or other metadata that
192occur before the data. For example, if the file contains a 512 byte
193header, set this parameter to 512 to skip over the header. If this
194parameter is not specified, the data will be read starting at the
195first byte of the file.</p></td></tr><tr><td class="info">Swap bytes (Optional) </td><td class="info" align="left"><p>If True, the byte ordering of the binary raster will be reversed
196prior to conversion.</p><p>This option is ignored if the raster data type is int8 or uint8.</p><p>This option is useful if the input file was produced on computer with a
197processor architecture that uses a different byte ordering than your computer.
198For example, if you are running on an Intel x86 processor, which uses "little
199endian" byte ordering, you might use this option to process data produced by a
200Sun SPARC processor, which uses "big endian" byte ordering.</p></td></tr><tr><td class="info">Transpose (Optional) </td><td class="info" align="left"><p>If True, the image will be transposed (flipped about the diagonal
201axis) prior to conversion. Use this option to fix an image that has
202the east/west axis going up and down instead of left and right.</p></td></tr><tr><td class="info">Mirror (Optional) </td><td class="info" align="left"><p>If True, the image will be flipped about the vertical axis prior
203to conversion. Use this option to fix an image that is the "mirror
204image" of what it is supposed to be.</p></td></tr><tr><td class="info">Flip (Optional) </td><td class="info" align="left"><p>If True, the image will be flipped about the horizontal axis prior
205to conversion. Use this option to fix an image that is
206upside-down.</p></td></tr><tr><td class="info">Swap hemispheres (Optional) </td><td class="info" align="left"><p>If True, the east and west hemispheres of the image will be
207swapped. Use this option to change the orientation of a global image
208from a 0 to 360 orientation centered on the Pacific ocean to a -180 to
209+180 orientation centered on the Atlantic ocean, or visa versa.</p></td></tr><tr><td class="info">Where clause (Optional) </td><td class="info" align="left"><p>SQL WHERE clause expression that specifies the subset of rows to
210process. If this parameter is not provided, all of the rows will be
211processed. If this parameter is provided but the underlying database
212does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying
213database. ESRI recommends you reference fields using the following
214syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or
215dBASE tables (.dbf files), enclose field names in double quotes in
216the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal
217geodatabase tables, enclose field names in square brackets:
218[MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
219class, or an ArcIMS image service sublayer, don't enclose field
220names: MY_FIELD.</p></li></ul></td></tr><tr><td class="info">Order By fields (Optional) </td><td class="info" align="left"><p>Fields that will be used to sort the rows (i.e., the columns
221specified in the ORDER BY clause of a SQL SELECT statement). If no
222fields are provided, the rows will be sorted in the default order
223determined by the underlying database. If this parameter is provided
224but this computer is not running ArcGIS 9.2 or later or the underlying
225database does not support ORDER BY clauses, an error will be raised.</p><p>In addition to specifying the ORDER BY fields, you must also specify
226the sort direction for each field.</p></td></tr><tr><td class="info">Order By directions (Optional) </td><td class="info" align="left"><p>List of strings, either 'Ascending' or 'Descending', that specify
227the sort directions for the ORDER BY fields. If this parameter is
228provided but this computer is not running ArcGIS 9.2 or later or the
229underlying database does not support ORDER BY clauses, an error will
230be raised.</p></td></tr><tr><td class="info">Skip existing outputs (Optional) </td><td class="info" align="left"><p>If True, processing will be skipped for output files that already exist.</p></td></tr><tr><td class="info">Base path (Optional) </td><td class="info" align="left"><p>Base path to prepend to relative paths.</p><p>If a base path is provided, it will be prepended to any relative paths
231that are obtained from the fields that list the inputs (and outputs,
232if this tool has outputs). If a base path is not provided, the
233workspace containing the table will be prepended instead.</p></td></tr></tbody></table></div></body></html>
Note: See TracBrowser for help on using the browser.