Tool errors and warnings: 10076-10100 |
|
Release 9.3
Last modified April 24, 2009 |
|
Note:
This topic was updated for 9.3.1.
Error code: | 010076: Could not create INFO directory <value>. |
Description: | There was an error in creating the output raster |
Solution: | Check that you have proper write permissions to the output workspace and that there is sufficient available disk space. |
Error code: | 010077: Grid (expression) <value> must be of integer type. |
Description: | The type of the data specified in the expression must be of integer type.
Check the syntax of the command, which should indicate the expected input types. |
Solution: | You can convert a float raster to an integer one with the Int Math tool. |
Error code: | 010078: Argument <value> is not a coverage, shapefile or link file name. |
Description: | The source for the link information can only be in the form of a coverage, shapefile or a link file. |
Solution: | Specify the correct link information.
Check the following locations for more details on the link formats: |
Error code: | 010079: Unable to estimate semivariogram. |
Description: | The variance is calculated based upon the average variance of all point pairs within each interval of the cell size. The variogram is then fit to the variance points using the Levenberg-Marquardt Method (Press et al., 1986) of non-linear least squares approximation. A minimum of three points (a variance value at three distances) are required for the fit.
The message: Unable to estimate semivariogram indicates that there were not sufficient points to calculate a variance at the minimum of three distances. Reference: Press, W.H. et al. Numerical Recipes in C, The Art of Scientific Computing. New York: Cambridge University Press, 1988. |
Solution: | By increasing the cellsize, you will increase the number of sample points per cellsize interval, thereby providing enough data points to estimate the semivariogram. Once the semivariogram is estimated, a smaller cellsize can be used in creating the actual output raster. |
Error code: | 010080: Could not initialize the sample point structure. |
Description: | There was a problem processing the point data. |
Solution: | Check that the dataset exists as specified, and is valid. |
Error code: | 010081: No GRAPH option for universal kriging. |
Description: | The GRAPH option is not available with the UNIVERSAL1 and UNIVERSAL2 kriging methods. |
Solution: | Use a different method or unselect the GRAPH option. |
Error code: | 010082: Error in writing semi-variogram table. |
Description: | When either the BOTH or GRAPH options are used, the semi-variogram information will be written to an output INFO file called out_grid.SVG. If this file does not exist, it will be then be created. If it already exists, the new results will be appended.
This error will occur if an attempt to write to an existing file fails, perhaps as a result of being locked by another ArcMap or ArcCatalog session. |
Solution: | Ensure that out_grid.SVG INFO datafile is not write-protected. |
Error code: | 010083: The band count is not valid. Number of bands must lie between 1 and 30 (both inclusive). |
Description: | The number of bands in the specified raster or ESRI Grid stack must be more than 0 (an empty raster or stack) and not more than 30. |
Solution: | Make sure the raster or ESRI Grid stack you want to use has at least one raster, and that there are not more than 30 bands in the stack. |
Error code: | 010084: Invalid command or expression. |
Description: | The specified command or expression the command is used in is invalid.
This may occur if an improper command name was used, or if the syntax of the expression was incorrect. |
Solution: | Ensure that the syntax of the command is correct.
You can find the correct command names and syntax in the Functional Reference documentation. Also, review the documentation for Map Algebra expressions. |
Error code: | 010085: <value> is an invalid field name. |
Description: | The specified field name is invalid. |
Solution: | Check the input field name and make sure it adheres to the following conventions:
The underlying DBMS may impose additional restrictions on field names. |
Error code: | 010086: Field used for Logistic Trend must contain values 0 or 1 only. |
Description: | When the Regression type for Trend surface analysis is Logistic, the z-field should only contain values of 0 and 1. |
Solution: | Ensure that the z-field of your input point data only has values of 0 and 1. |
Error code: | 010087: Invalid filter type specified. |
Description: | The value you have specified for the Filter type is not one of valid options. It can only be LOW or HIGH.
You may have made a typing error. |
Solution: | Check your command string and make sure that the filter type is correct. |
Error code: | 010088: Invalid input geodataset (Layer, Tin, etc.). |
Description: | The specified geodataset is invalid for the conversion.
The syntax help for the command you are using should indicate the supported types of input data. For example, for the particular conversion a RasterLayer may be an invalid type of geodataset. |
Solution: | Specify the appropriate type of input geodataset. |
Error code: | 010089: <value> is not a supported feature type. |
Description: | The input feature class type is not valid for the tool.
For example, when a tool expects a point feature class, a line feature class should not be used as the input. The documentation for the tool will list the geometry types that are supported as input. |
Solution: | Ensure that your input feature class is of the correct geometry type. |
Error code: | 010090: An invalid or null filename was obtained from the path specification. |
Description: | A valid file name could not be found after parsing the specified input path. |
Solution: |
Check the input path or pathname to remove any invalid characters or symbols, such as *, ?, ", <, >, and |. For accessing data on a network folder, the UNC path should have the following syntax: \\<computer name>\<shared directory>\... For example: \\majestic12\data\groom_lk\... In Python scripting, note that the backward slash ("\") is reserved for other purposes, and "\\" or "/" should be used as the separator in a path. For example: \\majestic12\\data\\groom_lk\\... |
Error code: | 010091: Numeric field lengths must be less than or equal to 19. |
Description: | The input field name is not a valid numerical field name because it contains more than 19 characters. |
Solution: | Limit the length of your field name used in an operation.
Note that different DBMS may have different restrictions on the length of field names. |
Error code: | 010092: Invalid output extent. |
Description: | The extent specified either in the environment or as a parameter is invalid for the output that will be created. |
Solution: | Specify a valid extent for the output.
If you are not sure what to use, set the Output extent in the Environment to Default. |
Error code: | 010093: Output raster format <value> is unsupported. |
Description: | The output raster format specified is not supported. |
Solution: | Use a valid output format.
A complete list of raster formats are listed in Supported raster dataset file formats. |
Error code: | 0010094: Projections are incompatible for earth curvature corrections. |
Description: | The earth curvature correction is not applied when the projections of the input raster and observer features are different. |
Solution: | Project either the raster or the feature dataset to a common projection. |
Error code: | 010095: An invalid type of semi-variogram was used. |
Description: | The type of semivariogram used is invalid.
For example, esriGeoAnalysisNoneVariogram may have been specified by default. |
Solution: | Specify a valid semivariogram.
Check the Kriging syntax for more information. |
Error code: | 010096: There is no Spatial Analyst license currently available or enabled. |
Description: | The tool requires a Spatial Analyst extension license.
The conditions where a license may not be available are:
|
Solution: |
|
Error code: | 010097: Unable to create the output of more than <value> cells. |
Description: | Unable to create the output raster of more than the specified number of cells. |
Solution: | Clip the input data into smaller datasets and run the tool on each of the smaller datasets, then mosaic the output datasets into one final raster.
Alternatively, you can set a larger cell size for the output raster to reduce the number of cells in the output raster. |
Error code: | 010098: Insufficient number of points. |
Description: | The polynomial transformation of the raster failed because there is not enough control points to solve the equation. |
Solution: | Create more control points to use in the transformation (Warp (Data Management) or Warp).
The number of points required by the tool is dependent on the type of transformation. |
Error code: | 010099: The number of classes must be 2 or more. |
Description: | When performing a classification, generally you are classifying a series of raster bands into classes. The classes are defined by the statistical properties of the identified classes. The classes can be identified by specified polygons (a supervised classification) or by a statistical groupings for a specified number of classes (an unsupervised classification).
If you specify less than two classes then you are telling ArcGIS to classify all cell values into one class. If this is the desired result, do not use the multivariate tools, use the reclass tools. |
Solution: | Make sure you specify more than one class. |
Error code: | 010100: The number of principal components cannot be larger than the number of bands to be used. |
Description: | A Principal Component Analysis describes the variability of the input bands. The first principal component describes the most variability defined by the input bands. The second principal component describes additional variability but less than the first principal component. The third component additional variability but less than the second, and so forth.
The analysis is known as a data reduction technique by describing the most variability in the least amount of bands. If all the variability is defined by the initial bands, by definition you cannot define more variability than that which is already present by using more than the number of bands in the input raster. |
Solution: | Make sure the number of principal components is less than or equal to the number of bands in the raster or ESRI Grid stack. |