[GRASS-user] v.colors usage [UPDATE]
st_kiefer at web.de
st_kiefer at web.de
Tue Nov 6 00:06:36 PST 2018
Hi Rich,
are there any entries in the table with bin_col is empty, i.e. null? I am not sure in this context, but I know from other cases that database driver failed in recognizing the datatype of a field while checking the first dataset in the table and the field was not set (i.e. null).
Regards.
Stefan
> Rich Shepard <rshepard at appl-ecosys.com> hat am 6. November 2018 um 00:02 geschrieben:
>
>
>
> On Sat, 3 Nov 2018, Rich Shepard wrote:
>
> >> v.colors -c map=stations use=attr column=site_nbr rgb_col=bin_col --o
> > Writing color rules...
> > ERROR: Data type of RGB column <bin_col> must be char
> >
> > Where have I made the syntactical mistake?
>
> I slightly modified the command to use a different column:
> > v.colors -c map=stations use=attr column=howmany rgb_col=bin_col --o
> Writing color rules...
> ERROR: Data type of RGB column <bin_col> must be char
>
> Checking that grass saw the postgres table:
> > db.connect -p
> driver: pg
> database: willamette-river-hg
> schema:
> group:
>
> Yep, it does.
>
> Looking at the table structure:
>
> > db.describe table=stations
> table:stations
> description:
> insert:?
> delete:?
> ncols:10
> nrows:82
> ...
>
> column:howmany
> description:
> type:INTEGER
> len:4
> scale:0
> precision:0
> default:
> nullok:yes
> select:?
> update:?
>
> column:bin_col
> description:
> type:CHARACTER
> len:12
> scale:0
> precision:0
> default:
> nullok:yes
> select:?
> update:?
>
> So, why does grass tell me the bin_col column needs to be CHAR when it is
> (unless grass differentiates between char and CHARACTER.)
>
> Rich
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
More information about the grass-user
mailing list