Hi,
IMHO it's good to document system's capabilities. Raster intro page
could have short subsection Technical details where current raster
limitations are noted. Probably without long explanations (link to
wikipedia/progman would be OK). Still I think they should be in user
docs - those, who
On Wed, 27 Feb 2008 [EMAIL PROTECTED] wrote:
Hi,
why do I need to add /usr/local/bin and /usr/local/lib to PATH variable before
to build GRASS (as suggested by Paul Kelly's notes)?
During GRASS compilation, after each module is compiled it is run with the
--html-description command-line
#70: i.target from GUI: strip @mapset part
--+-
Reporter: hamish | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: minor| Milestone: 6.4.0
Hi Paul,
thanks for the explanation! ;-)
I build a brand new MSYS environment for the compilation of GRASS, updating
libraries with latest releases and adding libtiff support (I succesfully built
also libjpeg, but some tests gave me errors, thus I decided to not include its
support)
in GRASS
Maciej Sieczka wrote:
Below follow details about CELL and DCELL datatypes in GRASS. It would
be good to have them summarrised in GRASS raster intro IMHO; + FCELL
specific notes. I'm not competent - anybody please do.
None of this belongs in the GRASS documentation, as it isn't
I have linux ubuntu 7.1. I have to installations of Grass: a 6.3.0 csv
version and a binary version 6.2.3 from the ubuntu repositories (which all
the dependecies: gdal, geos, proj4).
The database drivers (dbf, sqlite, etc) are all working, so it doesn't seem
directly linked to that..
--
View
Hi
Sorry for crossposting, but I think this can be of interest for GRASS and R
users.
I am planning to write a package to make the use of GRASS from R easier. The
idea is to wrap the system call to execute the GRASS command into an R
command of the same name.
e.g:
r.to.vect - function(...,
Marco,
FWIW, I also had a go at GRASS and wxPython on Win32 a while ago.
Compilation under MinGW is indeed a major effort.
I have not looked into this any further, but here are some links
with potentially helpful details:
http://www.mingw.org/cms/node/17
I very much agree with Glynn on this one, I have already written to
Maciek
something along this line.
If you are going to explain in GRASS man pages how computers handle
numbers should we then also explain (e.g. as part of r.slope.aspect),
how elevation is measured, what is the accuracy for
On Feb 27, 2008, at 1:47 AM, [EMAIL PROTECTED] wrote:
Date: Wed, 27 Feb 2008 02:08:14 -
From: GRASS GIS [EMAIL PROTECTED]
Subject: [GRASS-dev] [GRASS GIS] #70: i.target from GUI: strip @mapset
part
To: undisclosed-recipients:;
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain;
Hi Michael,
There is a separate dev Windows package that you need to instal for wx-config
oh... I thought it must exist! ;-) but I still didn't find it... I'll look
better...
That said, you don't need to install this unless you want to try to
compile the new in-development digitizer. Most
Sorry,
I'm really confused:
1) do I need to enable both Python and wxPython to let the new GRASS GUI work?
or do I need only to enable wx-widgets?
2) about the second case: basing on the fact that I need Python installed to
let wxPython work, how could I set them if I use a prebuilt
Ciao Marco,
2008/2/27, [EMAIL PROTECTED] [EMAIL PROTECTED]:
Michael:
There is a separate dev Windows package that you need to instal for
wx-config
Marco:
oh... I thought it must exist! ;-) but I still didn't find it... I'll look
better...
Michael:
That said, you don't need to install this
On Feb 27, 2008, at 9:09 AM, Martin Landa wrote:
straightforward on Linux machines (requires wxPseudoDC from wxPython),
seems to be not possible on Mac (AFAIU). I will try to find better
solution ASAP.
Martin,
I DID find the wxWidgets code for Mac. It IS installed, just in a
different
On Feb 27, 2008, at 9:09 AM, [EMAIL PROTECTED] wrote:
Date: Wed, 27 Feb 2008 17:06:29 +0100
From: [EMAIL PROTECTED]
Subject: [GRASS-dev] New wxPython GUI
To: grass-dev@lists.osgeo.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1
Sorry,
I'm really confused:
Sorry guys,
I really did a huge mess!!!
Now it's all clear! excuse me!
So, I repeat just to be clear at all (to me :-))
1) install prebuilt binaries of Python 2.5.2 (latest) in C:\DevTools\Python
2) install prebuilt binaries of wxPython 2.8.7.1 (latest) in
On Feb 27, 2008, at 9:35 AM, [EMAIL PROTECTED] wrote:
Sorry guys,
I really did a huge mess!!!
Now it's all clear! excuse me!
So, I repeat just to be clear at all (to me :-))
1) install prebuilt binaries of Python 2.5.2 (latest) in C:\DevTools
\Python
2) install prebuilt binaries of
I'm using today's Grass 6.3.svn source, gdal 1.5.0.
$ gdalinfo --formats | grep GRASS
GRASS (ro): GRASS Database Rasters (5.7+)
In Spearfish60:
$ r.info -t elevation.10m
datatype=DCELL
$ g.region rast=elevation.10m -p
projection: 1 (UTM)
zone: 13
datum: nad27
ellipsoid: clark66
Rainer M Krug wrote:
Sorry for crossposting, but I think this can be of interest for GRASS and R
users.
I am planning to write a package to make the use of GRASS from R easier. The
idea is to wrap the system call to execute the GRASS command into an R
command of the same name.
e.g:
Helena Mitasova wrote:
P.S. And regarding the requirement that more 16 digits are supported
that got all of this started - where do you need it?
I don't think the issue was that a lot of precision was actually
required, just that the way that the limitation manifests itself
appears strange if
Michael Barton wrote:
From the thread about this that I started a couple weeks ago, there
seem to be some difference of opinion on how to fix the issues about
reading @mapset. This can be dealt with in the GUI for the specific
cases where it's a problem. However, Glynn's point (I hope
Michael Barton wrote:
mhhh... confused! if I don't have wx-config I cannot enable the new
wxPython GUI! (configure fails)
Leave out the --with-wxwigets. This is only used for compiling vdigit.
Or maybe put in --without-wxwidgets.
Or you can leave it in and just ignore the error
On 27/02/2008, Glynn Clements [EMAIL PROTECTED] wrote:
Rainer M Krug wrote:
Sorry for crossposting, but I think this can be of interest for GRASS
and R
users.
I am planning to write a package to make the use of GRASS from R easier.
The
idea is to wrap the system call to execute the
Michael Barton wrote:
The GUI uses the global $GISBASE/etc/element.list to ID parsable
element types. gr is not in the list (unless you've added it since
last night). So it isn't parsed by the GUI.
I was just being lazy and not typing out the full any,group,group in
my post.
However,
Hi,
2008/2/21, Glynn Clements [EMAIL PROTECTED]:
Moritz Lennert wrote:
as wxgui is a shell script, g.gui wxpython (which does:
else if (strcmp(type-answer, wxpython) == 0) {
sprintf (progname, %s/etc/wxpython/scripts/wxgui, G_gisbase());
if (rc_file-answer) {
If GRASS is installed you can try a small batch script:
echo g.proj -w PROJ_INFO.WKT /tmp/get_grass_proj_info.sh
MAPSET=~/grassdata/spearfish60/user1/
GRASS_BATCH_JOB=/tmp/get_grass_proj_info.sh
export GRASS_BATCH_JOB
grass63 $MAPSET
unset GRASS_BATCH_JOB
cat PROJ_INFO.WKT
As mentioned
If GRASS is installed you can try a small batch script:
echo g.proj -w PROJ_INFO.WKT /tmp/get_grass_proj_info.sh
MAPSET=~/grassdata/spearfish60/user1/
GRASS_BATCH_JOB=/tmp/get_grass_proj_info.sh
export GRASS_BATCH_JOB
grass63 $MAPSET
unset GRASS_BATCH_JOB
cat PROJ_INFO.WKT
According to information on Graphic design lead vacat at
(http://grass.gdf-hannover.de/wiki/Project_jobs#Graphic_design_lead_.28open.29)
I'm looking for contact with person (responsible) who will help me starting
with this task.
I plan to start reworking icons for Grass.
Robert
--
View this
Hi,
2008/2/27, Robert Szczepanek [EMAIL PROTECTED]:
According to information on Graphic design lead vacat at
(http://grass.gdf-hannover.de/wiki/Project_jobs#Graphic_design_lead_.28open.29)
I'm looking for contact with person (responsible) who will help me starting
with this task.
On Feb 27, 2008, at 4:35 PM, [EMAIL PROTECTED] wrote:
Date: Wed, 27 Feb 2008 14:51:59 -0800 (PST)
From: Robert Szczepanek [EMAIL PROTECTED]
Subject: Re[GRASS-dev] ady to help with GRASS graphics
To: grass-dev@lists.osgeo.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain;
I can confirm this also with the new data set and ArcGIS. It looks like
r.out.gdal does not see the correct region and when the region is set
to the raster it adds one no-data row (or column - I don't remember now)
which is some huge negative number and that may be screwing up
the colors. I think
#72: gis.m: boundary rendering is off by one pixel
--+-
Reporter: hamish| Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: minor
On Wed, 27 Feb 2008, Rainer M Krug wrote:
Hi
Sorry for crossposting, but I think this can be of interest for GRASS and R
users.
Yes, please avoid cross-posting - the discussion ends up on many different
lists and threading can break down if the threading implementation in mail
clients and
On 28/02/2008, Roger Bivand [EMAIL PROTECTED] wrote:
On Wed, 27 Feb 2008, Rainer M Krug wrote:
Hi
Sorry for crossposting, but I think this can be of interest for GRASS
and R
users.
Yes, please avoid cross-posting - the discussion ends up on many different
lists and threading can
34 matches
Mail list logo
