Does v.category not work when connected to postgresql? I get a corrupt output for "v.category in=elev_contour_area out=elev_contour_area_cat op=add" on GRASS64.
The map is created and can be viewed, but there is no table and trying to view the attributes crashes GRASS.
Number of nodes: 878
Number of primitives: 869
Number of points: 0
Number of lines: 0
Number of boundaries: 457
Number of centroids: 412
Number of areas: 411
Number of isles: 411
Number of incorrect boundaries: 46
Number of duplicate centroids: 2
Number of areas without centroid: 1
v.category complete. 1 features modified.
Maybe this is a known issue?
Patrick
On Thu, Apr 17, 2014 at 2:48 PM, Patrick S. <patrick_GIS@gmx.ch> wrote:
Does v.category not work when connected to postgresql? I get a corrupt
output for "v.category in=elev_contour_area out=elev_contour_area_cat
op=add" on GRASS64.
The map is created and can be viewed, but there is no table and trying to
view the attributes crashes GRASS.
Number of nodes: 878
Number of primitives: 869
Number of points: 0
Number of lines: 0
Number of boundaries: 457
Number of centroids: 412
Number of areas: 411
Number of isles: 411
Number of incorrect boundaries: 46
Number of duplicate centroids: 2
Number of areas without centroid: 1
v.category complete. 1 features modified.
Maybe this is a known issue?
It would be very good to have a reproducible example with e.g. the
North Carolina data set since we do not have your data.
thanks
Markus