v.to.rast allow to use label_column alone

[marisn]

At the moment v.to.rast only supports label_column together with attr_column. It makes perfect sense, still misses one use case - when attr_column is absent and only labels are present. I.e. when attribute table contains land use labels but not class codes.

Proposal is to generate codes on the fly if only label column is provided.

How it could work: select labelcolumn from db distinct; Enumerate output rows; Use row number as a raster category.

[neteler]

Milestone renamed

[mmetz]

Replying to marisn:

At the moment v.to.rast only supports label_column together with attr_column. It makes perfect sense, still misses one use case - when attr_column is absent and only labels are present. I.e. when attribute table contains land use labels but not class codes.

Proposal is to generate codes on the fly if only label column is provided.

How it could work: select labelcolumn from db distinct; Enumerate output rows; Use row number as a raster category.

You can use v.reclass + v.to.rast, e.g. with the NC dataset

v.reclass in=soils_general@PERMANENT out=soils_reclass layer=1 column=GSL_NAME
g.region -pa vect=soils_reclass res=100
v.to.rast in=soils_reclass layer=1 use=cat label_column=GSL_NAME

or write a script that does the above for any given vector and label column for general use.

[neteler]

Ticket retargeted after milestone closed

[martinl]

All enhancement tickets should be assigned to 7.4 milestone.

[neteler]

Ticket retargeted after milestone closed

[martinl]

All enhancement tickets should be assigned to 7.6 milestone.

[martinl]

Ticket retargeted after milestone closed

[martinl]

Ticket retargeted after milestone closed