Please see other functions I have written in geolink_mach. This function you wrote should be placed in the geolinkmach script. This is where we will put to outer user functions that do the full stack of downloading, processing and combining of geospatial data with shapefile/survey i.e. all the geolink*** functions. Also, please do not leave function calls in any R/ folder script. Please remove the function call you have at the bottom of that script (even if you commented it out, this is what spielplatz is for).
Next, please write a full documentation in roxygen comments for the function you have written. Also see my examples. The goal is to explain in as much detail as possible to help the user understand what the function does. Please see the following link: https://r-pkgs.org/man.html
@dasalm20,
You can begin writing unit tests for geolink_landcover() once you have written the tests for geolink_downloadprocessor(). For each of these datasets, that we include being that you have tested geolink_downloadprocessor(). You need only to test that the download actually works because we should have certified that geolink_downloadprocessor() is done. Here is a link on writing unit tests in R: https://r-pkgs.org/testing-basics.html
@ifeanyi588 Documentation for geolink landcover is completed and placed in correct folder. Please review and update to master branch. Everything is in the geolink_updates branch.
@DianaJaganjac,
Please see other functions I have written in geolink_mach. This function you wrote should be placed in the geolinkmach script. This is where we will put to outer user functions that do the full stack of downloading, processing and combining of geospatial data with shapefile/survey i.e. all the geolink*** functions. Also, please do not leave function calls in any R/ folder script. Please remove the function call you have at the bottom of that script (even if you commented it out, this is what spielplatz is for).
Next, please write a full documentation in roxygen comments for the function you have written. Also see my examples. The goal is to explain in as much detail as possible to help the user understand what the function does. Please see the following link: https://r-pkgs.org/man.html
@dasalm20, You can begin writing unit tests for geolink_landcover() once you have written the tests for geolink_downloadprocessor(). For each of these datasets, that we include being that you have tested geolink_downloadprocessor(). You need only to test that the download actually works because we should have certified that geolink_downloadprocessor() is done. Here is a link on writing unit tests in R: https://r-pkgs.org/testing-basics.html