link_compar | R Documentation |
The function compares two link sets created in a Graphab project both quantitatively and spatially.
link_compar( proj_name, linkset1, linkset2, buffer_width = 200, min_length = NULL, proj_path = NULL )
proj_name |
A character string indicating the Graphab project name.
The project name is also the name of the project directory in which the
file proj_name.xml is. It can be created with |
linkset1 |
A character string indicating the name of the first link set
involved in the comparison. The link set has to be present in the project
and can be created with |
linkset2 |
A character string indicating the name of the second link set
involved in the comparison. The link set has to be present in the project
and can be created with |
buffer_width |
(default=200) An integer or numeric value indicating the width of the buffer created in each side of the links prior to spatial intersection. It is expressed in meters. |
min_length |
(optional, default=NULL) An integer or numeric value
indicating the minimum length in meters of the links to be compared. Links
whose length is larger than |
proj_path |
(optional, default=NULL) A character string indicating the
path to the directory that contains the project directory. It should be used
when the project directory is not in the current working directory.
Default is NULL. When 'proj_path = NULL', the project directory is equal
to |
The function compares two link sets linking the same habitat patches of the Graphab project but computed using different cost scenarios. It creates a buffer in each side of every link and then overlaps every link in linkset1 with the same link in linkset2. It returns the area of both buffered links and the area of their intersection. It also computes the Mantel correlation coefficient between the cost distances associated to the same links in both linksets.
P. Savary
## Not run: link_compar(proj_name = "grphb_ex", linkset1 = "lcp1", linkset2 = "lcp2" buffer_width = 200) ## End(Not run)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.