[GRASS-user] d.vect not using RGB values in attribute table

last weeks CVS:

using d.vect with the -a flag is not coloring areas based on colors stored in the attribute table.

+------+-------+--------------+---------------+---------+----------+
| cat | muid | suborder_pct | soil_suborder | rgb | GRASSRGB |
+------+-------+--------------+---------------+---------+----------+
| 2735 | CA007 | 15 | orthents | 254:1:1 | 254:1:1 |
+------+-------+--------------+---------------+---------+----------+

tried using both an attribute named GRASSRGB, and specifying the column with the rgb_column=GRASSRGB flag

anyone else noticing this odd behavior?

Thanks!

--
Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis
530.754.7341

I added wcolumn= and wscale= options last week. Hmm.. -a flag works well for
me. Try the following:

g.gisenv set=DEBUG=3
d.vect mapname -a 2>&1 | grep colorstring

Do you see any message?

Huidae Cho

On Sun, May 21, 2006 at 01:22:18PM -0700, Dylan Beaudette wrote:

last weeks CVS:

using d.vect with the -a flag is not coloring areas based on colors stored in
the attribute table.

+------+-------+--------------+---------------+---------+----------+
| cat | muid | suborder_pct | soil_suborder | rgb | GRASSRGB |
+------+-------+--------------+---------------+---------+----------+
| 2735 | CA007 | 15 | orthents | 254:1:1 | 254:1:1 |
+------+-------+--------------+---------------+---------+----------+

tried using both an attribute named GRASSRGB, and specifying the column with
the rgb_column=GRASSRGB flag

anyone else noticing this odd behavior?

Thanks!

--
Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis
530.754.7341

_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser

Thanks for the quick reply Huidae,

After adjusting the DEBUG level, and executing the commands you suggested:

d.vect -a ca_statsgo 2>&1 | grep colorstring
D3/3: area 508: colorstring: 28:58:205
D3/3: area 2962: colorstring: 28:58:205
D3/3: element 11933: colorstring: 179:113:29
D3/3: element 12037: colorstring: 174:0:239
D3/3: element 12038: colorstring: 174:0:239
D3/3: element 12393: colorstring: 28:58:205
D3/3: element 12772: colorstring: 179:113:29
D3/3: element 12776: colorstring: 179:113:29
D3/3: element 13616: colorstring: 89:107:16
D3/3: element 13703: colorstring: 241:44:3
D3/3: element 13777: colorstring: 179:113:29
...

these appear to be the colors that I inserted into the attribute table, but my
polygons are still being filled with the default color of grey.

not sure what is going on...

I have just updated to todays CVS, and will check to see what happens when it
is done compiling.

Cheers,

Dylan

On Monday 22 May 2006 08:15, Huidae Cho wrote:

I added wcolumn= and wscale= options last week. Hmm.. -a flag works well
for me. Try the following:

g.gisenv set=DEBUG=3
d.vect mapname -a 2>&1 | grep colorstring

Do you see any message?

Huidae Cho

On Sun, May 21, 2006 at 01:22:18PM -0700, Dylan Beaudette wrote:
> last weeks CVS:
>
>
> using d.vect with the -a flag is not coloring areas based on colors
> stored in the attribute table.
>
> +------+-------+--------------+---------------+---------+----------+
>
> | cat | muid | suborder_pct | soil_suborder | rgb | GRASSRGB |
>
> +------+-------+--------------+---------------+---------+----------+
>
> | 2735 | CA007 | 15 | orthents | 254:1:1 | 254:1:1 |
>
> +------+-------+--------------+---------------+---------+----------+
>
> tried using both an attribute named GRASSRGB, and specifying the column
> with the rgb_column=GRASSRGB flag
>
> anyone else noticing this odd behavior?
>
> Thanks!
>
>
> --
> Dylan Beaudette
> Soils and Biogeochemistry Graduate Group
> University of California at Davis
> 530.754.7341
>
> _______________________________________________
> grassuser mailing list
> grassuser@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grassuser

--
Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis
530.754.7341

Ok, a bit more information.

Rebuilt with today's CVS, and noticed that following:

