[GRASS-user] v.out.postgis

[Paul Shapley]

Hi Moritz,

My apologies... it appears that the result of 'r.to.vect was indeed sending
the attributes to postgres but i was expecting them to appear in sqlite had
i 'refreshed' the posgres schema i would have seen them.

Best Wishes and thank you,

Paul Shapley

On 29 June 2018 at 14:50, Moritz Lennert <mlennert at club.worldonline.be>
wrote:

> On 29/06/18 12:38, Paul Shapley wrote:
>
>> 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)
>>
>
> So, apparently your vector map is linked to a table that does not exist.
> Or it exists but not in the schema grass_gis. You will have to correct the
> link between the map and its attribute table before you can export it.
>
> Moritz
>
>


-- 
*Paul J. Shapley *MSc CGeog (GIS) FRGS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20180629/6639dada/attachment-0001.html>