On 09/02/2023 12:41 p.m., Alexandre Courtiol wrote:
Hi Igor,
I had the same issue using terra rather than sf a couple of weeks ago.
I thought of solving the issue as follow:
1.
store the shapefiles under extdata.
2.
create a function that loads the files:
.build_internal_files <
Thank you all for your help.
Adam, I followed your suggestion, but I still can't figure out why the data
is only available locally when I run the devtools::load_all() function.
When I install the package from GitHub, the data does not appear (even
using the data() function).
Extdata: https://git
Hi Igor,
I had the same issue using terra rather than sf a couple of weeks ago.
I thought of solving the issue as follow:
1.
store the shapefiles under extdata.
2.
create a function that loads the files:
.build_internal_files <- function() {
## This function should not be calle
On 09/02/2023 3:56 a.m., Ivan Krylov wrote:
В Wed, 8 Feb 2023 11:32:36 -0300
Igor L пишет:
spatial_aisp <- sf::st_read('data-raw/shp_aisp/lm_aisp_2019.shp')
plot(spatial_aisp) # works
# Same data from .rda file after use usethis::use_data(spatial_aisp,
overwrite = TRUE)
x <- ispdata::spatia
В Wed, 8 Feb 2023 11:32:36 -0300
Igor L пишет:
> spatial_aisp <- sf::st_read('data-raw/shp_aisp/lm_aisp_2019.shp')
>
> plot(spatial_aisp) # works
>
> # Same data from .rda file after use usethis::use_data(spatial_aisp,
> overwrite = TRUE)
>
> x <- ispdata::spatial_aisp
>
> plot(x) # do not wo
Hi Igor,
I’ve a couple packages that have spatial data in them that I maintain. I’ve
opted to package up the data as a geopackage file and import it as an {sf}
object. Edzer Pebesma suggests this to circumvent changes in the {sf} package
from affecting native {sf} objects that are distributed as
