diff --git a/man/geom_edge_bundle_force.Rd b/man/geom_edge_bundle_force.Rd index 6a544c80..4be4c551 100644 --- a/man/geom_edge_bundle_force.Rd +++ b/man/geom_edge_bundle_force.Rd @@ -302,6 +302,7 @@ Other geom_edge_*: \code{\link{geom_edge_loop}()}, \code{\link{geom_edge_parallel}()}, \code{\link{geom_edge_point}()}, +\code{\link{geom_edge_sf}()}, \code{\link{geom_edge_span}()}, \code{\link{geom_edge_tile}()} } diff --git a/man/geom_edge_bundle_minimal.Rd b/man/geom_edge_bundle_minimal.Rd index f92aad40..4c52743c 100644 --- a/man/geom_edge_bundle_minimal.Rd +++ b/man/geom_edge_bundle_minimal.Rd @@ -277,6 +277,7 @@ Other geom_edge_*: \code{\link{geom_edge_loop}()}, \code{\link{geom_edge_parallel}()}, \code{\link{geom_edge_point}()}, +\code{\link{geom_edge_sf}()}, \code{\link{geom_edge_span}()}, \code{\link{geom_edge_tile}()} } diff --git a/man/geom_edge_bundle_path.Rd b/man/geom_edge_bundle_path.Rd index b3963fb3..5bb842e9 100644 --- a/man/geom_edge_bundle_path.Rd +++ b/man/geom_edge_bundle_path.Rd @@ -291,6 +291,7 @@ Other geom_edge_*: \code{\link{geom_edge_loop}()}, \code{\link{geom_edge_parallel}()}, \code{\link{geom_edge_point}()}, +\code{\link{geom_edge_sf}()}, \code{\link{geom_edge_span}()}, \code{\link{geom_edge_tile}()} } diff --git a/man/geom_edge_sf.Rd b/man/geom_edge_sf.Rd index cacc112b..d4e63741 100644 --- a/man/geom_edge_sf.Rd +++ b/man/geom_edge_sf.Rd @@ -32,8 +32,10 @@ the plot data. The return value must be a \code{data.frame}, and will be used as the layer data. A \code{function} can be created from a \code{formula} (e.g. \code{~ head(.x, 10)}).} -\item{position}{Position adjustment, either as a string, or the result of -a call to a position adjustment function.} +\item{position}{Position adjustment, either as a string naming the adjustment +(e.g. \code{"jitter"} to use \code{position_jitter}), or the result of a call to a +position adjustment function. Use the latter if you need to change the +settings of the adjustment.} \item{show.legend}{logical. Should this layer be included in the legends? \code{NA}, the default, includes if any aesthetics are mapped. @@ -74,6 +76,9 @@ if (require("sfnetworks", quietly = TRUE)) { Other geom_edge_*: \code{\link{geom_edge_arc}()}, \code{\link{geom_edge_bend}()}, +\code{\link{geom_edge_bundle_force}()}, +\code{\link{geom_edge_bundle_minimal}()}, +\code{\link{geom_edge_bundle_path}()}, \code{\link{geom_edge_density}()}, \code{\link{geom_edge_diagonal}()}, \code{\link{geom_edge_elbow}()}, diff --git a/man/geom_node_sf.Rd b/man/geom_node_sf.Rd index 197a796a..3aa8dc06 100644 --- a/man/geom_node_sf.Rd +++ b/man/geom_node_sf.Rd @@ -32,8 +32,10 @@ the plot data. The return value must be a \code{data.frame}, and will be used as the layer data. A \code{function} can be created from a \code{formula} (e.g. \code{~ head(.x, 10)}).} -\item{position}{Position adjustment, either as a string, or the result of -a call to a position adjustment function.} +\item{position}{Position adjustment, either as a string naming the adjustment +(e.g. \code{"jitter"} to use \code{position_jitter}), or the result of a call to a +position adjustment function. Use the latter if you need to change the +settings of the adjustment.} \item{show.legend}{logical. Should this layer be included in the legends? \code{NA}, the default, includes if any aesthetics are mapped. diff --git a/man/ggraph-extensions.Rd b/man/ggraph-extensions.Rd new file mode 100644 index 00000000..aa1049a4 --- /dev/null +++ b/man/ggraph-extensions.Rd @@ -0,0 +1,103 @@ +% Generated by roxygen2: do not edit by hand +% Please edit documentation in R/aaa.R, R/facet_edges.R, R/facet_graph.R, +% R/facet_nodes.R, R/geom_axis_hive.R, R/geom_conn_bundle.R, R/geom_edge.R, +% R/geom_edge_arc.R, R/geom_edge_bend.R, R/geom_edge_bundle_force.R, +% R/geom_edge_bundle_minimal.R, R/geom_edge_bundle_path.R, +% R/geom_edge_density.R, R/geom_edge_diagonal.R, R/geom_edge_elbow.R, +% R/geom_edge_fan.R, R/geom_edge_hive.R, R/geom_edge_link.R, +% R/geom_edge_loop.R, R/geom_edge_parallel.R, R/geom_edge_sf.R, +% R/geom_node_arc_bar.R, R/geom_node_circle.R, R/geom_node_tile.R, +% R/geom_node_voronoi.R, R/ggproto-classes.R +\docType{data} +\name{StatFilter} +\alias{StatFilter} +\alias{StatReverse} +\alias{StatFilterSf} +\alias{FacetEdges} +\alias{FacetGraph} +\alias{FacetNodes} +\alias{StatAxisHive} +\alias{GeomAxisHive} +\alias{StatConnBundle} +\alias{StatConnBundle2} +\alias{StatConnBundle0} +\alias{GeomEdgePath} +\alias{GeomEdgeParallelPath} +\alias{GeomEdgeSegment} +\alias{GeomEdgeParallelSegment} +\alias{GeomEdgeSpanPath} +\alias{GeomEdgeSpanSegment} +\alias{GeomEdgePoint} +\alias{GeomEdgeTile} +\alias{GeomEdgeBezier} +\alias{GeomEdgeBspline} +\alias{StatEdgeArc} +\alias{StatEdgeArc2} +\alias{StatEdgeArc0} +\alias{StatEdgeBend} +\alias{StatEdgeBend2} +\alias{StatEdgeBend0} +\alias{StatEdgeBundleForce} +\alias{StatEdgeBundleForce2} +\alias{StatEdgeBundleForce0} +\alias{StatEdgeBundleMinimal} +\alias{StatEdgeBundleMinimal2} +\alias{StatEdgeBundleMinimal0} +\alias{StatEdgeBundlePath} +\alias{StatEdgeBundlePath2} +\alias{StatEdgeBundlePath0} +\alias{StatEdgeDensity} +\alias{GeomEdgeDensity} +\alias{StatEdgeDiagonal} +\alias{StatEdgeDiagonal2} +\alias{StatEdgeDiagonal0} +\alias{StatEdgeElbow} +\alias{StatEdgeElbow2} +\alias{StatEdgeElbow0} +\alias{StatEdgeFan} +\alias{StatEdgeFan2} +\alias{StatEdgeFan0} +\alias{StatEdgeHive} +\alias{StatEdgeHive2} +\alias{StatEdgeHive0} +\alias{StatEdgeLink} +\alias{StatEdgeLink2} +\alias{StatEdgeLoop} +\alias{StatEdgeLoop0} +\alias{StatEdgeParallel} +\alias{StatEdgeParallel2} +\alias{StatEdgeParallel0} +\alias{GeomEdgeSf} +\alias{StatNodeArcBar} +\alias{StatNodeCircle} +\alias{GeomNodeTile} +\alias{StatNodeVoronoi} +\alias{ggraph-extensions} +\title{ggraph extensions to ggplot2} +\description{ +This help page lists all exported ggproto classes defined by ggraph. In +general these should be of no concern to the user as the main interface to +the functionality is, as with ggplot2, the \verb{geom_*} format. As opposed +to ggplot2 there really aren't any use for separate \verb{stat_*} functions +as they are intimately linked to each geom and mixing and matching stats and +geoms would only cause a lot of trouble. +} +\details{ +Many of the \verb{geom_edge_*} geoms comes in different flavors dependent on +the functionality required. There will always be a base geom and some will +have a \code{geom_edge_*0} and \code{geom_edge_*2} version. The base geom +will, in the case of multiple versions, draw the edge as a sequence of small +segments. The different aesthetics will be repeated for each segment and a +counter will be added the enumerates the progression of segments, so that a +gradient of colour or size can be added along the edge by assigning the +respective aesthetic to \code{after_stat(index)}. \code{geom_edge_*2} will also draw +the edge as segments but will interpolate between the aesthetics at the end +points. This makes it possible for an edge to interpolate node properties of +its end nodes. \code{geom_edge_*2} is less performant than the base geom so +use only when interpolation is needed. \code{geom_edge_*0} is a +high-performance version that usually maps directly to a grid grob. It does +not allow for drawing gradients or interpolations though, so use only for +simple edge drawings. +} +\keyword{datasets} +\keyword{internal} diff --git a/man/layout_tbl_graph_cactustree.Rd b/man/layout_tbl_graph_cactustree.Rd index ca964ba1..07266ba1 100644 --- a/man/layout_tbl_graph_cactustree.Rd +++ b/man/layout_tbl_graph_cactustree.Rd @@ -76,6 +76,7 @@ Other layout_tbl_graph_*: \code{\link{layout_tbl_graph_matrix}()}, \code{\link{layout_tbl_graph_partition}()}, \code{\link{layout_tbl_graph_pmds}()}, +\code{\link{layout_tbl_graph_sf}()}, \code{\link{layout_tbl_graph_stress}()}, \code{\link{layout_tbl_graph_treemap}()}, \code{\link{layout_tbl_graph_unrooted}()} diff --git a/man/layout_tbl_graph_htree.Rd b/man/layout_tbl_graph_htree.Rd index b2f88544..22a08811 100644 --- a/man/layout_tbl_graph_htree.Rd +++ b/man/layout_tbl_graph_htree.Rd @@ -56,6 +56,7 @@ Other layout_tbl_graph_*: \code{\link{layout_tbl_graph_matrix}()}, \code{\link{layout_tbl_graph_partition}()}, \code{\link{layout_tbl_graph_pmds}()}, +\code{\link{layout_tbl_graph_sf}()}, \code{\link{layout_tbl_graph_stress}()}, \code{\link{layout_tbl_graph_treemap}()}, \code{\link{layout_tbl_graph_unrooted}()} diff --git a/man/layout_tbl_graph_sf.Rd b/man/layout_tbl_graph_sf.Rd index 9f5c69e7..579db56b 100644 --- a/man/layout_tbl_graph_sf.Rd +++ b/man/layout_tbl_graph_sf.Rd @@ -22,6 +22,7 @@ plot a graph on its geographical space, by extracting its X and Y coordinates Other layout_tbl_graph_*: \code{\link{layout_tbl_graph_auto}()}, \code{\link{layout_tbl_graph_backbone}()}, +\code{\link{layout_tbl_graph_cactustree}()}, \code{\link{layout_tbl_graph_centrality}()}, \code{\link{layout_tbl_graph_circlepack}()}, \code{\link{layout_tbl_graph_dendrogram}()}, @@ -29,6 +30,7 @@ Other layout_tbl_graph_*: \code{\link{layout_tbl_graph_fabric}()}, \code{\link{layout_tbl_graph_focus}()}, \code{\link{layout_tbl_graph_hive}()}, +\code{\link{layout_tbl_graph_htree}()}, \code{\link{layout_tbl_graph_igraph}()}, \code{\link{layout_tbl_graph_linear}()}, \code{\link{layout_tbl_graph_manual}()},