assess_polygons: Assess the geometry of a polygon
In GRID3/polyCheck: Verifies delineated polygons for the GRID3 project.

Description Usage Arguments Details Author(s) See Also

Runs a number of diagnostics on the delineated polygons to check the geometry. Checks the field parameters, the area of settled area covered and shape complexity. See the details for more information.

1 2	assess_polygons(polygons, survey_points, settlement_points, ornl, merged_polygons = NULL, progress = FALSE)

`survey_points`	Optional. The survey points where the delineation should occur
`settlement_points`	Optional. The settlement type points layer
`ornl`	Optional. A shapefile of the previously surveyed locations
`merged_polygons`	Optional. A SpatialPolygonDataFrame of the delineated polygons created from the `merge_delineated_polygons` function.
`progress`	should messages be displayed for the progress through the polygons? Default is TRUE

The full diagnostics checked are as follows:

Shapefile fields: check that the shapefiles contain the right date formats, ID etc.
Number of polygons per file: each file should only contain a single shapefile.
Coordinate reference system: each file should have a CRS of WGS84.
Proximity of polygon from survey point: the survey point should be contained within the polygon. However, it is sometimes not possible to locate sufficient settled area within the local area, and therefore there can be valid exceptions where there is a gap between the two.
Settled Area Covered: the polygon should cover between 450 and 550 settlement points.
Proportion of settlement type matching: the sample points have been selected to represent a single type of settlement area. The delineated survey area should cover a single area, although having a small percentage of other areas is not a major problem.
ORNL Overlap: the survey areas should not overlap areas which have previously been surveyed.

Additional diagnostics are provided which may also provide indications of polygons which require further inspection:

Shape Complexity: the number of sides of the polygon is extracted. Ideally, polygons should follow simple geometric elements but this is not always possible.
Polsby Popper: this is a test of compactness comparing the area against the perimeter of the shape. A value of 1 indicates a perfect circle. Ideally, shapes should not be too long and thin as these can be more difficult to survey.

Michael Harper

Polsby Popper Definition: https://www.azavea.com/blog/2016/07/11/measuring-district-compactness-postgis/

GRID3/polyCheck documentation built on May 26, 2019, 8:35 a.m.