Hello R-SIG-GEO list,
I know this has come up before but I am having an ongoing memory problem
with the gstat package (gstat out of dynamic memory) that I can't seem
to solve.
I am using R to interpolate DEMs from LiDAR xyz point files and mosaic
them together via RSAGA. The script uses a l
.g. jitter)
the coordinates very slightly. Either solution will do the work.
Cheers,
José M. Blanco
Murray Richardson escribió:
Hello R community,
I have cross-posted with r-sig-geo as this issue could fall under
either interest group I believe.
I just came accross the alphahull package a
Hello R community,
I have cross-posted with r-sig-geo as this issue could fall under either
interest group I believe.
I just came accross the alphahull package and am very pleased I may not
need to use CGAL anymore for this purpose. However, I am having a
problem computing alpha shapes wit
a way around it?
Essentially, I do not want polygon holes to be included in the merging
process.
Thanks in advance!
Murray
Roger Bivand wrote:
On Fri, 5 Sep 2008, Murray Richardson wrote:
Thanks Roger,
I have singletons with areas. I think the slivers will be quite
obvious based on
ions in package gpclib can do this?
--
Edzer
Murray Richardson wrote:
Thanks Friderike. I assumed this was the answer, but it doesn't
appear to work with two SPDF objects. i.e.:
> overlay(polysA,polysB)
Error in function (classes, fdef, mtable) :
unable to find an inherited method for
patialPolygonsDataFrame", "SpatialPolygonsDataFrame"
Murray
Oehler, Friderike (AGPP) wrote:
Try
?overlay
Regards,
Friderike
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Murray Richardson
Sent: 25 September 2008 06:01
To: r-sig-geo@stat.ma
Hello users,
There is probably a very simple solution to this that I am missing: is
there a way to select polygons in one SPDF that fall within the polygons
of another SPDF?
This would save me a lot of processing time as I am having to take a
very circuitous route to achieve the same outcome.
ivand wrote:
On Fri, 5 Sep 2008, Murray Richardson wrote:
Hi Roger
I'm just getting around to trying this out. I must say, I'm not clear
on how to work with the neighbour list object to accomplish this.
Specifically, how would I identify the largest neighbours of the
sl
erging based on other attributes.
Still waiting on that book...!
Murray
Roger Bivand wrote:
On Wed, 13 Aug 2008, Murray Richardson wrote:
Hello again r.sig.geo list,
Thanks Roger, for help on my previous question regarding iterating
through a shapefile.
I'm sure once I receive
Hello again users,
I'm having trouble figuring out how to format the data slot in spatial
SpatialPolygonsDataFrames. I need to use spRbind to combine polygons
from different shapefiles but encounter the problem of having different
numbers of columns, and also non-unique IDs. If the polygons
Aha yes, thanks, Alex. I thought I had tried that option but must have
used it incorrectly, that is a good enough workaround for me right now.
Thanks for the tip, I guess I missed that thread in SAGA archives too.
cheers
Murray
___
R-sig-Geo mailin
dDataFrame (i.e. something not too
computationally intensive) as I am having to do some expensive
formatting to make things work via RSAGA.
Thanks again,
Murray
Roger Bivand wrote:
On Fri, 15 Aug 2008, Murray Richardson wrote:
Oh maybe I've misunderstood the function.
I am using uni
Hello,
I am having a problem using the grid to shapes module, as follows:
rsaga.geoprocessor("grid_gridding", 3, list(GRID="tmpPolyGrid.sgrd",
INPUT="tmp", FIELD=1, TARGET_TYPE=2, GRID_GRID="filled.sgrd"))
This causes saga_cmd to crash on windows xp. I can't, for the life of
me, figure out
taFrame(sptmp, data=newID, match.ID=FALSE)
writePolyShape(merged, "up1merged", factor2char = TRUE, max_nchar=254)
So I am just using unionSpatialPolygons as a dissolve tool but I would
like non-adjacent polys within the same slope class to be separate
polygons when I'm done.
Thanks
for each ID I
used for the merge, but I need them back as separate polys.
Thanks
Murray
Roger Bivand wrote:
On Wed, 13 Aug 2008, Murray Richardson wrote:
Hello again r.sig.geo list,
Thanks Roger, for help on my previous question regarding iterating
through a shapefile.
I'm sure o
ith, but if I had to choose a rule I would have it
merge with the largest one.
Thanks in advance,
Murray Richardson
___
R-sig-Geo mailing list
R-sig-Geo@stat.math.ethz.ch
https://stat.ethz.ch/mailman/listinfo/r-sig-geo
e. I also
appreciate advice on updating records in a shapefile attribute table.
Thanks in advance.
Murray Richardson
___
R-sig-Geo mailing list
R-sig-Geo@stat.math.ethz.ch
https://stat.ethz.ch/mailman/listinfo/r-sig-geo
#x27;m sorry for bothering, how are you using R with CGAL?
>
>
> 2008/3/31, Murray Richardson <[EMAIL PROTECTED]>:
>
>> See below. Haven't tried this yet.
>>
>> Yes that is what CGAL stands for.
>>
>> Murray
>>
>>
>>
>>
See below. Haven't tried this yet.
Yes that is what CGAL stands for.
Murray
Hi Murray,
Regarding the first question, you can read into R first and then output
it again. You could also call ogr2ogr using a system call like:
system("ogr2ogr normal syntax stuff")
cheers,
Paul
G. Allegr
Actually I am currently running an R script to link output from cgal
routines to postGIS which allows me to handle massive tables and has
some other advantages for my problem. However, this clarifies the
import export option somewhat (although I just learned that I can invoke
ogr2ogr as a syst
Hello list members,
I think I must be missing some obvious documentation somewhere; I'm not
sure how I can access ogr2ogr vial R to convert a postGIS layer to a
shapefile. Must I use readOGR and writeOGR in rgdal instead or is there
a way to call ogr2ogr directly? If so do I have to call the o
resolution and the diagonal resolution. There were only 779 cells
> in patches here, but it ran so fast that scaling up shouldn't be a
> problem.
>
> Roger
>
>>
>> Agus
>>
>> Andrew Niccolai escribió:
>>> If you aren't dedicated to an R specif
ut it ran so fast that scaling up shouldn't be a
> problem.
>
> Roger
>
>>
>> Agus
>>
>> Andrew Niccolai escribió:
>>> If you aren't dedicated to an R specific solution, ImageJ is open
>>> source and
>>> does this under Analysi
Thakns Roger
Since I am more familiar with postGIS I took that approach. It worked
like a charm.
I can post the script if you think it's worthwhile.
Murra
Roger Bivand wrote:
> On Sun, 9 Mar 2008, Murray Richardson wrote:
>
>> Hi Roger
>>
>> Thanks so much for
of 27.
Just wondering if anyone has any suggestions. Maybe a function I don't
know about yet...
Thanks in advance,
Murray Richardson
___
R-sig-Geo mailing list
R-sig-Geo@stat.math.ethz.ch
https://stat.ethz.ch/mailman/listinfo/r-sig-geo
stGIS linestring
table and polygonize that, all via RODBC/postGIS. An added benefit is
that it would clean up dangling segments, which may also exist.
Thanks again
Murray
Roger Bivand wrote:
> Murray Richardson utoronto.ca> writes:
>
>
>> Hello,
>>
>> I am looking
26 matches
Mail list logo