Need to force it to be set? What is the default?

Using the geoR built-in dataset creates confusion for new users.

Potentially use https://github.com/jsta/gshhg or https://github.com/ropensci/rnaturalearth to pull a coastline from anywhere in the world.

Maybe it could be saved as a raster slot?

Hello,

I am planning to use your package to interpolate values from oceanographic sensors stationed around the coast of Nova Scotia.

I have looked through the functions in some detail and have a couple of questions :

1. How did you decide on the values of ipdw_range and ipdw_dist in pathdistGen()?
   I am particularly interested in why you chose the second break of the costfurf histogram for the first row of sf_ob (line 58).
   I am curious because I get different values of ipdw_dist depending on the order of sf_ob.

2. Also in regard to pathdistGen(): I think I followed most of the reclassifying, but why did you need to scale `costsurf_reclass' (line 74): costsurf_scaled <- ((ipdw_range / costsurf_reclass)^2)?

3. Finally, I am running into an issue where the contribution from some stations is 0 for the whole area (i.e., the raster layer output from ipdwInterp.R() is zero for every cell), despite the station being connected via water to the whole coast. I am trying to figure this out and will post a reprex if it doesn't get resolved, but let me know if this is a common/known issue.

Thanks!

Very large extents can hang or take a long time with the default resolution of 1.

Dear,

I am trying, first, to run the example found here (http://jsta.github.io/ipdw/articles/ipdw2.html) to see how to apply the function on my own dataset. However, I am not able to perform the pidw on salinity because of the following warning: Error in h(simpleError(msg, call)) : erreur d'�valuation de l'argument 'x' lors de la s�lection d'une m�thode pour la fonction 'extent' : ‘srs’ n'est pas un slot de la classe “BasicRaster”

Any ideas on how to deal with that?
Thank you very much,
Eric

Testing blocks that call the raster::raster() function give the following warnings:

1. raster should not given warning (@test-raster.R#37) - no non-missing arguments to min; returning Inf
2. raster should not given warning (@test-raster.R#37) - no non-missing arguments to max; returning -Inf

Minimum Reproducible Example

test_that("raster should not given warning", {
    skip_on_cran()
    skip_on_travis()
    skip_on_appveyor()

    m <- matrix(NA, 10, 10)
    foobar <- raster::raster(m, xmn = 0, xmx = 10, ymn = 0, ymx = 10)
    expect_s4_class(foobar, "RasterLayer")
})

In this case paths are much shorter than they should be. Create an artificial barrier around bbox extent?

Should an error be thrown if a projection is not NA? Are projection mismatches resolved?

Can you provide python version of IPDW implementation?
I need python version to evaluate the result.

Thanks.

This package depends on (depends, imports or suggests) raster and one or more of the retiring packages rgdal, rgeos or maptools (https://r-spatial.org/r/2022/04/12/evolution.html, https://r-spatial.org/r/2022/12/14/evolution2.html). Since raster 3.6.3, all use of external FOSS library functionality has been transferred to terra, making the retiring packages very likely redundant. It would help greatly if you could remove dependencies on the retiring packages as soon as possible.

Relates to #19

Keep the default as 1.

add ability to specify final raster resolution

This would also enable use of the fasterize package in costrasterGen. Polygon rasterization is a major speed killer.

Filled contours can be more visually appealing than straight-up rasters.

These can be reproduced by checking with --as-cran using current
r-devel, which for now sets 

  _R_CLASS_MATRIX_ARRAY_=true
  _R_CHECK_LENGTH_1_CONDITION_="package:_R_CHECK_PACKAGE_NAME_,verbose"

in the check environment, to the effect that

  R> class(matrix(1 : 4, 2, 2))
  [1] "matrix" "array" 

(and no longer just "matrix" as before), and that conditions of length
greater than one in 'if' and 'while' statements executing in the package
being checked give an error.

Need to adjust class checking of the xymat object?