[GRASS-dev] Re: [GRASS GIS] #1507: r.in.gdal & others: -e must only
modify the current mapset's WIND file
GRASS GIS
trac at osgeo.org
Wed Dec 14 08:11:23 EST 2011
#1507: r.in.gdal & others: -e must only modify the current mapset's WIND file
---------------------------------------------+------------------------------
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 6.4.2
Component: Default | Version: svn-trunk
Keywords: r.in.gdal, r.external, v.in.ogr | Platform: All
Cpu: All |
---------------------------------------------+------------------------------
Comment(by hamish):
... for the case of a location created before you knew what the default
bounds should be, & so you are left with n=1 s=0 e=1 w=0 in DEFAULT_WIND
and you want some way to easily update it (restarting in PERMANENT just to
fix that is a pain), consider that hiding that functionality in r.in.gdal
& co is a bit weird for something needing a general solution.
I could see a small "g.region.update_default" addon helper script which
ran g.mapset to temporarily switch into PERMANENT (with g.mapset's
appropriate locking tests) run `g.region -s`, then switch back to the
current mapset, but I don't think such a thing should be part of the main
distribution.
perhaps a better solution to that problem is a pop-up tool on the startup
mapset selection GUI which for the current location gave you a list of
available mapsets in the same location and let you quickly reset the
default region from the one you select. this still requires you to
remember to do it at startup; but maybe the startup GUI could scan for
0-1,0-1 default regions at startup and color the PERMANENT text orange to
remind you that it needs doing?
shrug,
Hamish
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1507#comment:4>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list