Troubleshooting Undefined Values In Lcc Xml Document - USEPA/ATtILA2 GitHub Wiki

Undefined Values in LCC XML Document

For tools in ATtILA that utilize an LCC XML document, (i.e., tools that utilize a land cover raster input) ATtILA will examine all of the values found in that tool's selected land cover raster and compare them to those values supplied in the LCC XML document. The values in the LCC XML document are gathered from both the Values Element section of the document and the Classes Element section. Any values found in the grid but not found in the LCC XML document will be reported to the user with a warning message is added to the tool's View Details box and the Geoprocessing > History window. The user can then determine if the reported values were either accidentally or purposely omitted from the LCC XML document or were possibly incorrectly transcribed. A report of missing values may also indicate that the wrong LCC Schema was selected for the input raster layer, or that the wrong raster layer was input for the selected LCC Schema.

Example:

LCC XML file: grid value(s) [31, 41, 42, 43, 52, 71, 81, 82, 90, 95] undefined in LCC XML file - Please refer to the ATtILA documentation regarding undefined values.

NOTE: Not all values found in the land cover grid need to be included in the LCC XML document. Only land cover values that are of interest to the user (e.g., values for forest or agriculture land cover types) need to be accounted for. If this is the case, and the LCC XML document was constructed to analyze only a subset of land cover classes from the land cover raster, then the warning message from ATtILA from ArcGIS is superfluous and can be ignored.


arrow_up Top of the page     |     arrow_left Unable to Determine Conversion Factor     |     arrow_right Appendix


⚠️ **GitHub.com Fallback** ⚠️