[GRASS-dev] Vector file naming

[Moritz Lennert]

Hamish wrote:
> Moritz Lennert wrote:
>> Yes, but r.to.vect doesn't allow you _not_ to create the
>> table...unless  you work with point data.
> 
> a -t flag could be added, please file as a wish if this is important to
> your work.

I actually think that maybe an option defining the table name of the 
table to be created together with the map might be the best solution. 
But this is valid for more than just r.to.vect (v.in.ogr jumps to mind).

But it has never been a problem for me.

Brad wrote:
> I understand the logic behind the present behavior, but I believe that
> logic would be best served if GRASS ceased to use it's own format and
> went with a real spatially aware SQL backend (there are several to
> choose from and SQLite as middleware makes interfacing a breeze).
> Perhaps, this will be the next incarnation of the vector architecture as
> spatial databases have matured significantly in recent years.

I don't really understand how this solves your problem. In a spatially 
aware SQL backend you wouldn't be able to use dots in table/map names 
either, or ?

Moritz