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

[martinl]

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.

[martinl]

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 retia -c "select f_table_name, srid from geometry_columns"
 f_table_name | srid 
--------------+------
 p1           | 5514

[martinl]

In 70385:

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

[martinl]

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

[martinl]

In 70422:

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

[martinl]

In 70424:

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

(merge r70422 from relbr72)