| 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>Extract Headers of SIR Files Listed in Table</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>Extract Headers of SIR Files Listed in Table</h1><p></p><p>Extracts the headers of SIR files in a table and saves them to text files.</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">SIRFileExtractHeaderArcGISTable_GeoEco <table> <sirFileField> <outputFileField> {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"><table></td><td class="info" align="left"><p>Table to query.</p></td></tr><tr><td class="info"><sirFileField></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. |
|---|
| 4 | MERS publishes various products derived from scatterometers bourne by |
|---|
| 5 | satellites such as QuikSCAT. These products include sea surface wind |
|---|
| 6 | vectors, sea ice masks, and raw scatterometer sigma-0 values, which |
|---|
| 7 | correlate with the roughness of the ocean surface.</p><p>Compressed files in a supported compression format will be |
|---|
| 8 | automatically decompressed. Archives (e.g. .zip or .tar) must contain |
|---|
| 9 | exactly one file, which must not be in a subdirectory.</p></td></tr><tr><td class="info"><outputFileField></td><td class="info" align="left"><p>Field containing the paths of the text files to create.</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 |
|---|
| 10 | process. If this parameter is not provided, all of the rows will be |
|---|
| 11 | processed. If this parameter is provided but the underlying database |
|---|
| 12 | does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying |
|---|
| 13 | database. ESRI recommends you reference fields using the following |
|---|
| 14 | syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or |
|---|
| 15 | dBASE tables (.dbf files), enclose field names in double quotes in |
|---|
| 16 | the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal |
|---|
| 17 | geodatabase tables, enclose field names in square brackets: |
|---|
| 18 | [MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature |
|---|
| 19 | class, or an ArcIMS image service sublayer, don't enclose field |
|---|
| 20 | names: 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 |
|---|
| 21 | specified in the ORDER BY clause of a SQL SELECT statement). If no |
|---|
| 22 | fields are provided, the rows will be sorted in the default order |
|---|
| 23 | determined by the underlying database. If this parameter is provided |
|---|
| 24 | but this computer is not running ArcGIS 9.2 or later or the underlying |
|---|
| 25 | database 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 |
|---|
| 26 | the 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 |
|---|
| 27 | the sort directions for the ORDER BY fields. If this parameter is |
|---|
| 28 | provided but this computer is not running ArcGIS 9.2 or later or the |
|---|
| 29 | underlying database does not support ORDER BY clauses, an error will |
|---|
| 30 | be raised.</p></td></tr><tr><td class="info">{skipExisting}</td><td class="info" align="left"><p>If True, processing will be skipped for text 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 |
|---|
| 31 | that are obtained from the fields that list the inputs (and outputs, |
|---|
| 32 | if this tool has outputs). If a base path is not provided, the |
|---|
| 33 | workspace 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">SIRFileExtractHeaderArcGISTable_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. |
|---|
| 34 | MERS publishes various products derived from scatterometers bourne by |
|---|
| 35 | satellites such as QuikSCAT. These products include sea surface wind |
|---|
| 36 | vectors, sea ice masks, and raw scatterometer sigma-0 values, which |
|---|
| 37 | correlate with the roughness of the ocean surface.</p><p>Compressed files in a supported compression format will be |
|---|
| 38 | automatically decompressed. Archives (e.g. .zip or .tar) must contain |
|---|
| 39 | exactly one file, which must not be in a subdirectory.</p></td></tr><tr><td class="info">Output text file field (Required) </td><td class="info" align="left"><p>Field containing the paths of the text files to create.</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 |
|---|
| 40 | process. If this parameter is not provided, all of the rows will be |
|---|
| 41 | processed. If this parameter is provided but the underlying database |
|---|
| 42 | does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying |
|---|
| 43 | database. ESRI recommends you reference fields using the following |
|---|
| 44 | syntax:</p><ul><li><p>If you're querying ArcInfo coverages, shapefiles, INFO tables or |
|---|
| 45 | dBASE tables (.dbf files), enclose field names in double quotes in |
|---|
| 46 | the SQL expression: "MY_FIELD".</p></li></ul><ul><li><p>If you're querying Microsoft Access tables or personal |
|---|
| 47 | geodatabase tables, enclose field names in square brackets: |
|---|
| 48 | [MY_FIELD].</p></li></ul><ul><li><p>If you're querying ArcSDE geodatabase tables, an ArcIMS feature |
|---|
| 49 | class, or an ArcIMS image service sublayer, don't enclose field |
|---|
| 50 | names: 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 |
|---|
| 51 | specified in the ORDER BY clause of a SQL SELECT statement). If no |
|---|
| 52 | fields are provided, the rows will be sorted in the default order |
|---|
| 53 | determined by the underlying database. If this parameter is provided |
|---|
| 54 | but this computer is not running ArcGIS 9.2 or later or the underlying |
|---|
| 55 | database 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 |
|---|
| 56 | the 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 |
|---|
| 57 | the sort directions for the ORDER BY fields. If this parameter is |
|---|
| 58 | provided but this computer is not running ArcGIS 9.2 or later or the |
|---|
| 59 | underlying database does not support ORDER BY clauses, an error will |
|---|
| 60 | be 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 text 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 |
|---|
| 61 | that are obtained from the fields that list the inputs (and outputs, |
|---|
| 62 | if this tool has outputs). If a base path is not provided, the |
|---|
| 63 | workspace containing the table will be prepended instead.</p></td></tr></tbody></table></div></body></html> |
|---|