d.vect -a ca_statsgo 2>&1 | grep colorstring
D3/3: area 508: colorstring: 28:58:205
D3/3: area 2962: colorstring: 28:58:205
D3/3: element 11933: colorstring: 179:113:29
D3/3: element 12037: colorstring: 174:0:239
D3/3: element 12038: colorstring: 174:0:239
D3/3: element 12393: colorstring: 28:58:205
D3/3: element 12772: colorstring: 179:113:29
D3/3: element 12776: colorstring: 179:113:29
D3/3: element 13616: colorstring: 89:107:16
D3/3: element 13703: colorstring: 241:44:3
D3/3: element 13777: colorstring: 179:113:29
D3/3: element 13860: colorstring: 254:1:1
D3/3: element 14253: colorstring: 202:158:185
D3/3: element 14290: colorstring: 110:182:71
D3/3: element 14369: colorstring: 254:1:1
D3/3: element 14847: colorstring: 28:58:205
D3/3: element 15466: colorstring: 254:1:1
D3/3: element 15508: colorstring: 254:1:1
D3/3: element 15640: colorstring: 181:166:34

... however there are hundreds of polygons in this map, and yet I only see
about 20 lines matching 'colorstring' .. note that a VERY small number of
polygons are being filled with a non-grey color- but I cannot detect any
pattern.

hereis a sample screen shot showing the results of the previous command:

http://169.237.35.250/~dylan/temp/d.vect_probs.png

vectors are labeled with their GRASSRGB attribute, note that only one of the
vectors has a fill color that differs from the default.

Dylan

On Monday 22 May 2006 08:15, Huidae Cho wrote:

I added wcolumn= and wscale= options last week. Hmm.. -a flag works well
for me. Try the following:

g.gisenv set=DEBUG=3
d.vect mapname -a 2>&1 | grep colorstring

Do you see any message?

Huidae Cho

On Sun, May 21, 2006 at 01:22:18PM -0700, Dylan Beaudette wrote:
> last weeks CVS:
>
>
> using d.vect with the -a flag is not coloring areas based on colors
> stored in the attribute table.
>
> +------+-------+--------------+---------------+---------+----------+
>
> | cat | muid | suborder_pct | soil_suborder | rgb | GRASSRGB |
>
> +------+-------+--------------+---------------+---------+----------+
>
> | 2735 | CA007 | 15 | orthents | 254:1:1 | 254:1:1 |
>
> +------+-------+--------------+---------------+---------+----------+
>
> tried using both an attribute named GRASSRGB, and specifying the column
> with the rgb_column=GRASSRGB flag
>
> anyone else noticing this odd behavior?
>
> Thanks!
>
>
> --
> Dylan Beaudette
> Soils and Biogeochemistry Graduate Group
> University of California at Davis
> 530.754.7341
>
> _______________________________________________
> grassuser mailing list
> grassuser@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grassuser

--
Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis
530.754.7341

Interesting... Were these polygons displayed correctly before I added wcolumn=
and wscale=? Or is this the first time you use -a for this map? try to insert
the following line just above "} /* end if table_colors_flag */" in area.c:

fprintf(stderr, "colorstring:: area=%d cat=%d rgb=%d r=%d g=%d b=%d\n", area, cat, rgb, red, grn, blu);

and run the same command. If you don't mind, could you send me (without CC to
the list) a copy of the map?

Huidae Cho

On Mon, May 22, 2006 at 10:04:26AM -0700, Dylan Beaudette wrote:

Ok, a bit more information.

Rebuilt with today's CVS, and noticed that following:

d.vect -a ca_statsgo 2>&1 | grep colorstring
D3/3: area 508: colorstring: 28:58:205
D3/3: area 2962: colorstring: 28:58:205
D3/3: element 11933: colorstring: 179:113:29
D3/3: element 12037: colorstring: 174:0:239
D3/3: element 12038: colorstring: 174:0:239
D3/3: element 12393: colorstring: 28:58:205
D3/3: element 12772: colorstring: 179:113:29
D3/3: element 12776: colorstring: 179:113:29
D3/3: element 13616: colorstring: 89:107:16
D3/3: element 13703: colorstring: 241:44:3
D3/3: element 13777: colorstring: 179:113:29
D3/3: element 13860: colorstring: 254:1:1
D3/3: element 14253: colorstring: 202:158:185
D3/3: element 14290: colorstring: 110:182:71
D3/3: element 14369: colorstring: 254:1:1
D3/3: element 14847: colorstring: 28:58:205
D3/3: element 15466: colorstring: 254:1:1
D3/3: element 15508: colorstring: 254:1:1
D3/3: element 15640: colorstring: 181:166:34

