@@ -40,7 +40,7 @@ <h2>NOTES</h2>
40
40
and north-south spline step length arguments allows the user to
41
41
account for some degree of anisotropy in the distribution of
42
42
observation points. Short spline step lengths, especially spline step
43
- lengths that are less than the distance between observation points,
43
+ lengths that are less than the distance between observation points,
44
44
can greatly increase the processing time.
45
45
46
46
< p > The maximum number of splines for each direction at each
@@ -64,15 +64,15 @@ <h2>NOTES</h2>
64
64
65
65
< p > < em > v.surf.bspline</ em > can produce raster (< b > raster_output</ b > ) OR
66
66
vector < b > output</ b > but NOT simultaneously. Note that topology is not
67
- built for output point vector layer. If required, the topology can be built
67
+ built for output point vector layer. If required, the topology can be built
68
68
using < em > < a href ="v.build.html "> v.build</ a > </ em > .
69
69
70
- < p > If output is a point vector layer and < b > sparse</ b > is not specified,
70
+ < p > If output is a point vector layer and < b > sparse</ b > is not specified,
71
71
the output vector layer will contain points at the
72
72
same locations as observation points in the input layer but the values
73
- of the output points will be interpolated values. If a < b > sparse</ b >
74
- point vector layer is specified, the output vector layer will contain points
75
- at the same locations as the sparse vector layer points. The values will be
73
+ of the output points will be interpolated values. If a < b > sparse</ b >
74
+ point vector layer is specified, the output vector layer will contain points
75
+ at the same locations as the sparse vector layer points. The values will be
76
76
those of the interpolated raster surface at those points.
77
77
78
78
< p > A cross validation "leave-one-out" analysis is available to help to
@@ -146,7 +146,7 @@ <h2>KNOWN ISSUES</h2>
146
146
< p >
147
147
In order to avoid RAM memory problems, an auxiliary table is needed
148
148
for recording some intermediate calculations. This requires
149
- the < i > GROUP BY</ i > SQL function is used. This function is not
149
+ the < i > GROUP BY</ i > SQL function is used. This function is not
150
150
supported by the DBF driver. For this reason, vector output
151
151
(< b > output</ b > ) is not permitted with the DBF driver. There are
152
152
no problems with the raster map output from the DBF driver.
0 commit comments