root/MGET/Branches/Jason/PythonPackage/dist/TracOnlineDocumentation/Documentation/ArcGISReference/SIRFile.ToArcInfoASCIIGridArcGISTable.html @ 376

Revision 376, 9.3 KB (checked in by jjr8, 4 years ago)

Fixed/implemented:

* #332: SIR file conversion tools should use WGS-72 datum for Lambert projections, and NSIDC's datum for polar stereographic projections
* Bugs in the previous revision related to pre-install scripts.

If this passes additional testing, it will be merged with the Trunk and released as MGET 0.7a12.
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 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 SIR Files Listed in Table To ArcInfo ASCII Grids</h1><p></p><p>Converts each SIR file 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="id103137">SIRFileToArcInfoASCIIGridArcGISTable_GeoEco &lt;table&gt; &lt;sirFileField&gt; &lt;outputFileField&gt; {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;outputFileField&gt;</td><td class="info" align="left"><p>Field containing the output ArcInfo ASCII Grid files to create.</p><p>ArcInfo ASCII Grid format is not formally specified by ESRI but you
10can find informal specifications by searching the Internet. The format
11is well-known, stable and very simple. A short example:</p><dl><dt></dt><dd><pre>ncols 4
12nrows 6
13xllcorner 0
14yllcorner 0
15cellsize 50
16NODATA_value -9999
17-9999 -9999 5 2
18-9999 20 100 36
193 8 35 10
2032 42 50 6
2188 75 27 9
2213 5 1 -9999</pre></dd></dl></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
23process. If this parameter is not provided, all of the rows will be
24processed. If this parameter is provided but the underlying database
25does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying
26database. ESRI recommends you reference fields using the following
27syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or
28dBASE tables (.dbf files), enclose field names in double quotes in
29the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal
30geodatabase tables, enclose field names in square brackets:
31[MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
32class, or an ArcIMS image service sublayer, don't enclose field
33names: 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
34specified in the ORDER BY clause of a SQL SELECT statement). If no
35fields are provided, the rows will be sorted in the default order
36determined by the underlying database. If this parameter is provided
37but this computer is not running ArcGIS 9.2 or later or the underlying
38database 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
39the 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
40the sort directions for the ORDER BY fields. If this parameter is
41provided but this computer is not running ArcGIS 9.2 or later or the
42underlying database does not support ORDER BY clauses, an error will
43be raised.</p></td></tr><tr><td class="info">{skipExisting}</td><td class="info" align="left"><p>If True, conversion 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
44that are obtained from the fields that list the inputs (and outputs,
45if this tool has outputs). If a base path is not provided, the
46workspace 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">SIRFileToArcInfoASCIIGridArcGISTable_GeoEco (table, sirFileField, outputFileField, 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.
47MERS publishes various products derived from scatterometers bourne by
48satellites such as QuikSCAT. These products include sea surface wind
49vectors, sea ice masks, and raw scatterometer sigma-0 values, which
50correlate with the roughness of the ocean surface.</p><p>Compressed files in a supported compression format will be
51automatically decompressed. Archives (e.g. .zip or .tar) must contain
52exactly one file, which must not be in a subdirectory.</p></td></tr><tr><td class="info">Output ArcInfo ASCII grid field (Required) </td><td class="info" align="left"><p>Field containing the output ArcInfo ASCII Grid files to create.</p><p>ArcInfo ASCII Grid format is not formally specified by ESRI but you
53can find informal specifications by searching the Internet. The format
54is well-known, stable and very simple. A short example:</p><dl><dt></dt><dd><pre>ncols 4
55nrows 6
56xllcorner 0
57yllcorner 0
58cellsize 50
59NODATA_value -9999
60-9999 -9999 5 2
61-9999 20 100 36
623 8 35 10
6332 42 50 6
6488 75 27 9
6513 5 1 -9999</pre></dd></dl></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
66process. If this parameter is not provided, all of the rows will be
67processed. If this parameter is provided but the underlying database
68does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying
69database. ESRI recommends you reference fields using the following
70syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or
71dBASE tables (.dbf files), enclose field names in double quotes in
72the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal
73geodatabase tables, enclose field names in square brackets:
74[MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
75class, or an ArcIMS image service sublayer, don't enclose field
76names: 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
77specified in the ORDER BY clause of a SQL SELECT statement). If no
78fields are provided, the rows will be sorted in the default order
79determined by the underlying database. If this parameter is provided
80but this computer is not running ArcGIS 9.2 or later or the underlying
81database 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
82the 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
83the sort directions for the ORDER BY fields. If this parameter is
84provided but this computer is not running ArcGIS 9.2 or later or the
85underlying database does not support ORDER BY clauses, an error will
86be 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 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
87that are obtained from the fields that list the inputs (and outputs,
88if this tool has outputs). If a base path is not provided, the
89workspace containing the table will be prepended instead.</p></td></tr></tbody></table></div></body></html>
Note: See TracBrowser for help on using the browser.