Closed TillF closed 10 months ago
@TillF Do you ever use the same raster name in different mapsets? I'm trying to disentangle the way g.list
handles names and mapsets through its pattern argument, which does not use the full path.
In the example case there is only mapset PERMANENT and, consequently, only one raster with this name. However, I have other locations with rasters of this name, but I guess this should be of no influence.
side note: According to my old script, in prior versions of both GRASS and rGRASS7, the name resolution seemed to work, except that "...@mapsetname" always had to be supplied whenever rasters of the same name existed in parallel mapsets, even when trying to access only the current mapset.
The reason for the tightening was to try to trap non-existing raster names causing problems at r.info
later in the process. I've committed and pushed https://github.com/rsbivand/rgrass/commit/d405eabf64ea618c5e261dcf73043bedd46a2325 to try to address this. Please let me know if it is sufficient; do you need a Windows build of the package?
I installed 0.4-2 via install_github(). It works as expected for me. Issue can be closed. Thanks a lot!
@TillF do you need a submission to CRAN in the very near future, or is it OK to wait a little to see whether the 0.4-1
release caused other difficulties first?
No sweat, I don't need any immediate release. Thanks, though.
read_RAST() successfully reads an existing raster map when only specified by its "first name", but fails when its "surname", i.e. its mapset is also supplied via "@...":
execGRASS("r.info", map="svc")
andexecGRASS("r.info", map="svc@PERMANENT")
work as expected:Specifying only the simple name works:
Using @-notation fails:
Tested with GRASS 8.3.1, standalone installer.