Opened 6 years ago

Closed 6 years ago

#3262 closed defect (fixed)

v.external.out: SRID lost when not exactly defined

Reported by: martinl Owned by: grass-dev@…
Priority: normal Milestone: 7.2.1
Component: Vector Version: svn-trunk
Keywords: v.external.out, postgis Cc:
CPU: Unspecified Platform: Unspecified

Description

We assume that we have location with EPSG defined:

g.proj -p
...
-PROJ_EPSG-------------------------------------------------
epsg       : 5514
...

We define external format (PostGIS in our case):

v.external.out output="PG:dbname=grassdb" format=PostgreSQL

and run some module

v.random p1 n=1000 -b

Check result:

psql grassdb -c "select f_table_name, srid from geometry_columns"
 f_table_name | srid 
--------------+------
 p1           |    0

SRID information is lost.

Change History (5)

comment:1 by martinl, 6 years ago

Note that currently it's possible to force SRID by G72:v.external.out option parameter which helps to overcome this issue.

v.external.out output="PG:dbname=grassdb" format=PostgreSQL options=SRID=5514
v.random p1 n=1000 -b --o
psql grassdb -c "select f_table_name, srid from geometry_columns"
 f_table_name | srid 
--------------+------
 p1           | 5514
Last edited 6 years ago by martinl (previous) (diff)

comment:2 by martinl, 6 years ago

In 70385:

v.external.out: SRID lost when not exactly defined (see #3262)

comment:3 by martinl, 6 years ago

Should be fixed in trunk (r70385). If no objection than will be backported to relbr72/70.

comment:4 by martinl, 6 years ago

In 70422:

v.external.out: SRID lost when not exactly defined (see #3262)

comment:5 by martinl, 6 years ago

Resolution: fixed
Status: newclosed

In 70424:

v.external.out: SRID lost when not exactly defined (fix #3262)

(merge r70422 from relbr72)

Note: See TracTickets for help on using tickets.