Closed Maschette closed 4 years ago
ignore it, it's meaningless we can't do much about it apart from
options(warn = -1)
and that'll turn off all warnings until they get turned back on.
it's just how things are for now, it's not reproj but rgdal/sf
looks like we can do this with the new rgdal (1.5-12, released 2020-06-26)
options("rgdal_show_exportToProj4_warnings"="none")
so this would go into our zzz.R, but the problem with that is it masks it for any use of rgdal if SOmap is loaded, so maybe that's too much
also, it only applies if this option is set before rgdal is loaded - on the whole, I think it's worthwhile but perhaps not worth conditioning SOmap on this version of rgdal
dev version now has quietly(...)
wrapped inside top-level functions, which selectively suppresses warnings. Currently only warnings with the string "Discarded datum WGS_1984" are suppressed.
@mdsumner SOauto_crop
throws "NULL source CRS comment, falling back to PROJ string" warnings - should these be suppressed too? I think they come from spTransform
yes I don't see any use for these warnings in this context at all - that particular warning is saying
"this S4-class 'CRS' object has an empty value in the comment attribute"
the comment attribute is a hidden attribute, using the comment()
mechanism - and it's been retrofit in sp to store WKT2, so that the back-end can transform using a full CRS, while the front-end presents only a PROJ.4 string. It's a kind of backwards compatibility.
(in sf context, sf only stores $input and $wkt now, and $wkt cannot be NULL, the $proj4string apparent value in sf is a dynamic function call)
Thanks. https://github.com/AustralianAntarcticDivision/SOmap/commit/abee8fdc1d7dbc0c800020e9d9ce160db4e5e971. I think this is OK as a workaround.
Soooo I updated all my packages and now get a warning frenzy when I call
SOmap()
Is this a reproj thing @mdsumner?
Created on 2020-06-25 by the reprex package (v0.3.0)