Very verbose usage of proj (-V) fails on Windows

[kbevers]

When using the -V option with proj on Windows something goes wrong and "Unknown error" is returned. I have only been able to reproduce on Windows. The problem seems to have beeen introduced some time between version 4.9.2 and 4.9.3.

With version 4.9.2:

C:\dev\build\proj4\bin>proj
Rel. 4.9.2, 08 September 2015
usage: proj [ -beEfiIlormsStTvVwW [args] ] [ +opts[=arg] ] [ files ]

C:\dev\build\proj4\bin>echo 10 55 | proj.exe -V +proj=utm +zone=32
#Universal Transverse Mercator (UTM)
#       Cyl, Sph
#       zone= south
# +proj=utm +zone=32 +ellps=WGS84
#Final Earth figure: ellipsoid
#  Major axis (a): 6378137.000
#  1/flattening: 298.257224
#  squared eccentricity: 0.006694379990

Longitude: 10dE [ 10 ]
Latitude:  55dN [ 55 ]
Easting (x):   563967.42
Northing (y):  6095248.71
Meridian scale (h) : 0.99965020  ( -0.03498 % error )
Parallel scale (k) : 0.99965020  ( -0.03498 % error )
Areal scale (s):     0.99930052  ( -0.06995 % error )
Angular distortion (w): 0.000
Meridian/Parallel angle: 90.00000
Convergence : 0d49'9.047" [ 0.81917959 ]
Max-min (Tissot axis a-b) scale error: 0.99965 0.99965

With version 4.9.3:

C:\>proj
Rel. 4.9.3, 15 August 2016
usage: proj [ -bCeEfiIlormsStTvVwW [args] ] [ +opts[=arg] ] [ files ]

C:\>echo 10 55 | proj -V +proj=utm +zone=32
#Universal Transverse Mercator (UTM)
#       Cyl, Sph
#       zone= south
# +proj=utm +zone=32 +ellps=WGS84
#Final Earth figure: ellipsoid
#  Major axis (a): 6378137.000
#  1/flattening: 298.257224
#  squared eccentricity: 0.006694379990
Rel. 4.9.3, 15 August 2016
<proj.exe>: while processing file: <stdin>, line 1
Unknown error

[turyatemba]

how did you manage to install proj4 on windows

[kbevers]

As mentioned here the easiest way is to install it via OSGeo4W

[turyatemba]

Thank you

…

On Mon, Apr 10, 2017 at 1:20 PM, Kristian Evers ***@***.***> wrote: As mentioned here <http://proj4.org/download.html#windows> the easiest way is to install it via OSGeo4W — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#484 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANGCAmlaNGu93ta3E75VM2ngKvRshjrGks5rugJxgaJpZM4Lyxhv> .

-- Best regards, Ronald Turyatemba *rotemba81@gmail.com <rotemba81@gmail.com>* *tel. +256 778092615* *skype id: ronald turyatemba* * <https://ug.linkedin.com/in/turyatemba-ronald-24637a74> <https://www.facebook.com/turyatemba.ronald.7?ref=br_rs>*

[kbevers]

Slight update on this:

The problem appears only to exists when building with Visual Studio / nmake.

The problem is located near line 212 in proj.c. It seems as if pj_errno is never initialized to 0 and instead holds an abitratry non-zero value that trips up the if-statement in line 212.

CC @busstoptaktik