root/MGET/Branches/Jason/PythonPackage/dist/TracOnlineDocumentation/Documentation/ArcGISReference/SIRFile.ToArcGISRasterArcGISTable.html @ 842

Revision 842, 27.6 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 SIR Files Listed in Table To ArcGIS Rasters</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 SIR Files Listed in Table To ArcGIS Rasters</h1><p></p><p>Converts each SIR file in a table to an ArcGIS raster.</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="id103139">SIRFileToArcGISRasterArcGISTable_GeoEco &lt;table&gt; &lt;sirFileField&gt; &lt;outputRasterField&gt; {projectedCoordinateSystem} {geographicTransformation} {NEAREST | BILINEAR | CUBIC} {projectedCellSize} {registrationPoint} {clippingRectangle} {mapAlgebraExpression} {buildPyramids} {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;sirFileField&gt;</td><td class="info" align="left"><p>Field containing the paths of SIR files.</p><p>The SIR format was designed by the Brigham Young University MERS lab.
4MERS publishes various products derived from scatterometers bourne by
5satellites such as QuikSCAT. These products include sea surface wind
6vectors, sea ice masks, and raw scatterometer sigma-0 values, which
7correlate with the roughness of the ocean surface.</p><p>Compressed files in a supported compression format will be
8automatically decompressed. Archives (e.g. .zip or .tar) must contain
9exactly one file, which must not be in a subdirectory.</p></td></tr><tr><td class="info">&lt;outputRasterField&gt;</td><td class="info" align="left"><p>Field containing the output rasters to create.</p></td></tr><tr><td class="info">{projectedCoordinateSystem}</td><td class="info" align="left"><p>New coordinate system to project the output raster to.</p><p>The raster may only be projected to a new coordinate system if the
10original projection is defined. An error will be raised if you specify
11a new coordinate system without defining the original coordinate
12system.</p><p>The ArcGIS Project Raster tool is used to perform the projection. The
13documentation for that tool recommends that you also specify a cell
14size for the new coordinate system.</p><p>I have noticed that for certain coordinate systems the ArcGIS 9.2
15Project Raster tool seems to clip the projected raster to an arbitrary
16extent that is too small. For example, when projecting a global MODIS
17Aqua 4 km chlorophyll image in geographic coordinates to
18Lambert_Azimuthal_Equal_Area with central meridian of -60 and latitude
19of origin of -63, the resulting image is clipped to show only
20one-quarter of the planet. This problem does not occur when Project
21Raster is invoked interactively from the ArcGIS user interface; it
22only occurs when the tool is invoked programmatically (the
23ProjectRaster_management method of the geoprocessor). Thus you may
24not see it when you use Project Raster yourself but it may happen when
25you use MGET tools that invoke Project Raster as part of their
26geoprocessing operations.</p><p>If you encounter this problem, you can work around it like this:</p><ul><li><p>First, run this tool without specifying a new coordinate system, to
27obtain the output raster in the original coordinate system.</p></li></ul><ul><li><p>In ArcCatalog, use the Project Raster tool to project the raster to
28the new coordinate system. Verify that the entire raster is present,
29that it has not been clipped to an extent that is too small.</p></li></ul><ul><li><p>In ArcCatalog, look up the extent of the projected raster by
30right-clicking on it in the catalog tree, selecting Properties, and
31scrolling down to Extent.</p></li></ul><ul><li><p>Now, before running the MGET tool that projects the raster, set the
32Extent environment setting to the values you looked up. If you are
33invoking the MGET tool interactively from ArcCatalog or ArcMap,
34click the Environments button on the tool's dialog box, open General
35Settings, change the Extent drop-down to "As Specified Below", and
36type in the values you looked up. If you're invoking it from a
37geoprocessing model, right-click on the tool in the model, select
38Make Variable, From Environment, General Settings, Extent. This will
39place Extent as a variable in your model, attached to the MGET tool.
40Open the Extent variable, change it to "As Specified Below" and type
41in the values you looked up. If you're invoking the MGET tool
42programmatically, you must set the Extent property of the
43geoprocessor to the values you looked up. Please see the ArcGIS
44documentation for more information about this and Environment
45settings in general.</p></li></ul><ul><li><p>Run the MGET tool. The extent of the output raster should now be the
46proper size.</p></li></ul></td></tr><tr><td class="info">{geographicTransformation}</td><td class="info" align="left"><p>A transformation method used to convert between the original
47coordinate system and the new coordinate system.</p><p>This parameter is a new option introduced by ArcGIS 9.2. You must have
48ArcGIS 9.2 to use this parameter.</p><p>This parameter is only needed when you specify that the raster should
49be projected to a new coordinate system and that new system uses a
50different datum than the original coordinate system, or there is some
51other difference between the two coordinate systems that requires a
52transformation. To determine if a transformation is needed, I
53recommend the following procedure:</p><ul><li><p>First, run this tool without specifying a new coordinate system, to
54obtain the output raster in the original coordinate system.</p></li></ul><ul><li><p>Next, use the ArcGIS 9.2 Project Raster tool on the output raster to
55project it to the desired coordinate system. If a geographic
56transformation is needed, that tool will prompt you for one. Write
57down the exact name of the transformation you used.</p></li></ul><ul><li><p>Finally, if a transformation was needed, type in the exact name into
58this tool, rerun it, and verify that the output raster was projected
59as you desired.</p></li></ul></td></tr><tr><td class="info">{NEAREST | BILINEAR | CUBIC}</td><td class="info" align="left"><p>The resampling algorithm to be used to project the original raster
60to a new coordinate system. The ArcGIS Project Raster tool is used to
61perform the projection and accepts the following values:</p><ul><li><p>NEAREST - nearest neighbor interpolation</p></li></ul><ul><li><p>BILINEAR - bilinear interpolation</p></li></ul><ul><li><p>CUBIC - cubic convolution</p></li></ul><p>You must specify one of these algorithms to project to a new
62coordinate system. An error will be raised if you specify a new
63coordinate system without selecting an algorithm.</p></td></tr><tr><td class="info">{projectedCellSize}</td><td class="info" align="left"><p>The cell size of the projected coordinate system. Although this
64parameter is optional, to receive the best results, the ArcGIS
65documentation recommends you always specify it when projecting to a
66new coordinate system.</p></td></tr><tr><td class="info">{registrationPoint}</td><td class="info" align="left"><p>The x and y coordinates (in the output space) used for pixel
67alignment.</p><p>This parameter is a new option introduced by ArcGIS 9.2. You must have
68ArcGIS 9.2 to use this parameter. It is ignored if you do not specify
69that the raster should be projected to a new coordinate system.</p></td></tr><tr><td class="info">{clippingRectangle}</td><td class="info" align="left"><p>Rectangle to which the raster should be clipped.</p><p>If a projected coordinate system was specified, the clipping is
70performed after the projection and the rectangle's coordinates should
71be specified in the new coordinate system. If no projected coordinate
72system was specified, the coordinates should be specified in the
73original coordinate system.</p><p>The ArcGIS Clip tool is used to perfom the clip. The clipping
74rectangle must be passed to this tool as a string of four numbers
75separated by spaces. The ArcGIS user interface automatically formats
76the string properly; when invoking this tool from the ArcGIS UI,
77you need not worry about the format. But when invoking it
78programmatically, take care to provide a properly-formatted string.
79The numbers are ordered LEFT, BOTTOM, RIGHT, TOP. For example, if the
80raster is in a geographic coordinate system, it may be clipped to 10
81W, 15 S, 20 E, and 25 N with the string:</p><dl><dt></dt><dd><p>10 15 20 25</p></dd></dl><p>Integers or decimal numbers may be provided.</p></td></tr><tr><td class="info">{mapAlgebraExpression}</td><td class="info" align="left"><p>Map algebra expression to execute on the output raster.</p><p><b>WARNING:</b> The ArcGIS Geoprocessing Model Builder may randomly and
82silently delete the value of this parameter. This is a bug in ArcGIS.
83Before running a model that you have saved, open this tool and
84validate that the parameter value still exists.</p><p>The expression is executed after the converted raster is projected and
85clipped (if those options are specified). Use the case-sensitive
86string inputRaster to represent the raster that you now want to
87perform map algebra upon. For example, to convert the raster to an
88integer raster and add 1 to all of the cells, use this expression:</p><dl><dt></dt><dd><pre>int(inputRaster) + 1</pre></dd></dl><p>The string inputRaster is case-sensitive. Prior to executing the map
89algebra expression, the string is replaced with the path to a
90temporary raster that represents the output raster being generated.
91The final expression must be less than 4000 characters long or ArcGIS
92will report an error.</p><p>The ArcGIS Single Output Map Algebra tool is used to execute the map
93algebra expression. You must have a license for the ArcGIS Spatial
94Analyst extension in order to perform map algebra.</p><p>Map algebra syntax can be very picky. Here are some tips that will
95help you succeed with this tool:</p><ul><li><p>Before using this tool, construct and test out your map algebra
96expression using the ArcGIS Single Output Map Algebra tool. Then
97paste the expression into this tool and edit it to use the
98inputRaster variable rather than the test value you used with Single
99Output Map Algebra.</p></li></ul><ul><li><p>If you do develop your expression directly in this tool, start with
100a very simple expression. Verify that it works properly, add a
101little to it, and verify again. Repeat this process until you have
102built up the complete expression.</p></li></ul><ul><li><p>Always separate mathematical operators from raster paths using
103spaces. In the example above, the / operator contains a space on
104either side. Follow this pattern. In some circumstances, ArcGIS will
105fail to process raster algebra expressions that do not separate
106raster paths from operators using spaces. The reported error message
107usually does not indicate that this is the problem, and tracking it
108down can be very frustrating.</p></li></ul></td></tr><tr><td class="info">{buildPyramids}</td><td class="info" align="left"><p>If True, pyramids will be built for the output raster, which will
109improve its display speed in the ArcGIS user interface. This is the
110last step performed in post-conversion processing.</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
111process. If this parameter is not provided, all of the rows will be
112processed. If this parameter is provided but the underlying database
113does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying
114database. ESRI recommends you reference fields using the following
115syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or
116dBASE tables (.dbf files), enclose field names in double quotes in
117the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal
118geodatabase tables, enclose field names in square brackets:
119[MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
120class, or an ArcIMS image service sublayer, don't enclose field
121names: 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
122specified in the ORDER BY clause of a SQL SELECT statement). If no
123fields are provided, the rows will be sorted in the default order
124determined by the underlying database. If this parameter is provided
125but this computer is not running ArcGIS 9.2 or later or the underlying
126database 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
127the 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
128the sort directions for the ORDER BY fields. If this parameter is
129provided but this computer is not running ArcGIS 9.2 or later or the
130underlying database does not support ORDER BY clauses, an error will
131be raised.</p></td></tr><tr><td class="info">{skipExisting}</td><td class="info" align="left"><p>If True, conversion will be skipped for output rasters 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
132that are obtained from the fields that list the inputs (and outputs,
133if this tool has outputs). If a base path is not provided, the
134workspace 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">SIRFileToArcGISRasterArcGISTable_GeoEco (table, sirFileField, outputRasterField, projectedCoordinateSystem, geographicTransformation, resamplingTechnique, projectedCellSize, registrationPoint, clippingRectangle, mapAlgebraExpression, buildPyramids, 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">SIR file field (Required) </td><td class="info" align="left"><p>Field containing the paths of SIR files.</p><p>The SIR format was designed by the Brigham Young University MERS lab.
135MERS publishes various products derived from scatterometers bourne by
136satellites such as QuikSCAT. These products include sea surface wind
137vectors, sea ice masks, and raw scatterometer sigma-0 values, which
138correlate with the roughness of the ocean surface.</p><p>Compressed files in a supported compression format will be
139automatically decompressed. Archives (e.g. .zip or .tar) must contain
140exactly one file, which must not be in a subdirectory.</p></td></tr><tr><td class="info">Output ArcGIS raster field (Required) </td><td class="info" align="left"><p>Field containing the output rasters to create.</p></td></tr><tr><td class="info">Project to new coordinate system (Optional) </td><td class="info" align="left"><p>New coordinate system to project the output raster to.</p><p>The raster may only be projected to a new coordinate system if the
141original projection is defined. An error will be raised if you specify
142a new coordinate system without defining the original coordinate
143system.</p><p>The ArcGIS Project Raster tool is used to perform the projection. The
144documentation for that tool recommends that you also specify a cell
145size for the new coordinate system.</p><p>I have noticed that for certain coordinate systems the ArcGIS 9.2
146Project Raster tool seems to clip the projected raster to an arbitrary
147extent that is too small. For example, when projecting a global MODIS
148Aqua 4 km chlorophyll image in geographic coordinates to
149Lambert_Azimuthal_Equal_Area with central meridian of -60 and latitude
150of origin of -63, the resulting image is clipped to show only
151one-quarter of the planet. This problem does not occur when Project
152Raster is invoked interactively from the ArcGIS user interface; it
153only occurs when the tool is invoked programmatically (the
154ProjectRaster_management method of the geoprocessor). Thus you may
155not see it when you use Project Raster yourself but it may happen when
156you use MGET tools that invoke Project Raster as part of their
157geoprocessing operations.</p><p>If you encounter this problem, you can work around it like this:</p><ul><li><p>First, run this tool without specifying a new coordinate system, to
158obtain the output raster in the original coordinate system.</p></li></ul><ul><li><p>In ArcCatalog, use the Project Raster tool to project the raster to
159the new coordinate system. Verify that the entire raster is present,
160that it has not been clipped to an extent that is too small.</p></li></ul><ul><li><p>In ArcCatalog, look up the extent of the projected raster by
161right-clicking on it in the catalog tree, selecting Properties, and
162scrolling down to Extent.</p></li></ul><ul><li><p>Now, before running the MGET tool that projects the raster, set the
163Extent environment setting to the values you looked up. If you are
164invoking the MGET tool interactively from ArcCatalog or ArcMap,
165click the Environments button on the tool's dialog box, open General
166Settings, change the Extent drop-down to "As Specified Below", and
167type in the values you looked up. If you're invoking it from a
168geoprocessing model, right-click on the tool in the model, select
169Make Variable, From Environment, General Settings, Extent. This will
170place Extent as a variable in your model, attached to the MGET tool.
171Open the Extent variable, change it to "As Specified Below" and type
172in the values you looked up. If you're invoking the MGET tool
173programmatically, you must set the Extent property of the
174geoprocessor to the values you looked up. Please see the ArcGIS
175documentation for more information about this and Environment
176settings in general.</p></li></ul><ul><li><p>Run the MGET tool. The extent of the output raster should now be the
177proper size.</p></li></ul></td></tr><tr><td class="info">Geographic transformation (Optional) </td><td class="info" align="left"><p>A transformation method used to convert between the original
178coordinate system and the new coordinate system.</p><p>This parameter is a new option introduced by ArcGIS 9.2. You must have
179ArcGIS 9.2 to use this parameter.</p><p>This parameter is only needed when you specify that the raster should
180be projected to a new coordinate system and that new system uses a
181different datum than the original coordinate system, or there is some
182other difference between the two coordinate systems that requires a
183transformation. To determine if a transformation is needed, I
184recommend the following procedure:</p><ul><li><p>First, run this tool without specifying a new coordinate system, to
185obtain the output raster in the original coordinate system.</p></li></ul><ul><li><p>Next, use the ArcGIS 9.2 Project Raster tool on the output raster to
186project it to the desired coordinate system. If a geographic
187transformation is needed, that tool will prompt you for one. Write
188down the exact name of the transformation you used.</p></li></ul><ul><li><p>Finally, if a transformation was needed, type in the exact name into
189this tool, rerun it, and verify that the output raster was projected
190as you desired.</p></li></ul></td></tr><tr><td class="info">Projection resampling technique (Optional) </td><td class="info" align="left"><p>The resampling algorithm to be used to project the original raster
191to a new coordinate system. The ArcGIS Project Raster tool is used to
192perform the projection and accepts the following values:</p><ul><li><p>NEAREST - nearest neighbor interpolation</p></li></ul><ul><li><p>BILINEAR - bilinear interpolation</p></li></ul><ul><li><p>CUBIC - cubic convolution</p></li></ul><p>You must specify one of these algorithms to project to a new
193coordinate system. An error will be raised if you specify a new
194coordinate system without selecting an algorithm.</p></td></tr><tr><td class="info">Cell size for projected coordinate system (Optional) </td><td class="info" align="left"><p>The cell size of the projected coordinate system. Although this
195parameter is optional, to receive the best results, the ArcGIS
196documentation recommends you always specify it when projecting to a
197new coordinate system.</p></td></tr><tr><td class="info">Registration point for projected coordinate system (Optional) </td><td class="info" align="left"><p>The x and y coordinates (in the output space) used for pixel
198alignment.</p><p>This parameter is a new option introduced by ArcGIS 9.2. You must have
199ArcGIS 9.2 to use this parameter. It is ignored if you do not specify
200that the raster should be projected to a new coordinate system.</p></td></tr><tr><td class="info">Clip to rectangle (Optional) </td><td class="info" align="left"><p>Rectangle to which the raster should be clipped.</p><p>If a projected coordinate system was specified, the clipping is
201performed after the projection and the rectangle's coordinates should
202be specified in the new coordinate system. If no projected coordinate
203system was specified, the coordinates should be specified in the
204original coordinate system.</p><p>The ArcGIS Clip tool is used to perfom the clip. The clipping
205rectangle must be passed to this tool as a string of four numbers
206separated by spaces. The ArcGIS user interface automatically formats
207the string properly; when invoking this tool from the ArcGIS UI,
208you need not worry about the format. But when invoking it
209programmatically, take care to provide a properly-formatted string.
210The numbers are ordered LEFT, BOTTOM, RIGHT, TOP. For example, if the
211raster is in a geographic coordinate system, it may be clipped to 10
212W, 15 S, 20 E, and 25 N with the string:</p><dl><dt></dt><dd><p>10 15 20 25</p></dd></dl><p>Integers or decimal numbers may be provided.</p></td></tr><tr><td class="info">Execute map algebra expression (Optional) </td><td class="info" align="left"><p>Map algebra expression to execute on the output raster.</p><p><b>WARNING:</b> The ArcGIS Geoprocessing Model Builder may randomly and
213silently delete the value of this parameter. This is a bug in ArcGIS.
214Before running a model that you have saved, open this tool and
215validate that the parameter value still exists.</p><p>The expression is executed after the converted raster is projected and
216clipped (if those options are specified). Use the case-sensitive
217string inputRaster to represent the raster that you now want to
218perform map algebra upon. For example, to convert the raster to an
219integer raster and add 1 to all of the cells, use this expression:</p><dl><dt></dt><dd><pre>int(inputRaster) + 1</pre></dd></dl><p>The string inputRaster is case-sensitive. Prior to executing the map
220algebra expression, the string is replaced with the path to a
221temporary raster that represents the output raster being generated.
222The final expression must be less than 4000 characters long or ArcGIS
223will report an error.</p><p>The ArcGIS Single Output Map Algebra tool is used to execute the map
224algebra expression. You must have a license for the ArcGIS Spatial
225Analyst extension in order to perform map algebra.</p><p>Map algebra syntax can be very picky. Here are some tips that will
226help you succeed with this tool:</p><ul><li><p>Before using this tool, construct and test out your map algebra
227expression using the ArcGIS Single Output Map Algebra tool. Then
228paste the expression into this tool and edit it to use the
229inputRaster variable rather than the test value you used with Single
230Output Map Algebra.</p></li></ul><ul><li><p>If you do develop your expression directly in this tool, start with
231a very simple expression. Verify that it works properly, add a
232little to it, and verify again. Repeat this process until you have
233built up the complete expression.</p></li></ul><ul><li><p>Always separate mathematical operators from raster paths using
234spaces. In the example above, the / operator contains a space on
235either side. Follow this pattern. In some circumstances, ArcGIS will
236fail to process raster algebra expressions that do not separate
237raster paths from operators using spaces. The reported error message
238usually does not indicate that this is the problem, and tracking it
239down can be very frustrating.</p></li></ul></td></tr><tr><td class="info">Build pyramids (Optional) </td><td class="info" align="left"><p>If True, pyramids will be built for the output raster, which will
240improve its display speed in the ArcGIS user interface. This is the
241last step performed in post-conversion processing.</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
242process. If this parameter is not provided, all of the rows will be
243processed. If this parameter is provided but the underlying database
244does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying
245database. ESRI recommends you reference fields using the following
246syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or
247dBASE tables (.dbf files), enclose field names in double quotes in
248the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal
249geodatabase tables, enclose field names in square brackets:
250[MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
251class, or an ArcIMS image service sublayer, don't enclose field
252names: 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
253specified in the ORDER BY clause of a SQL SELECT statement). If no
254fields are provided, the rows will be sorted in the default order
255determined by the underlying database. If this parameter is provided
256but this computer is not running ArcGIS 9.2 or later or the underlying
257database 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
258the 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
259the sort directions for the ORDER BY fields. If this parameter is
260provided but this computer is not running ArcGIS 9.2 or later or the
261underlying database does not support ORDER BY clauses, an error will
262be raised.</p></td></tr><tr><td class="info">Skip existing outputs (Optional) </td><td class="info" align="left"><p>If True, conversion will be skipped for output rasters 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
263that are obtained from the fields that list the inputs (and outputs,
264if this tool has outputs). If a base path is not provided, the
265workspace containing the table will be prepended instead.</p></td></tr></tbody></table></div></body></html>
Note: See TracBrowser for help on using the browser.