NEWS.md
s2 required by upcoming sf 1.0 release. This means checks on whether an aoi intersects a target layer can be run on the sphere, increasing accuracy. Code should run consistently whether sf is using s2 or GEOS.get_soils_point() and get_lscape_point(), which return non-spatial data summaries. The value for a pixel directly under a point can be requested, or statistical summaries of the area within n pixels of a point.get_soils_data() - component names for requesting soils data are different (‘VAL’ vs ‘value’ etc)get_soils_data() and get_lscape_data() no longer write rasters to your working directory unless you tell them to (use option write_out = TRUE).check_avail() for making sure a given soil attribute is available on a given product.metadata_soils() and metadata_lscape() to provide access to service metadata in XML or JSON format.get_slga_data() to get_soils_data().get_lscape_data() for landscape parameter retrieval, plus supporting internal functions.slga_product_info to contain landscape parameters.get_slga_data() to get raster values and confidence intervals in one object. For more complex requests involving multiple depth ranges, attributes, products or combinations thereof, use this with a map-style function e.g. base::lapply() or purrr::map().