Tool errors and warnings: 10201-10225 |
|
Release 9.3
Last modified April 24, 2009 |
![]() ![]() ![]()
|
Note:
This topic was updated for 9.3.1.
Error code: | 010201: PATHDISTANCE: Error in vertical factor modifiers. |
Description: | There was an error in specifying the modifiers for the vertical factor parameters.
Vertical factor parameters define the relationship between the vertical cost factor and the vertical relative moving angle (VRMA). The parameters are comprised of a keyword that specifies the vertical factor type and modifiers that apply to that type.
See the documentation for the PathDistance function you are using for further information on the factor and its parameters. As an example, a valid vertical factor parameter is: "LINEAR SLOPE=0.0111". |
Solution: | Check the following:
|
Error code: | 010202: PATHDISTANCE: Format error in the vertical factor parameter file. |
Description: | The vertical factor parameter file is incorrectly formatted.
The vertical factor file or table is an ASCII file with two columns. The first column identifies the vertical relative moving angle (VRMA) in degrees, and the second, the vertical factor (VF). Each line in the file specifies a point in a vertical factor graph. Two consecutive points produce a line segment in the VRMA-VF coordinate system. The angles must be in input in ascending order. |
Solution: | Check the following to ensure the horizontal factor parameter file is in the correct format:
|
Error code: | 010203: PATHDISTANCE: High cut angle is not between 0 to 90. |
Description: | The value specified for the high cut angle is not in expected range.
The vertical factor influences the total cost of moving into a cell by accounting for any vertical friction encountered. Determining the vertical cost for each cell is a two-step process. First, the prevailing vertical direction is defined by calculating the slope between each cell from the heights defined on the vertical-factor raster. This slope defines the vertical relative moving angle (VRMA). Once the VRMA is calculated, the vertical resistance to overcome the vertical factor is identified from the vertical factor graph. Since the VRMA is a degree of slope, it can only range from -90 (going down) to 90 (going up). The High cut angle identifies the threshold VRMA at which any VRMA equal to or greater than are assigned to infinity for the VF. In order to function as a barrier, the High cut angle needs to be between 0 and 90 since it defines the threshold to assign to infinity of a positive or up hill slope. |
Solution: | Make sure the specified high cut angle is between 0 and 90. |
Error code: | 010204: PATHDISTANCE: Illegal vertical factor modifier. |
Description: | The vertical factor modifier is not valid.
Vertical factor parameters define the relationship between the vertical cost factor and the vertical relative moving angle (VRMA). The parameters are comprised of a keyword specifying an existing graph or Table for a custom graph created from an ASCII file. The keyword parameters can have modifiers, and the entire string must be enclosed in quotes. Spaces must separate the keyword and modifiers. The format for vertical parameter modifiers is: "modifer_name=value". Valid vertical keywords are BINARY, LINEAR, SYM_LINEAR, SYM_INVERSE_LINEAR, COS, SEC, COS-SEC, SEC-COS, and TABLE. The valid modifiers are: ZEROFACTOR, LCUTANGLE, HCUTANGLE, SLOPE, and table_name. For example, a valid vertical factor parameter is "LINEAR SLOPE=0.0111". |
Solution: | The following list of issues identifies how to resolve the most common problems encountered with the vertical factor parameters:
The documentation for How PathDistance works gives more information on the formatting of the parameter file. |
Error code: | 010205: PATHDISTANCE: Low cut angle is not between -90 to 0. |
Description: | The value specified for the low cut angle is not in the expected range.
The vertical factor influences the total cost of moving into a cell by accounting for any vertical friction encountered. Determining the vertical cost for each cell is a two-step process. First, the prevailing vertical direction is defined by calculating the slope between each cell from the heights defined on the vertical-factor raster. This slope defines the vertical relative moving angle (VRMA). Once the VRMA is calculated, the vertical resistance to overcome the vertical factor is identified from the vertical factor graph. Since the VRMA is a degree of slope it can only range from -90 (going down) to 90 (going up). The Low cut angle identifies the threshold VRMA at which any VRMA equal to or less than are assigned to infinity for the VF. In order to function as a barrier, the Low cut angle needs to be between -90 and 0 since it defines the threshold to assign to infinity of a negative or down hill slope. |
Solution: | Make sure the specified low cut angle is between -90 and 0. |
Error code: | 010206: PATHDISTANCE: Undefined vertical factor parameters. |
Description: | The vertical factor parameters have not been correctly defined.
Vertical factor parameters define the relationship between the vertical cost factor and the vertical relative moving angle (VRMA). The parameters are comprised of a keyword specifying an existing graph or TABLE for a custom graph created from an ASCII file and modifiers. The keyword parameter and modifiers need to be in quotes. Spaces must separate the keyword and modifiers. The format for vertical parameter modifiers is modifier_name=value. Valid vertical keywords are BINARY, LINEAR, SYM_LINEAR, SYM_INVERSE_LINEAR, COS, SEC, COS-SEC, SEC-COS, and TABLE. Valid vertical factor modifiers to the keywords are ZEROFACTOR, LCUTANGLE, HCUTANGLE, SLOPE, and table_name. For example, a valid vertical factor parameter is "LINEAR SLOPE=0.0111". |
Solution: |
|
Error code: | 010207: PATHDISTANCE: Wrong vertical factor type keyword. |
Description: | The specified keyword for horizontal factor type is invalid.
Vertical factor parameters define the relationship between the vertical cost factor and the vertical relative moving angle (VRMA). The parameters are comprised of a keyword specifying an existing graph or TABLE for a custom graph created from an ASCII file and modifiers. The keyword parameter and modifiers need to be in quotes. Spaces must separate the keyword and modifiers. The format for vertical parameter modifiers is modifier_name=value. Valid vertical keywords are BINARY, LINEAR, SYM_LINEAR, SYM_INVERSE_LINEAR, COS, SEC, COS-SEC, SEC-COS, and TABLE. |
Solution: | Make sure a valid keyword is specified for the vertical factor.
The documentation for How PathDistance works gives more information on the formatting of the parameter file. |
Error code: | 010208: The PRJ of grid <value> does not match. |
Description: | The projection of the grid does not match the others.
When creating a grid stack, the input grids ordinarily all need to be the same coordinate system. Note that if an input does not have a coordinate system defined, it will be assumed to be the same projection as that defined in the other inputs. |
Solution: | Make sure that all of your inputs have the same coordinate system.
You can use Project Raster to project the raster to that of the other datasets. |
Error code: | 010209: <value> and <value> have incompatible projections. |
Description: | The input geodatasets have incompatible projections, and the Spatial Analyst function cannot be performed with them. |
Solution: | Either project one of the datasets to be the same as the other, or project them both to a mutually compatible projection.
Use the Project Raster or Project tools to project the data. Use this Project if you are using a coverage dataset. |
Error code: | 010210: Source location is out of the working window. |
Description: | The location of the source point dataset is either outside of the input data extent or outside of the output extent. |
Solution: | Check the coordinate of the source point and make sure that it is within the dataset or output extent. |
Error code: | 010211: Could not open the specified point file <value>. |
Description: | The input point file could not be read.
This might happen if you do not have the appropriate permissions to read the file. The point file may also be incorrectly formatted or an invalid ASCII text file. |
Solution: |
|
Error code: | 010212: Unable to read <value> from <value>. |
Description: | There was a problem reading the specified component (value1) of the input dataset (value2).
This might occur if the component is missing or possibly has been corrupted. |
Solution: | Check that the dataset is valid. If it is not, you may need to re-create it or retrieve a back-up copy if you have one. |
Error code: | 010213: Error in reading grid <value>. |
Description: | There was a error encountered when trying to read the specified grid.
Problems accessing a grid are most commonly the result of missing required component files in the grid's folder. Consult the documentation too see the required files for the About the ESRI Grid format. If all of the required components are present, it is also possible that the files that contain the binary raster data are internally corrupted. |
Solution: |
|
Error code: | 010214: Unable to read <value> of <value>. |
Description: | There was a problem reading the specified component (value1) of the input dataset (value2).
This might occur if the component is missing or possibly has been corrupted. |
Solution: | Check that the dataset is valid. If it is not, you may need to re-create it or retrieve a back-up copy if you have one. |
Error code: | 010215: Unable to read record <value> of file <value>. |
Description: | There was a failure in reading the specified record from the file. |
Solution: | Re-create or re-copy the file and try to run the tool again.
If the file is an INFO table, it may be corrupted because of incorrect handling of the table, such as copying or moving it using your operation system file manager instead of ArcCatalog. |
Error code: | 010216: Error in opening or reading attribute table (VAT) for <value>. |
Description: | The attribute table (VAT) of the input raster layer could not be accessed.
It is either missing or may be corrupted. |
Solution: | You may have accidentally deleted or corrupted the attribute table under the raster dataset workspace.
The attribute table can be rebuilt with the Build Raster Attribute Table tool, or BuildVAT in the Raster Calculator for ESRI Grids. To avoid corrupting the attribute table in the future, do not edit them or manually delete them with Windows Explorer. Use the Delete Raster Attribute Table tool to remove them instead. |
Error code: | 010217: Unable to reclass on the selection set. |
Description: | The selected values cannot be classified according to the specified remap values. |
Solution: | The selected values for analysis must be within the specified remap records to be classified.
Make sure that your selection was successful and you the selection set contains data to be classified according to the remap. |
Error code: | 010218: Could not reference the grid dataset. |
Description: | There was a problem in referencing a grid raster.
This may occur if the dataset does not exist at the location specified, or if you do not have the ability to access the location. |
Solution: | Ensure that the grid exists at the location specified, you have the appropriate permission to the directory, and the dataset is valid. |
Error code: | 010219: Bad single value remap record. Must have the lowest-output keyword defined. |
Description: | The specified remap file is formatted incorrectly. The lowest-output keyword is not defined. |
Solution: | Correct the remap table by defining the value for the lowest-output keyword.
See Using reclassification tables for more information on the format. |
Error code: | 010220: Duplicate remap record encountered. |
Description: | The specified remap file is formatted incorrectly. There is a duplicate entry. |
Solution: | Correct the remap table by removing any duplicate entries.
See Using reclassification tables for more information on the format. |
Error code: | 010221: Could not fill the string remap records table. |
Description: | The specified remap file is formatted incorrectly. |
Solution: | Correct the remap table.
See Using reclassification tables for more information on the format. |
Error code: | 010222: Error occurred while freeing remap object records. |
Description: | There is an error when clearing the remap objects. |
Solution: | Check the syntax and ensure the correct parameter information is specified when using the IRemap::DeleteRecord or IRemap::QueryRecord methods. |
Error code: | 010223: Could not find remap record by specified index. |
Description: | There was a problem when trying to query or delete the remap records, and the remap record information of the specified index could not be returned. |
Solution: | Make sure the correct parameter information is specified when using the IRemap::DeleteRecord or IRemap::QueryRecord methods. |
Error code: | 010224: Encountered multiple (single value, range, etc.) types of remap records in the same file. |
Description: | The remap file specified is formatted incorrectly. It has several different types of remap records. |
Solution: | Correct the remap table by using the same format for all of the remap records.
See Using reclassification tables for more information on the format. |
Error code: | 010225: A number remap object type is required. |
Description: | The remap table specified is formatted incorrectly. It must be an input object that supports the IRemap interface. |
Solution: | If reclassifying numbers, use the NumberRemap object. If reclassifying string values, use the StringRemap object.
See Reclass by Remap for more information. |