Backward compatibility with lidR v4.0.0
Has you know I'm working on lidR v4
which will no longer be based on old R spatial packages (sp
). One consequence is that LAS
objects will no longer have a slot @proj4string
.
Your package stores a serialized LAS
object in las_chablais3
. This object will no longer be valid in v4 because it has a proj4string
instead of a crs
. You cannot yet modify your las_chablais3
object because lidR v4
is not released and I won't be able to release lidR v4
because there is a backward incompatibility that triggers a warning with R CMD check
The easy backward/forward compatible fix is to do not serialize LAS
object. Instead save a las_chablais3.laz
file in inst/extdata
and load it with lidR::readLAS()
. In the man page change occurences of
data(las_chablais3)
to
LASfile <- system.file("extdata", "las_chablais3.laz", package="lidaRtRee")
las_chablais3 <- lidR::readLAS(LASfile)
By the way serialization of LAS
object is not a good idea because it contains a data.table
object. data.table
are weakly serializable.
Please update lidaRtRee
on CRAN before the release of lidR v4
. I do no have schedules but I won't release lidR v4
before 2022 so, it is not in a hurry. Actually I discourage you to do it has soon as possible because lidR v4
is still in development so I may detect another problem latter.
If you want to get an eye on lidR v4
the current state is available in the branch v4. See also NEWS
Cheers
PS: if you have any question please contact me by email (in French) or on github (in English). I'm unlikely to come back here. I just took the chance to open an issue here because I already have a gitlab.irstea account.