ms_rectify_map: Rectify one map to another
In mapscanner: Print Maps, Draw on Them, Scan Them Back in

Rectify two previously scanned-in pdf or png maps with RNiftyReg, and return the modifications in map_modified as spatial objects in sf format.

ms_rectify_map(
  map_original,
  map_modified,
  nitems = NULL,
  non_linear = 1,
  type = "hulls",
  downsample = 10,
  concavity = 0,
  length_threshold = 10,
  quiet = FALSE
)

`map_original`	File name of the original map without anything drawn over it (either a `.pdf` or `.png`; extension will be ignored).
`map_modified`	File name of the modified version with drawings (either a `.pdf` or `.png`; extension will be ignored).
`nitems`	Optional parameter to explicitly specify number of distinct items to be extracted from map; if possible, specifying this parameter may improve results.
`non_linear`	Integer value of 0, 1, or 2 representing degree of non-linearity in modified image - see Note.
`type`	Currently either "points", "polygons", or "hulls", where "points" simply reduces each distinct object to a single, central point; "polygons" identifies individual groups and returns the polygon representing the outer boundary of each; and "hulls" constructs convex or concave polygons around each group.
`downsample`	Factor by which to downsample `type = "polygons"`, noting that polygons initially include every outer pixel of image, so can generally be downsampled by at least an order or magnitude (`n = 10`). Higher values may be used for higher-resolution images; lower values will generally only be necessary for very low lower resolution images.
`concavity`	For `type = "hulls"`, a value between 0 and 1, with 0 giving convex hulls and 1 giving highly concave hulls.
`length_threshold`	For `type = "hulls"`, the minimal length of a segment to be made more convex. Low values will produce highly detailed hulls which may cause problems; if in doubt, or if odd results appear, increase this value.
`quiet`	If `FALSE`, display progress information on screen

An sf object representing the drawn additions to map_modified.

The non-linear parameter should generally set according to how the modified maps were digitised. A value of 0 will give fastest results, and should be used for directly scanned or photocopied images. A value of 1 (the default) still presumes modified images have been linearly translated, and will apply affine transformations (rotations, contractions, dilations). This value should be used when modified images have been photographed (potentially from an oblique angle). A value of 2 should only be used when modified maps have somehow been non-linearly distorted, for example through having been crumpled or screwed up. Rectification with non-linear = 2 will likely take considerably longer than with lower values.

mapscanner documentation built on Nov. 26, 2021, 1:07 a.m.