The bug is reported by Maciek Sieczka before, look at
http://grass.itc.it/pipermail/grass5/2005-January/017090.html.
I guess it is not taken care of after that.
Geir
-----Original Message-----
From: Systad, Geir
Sent: Thursday, March 17, 2005 12:40 PM
To: grasslist@baylor.edu; wingrass@grass.itc.it
Subject: RE: [GRASSLIST:6193] V.in.ogr and coor file bytes excessWhen importing shapefiles with areas in the graphical
interface, it hangs (even when the location is projected, and
when both the shapefile and the location is projected, it
doesn't matter), and the new vector file is incomplete. When
submitting the same commands as developed in the graphical
interface, it works fine.v.in.ogr dsn=/cygdrive/c/xxx/periode1a.shp output=p1a
min_area=0.0001 snap=-1Then I have a problem with the graphical interface of
v.in.ogr, both for grass6.0.0Cygwin and grass6.1.cvsCygwin.
Has any other seen this?Geir
System information
OS Name Microsoft Windows 2000 Professional
Version 5.0.2195 Service Pack 4 Build 2195
OS Manufacturer Microsoft Corporation
System Name xxx
System Manufacturer Dell Computer Corporation
System Model Precision M40
System Type X86-based PC
Processor x86 Family 6 Model 11 Stepping 1 GenuineIntel ~1196 Mhz
BIOS Version Phoenix ROM BIOS PLUS Version 1.10 A04
Windows Directory C:\WINNT
System Directory C:\WINNT\system32CYGWIN System Information
Platform Unix
Operating System CYGWIN_NT-5.0
OS Version 1.5.13(0.122/4/2)
Processor Type (arch) i686
Full OS ID CYGWIN_NT-5.0-1.5.13(0.122/4/2)-i686
Tcl Version/Patchlevel 8.4.7
Name of Executable /usr/local/bin/wish
Name of current Script /usr/local/grass6.1.cvs/etc/dm/tksys.tcl-----Original Message-----
From: owner-GRASSLIST@baylor.edu
[mailto:owner-GRASSLIST@baylor.edu] On Behalf Of Systad, Geir
Sent: Wednesday, March 16, 2005 2:14 PM
To: grasslist@baylor.edu; wingrass@grass.itc.it
Subject: [GRASSLIST:6193] V.in.ogr and coor file bytes excessSorry for the last header, it was not an answere to the
GRASSLIST:6191 message -I use the graphical interface of Grass6.0.0 Cygwin stable
(feb something).
I have tried to import shapefiles into grass, and get messages like
this:v.in.ogr dsn=/cygdrive/c/xxx/periode1a.shp output=p1a
min_area=0.0001 snap=-1
PROJ_INFO file not found for location N50kart
PROJ_UNITS file not found for location N50kart
Projection of input dataset and current location appear to
match. Proceeding with import...
Layer: periode1a
Building topology ...
Registering lines:
238 primitives registered
Building areas:238 areas built
238 isles built
Attaching islands:
Attaching centroids:When I try to present it on maps, only the boundaries of the
areas show up -GRASS 6.0.0 (N50kart):~ > WARNING: coor files of vector
'p1a@PERMANENT' is larger than it should be
(33479 bytes excess).
WARNING: Cannot display areas, topology not available
WARNING: Cannot display topology, not availableWhen I use v.external, the map writes out afterwards without
problems. The number of primitives is different.v.external dsn=/cygdrive/c/xxx/periode1a.shp output=p1d
layer=periode1a
Building topology ...eature: 100 200 238
Topology was built.
Number of nodes : 476
Number of primitives: 476
Number of points : 0
Number of lines : 0
Number of boundaries: 238
Number of centroids : 238
Number of areas : 238
Number of isles : 238What is the problem with the coor file made by v.in.ogr? Can
anyone help?Sincerely,
Geir