Opened 6 years ago
Last modified 6 years ago
#3836 new defect
GRASS: db.in.ogr fails where v.in.ogr succeeds
| Reported by: | Lads | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.6.2 |
| Component: | Database | Version: | unspecified |
| Keywords: | db.in.ogr | Cc: | |
| CPU: | x86-64 | Platform: | Linux |
Description
This report refers to GRASS 7.6. To import a spatial table from PostGIS I use, successfully, the following formulation with v.in.ogr:
> v.in.ogr input="PG:host=pg-server dbname=dsm user=duque004 password=secret" layer="observations.profiles" output=profiles -o Over-riding projection check Check if OGR layer <observations.profiles> contains polygons... ERROR 1: Could not fetch SRS: 100% Creating attribute table for layer <observations.profiles>... Importing 141584 features (OGR layer <observations.profiles>)... 100% ----------------------------------------------------- Building topology for vector map <profiles@test>... Registering primitives...
But if I feed the same parameters to db.in.ogr, it fails to find the table:
> db.in.ogr input="PG:host=pg-server dbname=dsm user=duque004 password=secret" db_table="observations.profiles" output=profiles
ERROR: Unable to open data source <observations.profiles>
ERROR: Input table <observations.profiles> not found or not
readable
This bug report is related to the following discussions at StackExchange:
Change History (1)
comment:1 by , 6 years ago
| Component: | Vector → Database |
|---|---|
| Keywords: | db.in.ogr added |
| Milestone: | → 7.6.2 |
Note:
See TracTickets
for help on using tickets.
