The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
see #87 - Windows QGIS standalone installations of GRASS GIS can be used only if R is started in the OSGeo4W shell bundled with the installation
write_VECT()
: when the SpatVector
object already refers to a source file, an intermediate temporary file
is no longer written to get the data into the GRASS GIS database (#93).
A similar shortcut was already in place for
write_RAST()
.
read_VECT()
: provide access to the standalone
GDAL-GRASS driver to read vector data, which skips the step of writing a
intermediate file (#93). Note that this standalone driver needs to be
set up separately. More information is in the driver’s
README.
read_VECT()
: support reading as
SpatVectorProxy
class of {terra}
, by providing
a proxy
argument (#93).
XML
with xml2
see #72reinstate grass-stable
https://github.com/OSGeo/grass-website/issues/357
fix #79 thanks to Adam B. Smith, use
terra::as.vector
method rather than internal slot
name
#73 guess gisBase=
in
initGRASS()
added SP_EVOLUTION_STATUS 2 to examples
#66 re-examining to protect from UInt maxing out; add stop for required manual NODATA
#68, #69 improvements to vignettes, thanks to Floris Vanderhaeghe and Veronica Andreo
#63 and #64, detection of GRASS path for initGRASS()
semi-automated if grass --config path
works or if
environment variable GRASS_INSTALLATION
set to path, thanks
to Robin Lovelace
correct NODATA logic in read_RAST()
for unsigned
rasters #66 thanks to Laura Poggio
first release to replace deprecated rgrass7
remove suggested packages planned for retirement (rgdal)
add vignettes
remove old code working around earlier use by GRASS of DBF rather than SQLite for storing vector attributes
remove use_sp()
and use_sf()
for file
transfer
remove code using GDAL GRASS plugin
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.