Closed Maschette closed 4 years ago
More of an FYI, I have no idea why this is the case but if you are using SOauto_map, SOmanagement and SOplot they need to be used in that order. If you switch SOplot and SOmanagement around it turns to shit.
library(graticule) #> Loading required package: sp library(SOmap) #> Loading required package: raster selection<-graticule(lons=c(163, 200), lats = c(-78.25,-69.6), proj = "+proj=stere +lon_0=-179.878730 +lat_0=-74.236502 +lat_ts=-71 +datum=WGS84 +ellps=WGS84 +towgs84=0,0,0", tiles = TRUE) #> Loading required namespace: rgeos RSS<-SOauto_map(x=selection, lcol=4, gratlon = c(-165,180,165), gratlat = c(-70,-72,-74,-76,-78), contours = FALSE ) b<-as(extent( -304925, 306949, -136285.9 , 56159.7), 'SpatialPolygons') ICE<-crop(SOproj(ice,target = RSS$projection),b) RSS SOmanagement(MPA = TRUE, basemap = RSS, mpacol = 2) SOplot(ICE, col=viridis::viridis(100), target = RSS$projection)
RSS SOplot(ICE, col=viridis::viridis(100), target = RSS$projection) SOmanagement(MPA = TRUE, basemap = RSS, mpacol = 2)
Created on 2019-04-16 by the reprex package (v0.2.1)
fixed https://github.com/AustralianAntarcticDivision/SOmap/commit/8ec00f85600cc260598447db66fe392410a457cc
More of an FYI, I have no idea why this is the case but if you are using SOauto_map, SOmanagement and SOplot they need to be used in that order. If you switch SOplot and SOmanagement around it turns to shit.
Created on 2019-04-16 by the reprex package (v0.2.1)