[GRASS-dev] grass-dev Digest, Vol 82, Issue 57

Mon Dec 31 05:44:26 PST 2012

Hi,

Actually my requirement is to run Python script outside GRASS Python shell.
For this i tried connecting to GRASS outside with Python following the
GRASS-wiki instructions, but failed. Then i tried to connect to GRASS with
OGR Python bindings, it too failed because gdal_grass plugin provided in
OSGEO4W does not install in GRASS (they are considered obsolete in
OSGEO4W). However i installed gdal1.6_grass with stable release of GRASS
6.4.3 (run with gdal latest version 1.9.x) in OSGEO4W. However, when
checked for the installed packages, gdal_grass support is not provided. It
is highly appreciated if it is included in the current OSGEO4W setup or any
suggestion.

Cheers, Brian

On Sun, Dec 30, 2012 at 1:30 AM, <grass-dev-request at lists.osgeo.org> wrote:

> Send grass-dev mailing list submissions to
>         grass-dev at lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.osgeo.org/mailman/listinfo/grass-dev
> or, via email, send a message with subject or body 'help' to
>         grass-dev-request at lists.osgeo.org
>
> You can reach the person managing the list at
>         grass-dev-owner at lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of grass-dev digest..."
>
> Today's Topics:
>
>    1. Re: GRASS Vector Support (J?rgen E. Fischer)
>    2. Re: Grass7 GUI compilation failed (Rashad M)
>
>
> ---------- Forwarded message ----------
> From: "Jürgen E." Fischer <jef at norbit.de>
> To: grass-dev at lists.osgeo.org
> Cc:
> Date: Sat, 29 Dec 2012 17:42:00 +0100
> Subject: Re: [GRASS-dev] GRASS Vector Support
> Hi Brian,
>
> On Sat, 29. Dec 2012 at 10:58:19 +0530, Brian Sanjeewa Rupasinghe wrote:
> > I need to automate some GRASS functions in my research work. If there is
> a
> > possibility to build gdal_grass plugin for Windows it is highly
> > appreciated. Even the Python scripts that call GRASS functions from
> > outside for MS_Windows do not connect with GRASS even though the
> > instructions provided in the GRASS wiki is followed. I have posted this
> > problem in grass-windows forum and finally advised me to bring the
> problem
> > down to grass-dev list.
>
> And you are positive that the GDAL plugin would help?  The above
> description
> sounds like a more general problem and I don't see any connection to the
> missing plugin at all.
>
> Does GRASS itself need the GDAL GRASS plugin at all?
>
>
> Jürgen
>
> --
> Jürgen E. Fischer         norBIT GmbH               Tel. +49-4931-918175-31
> Dipl.-Inf. (FH)           Rheinstraße 13            Fax. +49-4931-918175-50
> Software Engineer         D-26506 Norden
> http://www.norbit.de
> committ(ed|ing) to Quantum GIS                         IRC: jef on FreeNode
>
> --
> norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
> Rheinstrasse 13, 26506 Norden
> GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502
>
>
>
>
> ---------- Forwarded message ----------
> From: Rashad M <mohammedrashadkm at gmail.com>
> To: grass-dev at lists.osgeo.org
> Cc:
> Date: Sat, 29 Dec 2012 23:55:17 +0530
> Subject: Re: [GRASS-dev] Grass7 GUI compilation failed
> here is output from v.digit
> make
> ml
> make[6]: Entering directory `/code/grass/grass70/gui/wxpython/vdigit'
> GISRC=/code/grass/grass70/dist.x86_64-unknown-linux-gnu/demolocation/.grassrc70
> GISBASE=/code/grass/grass70/dist.x86_64-unknown-linux-gnu
> PATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:$PATH"
> PYTHONPATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/etc/python:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/etc/python:$PYTHONPATH"
> LD_LIBRARY_PATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/lib:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/lib:"
> LC_ALL=C
> /code/grass/grass70/dist.x86_64-unknown-linux-gnu/scripts/g.gui.vdigit
> --html-description < /dev/null | grep -v '</body>\|</html>' >
> g.gui.vdigit.tmp.html
> Traceback (most recent call last):
>   File
> "/code/grass/grass70/dist.x86_64-unknown-linux-gnu/scripts/g.gui.vdigit",
> line 39, in <module>
>     import wx
> ImportError: No module named wx
> make[6]: *** [g.gui.vdigit.tmp.html] Error 1
> rm g.gui.vdigit.tmp.html
> make[6]: Leaving directory `/code/grass/grass70/gui/wxpython/vdigit'
> make[5]: *** [guiscript] Error 2
>
>
> On Sat, Dec 29, 2012 at 9:57 PM, Rashad M <mohammedrashadkm at gmail.com>wrote:
>
>> grass7.0 fails compilation at first and continues only after setting
>> PYTHONPATH.
>>
>> This becomes a routine for recompilation. Is there any work around to
>> automatically pickup wxPython?
>>
>> Here is my error log:
>>
>> Started compilation: Sat Dec 29 21:46:17 IST 2012
>> --
>> Errors in:
>> /code/grass/grass70/gui/wxpython/animation
>> /code/grass/grass70/gui/wxpython/mapswipe
>> /code/grass/grass70/gui/wxpython/gmodeler
>> /code/grass/grass70/gui/wxpython/rlisetup
>> /code/grass/grass70/gui/wxpython/psmap
>> /code/grass/grass70/gui/wxpython/dbmgr
>> /code/grass/grass70/gui/wxpython/vdigit
>> --
>> In case of errors please change into the directory with error and run
>> 'make'.
>> If you get multiple errors, you need to deal with them in the order they
>> appear in the error log. If you get an error building a library, you will
>> also get errors from anything which uses the library.
>> --
>> Finished compilation: Sat Dec 29 21:53:10 IST 2012
>>
>>
>> wxpython is installed from ubuntu repos. so its in the default path
>>
>>
>> --
>> Regards,
>>    Rashad
>>
>
>
>
> --
> Regards,
>    Rashad
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20121231/a9907768/attachment.html>