You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title is pretty much self explanatory. The packages sp and raster, actually used by leastcostpath, are going to be replaced soon by sf and terra, while rgdal and rgeos, also used by leastcostpath "will be retired by the end of 2023"
It's then probably time to start this transition for leastcostpath!
One issue, and the reason why leastcostpath still relies on sp and raster, is its dependancy to gdistance, which still uses those packages. Thought this has already been mentioned two years ago in: AgrDataSci/gdistance#3, it's not clear if the switch will be done anytime soon. A first, temporary easy fix would be to cast all object into raster and Spatial before calling for gdistances functions.
The text was updated successfully, but these errors were encountered:
Title is pretty much self explanatory. The packages
sp
andraster
, actually used byleastcostpath
, are going to be replaced soon bysf
andterra
, whilergdal
andrgeos
, also used byleastcostpath
"will be retired by the end of 2023"It's then probably time to start this transition for
leastcostpath
!One issue, and the reason why
leastcostpath
still relies onsp
andraster
, is its dependancy togdistance
, which still uses those packages. Thought this has already been mentioned two years ago in: AgrDataSci/gdistance#3, it's not clear if the switch will be done anytime soon. A first, temporary easy fix would be to cast all object intoraster
andSpatial
before calling forgdistances
functions.The text was updated successfully, but these errors were encountered: