[GRASS-user] simple way to join some attribute data w/o geometries

[Benjamin Ducke]

Alright. One more question. Probably stupid, but I haven't done much
DBMS management with GRASS up to now, so here it goes:

what is the default DB output format (backend) for db.in.ogr?

The one that is currently active (db.connect)?
If that's DBF, then we would still face the problem that the user
can't use v.db.join on it unless we patch that one, too, no?

Benjamin


Markus Neteler wrote:
> On Jan 8, 2008 4:20 PM, Markus Neteler <neteler at osgeo.org> wrote:
>> On Jan 8, 2008 3:36 PM, Benjamin Ducke <benjamin.ducke at ufg.uni-kiel.de> wrote:
> ...
>>> Question is:
>>>
>>> Patch the actual OGR sources or the stuff in grass6/db/drivers/ogr or
>>> the db.in.ogr module itself? Where would be the best place to put the
>>> type recognition?
>> db.in.ogr simply calls v.in.ogr which calls OGR lib which calls OGR-CSV
>> driver... the best place is there:
>>
>> - if .csvt is there, use it
>> - if .csvt is absent, try recognition. Have env var to disable/enable this.
>> - if .csvt is absent and recognition disable, proceed as usual
>>
>> Or rewrite db.in.ogr as C program...
> 
> Ah sorry, another idea:
> 
> - or fix that C program to become an $ETC tool for GRASS which simply
> creates the .csvt file! That could be an elegant and easy solution.
> 
> Store in tools/csvdetect/ or so then within GRASS.
> 
> Good luck,
> Markus
> 
> 

-- 
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel
Johanna-Mestorf-Straße 2-6
D 24098 Kiel
Germany

Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg