search for: gbuffers

Dear list! I have problem with buffer size (width) in package rgeos. I would like to expand given geometry (points) to specified width based on the z value from attribute table. Here is example: point <- data.frame(x=c(10,20), y=c(10, 10), z = c(2,7)) point_shp <- SpatialPointsDataFrame(point[,1:2],point) plot(point_shp, xlim = c(0,30), ylim = c(0,20)) plot(gBuffer(point_shp, width = 5,

...poration Bt878 Audio Capture (rev 11) > > Are you supplying options when loading the bttv module? On and off, I've been googling to find if there's something I can tell it, or the kernel on boot. Currently, I have, in /etc/modprobe.d/bttv: options i2c-algo-bit bit_test=1 options bttv gbuffers=16 card=98,98,98,98,98,98,98,98 radio=0,0,0,0,0,0,0,0 tuner=4,4,4,4,4,4,4,4 chroma_agc=1 combfilter=2 full_luma_range=1 coring=1 which is something I got from googling as to how to get it working. Think there's something in that - the first line? that is not a good thing? mark...

[Mod: Other lists removed from the headers. The patch looks okay but I did not really checked it line by line -- alex] Last night I sent to redhat-list a letter with a patch. After sleeping a little I found that my patch is not enough correct. Now I post the new patch and description of the problem. In redhat distribution passwd program uses PAM, namely, pam_unix_passwd.so. This module use

...> Are you supplying options when loading the bttv module? >> >> On and off, I've been googling to find if there's something I can tell >> it,or the kernel on boot. Currently, I have, in /etc/modprobe.d/bttv: >> options i2c-algo-bit bit_test=1 >> options bttv gbuffers=16 card=98,98,98,98,98,98,98,98 >> radio=0,0,0,0,0,0,0,0 tuner=4,4,4,4,4,4,4,4 chroma_agc=1 combfilter=2 >> full_luma_range=1 coring=1 > > The options line 1 is used widely and only worth changing if all else > fails. > > The second options line option of combfilter by do...

...odule? >> >> >> >> On and off, I've been googling to find if there's something I can >> tell >> >> it,or the kernel on boot. Currently, I have, in /etc/modprobe.d/bttv: >> >> options i2c-algo-bit bit_test=1 >> >> options bttv gbuffers=16 card=98,98,98,98,98,98,98,98 >> >> radio=0,0,0,0,0,0,0,0 tuner=4,4,4,4,4,4,4,4 chroma_agc=1 combfilter=2 >> >> full_luma_range=1 coring=1 >> > >> > The options line 1 is used widely and only worth changing if all else >> > fails. >> > &...

...1) > > > > Are you supplying options when loading the bttv module? > > On and off, I've been googling to find if there's something I can tell it, > or the kernel on boot. Currently, I have, in /etc/modprobe.d/bttv: > options i2c-algo-bit bit_test=1 > options bttv gbuffers=16 card=98,98,98,98,98,98,98,98 > radio=0,0,0,0,0,0,0,0 tuner=4,4,4,4,4,4,4,4 chroma_agc=1 combfilter=2 > full_luma_range=1 coring=1 > > which is something I got from googling as to how to get it working. Think > there's something in that - the first line? that is not a good thi...

Hi All, Does anybody know of any existing functions that will calculate distance inland from a coastline? It's possible to test if a lon,lat location is land or sea using map.where(), but I need to add a buffer to this of say 2km, to allow for points that are just on the coast, and below the resolution of the worldHires database. I'm working with a marine mammal satellite telemetry

...tions when loading the bttv module? > >> > >> On and off, I've been googling to find if there's something I can tell > >> it,or the kernel on boot. Currently, I have, in /etc/modprobe.d/bttv: > >> options i2c-algo-bit bit_test=1 > >> options bttv gbuffers=16 card=98,98,98,98,98,98,98,98 > >> radio=0,0,0,0,0,0,0,0 tuner=4,4,4,4,4,4,4,4 chroma_agc=1 combfilter=2 > >> full_luma_range=1 coring=1 > > > > The options line 1 is used widely and only worth changing if all else > > fails. > > > > The second opti...

Now, this is one we have an issue with: it's got a bttv card, and motion running on it. It's a Dell PE R720. For some reason, it has never liked the card: 20 min after reboot, it says fatal bus error... but nothing's wrong, and it runs just fine. Well, expect that we need to keep it on the 2.6.32-431.20.3 kernel, because *everything* later, it randomly starts rebooting, several times a