On Thu, 20 Dec 2012, Francis Markham wrote:
Is there interest in something like this code for generating SpatialLines?
I use a variation of this fairly regularly:
If the geometry is simple, why not construct a WKT string and use
available functions? Try:
library(rgeos)
set.seed(1)
On Thu, Dec 20, 2012 at 8:56 AM, Roger Bivand roger.biv...@nhh.no wrote:
On Thu, 20 Dec 2012, Francis Markham wrote:
Is there interest in something like this code for generating SpatialLines?
I use a variation of this fairly regularly:
If the geometry is simple, why not construct a WKT
Is there interest in something like this code for generating SpatialLines?
I use a variation of this fairly regularly:
SimpleSpatialLines - function(coords.1, coords.2, proj4string =
CRS(as.character(NA))){
coords.1 - coordinates(coords.1)
coords.2 - coordinates(coords.2)
if
On Mon, Dec 17, 2012 at 4:25 AM, Robert J. Hijmans r.hijm...@gmail.com wrote:
Barry,
Interesting idea. The proj4string discussion is good, but somewhat trivial;
a major R release merits more than that. Are there bigger things to be done?
How about a redesign of sp to accommodate objects that
On Mon, Dec 17, 2012 at 4:05 AM, Robert J. Hijmans r.hijm...@gmail.com wrote:
that would allow the possible use of other reference system specs, e.g.
CRS(foo) = wktProj('GEOGCS[WGS 84 etc]')
That is a transformation, so I would think:
foo = spTransform('GEOGCS[WGS 84 etc]')
On Sun, 16 Dec 2012, Barry Rowlingson wrote:
There's been an announcement that the next version of R will be called
3.0.0. Although not a massive change (compared to Python 2.x and 3.x,
or Perl 4 to Perl 5),
While I won't comment on the ideas discussed in this thread (now), I think
that it
There's been an announcement that the next version of R will be called
3.0.0. Although not a massive change (compared to Python 2.x and 3.x,
or Perl 4 to Perl 5), it might be a good opportunity to revise all the
spatial classes in order to:
* clear out any cruft
* remove any inconsistencies
*
Where is the announcement?
On Sunday, December 16, 2012, Barry Rowlingson wrote:
There's been an announcement that the next version of R will be called
3.0.0. Although not a massive change (compared to Python 2.x and 3.x,
or Perl 4 to Perl 5), it might be a good opportunity to revise all
Hi Barry, that sounds like a great project. As of your (only) example, I
already see, after loading package raster:
showMethods(proj4string)
Function: proj4string (package sp)
obj=Raster
obj=Spatial
Loading Tcl/Tk interface ... done
getMethod(proj4string, Raster)
Method Definition:
function
-Geo] R 3.0.0 and spatial classes
There's been an announcement that the next version of R will be called
3.0.0. Although not a massive change (compared to Python 2.x and 3.x,
or Perl 4 to Perl 5), it might be a good opportunity to revise all the
spatial classes in order to:
* clear out any
Polygons, Spatial Grids and Spatial Pixels get
all the love.
Date: Sun, 16 Dec 2012 15:13:07 +
From: b.rowling...@lancaster.ac.uk
To: r-sig-geo@r-project.org
Subject: [R-sig-Geo] R 3.0.0 and spatial classes
There's been an announcement that the next version of R will be called
3.0.0. Although
-project.org
Subject: Re: [R-sig-Geo] R 3.0.0 and spatial classes
Could you please detail in which respect you believe they are orphaned,
right now, and what kind of love they should receive?
On 12/16/2012 07:16 PM, Chris English wrote:
Well, I hope something is done with Spatial Lines that seem
On Sun, Dec 16, 2012 at 6:53 PM, Chris English sgl...@hotmail.com wrote:
Edzer:
On Tue, Jul 17, 2012 at 2:34 PM, Agustin Lobo ~ from Barry Rowlingson
wrote:
To convert to SpatialLines, get the coordinates and build in the
usual convoluted manner:
On Sun, Dec 16, 2012 at 5:19 PM, Edzer Pebesma
edzer.pebe...@uni-muenster.de wrote:
Hi Barry, that sounds like a great project. As of your (only) example, I
already see, after loading package raster:
showMethods(proj4string)
Function: proj4string (package sp)
obj=Raster
obj=Spatial
On Sun, Dec 16, 2012 at 12:15 PM, Barry Rowlingson
b.rowling...@lancaster.ac.uk wrote:
On Sun, Dec 16, 2012 at 5:19 PM, Edzer Pebesma
edzer.pebe...@uni-muenster.de wrote:
Hi Barry, that sounds like a great project. As of your (only) example, I
already see, after loading package raster:
In raster there are as methods to coerce the geometries of
SpatialPolygons and SpatialLines to a data.frame and back. I am not sure if
they are documented and whether anyone has discovered and used these; but I
found them helpful. sp would be a more natural place for such functions.
Robert
On
Barry,
Interesting idea. The proj4string discussion is good, but somewhat trivial;
a major R release merits more than that. Are there bigger things to be
done? How about a redesign of sp to accommodate objects that have data on
disk (in a database, wherever) both for raster and points/lines/polys.
17 matches
Mail list logo