... however there are hundreds of polygons in this map, and yet I only see
about 20 lines matching 'colorstring' .. note that a VERY small number of
polygons are being filled with a non-grey color- but I cannot detect any
pattern.

hereis a sample screen shot showing the results of the previous command:

http://169.237.35.250/~dylan/temp/d.vect_probs.png

vectors are labeled with their GRASSRGB attribute, note that only one of the
vectors has a fill color that differs from the default.

Dylan

On Monday 22 May 2006 08:15, Huidae Cho wrote:
> I added wcolumn= and wscale= options last week. Hmm.. -a flag works well
> for me. Try the following:
>
> g.gisenv set=DEBUG=3
> d.vect mapname -a 2>&1 | grep colorstring
>
> Do you see any message?
>
> Huidae Cho
>
> On Sun, May 21, 2006 at 01:22:18PM -0700, Dylan Beaudette wrote:
> > last weeks CVS:
> >
> >
> > using d.vect with the -a flag is not coloring areas based on colors
> > stored in the attribute table.
> >
> > +------+-------+--------------+---------------+---------+----------+
> >
> > | cat | muid | suborder_pct | soil_suborder | rgb | GRASSRGB |
> >
> > +------+-------+--------------+---------------+---------+----------+
> >
> > | 2735 | CA007 | 15 | orthents | 254:1:1 | 254:1:1 |
> >
> > +------+-------+--------------+---------------+---------+----------+
> >
> > tried using both an attribute named GRASSRGB, and specifying the column
> > with the rgb_column=GRASSRGB flag
> >
> > anyone else noticing this odd behavior?
> >
> > Thanks!
> >
> >
> > --
> > Dylan Beaudette
> > Soils and Biogeochemistry Graduate Group
> > University of California at Davis
> > 530.754.7341
> >
> > _______________________________________________
> > grassuser mailing list
> > grassuser@grass.itc.it
> > http://grass.itc.it/mailman/listinfo/grassuser

--
Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis
530.754.7341

Dylan,

Here is a screenshot of "d.vect -a mapname type=area". I have no idea what's
going on in your grass.

http://geni.ath.cx/tmp/screenshot.png

Does anyone have any idea?

Huidae Cho

On Mon, May 22, 2006 at 11:38:50AM -0700, Dylan Beaudette wrote:

On Monday 22 May 2006 10:16, Huidae Cho wrote:
> Interesting... Were these polygons displayed correctly before I added
> wcolumn= and wscale=? Or is this the first time you use -a for this map?
> try to insert the following line just above "} /* end if table_colors_flag
> */" in area.c:
>
> fprintf(stderr, "colorstring:: area=%d cat=%d rgb=%d r=%d g=%d b=%d\n",
> area, cat, rgb, red, grn, blu);
>
> and run the same command. If you don't mind, could you send me (without CC
> to the list) a copy of the map?
>
> Huidae Cho
>

Huidae,

thanks for the quick reply.

This is the first time that I have tried using the -a flag on this map.

here is a link to a shapefile of this map:
http://169.237.35.250/~dylan/temp/ca_suborder.tar.gz

I will try the source code modification a little later today.

Cheers,

Dylan

