[GRASS-dev] G7: how to get rid of multiple listing of identical map names?
Markus Neteler
neteler at osgeo.org
Sat Jun 21 18:01:08 PDT 2014
Hi Huidae, all,
if I recall correctly you (Huidae) fixed in trunk the problem that
same map names in different mapsets (which are in the search path) are
listed several times.
This still happens for d.rast, r.info (see below) and others. I don't
remember the patch number. Perhaps it could be put at library level
to make all modules better?
Here the simulation:
# clone landsat mapset:
[neteler at oboe nc_spm_08_grass7]$ cp -rp landsat landsat2
[neteler at oboe nc_spm_08_grass7]$ cp -rp landsat landsat3
# run
grass70 ~/grassdata/nc_spm_08_grass7/landsat3/
r.info lsat5_1987_50
WARNING: 'cell/lsat5_1987_50' was found in more mapsets (also found in
<landsat2>)
WARNING: 'cell/lsat5_1987_50' was found in more mapsets (also found in
<landsat>)
WARNING: Using <lsat5_1987_50 at landsat3>
WARNING: 'cellhd/lsat5_1987_50' was found in more mapsets (also found in
<landsat2>)
WARNING: 'cellhd/lsat5_1987_50' was found in more mapsets (also found in
<landsat>)
WARNING: Using <lsat5_1987_50 at landsat3>
WARNING: 'cellhd/lsat5_1987_50' was found in more mapsets (also found in
<landsat2>)
WARNING: 'cellhd/lsat5_1987_50' was found in more mapsets (also found in
<landsat>)
WARNING: Using <lsat5_1987_50 at landsat3>
WARNING: 'cell/lsat5_1987_50' was found in more mapsets (also found in
<landsat2>)
WARNING: 'cell/lsat5_1987_50' was found in more mapsets (also found in
<landsat>)
WARNING: Using <lsat5_1987_50 at landsat3>
WARNING: 'cats/lsat5_1987_50' was found in more mapsets (also found in
<landsat2>)
WARNING: 'cats/lsat5_1987_50' was found in more mapsets (also found in
<landsat>)
WARNING: Using <lsat5_1987_50 at landsat3>
WARNING: 'hist/lsat5_1987_50' was found in more mapsets (also found in
<landsat2>)
WARNING: 'hist/lsat5_1987_50' was found in more mapsets (also found in
<landsat>)
[....]
g.mapsets -p
Accessible mapsets:
landsat3 PERMANENT landsat2 landsat
I don't know where to look for the problem.
thanks for any pointers,
Markus
More information about the grass-dev
mailing list