root/MGET/Branches/Jason/PythonPackage/dist/TracOnlineDocumentation/Documentation/PythonReference/Method_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.ToArcGISRasterTable.html @ 316

Revision 316, 32.0 KB (checked in by jjr8, 5 years ago)

Built MGET 0.7a1. Forgot to mention that the checkin before the last one also fixed #308: When a GAM uses the loess function (lo) and is fitted with the R gam package, Predict GAM fails when rasters include NODATA values.

This will be merged into Trunk and released as MGET 0.7a1.
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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ToArcGISRasterTable Method</title><link rel="stylesheet" type="text/css" href="lib.css?format=raw" /><style xml:space="preserve">
4            td.metadataTitle { font-size: 80%; font-weight: bold; font-family: avantgarde, sans-serif; }
5            td.metadataValue { padding-left: 0.5em; }
6          </style></head><body><div class="navigation"><div><table align="center" width="100%" cellpadding="0" cellspacing="2"><tr><td class="online-navigation"><a title="ToArcGISRasterList Method" href="Method_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.ToArcGISRasterList.html?format=raw"><img src="previous.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Previous Page" /></a></td><td class="online-navigation"><a title="ArcInfoASCIIGrid Class" href="Class_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.html?format=raw"><img src="up.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Up one Level" /></a></td><td class="online-navigation"><a title="GeoEco.DataManagement.BinaryRasters Module" href="Module_GeoEco.DataManagement.BinaryRasters.html?format=raw"><img src="next.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Next Page" /></a></td><td align="center" width="100%">GeoEco Python Reference</td><td class="online-navigation"><a title="Table of Contents" href="TableOfContents.html?format=raw"><img src="contents.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Table of Contents" /></a></td><td class="online-navigation"><a title="Module Index" href="ModuleIndex.html?format=raw"><img src="modules.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Module Index" /></a></td><td class="online-navigation"><img src="blank.png?format=raw" border="0" align="bottom" height="32" width="32" alt="" /></td></tr></table><div class="online-navigation"><b class="navlabel">Previous:</b> <a class="sectref" href="Method_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.ToArcGISRasterList.html?format=raw">ToArcGISRasterList Method</a> <b class="navlabel">Up:</b> <a class="sectref" href="Class_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.html?format=raw">ArcInfoASCIIGrid Class</a> <b class="navlabel">Next:</b> <a class="sectref" href="Module_GeoEco.DataManagement.BinaryRasters.html?format=raw">GeoEco.DataManagement.BinaryRasters Module</a> </div><hr /></div></div><h1><tt class="member">ToArcGISRasterTable</tt> Method</h1><p>Converts each ArcInfo ASCII Grid text file in a table to an ArcGIS raster.</p><table cellpadding="0" cellspacing="0"><tr valign="baseline"><td class="metadataTitle">Class:</td><td class="metadataValue"><tt class="class"><a href="Class_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.html?format=raw">ArcInfoASCIIGrid</a></tt></td></tr><tr valign="baseline"><td class="metadataTitle">Intended use:</td><td class="metadataValue">Recommended for external callers</td></tr><tr valign="baseline"><td class="metadataTitle">COM:</td><td class="metadataValue">Not exposed by a COM class</td></tr><tr valign="baseline"><td class="metadataTitle">ArcGIS:</td><td class="metadataValue">Not exposed as an ArcGIS geoprocessing tool</td></tr><tr valign="baseline"><td class="metadataTitle">Method type:</td><td class="metadataValue">Classmethod</td></tr></table><h3>Usage</h3><table cellpadding="0" cellspacing="0"><tr valign="baseline"><td style="white-space: nowrap;"><b><tt class="method">ArcInfoASCIIGrid.ToArcGISRasterTable</tt></b>(</td><td><var>connection</var><var>, table</var><var>, inputFileField</var><var>, outputRasterField</var><big>[</big><var>, isInteger</var><big>[</big><var>, coordinateSystem</var><big>[</big><var>, projectedCoordinateSystem</var><big>[</big><var>, geographicTransformation</var><big>[</big><var>, resamplingTechnique</var><big>[</big><var>, projectedCellSize</var><big>[</big><var>, registrationPoint</var><big>[</big><var>, clippingRectangle</var><big>[</big><var>, mapAlgebraExpression</var><big>[</big><var>, buildPyramids</var><big>[</big><var>, where</var><big>[</big><var>, orderBy</var><big>[</big><var>, directions</var><big>[</big><var>, skipExisting</var><big>[</big><var>, overwriteExisting</var><big>[</big><var>, basePath</var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table><h3>Arguments</h3><dl><dt><var>connection</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">GeoEco.DatabaseAccess.DatabaseConnection</tt></td></tr></table><p>Connection opened to the database that contains the table.</p></dd></dl><dl><dt><var>table</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr></table><p>Name of the table to query.</p></dd></dl><dl><dt><var>inputFileField</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr></table><p>Field containing the paths of the input text files in ArcInfo ASCII Grid format.</p><p>ArcInfo ASCII Grid format is not formally specified by ESRI but you
7can find informal specifications by searching the Internet. The format
8is well-known, stable and very simple. A short example:</p><div class="verbatim"><pre xml:space="preserve">ncols 4
9nrows 6
10xllcorner 0
11yllcorner 0
12cellsize 50
13NODATA_value -9999
14-9999 -9999 5 2
15-9999 20 100 36
163 8 35 10
1732 42 50 6
1888 75 27 9
1913 5 1 -9999</pre></div><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></dd></dl><dl><dt><var>outputRasterField</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr></table><p>Field containing the output rasters to create.</p></dd></dl><dl><dt><var>isInteger</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">bool</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><code>False</code></td></tr></table><p>If True, the output raster will have an integer data type. If
23False, the default, the output raster will have a floating-point data
24type.</p><p>The raster is created using the ArcGIS ASCII To Raster geoprocessing
25tool. For integer rasters, the tool determines the specific integer
26data type from the values present in the input file. It usually picks
27the most compact data type capable of representing all of the values.
28For example, if the values range from 0 to 255, it usually picks the
29unsigned 8-bit integer data type. But it also exhibits some strange
30behavior, at least with ArcGIS 9.1:</p><ul><li>If the ASCII file contains values ranging from -128 to 127, the tool
31will create an signed 16-bit raster even though the values are most
32compactly stored as signed 8-bit integers. It will create a signed
338-bit raster if the value -128 does not appear in the file, or if
34128 is designated the NODATA value. Specifying a different NODATA
35value, such as 0, still yields an int16 raster if -128 appears.</li><li>Similarly, if the ASCII file contains values ranging from -32768 to
3632767, the tool will create an signed 32-bit raster if the value
37-32768 appears in the ASCII file, unless it is designated the NODATA
38value.</li><li>Worse, if the ASCII file contains values ranging from -2147483648 to
392147483647, the tool will report an error if the value -2147483648
40appears in the ASCII file unless it is designated the NODATA value.
41Even stranger, the value -2147483647 is always translated to NODATA,
42no matter what.</li><li>For all types of integer rasters, the tool produces strange behavior
43when you specify a NODATA value that is not the smallest possible
44value for the data type. For example, if the ASCII file contains
45values from 0 to 255 and 0 is designated the NODATA value, the tool
46produces an unsigned 8-bit raster. But if 1 is designated the NODATA
47value, it produces a signed 16-bit raster, and ArcCatalog shows
48under Raster Dataset Properties that the NoData Value is -32768,
49although the Identify tool shows cells that had value 1 are actually
50NODATA. Similar strange results can be obtained for integer rasters
51of other data types when you designate a NODATA that is not the
52smallest possible value.</li></ul><p>For floating-point rasters, the 32-bit floating-point data type is
53always used. The ArcGIS raster format does not support the 64-bit
54floating-point data type (often called "double"). The ArcGIS ASCII To
55Raster geoprocessing tool appears to accept ASCII files that contain
56floating-point values that are higher precision and that exceed the
57exponential range of that provided by the 32-bit data type. The
58behavior of the tool is not documented, but in ArcGIS 9.1 it appears
59to be:</p><ul><li>Values where the exponent ranges from -38 to +38 are properly
60represented in the resulting 32-bit float raster.</li><li>Values where the exponent is less than -38 (e.g. -39, -40, and so
61on) are converted to 0.</li><li>Values where the exponent is greater than +38 are converted to -INF
62or +INF, depending on the sign of the value (e.g.
63-5.3083635279597874e-212 appears as -1.#INF in the ArcCatalog GUI,
64while 2.5502286890301497e+084 appears as 1.#INF).</li></ul></dd></dl><dl><dt><var>coordinateSystem</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr></table><p>Coordinate system to define for the output raster. If a value is
65not provided, the coordinate system of the output raster will remain
66undefined.</p></dd></dl><dl><dt><var>projectedCoordinateSystem</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr></table><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
67original projection is defined. An error will be raised if you specify
68a new coordinate system without defining the original coordinate
69system.</p><p>The ArcGIS Project Raster tool is used to perform the projection. The
70documentation for that tool recommends that you also specify a cell
71size for the new coordinate system.</p><p>I have noticed that for certain coordinate systems the ArcGIS 9.2
72Project Raster tool seems to clip the projected raster to an arbitrary
73extent that is too small. For example, when projecting a global MODIS
74Aqua 4 km chlorophyll image in geographic coordinates to
75Lambert_Azimuthal_Equal_Area with central meridian of -60 and latitude
76of origin of -63, the resulting image is clipped to show only
77one-quarter of the planet. This problem does not occur when Project
78Raster is invoked interactively from the ArcGIS user interface; it
79only occurs when the tool is invoked programmatically (the
80ProjectRaster_management method of the geoprocessor). Thus you may
81not see it when you use Project Raster yourself but it may happen when
82you use MGET tools that invoke Project Raster as part of their
83geoprocessing operations.</p><p>If you encounter this problem, you can work around it like this:</p><ul><li>First, run this tool without specifying a new coordinate system, to
84obtain the output raster in the original coordinate system.</li><li>In ArcCatalog, use the Project Raster tool to project the raster to
85the new coordinate system. Verify that the entire raster is present,
86that it has not been clipped to an extent that is too small.</li><li>In ArcCatalog, look up the extent of the projected raster by
87right-clicking on it in the catalog tree, selecting Properties, and
88scrolling down to Extent.</li><li>Now, before running the MGET tool that projects the raster, set the
89Extent environment setting to the values you looked up. If you are
90invoking the MGET tool interactively from ArcCatalog or ArcMap,
91click the Environments button on the tool's dialog box, open General
92Settings, change the Extent drop-down to "As Specified Below", and
93type in the values you looked up. If you're invoking it from a
94geoprocessing model, right-click on the tool in the model, select
95Make Variable, From Environment, General Settings, Extent. This will
96place Extent as a variable in your model, attached to the MGET tool.
97Open the Extent variable, change it to "As Specified Below" and type
98in the values you looked up. If you're invoking the MGET tool
99programmatically, you must set the Extent property of the
100geoprocessor to the values you looked up. Please see the ArcGIS
101documentation for more information about this and Environment
102settings in general.</li><li>Run the MGET tool. The extent of the output raster should now be the
103proper size.</li></ul></dd></dl><dl><dt><var>geographicTransformation</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr></table><p>A transformation method used to convert between the original
104coordinate system and the new coordinate system.</p><p>This parameter is a new option introduced by ArcGIS 9.2. You must have
105ArcGIS 9.2 to use this parameter.</p><p>This parameter is only needed when you specify that the raster should
106be projected to a new coordinate system and that new system uses a
107different datum than the original coordinate system, or there is some
108other difference between the two coordinate systems that requires a
109transformation. To determine if a transformation is needed, I
110recommend the following procedure:</p><ul><li>First, run this tool without specifying a new coordinate system, to
111obtain the output raster in the original coordinate system.</li><li>Next, use the ArcGIS 9.2 Project Raster tool on the output raster to
112project it to the desired coordinate system. If a geographic
113transformation is needed, that tool will prompt you for one. Write
114down the exact name of the transformation you used.</li><li>Finally, if a transformation was needed, type in the exact name into
115this tool, rerun it, and verify that the output raster was projected
116as you desired.</li></ul></dd></dl><dl><dt><var>resamplingTechnique</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Allowed values:</td><td class="metadataValue"><code>u'NEAREST'</code>, <code>u'BILINEAR'</code>, <code>u'CUBIC'</code></td></tr></table><p>The resampling algorithm to be used to project the original raster
117to a new coordinate system. The ArcGIS Project Raster tool is used to
118perform the projection and accepts the following values:</p><ul><li>NEAREST - nearest neighbor interpolation</li><li>BILINEAR - bilinear interpolation</li><li>CUBIC - cubic convolution</li></ul><p>You must specify one of these algorithms to project to a new
119coordinate system. An error will be raised if you specify a new
120coordinate system without selecting an algorithm.</p></dd></dl><dl><dt><var>projectedCellSize</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">float</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr></table><p>The cell size of the projected coordinate system. Although this
121parameter is optional, to receive the best results, the ArcGIS
122documentation recommends you always specify it when projecting to a
123new coordinate system.</p></dd></dl><dl><dt><var>registrationPoint</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr><tr valign="baseline"><td class="metadataTitle">Must match regular expression:</td><td class="metadataValue"><code>([-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?)\s+([-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?)</code></td></tr></table><p>The x and y coordinates (in the output space) used for pixel
124alignment.</p><p>This parameter is a new option introduced by ArcGIS 9.2. You must have
125ArcGIS 9.2 to use this parameter. It is ignored if you do not specify
126that the raster should be projected to a new coordinate system.</p></dd></dl><dl><dt><var>clippingRectangle</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr><tr valign="baseline"><td class="metadataTitle">Must match regular expression:</td><td class="metadataValue"><code>([-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?)\s+([-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?)\s+([-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?)\s+([-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?)</code></td></tr></table><p>Rectangle to which the raster should be clipped.</p><p>If a projected coordinate system was specified, the clipping is
127performed after the projection and the rectangle's coordinates should
128be specified in the new coordinate system. If no projected coordinate
129system was specified, the coordinates should be specified in the
130original coordinate system.</p><p>The ArcGIS Clip tool is used to perfom the clip. The clipping
131rectangle must be passed to this tool as a string of four numbers
132separated by spaces. The ArcGIS user interface automatically formats
133the string properly; when invoking this tool from the ArcGIS UI,
134you need not worry about the format. But when invoking it
135programmatically, take care to provide a properly-formatted string.
136The numbers are ordered LEFT, BOTTOM, RIGHT, TOP. For example, if the
137raster is in a geographic coordinate system, it may be clipped to 10
138W, 15 S, 20 E, and 25 N with the string:</p><p>10 15 20 25</p><p>Integers or decimal numbers may be provided.</p></dd></dl><dl><dt><var>mapAlgebraExpression</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr><tr valign="baseline"><td class="metadataTitle">Maximum length:</td><td class="metadataValue">4000</td></tr></table><p>Map algebra expression to execute on the output raster.</p><p><strong>WARNING:</strong> The ArcGIS Geoprocessing Model Builder may randomly and
139silently delete the value of this parameter. This is a bug in ArcGIS.
140Before running a model that you have saved, open this tool and
141validate that the parameter value still exists.</p><p>The expression is executed after the converted raster is projected and
142clipped (if those options are specified). Use the case-sensitive
143string inputRaster to represent the raster that you now want to
144perform map algebra upon. For example, to convert the raster to an
145integer raster and add 1 to all of the cells, use this expression:</p><div class="verbatim"><pre xml:space="preserve">int(inputRaster) + 1</pre></div><p>The string inputRaster is case-sensitive. Prior to executing the map
146algebra expression, the string is replaced with the path to a
147temporary raster that represents the output raster being generated.
148The final expression must be less than 4000 characters long or ArcGIS
149will report an error.</p><p>The ArcGIS Single Output Map Algebra tool is used to execute the map
150algebra expression. You must have a license for the ArcGIS Spatial
151Analyst extension in order to perform map algebra.</p><p>Map algebra syntax can be very picky. Here are some tips that will
152help you succeed with this tool:</p><ul><li>Before using this tool, construct and test out your map algebra
153expression using the ArcGIS Single Output Map Algebra tool. Then
154paste the expression into this tool and edit it to use the
155inputRaster variable rather than the test value you used with Single
156Output Map Algebra.</li><li>If you do develop your expression directly in this tool, start with
157a very simple expression. Verify that it works properly, add a
158little to it, and verify again. Repeat this process until you have
159built up the complete expression.</li><li>Always separate mathematical operators from raster paths using
160spaces. In the example above, the / operator contains a space on
161either side. Follow this pattern. In some circumstances, ArcGIS will
162fail to process raster algebra expressions that do not separate
163raster paths from operators using spaces. The reported error message
164usually does not indicate that this is the problem, and tracking it
165down can be very frustrating.</li></ul></dd></dl><dl><dt><var>buildPyramids</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">bool</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><code>False</code></td></tr></table><p>If True, pyramids will be built for the output raster, which will
166improve its display speed in the ArcGIS user interface. This is the
167last step performed in post-conversion processing.</p></dd></dl><dl><dt><var>where</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr></table><p>SQL WHERE clause expression that specifies the subset of rows to
168process. If this parameter is not provided, all of the rows will be
169processed. If this parameter is provided but the underlying database
170does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying database
171and the type of connection used to access it. If you are using the
172ArcGIS geoprocessor to access the database, ESRI recommends you
173reference fields using the following syntax:</p><ul><li>If you're querying ArcInfo coverages, shapefiles, INFO tables or
174dBASE tables (.dbf files), enclose field names in double quotes in
175the SQL expression: "MY_FIELD".</li><li>If you're querying Microsoft Access tables or personal
176geodatabase tables, enclose field names in square brackets:
177[MY_FIELD].</li><li>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
178class, or an ArcIMS image service sublayer, don't enclose field
179names: MY_FIELD.</li></ul></dd></dl><dl><dt><var>orderBy</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">list</tt> of <tt class="class">unicode</tt>, or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">0</td></tr></table><p>Fields that will be used to sort the rows (i.e., the columns
180specified in the ORDER BY clause of a SQL SELECT statement). If no
181fields are provided, the rows will be sorted in the default order
182determined by the underlying database. If this parameter is provided
183but the underlying database does not support ORDER BY clauses, an
184error will be raised.</p><p>In addition to specifying the ORDER BY fields, you must also specify
185the sort direction for each field.</p></dd></dl><dl><dt><var>directions</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">list</tt> of <tt class="class">unicode</tt>, or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">0</td></tr></table><p>List of strings, either 'Ascending' or 'Descending', that specify
186the sort directions for the ORDER BY fields. If this parameter is
187provided but the underlying database does not support ORDER BY
188clauses, an error will be raised.</p></dd></dl><dl><dt><var>skipExisting</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">bool</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><code>False</code></td></tr></table><p>If True, processing will be skipped for output rasters that already exist.</p></dd></dl><dl><dt><var>overwriteExisting</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">bool</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><code>False</code></td></tr></table><p>If True and skipExisting is False, existing output rasters will be overwritten.</p></dd></dl><dl><dt><var>basePath</var></dt><dd><table cellpadding="0" cellspacing="0" style="margin-top: 1.0em;"><tr valign="baseline"><td class="metadataTitle">Python type:</td><td class="metadataValue"><tt class="class">unicode</tt> or <tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Default value:</td><td class="metadataValue"><tt class="class">None</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum length:</td><td class="metadataValue">1</td></tr><tr valign="baseline"><td class="metadataTitle">Maximum length:</td><td class="metadataValue">255</td></tr><tr valign="baseline"><td class="metadataTitle">Must exist:</td><td class="metadataValue">No</td></tr></table><p>Base path to prepend to relative paths.</p><p>If any of the input paths (or output paths, if this method has
189outputs) obtained from the table are relative paths, they will be
190converted to absolute paths prior to processing, as follows:</p><ul><li>If a base path is provided, it will be prepended to the relative
191path.</li><li>Otherwise, if the ArcGIS geoprocessor has been initialized and the
192geoprocessing workspace has been set (i.e. the Workspace property of
193the geoprocessor is not empty), it will be prepended to the relative
194path.</li><li>Otherwise, the current working directory for the executing process
195will be prepended to the path. If you have not explicitly changed
196the working directory, it is usually the directory that contains the
197Python interpreter (e.g., on Windows computers, it would be
198C:\Python24, if you're running Python 2.4).</li></ul></dd></dl><div class="navigation"><div class="online-navigation"><p></p><hr /><table align="center" width="100%" cellpadding="0" cellspacing="2"><tr><td class="online-navigation"><a title="ToArcGISRasterList Method" href="Method_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.ToArcGISRasterList.html?format=raw"><img src="previous.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Previous Page" /></a></td><td class="online-navigation"><a title="ArcInfoASCIIGrid Class" href="Class_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.html?format=raw"><img src="up.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Up one Level" /></a></td><td class="online-navigation"><a title="GeoEco.DataManagement.BinaryRasters Module" href="Module_GeoEco.DataManagement.BinaryRasters.html?format=raw"><img src="next.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Next Page" /></a></td><td align="center" width="100%">GeoEco Python Reference</td><td class="online-navigation"><a title="Table of Contents" href="TableOfContents.html?format=raw"><img src="contents.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Table of Contents" /></a></td><td class="online-navigation"><a title="Module Index" href="ModuleIndex.html?format=raw"><img src="modules.png?format=raw" border="0" align="bottom" height="32" width="32" alt="Module Index" /></a></td><td class="online-navigation"><img src="blank.png?format=raw" border="0" align="bottom" height="32" width="32" alt="" /></td></tr></table><div class="online-navigation"><b class="navlabel">Previous:</b> <a class="sectref" href="Method_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.ToArcGISRasterList.html?format=raw">ToArcGISRasterList Method</a> <b class="navlabel">Up:</b> <a class="sectref" href="Class_GeoEco.DataManagement.ArcInfoASCIIGrids.ArcInfoASCIIGrid.html?format=raw">ArcInfoASCIIGrid Class</a> <b class="navlabel">Next:</b> <a class="sectref" href="Module_GeoEco.DataManagement.BinaryRasters.html?format=raw">GeoEco.DataManagement.BinaryRasters Module</a> </div><hr /><span class="release-info">Marine Geospatial Ecology Tools version 0.7a1</span></div></div></body></html>
Note: See TracBrowser for help on using the browser.