On Wed, Sep 7, 2016 at 12:28 AM, Paul Kelly
wrote:
...
> The proj4 parameter in g.proj takes a PROJ string description, not a file
> containing one.
> So,
> g.proj -c proj4="+proj=longlat +datum=WGS84"
>
> should work, as far as I can think.
BTW:
Are there reasons to not support proj4= also in th
Hi,
I have a vector line map (river network) which I want to clean and break
the lines at intersections. Therefore, I use the tool v.clean with the
option break. This of course increases the number of vector lines as
several lines got broken into two or more separate lines. Now there is a
attribut
>there is already a ticket for this in OSGEO4W-winGRASS; the interesting
thing is that this issue isn't in >standalone winGRASS of the same version.
https://trac.osgeo.org/grass/ticket/3057
-
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/grass73-
On Tue, 6 Sep 2016, Vaclav Petras wrote:
You can try the following commands in and outside of GRASS GIS session:
echo $GRASS_PYTHON
which python
python -c "import sys; print(sys.path)"
python -c "import numpy"
Vaclav,
External to grass:
$ echo $GRASS_PYTHON
$ which python
/usr/bin/python
On Wed, 7 Sep 2016, Helmut Kudrnovsky wrote:
there is already a ticket for this in OSGEO4W-winGRASS; the interesting
thing is that this issue isn't in >standalone winGRASS of the same version.
https://trac.osgeo.org/grass/ticket/3057
Helmut,
This references two Windows flavors. I run Slack
On Wed, Sep 7, 2016 at 9:22 AM, Rich Shepard
wrote:
>
> python -c "import numpy"
>>
> GRASS 7.2.svn
>
>>
>>
I suppose this means no output. No traceback means that it works. So numpy
works in the GRASS GIS session and it works outside.
>
> The environment variable GRASS_PYTHON is set with gra
On Wed, Sep 7, 2016 at 4:01 AM, Markus Neteler wrote:
> BTW:
> Are there reasons to not support proj4= also in the startup script
> "grass72"?
>
I don't think so. If somebody wants to look at it, this is the file to
change (long, but you can ignore most of it for this project):
https://trac.os
On Wed, 7 Sep 2016, Vaclav Petras wrote:
I suppose this means no output. No traceback means that it works. So numpy
works in the GRASS GIS session and it works outside.
Vaclav,
Correct.
OK, still no clues for me. Can you run the GUI (what you get when you start
or/and g.gui from command l
hi,
I compile GRASS 7.3. Postgresql connection not possible too.
Very annoying
Benoit
Le 05/09/16 09:35, Benoit ANDRE a écrit :
I confirm what I said saturday.
I just recompile and reinstall 7.0.0. This version has no problem with
postgresql and works fine.
Can that help you to find t
On Wed, Sep 7, 2016 at 11:52 AM, Rich Shepard
wrote:
>
> Cannot copy from the tab window to here. See attached .png.
>
The Python the Python tab in GUI *is* the Python running the GUI. If it is
able to import numpy there, it should be able to import it during startup.
Does the g.gui give you t
On Wed, 7 Sep 2016, Vaclav Petras wrote:
The Python the Python tab in GUI *is* the Python running the GUI.
And that's what the first line in the tab display box indicates.
If it is able to import numpy there, it should be able to import it during
startup.
That it is not importing durin
Rich Shepard wrote
> On Wed, 7 Sep 2016, Helmut Kudrnovsky wrote:
>
>> there is already a ticket for this in OSGEO4W-winGRASS; the interesting
>> thing is that this issue isn't in >standalone winGRASS of the same
>> version.
>>
>> https://trac.osgeo.org/grass/ticket/3057
>
> Helmut,
>
>This
On Wed, 7 Sep 2016, Helmut Kudrnovsky wrote:
Yes, reported on windows, but the same issue.
Helmut,
Can we who are affected expect a fix soon? I've a client who needs the
results of topographic and hydrologic modeling, and sooner is better than
later.
If I can assist I'll certainly do so.
On Wed, Sep 7, 2016 at 10:06 AM, Johannes Radinger
wrote:
> Hi,
>
> I have a vector line map (river network) which I want to clean and break the
> lines at intersections. Therefore, I use the tool v.clean with the option
> break. This of course increases the number of vector lines as several lines
Rich Shepard wrote
> On Wed, 7 Sep 2016, Helmut Kudrnovsky wrote:
>
>> Yes, reported on windows, but the same issue.
>
> Helmut,
>
>Can we who are affected expect a fix soon? I've a client who needs the
> results of topographic and hydrologic modeling, and sooner is better than
> later.
>
>
On Wed, 7 Sep 2016, Helmut Kudrnovsky wrote:
all C GRASS modules and most python GRASS modules are working here ; so
modelling should be possible.
Helmut,
Good. I'll proceed, then.
Thanks,
Rich
___
grass-user mailing list
grass-user@lists.osgeo.
On Tue, Sep 6, 2016 at 10:22 PM, Markus Metz
wrote:
> On Tue, Sep 6, 2016 at 8:12 PM, Helmut Kudrnovsky wrote:
>>> According to gdalinfo, the pixel sizes are
>>> Pixel Size = (0.0083330,-0.0083330)
>>> should be
>>> Pixel Size = (0.008,-0.008)
>>> i.e. fp p
This is perhaps important to highlight:
On Tue, Sep 6, 2016 at 7:39 PM, Anna Petrášová
wrote:
> > Does this mean I ignore the startup errors?
>
> the error means that 'import numpy' fails, so I am surprised it works
> for you otherwise. The import happens in gui_core/wxlibplot.py,
> wxplot/pro
The graphics context is not included by default in the SlackBuilds.org
configuration for wxPython. I am preparing to build version 3.0.2.0 and want
to know how to specify the --enable- command. Is it '--enable-gcdc' or
some other name?
TIA,
Rich
___
Hello, I don't know if this is the appropriate forum for this question, but
because I saw the blog post in the subject line I figured I would reach out
to see if this problem has been solved.
--
Let's not spend our time and resources thinking about things that are so
little or so large that all
On Wed, Sep 7, 2016 at 11:26 PM, Rich Shepard wrote:
> The graphics context is not included by default in the SlackBuilds.org
> configuration for wxPython. I am preparing to build version 3.0.2.0 and want
> to know how to specify the --enable- command. Is it '--enable-gcdc' or
> some other name?
On Wed, Sep 7, 2016 at 11:29 PM, stephen sefick wrote:
> Hello, I don't know if this is the appropriate forum for this question, but
> because I saw the blog post in the subject line I figured I would reach out
> to see if this problem has been solved.
What is exactly the problem?
Markus
___
Couldn't load plugin 'processing' from *
I can copy whole error message if needed.
On Wed, Sep 7, 2016 at 4:36 PM, Markus Neteler wrote:
> On Wed, Sep 7, 2016 at 11:29 PM, stephen sefick wrote:
> > Hello, I don't know if this is the appropriate forum for this question,
> but
> > because I saw
Thank you for your help in advance.
kindest regards,
Stephen
On Wed, Sep 7, 2016 at 4:42 PM, stephen sefick wrote:
> Couldn't load plugin 'processing' from *
>
>
> I can copy whole error message if needed.
>
> On Wed, Sep 7, 2016 at 4:36 PM, Markus Neteler wrote:
>
>> On Wed, Sep 7, 2016 at 11
On Wed, 7 Sep 2016, Markus Neteler wrote:
I got this problem back in May 2009 and the solution was to recompile
wxPythonGTK with '--enable-graphics_ctx'.
Markus,
Well, this is interesting. The current build of wxPython-2.8.12.1 does
have graphics_ctx enabled so I should not have seen this p
On Tue, 6 Sep 2016, Rich Shepard wrote:
When I start grass73 I see this in a virtual console:
Welcome to GRASS GIS 7.3.svn (r69357)
...
Launching GUI in the background, please wait...
GRASS 7.3.svn
(Oregon-Dayton):~/projects/oregon/washington-eichler/data/topography >
Numeric,numarray or N
26 matches
Mail list logo