Hi Moritz,
Here is the result:-
v.db.select APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector
DBMI-PostgreSQL driver error:
Unable to select:
SELECT * FROM grass_gis.APGB_aerial_2_i_segment_drained_peat
_with_exposed_haggs_vector
ERROR: relation "grass_gis.apgb_aerial_2_i_segment_drained_
peat_with_exposed_haggs_vector" does not exist
LINE 1: SELECT * FROM
grass_gis.APGB_aerial_2_i_segment_drained_peat...
^
DBMI-PostgreSQL driver error:
Unable to select:
SELECT * FROM grass_gis.APGB_aerial_2_i_segment_drained_peat
_with_exposed_haggs_vector
ERROR: relation "grass_gis.apgb_aerial_2_i_segment_drained_
peat_with_exposed_haggs_vector" does not exist
LINE 1: SELECT * FROM
grass_gis.APGB_aerial_2_i_segment_drained_peat...
^
ERROR: Unable to open select cursor
(Fri Jun 29 11:24:18 2018) Command finished (0 sec)
---------------------------------------------------------------------------------------------
I have two databases that i use in grass, the (sqlite.db) for vector data
(e.g using r.to.vect) then i usually export the results to
postgresql/postgis (webgis). The 'db.login' file holds the PostGIS details
above the sqlite details. If i try to open the attributes (of sqlite) from
within Grass it is trying to find them in postgres/postgis (webgis). see
cmdline error:-
GRASS_INFO_WARNING<1408,1>:Table
<grass_gis.APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector>
not found in database <webgis> using driver <pg> GRASS_INFO_END<1408,1>
Is the order of the connection details in 'pg.login' important?
Paul Shapley
On 29 June 2018 at 11:17, Moritz Lennert <[email protected]>
wrote:
> On 29/06/18 10:39, Paul Shapley wrote:
>
>> Hi Markus,
>>
>> OK here is the result of v.db.connect -p
>>
>> v.db.connect -p APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_
>> vector
>> Vector map <APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector>
>> is connected by:
>> layer
>> <1/grass_gis.APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector>
>> table
>> <grass_gis.APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector>
>> in database <webgis> through driver <pg> with key <cat>
>>
>
> So it's PostgreSQL as attribute database backend.
>
> What is the output of
>
> v.db.select APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector
>
> ?
>
> Moritz
>
>
>> I recall some years ago you had to delete the 'db.login' file and
>> recreate it but this would lose the connection to the vector layer
>> attribute table (sqlite.db).
>>
>> Thanks,
>>
>> Paul Shapley
>>
>> On 28 June 2018 at 13:22, Markus Metz <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>
>>
>> On Thu, Jun 28, 2018 at 1:40 PM, Moritz Lennert
>> <[email protected] <mailto:[email protected]>>
>> wrote:
>> >
>> > On 28/06/18 09:59, Paul Shapley wrote:
>> >>
>> >> Hi,
>> >>
>> >> I am trying to export a vector map to PostGIS. Has anyone come
>> across the 'Unable to describe table' error? I suspect my config
>> could be wrong.
>> >>
>> >> v.out.postgis --overwrite
>> input=APGB_aerial_2_i_segment_drained_peat_with_exposed_hagg
>> s_vct@PERMANENT
>> output=PG:dbname=webgis
>> output_layer=APGB_aerial_2_i_segment_drained_peat_with_expos
>> ed_haggs_vct
>> options=FID=cat, GEOMETRY_NAME=wkb_geometry, SPATIAL_INDEX=YES,
>> PRIMARY_KEY=YES
>> >> DBMI-PostgreSQL driver error:
>> >> select * from grass_gis.APGB_aerial_2_i_segment_drained_peat
>> >> _with_exposed_haggs_vct where 1 = 0
>> >> ERROR: relation "grass_gis.apgb_aerial_2_i_segment_drained_
>> >> peat_with_exposed_haggs_vct" does not exist
>> >> LINE 1: select * from
>> >> grass_gis.APGB_aerial_2_i_segment_drained_peat...
>> >> ^
>> >> DBMI-PostgreSQL driver error:
>> >> select * from grass_gis.APGB_aerial_2_i_segment_drained_peat
>> >> _with_exposed_haggs_vct where 1 = 0
>> >> ERROR: relation "grass_gis.apgb_aerial_2_i_segment_drained_
>> >> peat_with_exposed_haggs_vct" does not exist
>> >> LINE 1: select * from
>> >> grass_gis.APGB_aerial_2_i_segment_drained_peat...
>> >> ^
>> >> *ERROR: Unable to describe table*
>> <grass_gis.APGB_aerial_2_i_segment_drained_peat_with_exposed
>> _haggs_vct>
>> >
>> >
>> > It looks like it is trying to read the input attrubute table from
>> postgresql (schema grass_gis). Do you use PostgreSQL as attribute
>> table backend ? Could you provide the output of db.connect -p in
>> that mapset ?
>>
>> ore precise would be
>> v.db.connect -p
>> APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vct@PERMANENT
>>
>> because there may be a bug in v.out.postgis, not properly reading
>> the database connection of the input vector.
>>
>> Markus Metz
>>
>> >
>> > Moritz
>> >
>> > _______________________________________________
>> > grass-user mailing list
>> > [email protected] <mailto:[email protected]>
>> > https://lists.osgeo.org/mailman/listinfo/grass-user
>> <https://lists.osgeo.org/mailman/listinfo/grass-user>
>>
>>
>>
>>
>> --
>> *Paul J. Shapley *MSc CGeog (GIS) FRGS
>> *
>> *
>>
>>
>> _______________________________________________
>> grass-user mailing list
>> [email protected]
>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>
>>
>
>
--
*Paul J. Shapley *MSc CGeog (GIS) FRGS
_______________________________________________
grass-user mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-user
