>
> The reason for that is very simple. D_cell ist just an image of whatever you
> displayed on the monitor. This could be a raster or vector file but also
> justtext, a 3d view or icons. Thus, it's not georeferenced and it's region
> is defined by the number of rows and columns only, like a raw image. Hope
> this helps.
>
>
> Stefan Jaeger currently at
> Dept. of Geography USGS
> University of Heidelberg National Center
> INF 348 Reston, VA 22092
> 69120 Heidelberg USA
> Germany
> stefan@geo0.geog.uni-heidelberg.de sjaeger@resdgs2.er.usgs.gov
>
>
>
> >
> > Thanks again to those who answered off-list: for reasons I don't even
> > want to inquire into, g.region rast=D_cell will straighten out
> > any unusual ideas about the region setting resulting from running
> > graphics to a CELL monitor.
> >
> > Neel Smith
> > nsmith@abacus.bates.edu
> >
>
>That makes sense to me -- what I don't see is why g.region rast=D_cell
should work!
It works because it reads the header-file of D_cell and sets the region to
those values. After that, of course you are not able to display any other of
your maps, because they are outside of that region. Use g.region -p to see
the effect.
Stefan
Neel Smith
nsmith@abacus.bates.edu