Tool Population Land Cover Views
Estimates the percentage of the population in each reporting unit that have potential views of selected land cover classes within a given distance from their location and creates an output table. A land cover class is visible if it is found within the neighborhood defined by the View radius and in a group of cells larger than or equal to the Minimum visible patch size. The Minimum visible patch size and View radius are provided by the user.
Additional fields for total population count within the reporting unit, the total population count in the reporting unit with potential views, the total population count in the reporting unit without potential views, and the percentage of the total population in the reporting unit without potential views are also output.
To be edited.
PLCV (Reporting_unit_feature, Reporting_unit_ID_field, Land_cover_grid, Land_cover_classification_scheme, Land_cover_classification_file, Report_metrics_for_these_classes, View_radius, Minimum_visible_patch_size, Population_raster, Output_table, {Processing_cell_size}, {Snap_raster}, Select_options)
| Parameter | Explanation | Data Type |
|---|---|---|
| Reporting_unit_feature | The vector polygon dataset that defines the reporting units. | Feature Layer |
| Reporting_unit_ID_field | The field in the Reporting unit feature layer that contains the unique ID for each reporting unit. It may be an integer or a string data type. |
Field |
| Land_cover_grid | The raster dataset representing land cover classes to be summarized within each Reporting unit feature. The grid input must be an integer raster layer. |
Raster Layer |
| Land_cover_classification_scheme | The land cover classification schemes included in ATtILA and a User Defined option. The default schemes correspond to common input land cover datasets. Two schemes are supplied for each dataset included in ATtILA:
|
String |
| Land_cover_classification_file | The full pathname to the user-defined .xml file for custom or non-standard land cover classification schemes. Pathname is automatically filled when a default scheme is selected. |
File |
| Report_metrics_for_these_classes | A list of the land cover classes and metric combinations for processing. Check the box to calculate metrics for each land cover class and/or combination class desired within the reporting units. |
Multiple Value |
| View_radius | The radius of the view neighborhood, measured in number of grid cells. The input must be an integer value. |
Long |
| Minimum_visible_patch_size | The minimum patch size, measured in number of grid cells, necessary to be considered a visible patch. Connectivity is defined within the immediate eight-cell neighborhood. Cells of the same class to the right, left, above, below, or diagonal to each other are considered as part of the same patch. The input must be an integer value. |
Long |
| Population_raster | The raster dataset that contains population data. The grid input can be either an integer or floating-point raster layer. |
Raster Layer |
| Output_table | The output reporting unit metrics table to be created. It is recommended that the Output table be saved within a file geodatabase. |
Table |
| Select_options (Optional) | One tool option is available to provide additional information:
|
Multiple Value |
Population Land Cover Views example (Python window)
NOTE: ATtILA tools that utilize the Report metrics for these classes parameter will clear all class selections when the tool is opened. This results in setting any variable set for that parameter to None when calling the tool from a script. Because of this, the standard scripting syntax (e.g. arcpy.ATtILA.LCP(variable 1, variable 2, variable 3, etc.) will fail. To overcome this idiosyncrasy, use the scripting example provided below. When using this technique, all variables are passed in as strings.
There are no tags for this item.
There are no credits for this item.
There are no access and use limitations for this item.
Page
