When I first ran analyses and created maps for this project it was about
18 months ago, and my notes are not as complete as I would wish.
I have an ASCII file with 5 rows and 3 columns: easting, northing, and
label. I ran that through v.in.ascii (after setting the region
appropriately) and it worked:
WARNING: Vector map <proj_pts> already exists and will be overwritten
Scanning input for column types...
Maximum input row length: 32
Maximum number of columns: 3
Minimum number of columns: 3
Column: 1 type: double
Column: 2 type: double
Column: 3 type: string length: 11
Importing points...
100%
Populating table...
v.in.ascii complete.
But, when I try to display this map GRASS tells me I cannot do so:
GRASS 6.5.svn (Oregon):~/grassdata/Oregon/beaver_lake > d.vect map=proj_pts
WARNING: Unable to display areas, topology not available
I also cannot disply it using the gui.
Since I'm not seeing what I'm not doing correctly I humbly ask for
assistance.
TIA,
Rich
On Tue, 23 Aug 2011, Rich Shepard wrote:
GRASS 6.5.svn (Oregon):~/grassdata/Oregon/beaver_lake > d.vect map=proj_pts
WARNING: Unable to display areas, topology not available
Rebuilding the topology fixed the problem. I thought that points had no
topology as they are unrelated to each other.
Rich
On Wed, Aug 24, 2011 at 12:48 AM, Rich Shepard <rshepard@appl-ecosys.com> wrote:
On Tue, 23 Aug 2011, Rich Shepard wrote:
GRASS 6.5.svn (Oregon):~/grassdata/Oregon/beaver_lake > d.vect
map=proj_pts
WARNING: Unable to display areas, topology not available
Rebuilding the topology fixed the problem. I thought that points had no
topology as they are unrelated to each other.
Also points have some support structures which are built together with
topology, e.g. a spatial index needed in turn by v.what, v.select,
v.overlay etc.
Looking at the above warning, d.vect map=proj_pts type=point should
work even without topology.
Markus M
On Wed, 24 Aug 2011, Markus Metz wrote:
Also points have some support structures which are built together with
topology, e.g. a spatial index needed in turn by v.what, v.select,
v.overlay etc.
Thank you, Markus. I'll keep this for future reference.
Looking at the above warning, d.vect map=proj_pts type=point should
work even without topology.
Should, ... but it didn't here. 
Today's task is to determine why this revised points map does not display
with the other maps in a script. Before I added the two points the shell script
ran and the points and their associated labels were there. Now they're not.
I know it doesn't make sense so I need to reproduce the script commands one
at a time in the GUI and see where it fails. Always something.
Rich
On Wed, 24 Aug 2011, Markus Metz wrote:
Looking at the above warning, d.vect map=proj_pts type=point should work
even without topology.
Markus,
It turns out that the entire issue about mis-matched boundary boxes was
caused by my mistakes: DMS values that are invalid (e.g., > 60 minutes or
seconds). What surprised me is that v.in.ascii did not catch these errors,
nor did cs2cs.
Would it be practical and useful to have domain checks in input routines?
Rich