Re: [GRASS-user] Collapsing many layers into 1

2008-01-23 Thread Neil Godfrey
My problem is a little different. I have just one map, but many layers. I want to get one map, with just one layer. On Tue, 2008-01-22 at 10:58 +0100, Martin Landa wrote: Hi, 2008/1/22, Neil Godfrey [EMAIL PROTECTED]: The census 2000 administrative boundaries are shapefiles, where every

Re: [GRASS-user] Collapsing many layers into 1

2008-01-23 Thread Martin Landa
Hi, 2008/1/23, Neil Godfrey [EMAIL PROTECTED]: My problem is a little different. I have just one map, but many layers. I want to get one map, with just one layer. you can use `v.category chlayer=` to change layer number, but it will not touch attribute data. v.category in=map out=map_1

Re: [GRASS-user] Collapsing many layers into 1

2008-01-23 Thread Martin Landa
Hi, 2008/1/23, Martin Landa [EMAIL PROTECTED]: v.category in=map out=map_1 chlayer=2,1,3,1,4,1 ops, sorry, of course v.category in=map out=map_1 opt=chlayer layer=2,1,3,1,4,1 Martin -- Martin Landa [EMAIL PROTECTED] * http://gama.fsv.cvut.cz/~landa *

Re: [GRASS-user] Collapsing many layers into 1

2008-01-22 Thread Martin Landa
Hi, 2008/1/22, Neil Godfrey [EMAIL PROTECTED]: The census 2000 administrative boundaries are shapefiles, where every county is a separate file. So v.in.ogr creates a layer for every county. So for example, I get 83 layers for the 83 counties in Michigan, which correspond to 83 tables, each

[GRASS-user] Collapsing many layers into 1

2008-01-21 Thread Neil Godfrey
Hello, The census 2000 administrative boundaries are shapefiles, where every county is a separate file. So v.in.ogr creates a layer for every county. So for example, I get 83 layers for the 83 counties in Michigan, which correspond to 83 tables, each with just one category. What I want is one