[GRASS-dev] Re: [GRASS GIS] #1165: wingrass: cs2cs fails from the msys command line

[GRASS GIS]

#1165: wingrass: cs2cs fails from the msys command line
--------------------------------+-------------------------------------------
 Reporter:  hamish              |       Owner:  grass-dev@…              
     Type:  defect              |      Status:  new                      
 Priority:  normal              |   Milestone:  6.4.1                    
Component:  Projections/Datums  |     Version:  svn-develbranch6         
 Keywords:  cs2cs, wingrass     |    Platform:  MSWindows XP             
      Cpu:  x86-64              |  
--------------------------------+-------------------------------------------

Comment(by hellik):

 Replying to [comment:6 hellik]:
 > this should be edited as:
 >
 > (1) open OSGeo4W Shell (which is a windows-command-line with all
 osgeo4w-utilities):
 >
 > {{{
 > C:\>echo %PROJ_LIB%
 > C:\OSGeo4W\share\proj
 > }}}
 >
 > {{{
 > C:\>cs2cs +proj=latlong +datum=WGS84 +to +proj=latlong +datum=WGS84
 +pm=madrid
 > > 0 0
 > 3d41'16.58"E    0dN 0.000
 > }}}
 >
 > all works fine, '''but'''
 >
 > (2) open osgeo4w-msys-shell
 >
 > {{{
 > syringia at NADA ~
 > >$ echo $PROJ_LIB
 > C:\OSGeo4W\share\proj
 > }}}
 >
 > {{{
 > syringia at NADA ~
 > > $ cs2cs +proj=latlong +datum=WGS84 +to +proj=latlong +datum=WGS84
 +pm=madrid
 > 0 0
 >
 > }}}
 >
 > nothing happens, no computations of the new coordinates, a blank line is
 waiting (I've waited about 10 minutes, but nothing happend)
 >
 > so maybe there are underlying problems of proj4/cs2cs in an (osgeo4w-
 inherited) msys-environment?
 >
 > Helmut

 AFAICT this issue above is inherited by WinGrass-installer

 (1) trying above example in a patched WinGrass65-installer in ''GRASS
 6.5.SVN with MSYS'', that means in the delivered msys-command-line,
 nothing happens with cs2cs

 (2) the patched WinGrass65 started in text-mode (in a windows-command-
 line), the cs2cs-example works like a charm.

 so maybe a strong argument to leave msys behind in WinGrass64/65 and
 deliver a shell-environment in a windows-commandline, as actuall
 WinGrass70 does?

 best regards
 Helmut

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1165#comment:7>
GRASS GIS <http://grass.osgeo.org>