Agus,

This is likely because there are some longitude coordinates that are  <
-180 or > 180.
OGR does not complain, but, as these are lon/lat data, sp runs
 sp:::.ll_sanity  and throws an error.

I think it would be preferable if sp gave a warning rather than an error,
at least when longitudes are within a reasonable number (-360 -- 360 ?). I
think that a longitude of, e.g. 181 is perfectly interpretable, and
sometimes useful. For example to plot Russia, or Fiji in one piece in
lon/lat coordinates.

Robert


On Fri, Dec 16, 2011 at 4:24 AM, Agustin Lobo <alobolistas@gmail.com> wrote:

> Hi!
> I' trying to read this shapefile that is just in lon,lat WGS84
> > ogrInfo(dsn=datad,layer="world_adm0v2")
> Source: "/media/Iomega_HDD/JACOB/ExIE2011DATA/ExFireBorneoDATA/world_adm0",
> layer: "world_adm0v2"
> Driver: ESRI Shapefile number of rows 209
> Feature type: wkbPolygon with 2 dimensions
> +proj=longlat +datum=WGS84 +no_defs
> Number of fields: 3
>       name type length typeName
> 1      NAME    4     40   String
> 2 GMI_CNTRY    4      3   String
> 3    REGION    4     25   String
>
> but I get:
> > world <-readOGR(dsn=datad,layer="world_adm0v2")
> OGR data source with driver: ESRI Shapefile
> Source: "/media/Iomega_HDD/JACOB/ExIE2011DATA/ExFireBorneoDATA/world_adm0",
> layer: "world_adm0v2"
> with 209 features and 3 fields
> Feature type: wkbPolygon with 2 dimensions
> Error in validityMethod(as(object, superClass)) :
>  Geographical CRS given to non-conformant data
> I've tried
> > world
> <-readOGR(dsn=datad,layer="world_adm0v2",p4s=CRSargs(CRS("+init=epsg:4326")))
> but get the same result
>
> can't this CRS (epsg:4326)
> +proj=longlat +ellps=WGS84 +datum=WGS84 +no_defs +towgs84=0,0,0
> be read by readOGR() ?
>
> Thanks
> Agus
>
> _______________________________________________
> R-sig-Geo mailing list
> R-sig-Geo@r-project.org
> https://stat.ethz.ch/mailman/listinfo/r-sig-geo
>

	[[alternative HTML version deleted]]

