[GRASS-dev] [GRASS GIS] #555: v.in.gpsbabel on wingrass: g.proj error

#555: v.in.gpsbabel on wingrass: g.proj error
-----------------------------------+----------------------------------------
Reporter: hamish | Owner: grass-dev@lists.osgeo.org
     Type: defect | Status: new
Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Keywords: v.in.gpsbabel, g.proj | Platform: MSWindows XP
      Cpu: x86-32 |
-----------------------------------+----------------------------------------
Hi,

when running v.in.gpsbabel on wingrass (latest 6.4.0svn) a window pops up
that says that g.proj.exe has exited unexpectedly. but then the modules
mostly works fine. (but data is not automatically reprojected to the
current location; it stays in wgs84 lat/lon)

'g.proj -jf' works fine from the wxGUI command prompt thingie.

??
Hamish

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/555&gt;
GRASS GIS <http://grass.osgeo.org>

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------+------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Resolution: | Keywords: wingrass, v.in.gpsbabel, g.proj
  Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Changes (by neteler):

  * keywords: v.in.gpsbabel, g.proj => wingrass, v.in.gpsbabel, g.proj

Comment:

Does the problem persist with a recent installer from
http://josef.fsv.cvut.cz/wingrass/grass64/ ?

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/555#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------+------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Resolution: | Keywords: wingrass, v.in.gpsbabel, g.proj
  Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by hamish):

Yes, still happens with the6.4.0svn r40456 binary build.

I can confirm that it happens on this line of the script:
  OUT_PROJ="`g.proj -jf`"

running that from the MSys terminal prompt works as expected.

??,
Hamish

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/555#comment:2&gt;
GRASS GIS <http://grass.osgeo.org>

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------+------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Resolution: | Keywords: wingrass, v.in.gpsbabel, g.proj
  Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by neteler):

Could you try to remove -f from that line in the script? Just to see which
if the "dontprettify" is the problem?

Markus

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/555#comment:3&gt;
GRASS GIS <http://grass.osgeo.org>

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------+------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Resolution: | Keywords: wingrass, v.in.gpsbabel, g.proj
  Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by hamish):

Still breaks with -f removed. $? is "5".

even if I put "`g.proj -p`" in the script just before the {{{
OUT_PROJ=`g.proj -jf` }}} line that dies with exit code 5 too.

... so what does exit code 5 mean in WinXP?

"`g.proj --help`" in the script does work as expected and exits with
$?==0.

Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/555#comment:4&gt;
GRASS GIS <http://grass.osgeo.org>

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------+------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Resolution: | Keywords: wingrass, v.in.gpsbabel, g.proj
  Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by hamish):

Replying to [comment:4 hamish]:
> Still breaks with -f removed. $? is "5".

apparently exit code 5 is "ERROR_ACCESS_DENIED".
   http://msdn.microsoft.com/en-us/library/ms681382(VS.85).aspx

It could be for the PROJ_INFO file, but as the program works fine from the
command line I'm not sure what to make it.

Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/555#comment:5&gt;
GRASS GIS <http://grass.osgeo.org>

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------+------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Resolution: | Keywords: wingrass, v.in.gpsbabel, g.proj
  Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by hamish):

I would guess that these modules would also be affected-

{{{
m.proj
r.in.aster
r.in.wms
r.tileset
v.in.garmin
v.in.geonames
v.in.gns
v.in.gpsbabel
}}}

but e.g. m.proj works fine:

{{{
#spearfish
g.region -l | grep center
echo "103d45'W 44d26'15N" | m.proj -i
}}}

very weird. can anyone else reproduce this bug? my test case is importing
a GPX track file into a lat/long location.

??,
Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/555#comment:6&gt;
GRASS GIS <http://grass.osgeo.org>

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------+------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Resolution: | Keywords: wingrass, v.in.gpsbabel, g.proj
  Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by hamish):

see also #827

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

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------+------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Resolution: | Keywords: wingrass, v.in.gpsbabel, g.proj
  Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by hamish):

I am still completely baffled by this one.

why does g.proj consistently fail in one particular script with exit code
5, "ERROR_ACCESS_DENIED", and yet works fine from the MSys command line
and in other scripts?

Hamish

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/555#comment:8&gt;
GRASS GIS <http://grass.osgeo.org>

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------------------------+------------------------------
Reporter: hamish | Owner: grass-dev@…
     Type: defect | Status: new
Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Keywords: wingrass, v.in.gpsbabel, g.proj | Platform: MSWindows XP
      Cpu: x86-32 |
---------------------------------------------+------------------------------

Comment(by mmetz):

Replying to [comment:8 hamish]:
> I am still completely baffled by this one.
>
> why does g.proj consistently fail in one particular script with exit
code 5, "ERROR_ACCESS_DENIED", and yet works fine from the MSys command
line and in other scripts?
>

Just tested v.in.gpsbabel on a recent (r42640) wingrass installation,
works fine, coordinates are properly reprojected, seems to be fixed.

Markus M

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/555#comment:9&gt;
GRASS GIS <http://grass.osgeo.org>

#555: v.in.gpsbabel on wingrass: g.proj error
---------------------------+------------------------------------------------
  Reporter: hamish | Owner: grass-dev@…
      Type: defect | Status: closed
  Priority: minor | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Resolution: fixed | Keywords: wingrass, v.in.gpsbabel, g.proj
  Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Changes (by hamish):

  * status: new => closed
  * resolution: => fixed

Comment:

tested on XP using last night's 6.5svn nightly build, imports and
reprojects data fine. I'm not sure why though, there hasn't been a change
to the g.proj code in a year AFAICT. maybe it was the spawn() code or
missing manifest?

still need to retest with 6.4.0, but closing bug as it seems fixed.

Hamish

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/555#comment:10&gt;
GRASS GIS <http://grass.osgeo.org>