-
Notifications
You must be signed in to change notification settings - Fork 59
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
geojsonio vulnerable to forthcoming changes in sp and rgdal #157
Comments
thanks @rsbivand - I can't replicate the error. I used the
do i have the wrong versions of anything? |
Ah I see, I needed dev sp on github, now I can see the error |
@rsbivand What is the proper way? I couldn't figure it out from the links |
First, PROJ 6 (I use 6.2.1), then GDAL 3 built on PROJ 6 (I use 3.0.2). Next, current rgdal on R-Forge https://r-forge.r-project.org/R/?group_id=884, for example source install of A range of somewhat splattered sanguineous details in r-spatial/discuss#28 - I/we don't really see the full contours of the unavoidable/desirable GDAL3/PROJ6 regression, involving silent accuracy degradation if we carry on using PROJ strings with |
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
Related to #150 and #148:
Running revdep checks for current rgdal on R-Forge - see:
https://stat.ethz.ch/pipermail/r-sig-geo/2019-November/027801.html
shows the errors in the attached check log, related to use of PROJ&/GDAL3
and required changes to sp and rgdal. If useful find a regerence to a docker
image in this thread:
r-spatial/discuss#28
Changes will occur quite fast, and packages need to be prepared.
The problems seem to come from not preparing the sp::CRS objects in a way that lets us modify them outside S4 to use WKT in comments. I tried to trace the crs object through your nested function calls, but lost trace.
The text was updated successfully, but these errors were encountered: