#1190 closed bug (fixed)
GRASS modules: v.out.ogr wrong for PostGIS
Reported by: | pcav | Owned by: | nobody |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.0.3 |
Component: | GRASS | Version: | Trunk |
Keywords: | Cc: | rblazek | |
Must Fix for Release: | Yes | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
the module v.out.ogr does not work for exporting data to PostGIS, as the module misses the crucial parameters (dbname etc.) for this format.
Attachments (1)
Change History (6)
comment:1 by , 15 years ago
follow-up: 3 comment:2 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in revision 10899. Added new script + qgis module with separate fields for each db connection parameter.
Work sponsored by http://www.faunalia.it
Radim
comment:3 by , 15 years ago
Replying to rblazek:
Fixed in revision 10899. Added new script + qgis module with separate fields for each db connection parameter.
Work sponsored by http://www.faunalia.it
Radim
I just tried those two scripts using QGIS 1.2 w/ GRASS 6.5.svn. I get a error message:
Traceback (most recent call last): File "/home/bobm/usr/share/qgis/grass/scripts/qgis.v.out.ogr.pg2.py", line 137, in <module> options, flags = grass.parser() AttributeError: 'module' object has no attribute 'parser'
I did a little check and found that this errors is related to a reorganization of grass.py (see http://trac.osgeo.org/grass/changeset/37447). I'm attaching a patch that seems to fix this problem.
Btw, I wasn't sure if I should reopen this ticket or submit a new one?
comment:4 by , 15 years ago
I have commited you patch in revision 10936. Non need to open a new ticket I believe. Thanks.
Radim
comment:5 by , 15 years ago
Cc: | added |
---|
The problem is not clear to me, on cmd line one has to enter:
Is it impossible to define dsn like that or just annoying? If the latter, could different fields be defined and composed on the fly to one dsn string?