> On Mon, May 22, 2006 at 10:04:26AM -0700, Dylan Beaudette wrote:
> > Ok, a bit more information.
> >
> > Rebuilt with today's CVS, and noticed that following:
> >
> > d.vect -a ca_statsgo 2>&1 | grep colorstring
> > D3/3: area 508: colorstring: 28:58:205
> > D3/3: area 2962: colorstring: 28:58:205
> > D3/3: element 11933: colorstring: 179:113:29
> > D3/3: element 12037: colorstring: 174:0:239
> > D3/3: element 12038: colorstring: 174:0:239
> > D3/3: element 12393: colorstring: 28:58:205
> > D3/3: element 12772: colorstring: 179:113:29
> > D3/3: element 12776: colorstring: 179:113:29
> > D3/3: element 13616: colorstring: 89:107:16
> > D3/3: element 13703: colorstring: 241:44:3
> > D3/3: element 13777: colorstring: 179:113:29
> > D3/3: element 13860: colorstring: 254:1:1
> > D3/3: element 14253: colorstring: 202:158:185
> > D3/3: element 14290: colorstring: 110:182:71
> > D3/3: element 14369: colorstring: 254:1:1
> > D3/3: element 14847: colorstring: 28:58:205
> > D3/3: element 15466: colorstring: 254:1:1
> > D3/3: element 15508: colorstring: 254:1:1
> > D3/3: element 15640: colorstring: 181:166:34
> >
> >
> > ... however there are hundreds of polygons in this map, and yet I only
> > see about 20 lines matching 'colorstring' .. note that a VERY small
> > number of polygons are being filled with a non-grey color- but I cannot
> > detect any pattern.
> >
> > hereis a sample screen shot showing the results of the previous command:
> >
> > http://169.237.35.250/~dylan/temp/d.vect_probs.png
> >
> > vectors are labeled with their GRASSRGB attribute, note that only one of
> > the vectors has a fill color that differs from the default.
> >
> > Dylan
> >
> > On Monday 22 May 2006 08:15, Huidae Cho wrote:
> > > I added wcolumn= and wscale= options last week. Hmm.. -a flag works
> > > well for me. Try the following:
> > >
> > > g.gisenv set=DEBUG=3
> > > d.vect mapname -a 2>&1 | grep colorstring
> > >
> > > Do you see any message?
> > >
> > > Huidae Cho
> > >
> > > On Sun, May 21, 2006 at 01:22:18PM -0700, Dylan Beaudette wrote:
> > > > last weeks CVS:
> > > >
> > > >
> > > > using d.vect with the -a flag is not coloring areas based on colors
> > > > stored in the attribute table.
> > > >
> > > > +------+-------+--------------+---------------+---------+----------+
> > > >
> > > > | cat | muid | suborder_pct | soil_suborder | rgb | GRASSRGB |
> > > >
> > > > +------+-------+--------------+---------------+---------+----------+
> > > >
> > > > | 2735 | CA007 | 15 | orthents | 254:1:1 | 254:1:1 |
> > > >
> > > > +------+-------+--------------+---------------+---------+----------+
> > > >
> > > > tried using both an attribute named GRASSRGB, and specifying the
> > > > column with the rgb_column=GRASSRGB flag
> > > >
> > > > anyone else noticing this odd behavior?
> > > >
> > > > Thanks!
> > > >
> > > >
> > > > --
> > > > Dylan Beaudette
> > > > Soils and Biogeochemistry Graduate Group
> > > > University of California at Davis
> > > > 530.754.7341
> > > >
> > > > _______________________________________________
> > > > grassuser mailing list
> > > > grassuser@grass.itc.it
> > > > http://grass.itc.it/mailman/listinfo/grassuser
> >
> > --
> > Dylan Beaudette
> > Soils and Biogeochemistry Graduate Group
> > University of California at Davis
> > 530.754.7341

--
Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis
530.754.7341

On Monday 22 May 2006 11:47, Huidae Cho wrote:

Dylan,

Here is a screenshot of "d.vect -a mapname type=area". I have no idea
what's going on in your grass.

http://geni.ath.cx/tmp/screenshot.png

Does anyone have any idea?

Huidae Cho

Yikes... I just tried re-importing the shapefile that I sent you, and it
renders correctly.... I wonder if this has something to do with db
connectivity / naming issues...

I tried making a copy of the GRASS vector such that the copy had matching
vector and table names... but colors are still not displayed correctly.

I might have to give up on this for now, but it is very odd that features are
not being colored in the original vector.

I connected up the original table to the vector in question, and added a
GRASSRGB column to it. These colors displayed fine. However connecting a
different table to the same vector results in only a few areas being colored.
Interactively querying the vector with d.what.vect reveals that there are in
fact attributes associated with these areas, including the GRASSRGB values...

Dylan

On Mon, May 22, 2006 at 11:38:50AM -0700, Dylan Beaudette wrote:
> On Monday 22 May 2006 10:16, Huidae Cho wrote:
> > Interesting... Were these polygons displayed correctly before I added
> > wcolumn= and wscale=? Or is this the first time you use -a for this
> > map? try to insert the following line just above "} /* end if
> > table_colors_flag */" in area.c:
> >
> > fprintf(stderr, "colorstring:: area=%d cat=%d rgb=%d r=%d g=%d b=%d\n",
> > area, cat, rgb, red, grn, blu);
> >
> > and run the same command. If you don't mind, could you send me
> > (without CC to the list) a copy of the map?
> >
> > Huidae Cho
>
> Huidae,
>
> thanks for the quick reply.
>
> This is the first time that I have tried using the -a flag on this map.
>
> here is a link to a shapefile of this map:
> http://169.237.35.250/~dylan/temp/ca_suborder.tar.gz
>
> I will try the source code modification a little later today.
>
> Cheers,
>
> Dylan
>
> > On Mon, May 22, 2006 at 10:04:26AM -0700, Dylan Beaudette wrote:
> > > Ok, a bit more information.
> > >
> > > Rebuilt with today's CVS, and noticed that following:
> > >
> > > d.vect -a ca_statsgo 2>&1 | grep colorstring
> > > D3/3: area 508: colorstring: 28:58:205
> > > D3/3: area 2962: colorstring: 28:58:205
> > > D3/3: element 11933: colorstring: 179:113:29
> > > D3/3: element 12037: colorstring: 174:0:239
> > > D3/3: element 12038: colorstring: 174:0:239
> > > D3/3: element 12393: colorstring: 28:58:205
> > > D3/3: element 12772: colorstring: 179:113:29
> > > D3/3: element 12776: colorstring: 179:113:29
> > > D3/3: element 13616: colorstring: 89:107:16
> > > D3/3: element 13703: colorstring: 241:44:3
> > > D3/3: element 13777: colorstring: 179:113:29
> > > D3/3: element 13860: colorstring: 254:1:1
> > > D3/3: element 14253: colorstring: 202:158:185
> > > D3/3: element 14290: colorstring: 110:182:71
> > > D3/3: element 14369: colorstring: 254:1:1
> > > D3/3: element 14847: colorstring: 28:58:205
> > > D3/3: element 15466: colorstring: 254:1:1
> > > D3/3: element 15508: colorstring: 254:1:1
> > > D3/3: element 15640: colorstring: 181:166:34
> > >
> > >
> > > ... however there are hundreds of polygons in this map, and yet I
> > > only see about 20 lines matching 'colorstring' .. note that a VERY
> > > small number of polygons are being filled with a non-grey color- but
> > > I cannot detect any pattern.
> > >
> > > hereis a sample screen shot showing the results of the previous
> > > command:
> > >
> > > http://169.237.35.250/~dylan/temp/d.vect_probs.png
> > >
> > > vectors are labeled with their GRASSRGB attribute, note that only one
> > > of the vectors has a fill color that differs from the default.
> > >
> > > Dylan
> > >
> > > On Monday 22 May 2006 08:15, Huidae Cho wrote:
> > > > I added wcolumn= and wscale= options last week. Hmm.. -a flag works
> > > > well for me. Try the following:
> > > >
> > > > g.gisenv set=DEBUG=3
> > > > d.vect mapname -a 2>&1 | grep colorstring
> > > >
> > > > Do you see any message?
> > > >
> > > > Huidae Cho
> > > >
> > > > On Sun, May 21, 2006 at 01:22:18PM -0700, Dylan Beaudette wrote:
> > > > > last weeks CVS:
> > > > >
> > > > >
> > > > > using d.vect with the -a flag is not coloring areas based on
> > > > > colors stored in the attribute table.
> > > > >
> > > > > +------+-------+--------------+---------------+---------+--------
> > > > >--+
> > > > >
> > > > > | cat | muid | suborder_pct | soil_suborder | rgb |
> > > > > | GRASSRGB |
> > > > >
> > > > > +------+-------+--------------+---------------+---------+--------
> > > > >--+
> > > > >
> > > > > | 2735 | CA007 | 15 | orthents | 254:1:1 | 254:1:1
> > > > > | |
> > > > >
> > > > > +------+-------+--------------+---------------+---------+--------
> > > > >--+
> > > > >
> > > > > tried using both an attribute named GRASSRGB, and specifying the
> > > > > column with the rgb_column=GRASSRGB flag
> > > > >
> > > > > anyone else noticing this odd behavior?
> > > > >
> > > > > Thanks!
> > > > >
> > > > >
> > > > > --
> > > > > Dylan Beaudette
> > > > > Soils and Biogeochemistry Graduate Group
> > > > > University of California at Davis
> > > > > 530.754.7341
> > > > >
> > > > > _______________________________________________
> > > > > grassuser mailing list
> > > > > grassuser@grass.itc.it
> > > > > http://grass.itc.it/mailman/listinfo/grassuser
> > >
> > > --
> > > Dylan Beaudette
> > > Soils and Biogeochemistry Graduate Group
> > > University of California at Davis
> > > 530.754.7341
>
> --
> Dylan Beaudette
> Soils and Biogeochemistry Graduate Group
> University of California at Davis
> 530.754.7341

--
Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis
530.754.7341