gis.m/Map Display fails to handle vector layers with multiple databse layers
|Reported by:||ploewe||Owned by:|
|Keywords:||gis.m database query||Cc:|
GRASS 6.3 gives strange effects when one is attempting to query or display data from database layers greater than 1. This can be reproduced.
A polygon layer has been connected (in postgres) to two tables in layer 1 and layer 2:
GRASS 6.3.0 (meteo):~ > v.db.connect -p map=counties_pie01 Vector map <counties_pie01> is connected by: layer <1> table <counties_pie01> in database <host=localhost,dbname=meteo> through driver <pg> with key <cat> layer <2> table <counties_pie01_a> in database <host=localhost,dbname=meteo> through driver <pg> with key <cat>
The layer can be displayed in a map display, including its centroids. While the "Layer for labels"/"Layer for query" is set to 1 (default), performance is normal.
Hell breaks loose when the "Layer for query" is set to "2": Out of a sudden all centroids and filled areas disappear from from the map display (polygon outlines are still displayed).
The phenomena for "Layer for label"=2 are less severe: A "Attribute col for labels" from the second table is just ignored, while polygon outlines, area fills and centroids are properly rendered.
The gis.m output window does not provide any error messages or warnings while these phenomena occur.
Change History (9)
follow-ups: 3 4 comment:2 by , 13 years ago
|Component:||Tcl → Vector|
|CPU:||x86-32 → OSX/Intel|
|Platform:||Linux → All|
|Version:||6.3.0 → svn-develbranch6|