[GRASS-user] import a folder full of shapefiles and reproject on-the-fly?

[Paul Kelly]

On Thu, 24 Jul 2008, Moritz Lennert wrote:

> I won't make an issue of this, but there is a difference in that v.in.ogr 
> takes a data source (directory or file) as input, and this data source can 
> contain many layers. AFAIK, it's the only *.in.* module to do this.
>
> But I don't care enough to worry about it... loops work fine for me. Just 
> don't really understand the advantage of loading all layers into different 
> layers of a GRASS map...

If I might barge in here and suggest a couple of things without fully 
researching the issue, perhaps (a) this is the simplest solution to avoid 
the problem of conflicting category IDs in the different Shapefiles 
and associated dbf files - I would hazard a guess that category IDs 
can be duplicated between GRASS layers? Complicated cat-renumbering 
systems are thus neatly avoided by using separate layers. And (b) given 
discussion in the past about how confusing the GRASS concept of layers 
is, this would seem to be a case where the GRASS term "layer" makes 
perfect sense in the context - perhaps the term originally derived from 
this analogy with the OGR data model?

Paul