root/MGET/Branches/Jason/PythonPackage/dist/TracOnlineDocumentation/Documentation/PythonReference/Method_GeoEco.DataManagement.BinaryRasters.BinaryRaster.ToArcInfoASCIIGridTable.html @ 376

Revision 376, 26.8 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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ToArcInfoASCIIGridTable 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="ToArcInfoASCIIGridList Method" href="Method_GeoEco.DataManagement.BinaryRasters.BinaryRaster.ToArcInfoASCIIGridList.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="BinaryRaster Class" href="Class_GeoEco.DataManagement.BinaryRasters.BinaryRaster.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.Directories Module" href="Module_GeoEco.DataManagement.Directories.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.BinaryRasters.BinaryRaster.ToArcInfoASCIIGridList.html?format=raw">ToArcInfoASCIIGridList Method</a> <b class="navlabel">Up:</b> <a class="sectref" href="Class_GeoEco.DataManagement.BinaryRasters.BinaryRaster.html?format=raw">BinaryRaster Class</a> <b class="navlabel">Next:</b> <a class="sectref" href="Module_GeoEco.DataManagement.Directories.html?format=raw">GeoEco.DataManagement.Directories Module</a> </div><hr /></div></div><h1><tt class="member">ToArcInfoASCIIGridTable</tt> Method</h1><p>Converts each two-dimensional binary raster in a table to a text file in ArcInfo ASCII Grid format.</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.BinaryRasters.BinaryRaster.html?format=raw">BinaryRaster</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">BinaryRaster.ToArcInfoASCIIGridTable</tt></b>(</td><td><var>connection</var><var>, table</var><var>, inputFileField</var><var>, outputFileField</var><var>, dataType</var><var>, columnCount</var><var>, rowCount</var><var>, xLowerLeftCorner</var><var>, yLowerLeftCorner</var><var>, cellSize</var><big>[</big><var>, nodataValue</var><big>[</big><var>, offset</var><big>[</big><var>, swapBytes</var><big>[</big><var>, transpose</var><big>[</big><var>, mirror</var><big>[</big><var>, flip</var><big>[</big><var>, swapHemispheres</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>)</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 binary rasters.</p><p>A binary raster is a file that contains a raw array of numbers stored
7in binary format, as if a snapshot of in-memory data had been written
8directly to disk. In ArcGIS, this is the type of file output by the
9Raster to Float tool, although that tool can only output binary
10rasters that use a 32-bit floating point data type. This tool can use
11any standard numeric data type.</p><p>The data must have two dimensions. By default, it is assumed that the
12data are in "row-major order", the approach used by the C programming
13language: the cells are ordered left-to-right, top-to-bottom, with
14columns increasing before rows. The upper-left cell is the first cell,
15followed by the cell to its right, and so on to the end of the first
16row. The second row comes next, and so on to the end. The lower-right
17cell is the last one. If the data are in "column-major order", the
18approach used by Fortran and MATLAB, use the Transpose option to flip
19the data about the diagonal axis.</p><p>By default, it is assumed that the data should be read starting with
20the first byte of the file. If the file contains a header of a known
21length, use the Offset parameter to skip over it.</p><p>If the file contains extra bytes that occur after the data, they will
22be ignored.</p><p>If you provide compressed files in a supported compression format,
23they will be automatically decompressed. If files are compressed in an
24archive format (e.g. .zip or .tar), each archive must contain exactly
25one file, which must not be in a subdirectory.</p></dd></dl><dl><dt><var>outputFileField</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 ArcInfo ASCII Grid files to write.</p><p>ArcInfo ASCII Grid format is not formally specified by ESRI but you
26can find informal specifications by searching the Internet. The format
27is well-known, stable and very simple. A short example:</p><div class="verbatim"><pre xml:space="preserve">ncols 4
28nrows 6
29xllcorner 0
30yllcorner 0
31cellsize 50
32NODATA_value -9999
33-9999 -9999 5 2
34-9999 20 100 36
353 8 35 10
3632 42 50 6
3788 75 27 9
3813 5 1 -9999</pre></div></dd></dl><dl><dt><var>dataType</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">Allowed values:</td><td class="metadataValue"><code>u'int8'</code>, <code>u'uint8'</code>, <code>u'int16'</code>, <code>u'uint16'</code>, <code>u'int32'</code>, <code>u'uint32'</code>, <code>u'float'</code>, <code>u'double'</code></td></tr></table><p>Data type of the binary raster.</p><p>This may be one of the following values:</p><ul><li>int8 - 8-bit signed integer, range -128 to 127</li><li>uint8 - 8-bit unsigned integer, range 0 to 255</li><li>int16 - 16-bit signed integer, range -32768 to 32767</li><li>uint16 - 16-bit unsigned integer, range 0 to 65535</li><li>int32 - 32-bit signed integer, range -2147483648 to 2147483647</li><li>uint32 - 32-bit unsigned integer, range 0 to 4294967295</li><li>float - 32-bit single-precision floating point</li><li>double - 64-bit double-precision floating point</li></ul><p>Binary rasters with other data types cannot be converted because the
39ArcInfo ASCII Grid format does not support them.</p><p>The exact format, precision and range of the floating types depend on the
40processor architecture of your computer. Most processors implement the IEEE
41Standard for Binary Floating-Point Arithmetic (IEEE 754).</p><p>Binary rasters that use the float or double data type must not contain
42"infinity" (INF) or "not a number" (NAN) values. A ValueError will be raised if
43these values are discovered.</p><p>The ArcGIS raster format supports the 32-bit float data type but not the 64-bit
44double data type. You may still run the ArcGIS ASCII to Raster geoprocessing
45tool to convert ASCII files created from double-precision binary rasters. The
46tool's behavior in this situation is not documented. In ArcGIS 9.1 it appears to
47be:</p><ul><li>Values where the exponent ranges from -38 to +38 are properly represented in
48the resulting 32-bit float raster.</li><li>Values where the exponent is less than -38 (e.g. -39, -40, and so on) are
49converted to 0.</li><li>Values where the exponent is greater than +38 are converted to -INF or +INF,
50depending on the sign of the value (e.g. -5.3083635279597874e-212 appears as
51-1.#INF in the ArcCatalog GUI, while 2.5502286890301497e+084 appears as
521.#INF).</li></ul><p>The ArcGIS 9.1 ASCII to Raster tool also exhibits some quirks when converting
53integer rasters:</p><ul><li>For an ASCII file created from an int8 binary file, the tool will create an
54int16 raster if the value -128 appears in the ASCII file, unless -128 is
55designated the NODATA value. Specifying a different NODATA value, such as 0,
56still yields an int16 raster if -128 appears.</li><li>Similarly, for an ASCII file created from an int16 binary file, the tool will
57create an int32 raster if the value -32768 appears in the ASCII file, unless
58it is designated the NODATA value.</li><li>Worse, for an ASCII file created from an int32 binary file, the tool will
59report an error if the value -2147483648 appears in the ASCII file unless it
60is designated the NODATA value. Even stranger, the value -2147483647 is
61always translated to NODATA, no matter what.</li><li>For all types of integer rasters, the tool produces strange behavior when you
62specify a NODATA value that is not the smallest possible value for the data
63type. For example, if the ASCII file contains values from 0 to 255 and 0 is
64designated the NODATA value, the tool produces a uint8 output raster. But if
651 is designated the NODATA value, it produces an int16 output raster, and
66ArcCatalog shows under Raster Dataset Properties that the NoData Value is
67-32768, although the Identify tool shows cells that had value 1 are actually
68NODATA. Similar strange results can be obtained for integer rasters of other
69data types, when you designate a NODATA that is not the smallest possible
70value.</li></ul></dd></dl><dl><dt><var>columnCount</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">int</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum value:</td><td class="metadataValue"><code>1</code></td></tr></table><p>Number of columns in the binary raster.</p></dd></dl><dl><dt><var>rowCount</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">int</tt></td></tr><tr valign="baseline"><td class="metadataTitle">Minimum value:</td><td class="metadataValue"><code>1</code></td></tr></table><p>Number of rows in the binary raster.</p></dd></dl><dl><dt><var>xLowerLeftCorner</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></td></tr></table><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
71cell. For example, if the raster is a geographic projection of the entire Earth,
72the coordinate of the lower left corner would be -180.0, corresponding to a
73longitude of 180 degrees West.</p></dd></dl><dl><dt><var>yLowerLeftCorner</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></td></tr></table><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
74cell. For example, if the raster is a geographic projection of the entire Earth,
75the coordinate of the lower left corner would be -90.0, corresponding to a
76latitude of 90 degrees South.</p></dd></dl><dl><dt><var>cellSize</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></td></tr></table><p>Size of each raster cell.</p><p>For example, if the raster is a geographic projection of the entire Earth, with
77720 columns and 360 rows, it would have a cell size of 0.5, corresponding to
781/2 of a geographic degree.</p><p>The underlying data format requires the cells be square. It is not possible to
79specify a cell size for each dimension.</p></dd></dl><dl><dt><var>nodataValue</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>Value that indicates a cell has no data.</p></dd></dl><dl><dt><var>offset</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">int</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 value:</td><td class="metadataValue"><code>1</code></td></tr></table><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
80occur before the data. For example, if the file contains a 512 byte
81header, set this parameter to 512 to skip over the header. If this
82parameter is not specified, the data will be read starting at the
83first byte of the file.</p></dd></dl><dl><dt><var>swapBytes</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 byte ordering of the binary raster will be reversed
84prior 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
85processor architecture that uses a different byte ordering than your computer.
86For example, if you are running on an Intel x86 processor, which uses "little
87endian" byte ordering, you might use this option to process data produced by a
88Sun SPARC processor, which uses "big endian" byte ordering.</p></dd></dl><dl><dt><var>transpose</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 image will be transposed (flipped about the diagonal
89axis) prior to conversion. Use this option to fix an image that has
90the east/west axis going up and down instead of left and right.</p></dd></dl><dl><dt><var>mirror</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 image will be flipped about the vertical axis prior
91to conversion. Use this option to fix an image that is the "mirror
92image" of what it is supposed to be.</p></dd></dl><dl><dt><var>flip</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 image will be flipped about the horizontal axis prior
93to conversion. Use this option to fix an image that is
94upside-down.</p></dd></dl><dl><dt><var>swapHemispheres</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 east and west hemispheres of the image will be
95swapped. Use this option to change the orientation of a global image
96from a 0 to 360 orientation centered on the Pacific ocean to a -180 to
97+180 orientation centered on the Atlantic ocean, or visa versa.</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
98process. If this parameter is not provided, all of the rows will be
99processed. If this parameter is provided but the underlying database
100does not support WHERE clauses, an error will be raised.</p><p>The exact syntax of this expression depends on the underlying database
101and the type of connection used to access it. If you are using the
102ArcGIS geoprocessor to access the database, ESRI recommends you
103reference fields using the following syntax:</p><ul><li>If you're querying ArcInfo coverages, shapefiles, INFO tables or
104dBASE tables (.dbf files), enclose field names in double quotes in
105the SQL expression: "MY_FIELD".</li><li>If you're querying Microsoft Access tables or personal
106geodatabase tables, enclose field names in square brackets:
107[MY_FIELD].</li><li>If you're querying ArcSDE geodatabase tables, an ArcIMS feature
108class, or an ArcIMS image service sublayer, don't enclose field
109names: 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
110specified in the ORDER BY clause of a SQL SELECT statement). If no
111fields are provided, the rows will be sorted in the default order
112determined by the underlying database. If this parameter is provided
113but the underlying database does not support ORDER BY clauses, an
114error will be raised.</p><p>In addition to specifying the ORDER BY fields, you must also specify
115the 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
116the sort directions for the ORDER BY fields. If this parameter is
117provided but the underlying database does not support ORDER BY
118clauses, 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 files 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 files 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
119outputs) obtained from the table are relative paths, they will be
120converted to absolute paths prior to processing, as follows:</p><ul><li>If a base path is provided, it will be prepended to the relative
121path.</li><li>Otherwise, if the ArcGIS geoprocessor has been initialized and the
122geoprocessing workspace has been set (i.e. the Workspace property of
123the geoprocessor is not empty), it will be prepended to the relative
124path.</li><li>Otherwise, the current working directory for the executing process
125will be prepended to the path. If you have not explicitly changed
126the working directory, it is usually the directory that contains the
127Python interpreter (e.g., on Windows computers, it would be
128C:\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="ToArcInfoASCIIGridList Method" href="Method_GeoEco.DataManagement.BinaryRasters.BinaryRaster.ToArcInfoASCIIGridList.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="BinaryRaster Class" href="Class_GeoEco.DataManagement.BinaryRasters.BinaryRaster.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.Directories Module" href="Module_GeoEco.DataManagement.Directories.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.BinaryRasters.BinaryRaster.ToArcInfoASCIIGridList.html?format=raw">ToArcInfoASCIIGridList Method</a> <b class="navlabel">Up:</b> <a class="sectref" href="Class_GeoEco.DataManagement.BinaryRasters.BinaryRaster.html?format=raw">BinaryRaster Class</a> <b class="navlabel">Next:</b> <a class="sectref" href="Module_GeoEco.DataManagement.Directories.html?format=raw">GeoEco.DataManagement.Directories Module</a> </div><hr /><span class="release-info">Marine Geospatial Ecology Tools version 0.7a12</span></div></div></body></html>
Note: See TracBrowser for help on using the browser.