-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRS("+axis=wsu") support #42
Comments
No, this is a case that is not allowed by library(sf)
s = st_as_sf(wrld_simpl)
s2 = st_transform(s, "+proj=latlong +axis=wsd")
plot(s2) but doesn't seem to do much. |
Re: email from Nick Tate 5/1-18 Using that example, I see:
which is upside-down - is that what you wanted? This doesn't work for sf:
which is not upside-down, and reverses the signs on the bounding box y-axis
I tried using the with_geos argument FALSE in st_transform, but I think the outcome was the same - unsure because I had an older lwgeom attached. I'm copying this into the GitHub issue. Email:
The proj4 definition below is for the standard Hobo Dyer (from tmap definitions) P.S. it seems some comment on this has appeared. I suspect what I want is to replace the default +axis=enu with +axis=wsu |
s3 = lwgeom::st_transform_proj(s, "+proj=cea +lat_ts=37.5 +ellps=WGS84 +datum=WGS84 +units=m +axis=wsu +no_defs +towgs84=0,0,0")
plot(st_geometry(s3)) does plot the world upside down; |
Good, that is what I suspected. |
With upside down, do you imply only y is affected? In any case, they are both; |
Interestingly, following this suggestion, s2 = st_transform(s, "+proj=cea +lat_ts=37.5 +ellps=WGS84 +datum=WGS84 +units=m +axis=wsu +no_defs +towgs84=0,0,0 +wktext")
plot(st_geometry(s2)) does work as intended. |
Following this, axis orientation was first introduced into proj4 in 2010 and became part of standard in 2012 (listed now among common parameters
However, when I try to "turn my world upside down" I get the error. Does it follow that the
proj4
version used byCRS()
does not (yet?) support+axis
param?The text was updated successfully, but these errors were encountered: