[GRASS-dev] get_proj() python function

[Markus Neteler]

On Mon, Jun 6, 2011 at 12:09 PM, Luca Delucchi <lucadeluge at gmail.com> wrote:
> 2011/6/5 Glynn Clements <glynn at gclements.plus.com>:
>>
>> Luca Delucchi wrote:
>>
>>> Hi all, today I needed a python function for g.proj interface. I
>>> developed it and I think it could integrate in the main core.
>>
>> For parsing, g.proj should be run with -j, e.g.:
>>
>
> You are right but with -p the output contain more values like datum
> and units... for this I used -p flag

There are some differences, though:

Gauss-Boaga Fuso 1 example:

GRASS 6.4.2svn (patGB1):~ > g.proj -p
-PROJ_INFO-------------------------------------------------
name       : Transverse Mercator
datum      : rome40
datumparams: towgs84=-104.1,-49.1,-9.9,0.971,-2.917,0.714,-11.68
proj       : tmerc
ellps      : international
a          : 6378388.0000000000
es         : 0.0067226700
f          : 297.0000000000
lat_0      : 0.0000000000
lon_0      : 9.0
k_0        : 0.9996000000
x_0        : 1500000.0000000000
-PROJ_UNITS------------------------------------------------
unit       : Meter
units      : Meters
meters     : 1


GRASS 6.4.2svn (patGB1):~ > g.proj -j
+proj=tmerc
+lat_0=0.0000000000
+lon_0=9.0
+k_0=0.9996000000
+x_0=1500000.0000000000
+a=6378388
+rf=297
+no_defs
+towgs84=-104.1,-49.1,-9.9,0.971,-2.917,0.714,-11.68
+to_meter=1

The question is if the -p output is "over"described or not.

Markus