File: drape3d.Rd

package info (click to toggle)
rgl 1.3.34-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 13,968 kB
  • sloc: cpp: 23,234; ansic: 7,462; javascript: 6,125; sh: 3,555; makefile: 2
file content (104 lines) | stat: -rw-r--r-- 2,989 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
\name{drape3d}
\alias{drape3d}
\alias{drape3d.default}
\alias{drape3d.mesh3d}
\title{
Drape lines over a scene.
}
\description{
Project a line onto the surface in a scene so that it appears to drape itself
onto the surface.
}
\usage{
drape3d(obj, ...)
\method{drape3d}{mesh3d}(obj, x, y = NULL, z = NULL, plot = TRUE,
                         up = c(0, 0, 1),
                         P = projectDown(up), ...)
\method{drape3d}{default}(obj, ...)
}
\arguments{
  \item{obj}{
The object(s) upon which to drape lines.
}
  \item{x,y,z}{Coordinates of the line segments
to be draped.  Any reasonable way of defining the
coordinates is acceptable.  See the function \code{\link[grDevices]{xyz.coords}} for details.
}
  \item{plot}{
Should the result be plotted, or returned as a data frame?
}
  \item{up}{
The direction to consider as \dQuote{up}.
  }
  \item{P}{
The projection to use for draping, a 4x4 matrix.
  }
  \item{\dots}{
For the \code{"mesh3d"} method, additional parameters to pass to \code{\link{segments3d}}
when drawing the draped lines.
For the \code{"default"} method, additional parameters to pass to the
\code{"mesh3d"} method.
}
}
\details{
The default method converts \code{obj} to a mesh
using \code{\link{as.mesh3d}}, then uses the \code{"mesh3d"}
method.

The current implementation constructs the segments to drape
across the surface using the same method as
\code{\link{lines3d}} uses:  each successive point is
joined to the previous one.  Use \code{NA} coordinates to
indicate breaks in the line.

The \code{P} matrix is used to project points to a plane as
follows:  They are transformed by \code{P} in 
homogeneous coordinates, then only first two (Euclidean)
coordinates are kept.
}
\value{
If \code{plot = TRUE}, 
plots the result and invisibly returns the object ID of the collection of segments. 

If \code{plot = FALSE}, returns a matrix containing "x", "y" and "z"
values for the line(s) 
(for use with \code{\link{segments3d}}),
}
\author{
George Helffrich and Duncan Murdoch
}
\seealso{\code{\link{shadow3d}}, \code{\link{facing3d}}}
\examples{
#
# volcano example taken from "persp"
#

z <- 2 * volcano        # Exaggerate the relief

x <- 10 * (1:nrow(z))   # 10 meter spacing (S to N)
y <- 10 * (1:ncol(z))   # 10 meter spacing (E to W)

zlim <- range(z)
zlen <- zlim[2] - zlim[1] + 1

colorlut <- terrain.colors(zlen) # height color lookup table

col <- colorlut[ z - zlim[1] + 1 ] # assign colors to heights for each point

open3d()
id <- surface3d(x, y, z, color = col, polygon_offset = 1)

segs <- data.frame(x = range(x) + c(100, -100),
                   y = range(y) + c(150, -100), z = 325)
drape3d(id, segs, col = 'yellow', lwd = 3)
lines3d(segs, col='red', lwd=3)

p <- c(350, 205)         # (x,y) of strike & dip reading
off <- 20*c(-1, +1)      # X-marks-the-spot offset
segs <- data.frame(
    x = c(p[1] + off, NA, p[1] + off),
    y = c(p[2] + off, NA, p[2] - off),
    z = rep(350, 5)
    )
drape3d(id, segs, col = "yellow", lwd = 3)
}