I need a reminder, and reading the g.region man page a couple of times
didn't show me the answer.
When I added two points to an ASCII point file and processed the revised
file through v.in.ascii I could see the points (but for two very close
together, but that's not material). However, the map no longer has the
region definition that others in the project have.
The new proj_pts region is:
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: grs80
north: 408407.13
south: 397768.55
west: 242018.4
east: 243757.62
nsres: 7.49723749
ewres: 3.37712621
rows: 1419
cols: 515
cells: 730785
The project region is:
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: grs80
north: 1334419.15160578
south: 1279151.24118496
west: 769192.92822895
east: 819255.92362222
nsres: 7.49700358
ewres: 3.37898187
rows: 7372
cols: 14816
cells: 109223552
What I no longer remember is whether I can manually modify the regional
parameters of the proj_pts map to those of the project, or whether I need to
process the map through another module to do this. They're both in the same
projection and all proj_pts represent a small area of the project region.
Rich
On Wed, 24 Aug 2011, Rich Shepard wrote:
When I added two points to an ASCII point file and processed the revised
file through v.in.ascii I could see the points (but for two very close
together, but that's not material). However, the map no longer has the
region definition that others in the project have.
The exact error message is "The bounding box of the map is outside the
current region, nothing drawn." How do I correct this?
Rich
When I added two points to an ASCII point file and processed the revised
file through v.in.ascii I could see the points (but for two very close
together, but that’s not material). However, the map no longer has the
region definition that others in the project have.
The exact error message is “The bounding box of the map is outside the
current region, nothing drawn.” How do I correct this?
g.region -p vect=proj_pts ?
The region is part of the mapset, NOT the vector (or raster for that matter).
···
--
Micha Silver
Arava Development Co. +972-52-3665918
[http://surfaces.co.il](http://surfaces.co.il)
On Wed, 24 Aug 2011, Micha Silver wrote:
g.region -p vect=proj_pts ?
Micha,
The proj_pts region is different from the project (mapset) region.
The region is part of the mapset, NOT the vector (or raster for that matter).
I know this. When one recreated map turns up with a different bounding
box, although it's in the same mapset as the other maps, I'd like to learn
how to adjust that one map's region to match everyone else's.
Toda,
Rich
On Wed, 24 Aug 2011, Micha Silver wrote:
The region is part of the mapset, NOT the vector (or raster for that matter).
Let me try this again:
First, I set the region to the desired one (called 'basin' for this part
of the project), then I try to display the proj_pts map in it:
GRASS 6.5.svn (Oregon):~/grassdata > g.region region=basin
GRASS 6.5.svn (Oregon):~/grassdata > d.mon start=x0
using default visual which is TrueColor
ncolors: 16777216
Graphics driver [x0] started
GRASS 6.5.svn (Oregon):~/grassdata > d.vect map=proj_pts
The bounding box of the map is outside the current region, nothing drawn.
GRASS 6.5.svn (Oregon):~/grassdata >
All in the same location and mapset.
Rich
The region is part of the mapset, NOT the vector (or raster for that matter).
Let me try this again:
First, I set the region to the desired one (called ‘basin’ for this part
of the project), then I try to display the proj_pts map in it:
GRASS 6.5.svn (Oregon):~/grassdata > g.region region=basin
GRASS 6.5.svn (Oregon):~/grassdata > d.mon start=x0
using default visual which is TrueColor
ncolors: 16777216
Graphics driver [x0] started
GRASS 6.5.svn (Oregon):~/grassdata > d.vect map=proj_pts
The bounding box of the map is outside the current region, nothing drawn.
GRASS 6.5.svn (Oregon):~/grassdata >
I guess what you mean is that you’re trying to display several maps which all have different non-overlapping bounding boxes. You need to reset the mapset’s region so that it covers all relevant maps. Is that it?
Is so, then
g.region -p vect=proj_pts,other_vector,third_vector
(This sets the current region to the min extent required to cover all the vectors)
HTH
On Thu, 25 Aug 2011, Micha Silver wrote:
I guess what you mean is that you're trying to display several maps which
all have different non-overlapping bounding boxes.
Micha,
One map has a different bounding box. They all should be the same. Last
evening I discovered that there was a typographic error in the ASCII lon/lat
file that did not generate an error by either cs2cs or v.in.ascii. They just
ate the wrong data and took me into this situation.
I'll write back in a while with the results of re-importing the corrected
data.
Toda,
Rich
On Thu, 25 Aug 2011, Micha Silver wrote:
I guess what you mean is that you're trying to display several maps which
all have different non-overlapping bounding boxes.
Got it fixed. Still needs tuning but it was a typo that did not assert an
error that caused the problem.
Thanks,
Rich