[Bug] v.colors prevents display of object boundaries

[cmbarton]

Describe the bug

When a color table for a vector map is created using v.colors, there is no way to display the object boundaries. As best I a tell, what happens is that both the object fill and the object feature (border) are assigned the same colors. Because of this, object borders become invisible. This considerably reduces the usefulness of assigning colors in this way. There needs to be a way of differentiating the object border from the fill so as to more clearly distinguish vector objects.

Screenshots

Census map from the NC sample data with a 'reds' color table assigned to census tracks using the TOTAL_POP attribute

System description

• Operating System: Mac OS 15.5
• GRASS GIS version: 8.5f

[echoix]

Is this related to the behavior you're describing? #1146

[cmbarton]

I'm not sure. That discussion was long and involved other aspects of vector display. But this gets somewhat weirder. The borders are not drawn ONLY if a filter is created in the where argument of d.vect.

I had set where to TOTAL_POP>0. Lines are only drawn for areas with values below the minimum in the v.colors range argument. But when I removed the filter in d.vect, border lines were drawn for ALL areas.

[petrasovaa]

It looks this bug is solved by #1146, but that solution had some issues and it was probably unclear what it is we want.