Hamish ha scritto:
Also there are QGIS's GRASS toolbox icons to draw inspiration from, use
as placeholders, or just plain reuse:
http://trac.osgeo.org/qgis/browser/trunk/qgis/src/plugins/grass/modules
(maybe easier to browse those by just loading up the toolbox in QGIS...)
I guess
Hi Hamish,
hamish_b wrote:
(...)
I guess eventually we can push compatible icons over to QGIS so the user
only has to remember one icon per task and so using the QGIS toolbox
becomes a familiar and natural experience ( vice versa).
(...)
Hamish
I try to make it as universal as
On Thu, Mar 27, 2008 at 2:53 AM, Hamish [EMAIL PROTECTED] wrote:
Hamish wrote:
is it possible to turn on a spam filter for the grass-web mailing
list? The recent archives seem to contain more noise than signal.
[greylisting enabled]
and yet still they come :-(
Markus,
actually... NO!
I read the *alert* in the *error* lines, but I thought that it was a part of
wxpython install, and that, in some way, I didn't found it because of
*internal* errors! all that because python-NumPy is not included in python GUI
requirements
so, I'll install it and
20080327
python-wxgtk 2.8.7.1
python 2.4.4
Moritz
--
Ticket URL: http://trac.osgeo.org/grass/ticket/106
GRASS GIS http://grass.osgeo.org
GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/___
grass-dev mailing list
grass-dev
'
My config: grass svn-head 20080327 python-wxgtk 2.8.7.1 python 2.4.4
--
Ticket URL: http://trac.osgeo.org/grass/ticket/107
GRASS GIS http://grass.osgeo.org
GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/___
grass-dev mailing
/home/mlennert/SRC/GRASS/grass_trunk/dist.i486-pc-linux-
gnu/etc/wxpython/gui_modules/gcmd.py, line 355, in __init__
message=%s '%s'%s%s%s %s%s %
UnicodeDecodeError
:
'ascii' codec can't decode byte 0xc3 in position 17: ordinal not in
range(128)
grass svn-head 20080327 python-wxgtk 2.8.7.1
#106: wxgrass: zoom to computational region does not respect resolution set with
g.region
---+
Reporter: mlennert | Owner: martinl
Type: defect| Status: assigned
#107: wxgrass: trying to set options for scalebar or legend gives TypeError
---+
Reporter: mlennert | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
#106: wxgrass: zoom to computational region does not respect resolution set with
g.region
---+
Reporter: mlennert | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
#106: wxgrass: zoom to computational region does not respect resolution set with
g.region
--+-
Reporter: mlennert | Owner: martinl
Type: enhancement | Status: assigned
I made some test using r.water.outlet with Spearfish location and
output coming from GRASS and from TerraSTREAM:
http://www.movedigital.com/go/doktoreas/114926/grass_terrastream.jpg
The drainage map created with TerraSTREAM has been reclassified using those
rules:
0=-1
128=1
1=2
2=3
4=4
8=5
Hi all,
FWIW, some observations on the wxPython GUI, running on a Ubuntu (7.10)
box with an SVN checkout from 10 minutes ago:
1. Starting from scratch, i.e. with no prior GRASS login and
no .grassrc6 file present, the wx GUI intro screen is dysfunctional.
It does not let you specify any mapsets
On 27/03/08 11:04, Martin Landa wrote:
Hi,
2008/3/27, Moritz Lennert [EMAIL PROTECTED]:
[snip]
However, I just can't get it to work:
I have
GRASS 6.3.svn (spearfish60):~ v.db.connect -p roads
Vector map [EMAIL PROTECTED] is connected by:
layer 1 table roads in database
Luca,
Are you using the same easting/northing in r.water.outlet for both the
results generated by r.watershed and terrastream? As the images show,
the flow lines are bit different in the two images and you might have to
shift the basin outlet coordinates a bit. Also, are you sure the mapping
of
#109: wxgrass - d.vect and d.vect.chart: changing default checkbox options in
GUI
results in KeyError
-+--
Reporter: mlennert | Owner: grass-dev@lists.osgeo.org
Type: defect |
On 27/03/08 13:28, [EMAIL PROTECTED] wrote:
Hi all,
FWIW, some observations on the wxPython GUI, running on a Ubuntu (7.10)
box with an SVN checkout from 10 minutes ago:
If it is of any help: I can confirm all of those.
Moritz
1. Starting from scratch, i.e. with no prior GRASS login and
On Mar 27, 2008, at 4:44 AM, Glynn Clements wrote:
Platform-specific targets should be implemented using make
conditionals, rather than an unconditional target which performs the
test within the commands. IOW:
ifneq ($(MACOSX_APP),)
FILES += \
$(ETC)/grass-xterm-mac \
Hi,
2008/3/27, [EMAIL PROTECTED] [EMAIL PROTECTED]:
1. Starting from scratch, i.e. with no prior GRASS login and
no .grassrc6 file present, the wx GUI intro screen is dysfunctional.
It does not let you specify any mapsets in a GRASS DB directory.
The error message is:
Error in
Hi,
2008/3/27, Martin Landa [EMAIL PROTECTED]:
4. When starting with an empty Layer Manager: after adding the first
layer (vector in my case), the Map Display does not draw anything when
clicking on the Display map icon. I need to click on Re-render map.
This seems
Browsing to a GRASS DB location and selecting a mapset now works.
However, if I just enter the directorz manually, I get:
Traceback (most recent call last):
File /usr/local/grass-6.3.svn/etc/wxpython/gis_set.py, line 676, in
OnStart
set=LOCATION_NAME=%s %
#104: saving display to tiff or ppm garbled when NVIZ is not top window
--+-
Reporter: dylan| Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: minor
Hi.
2008/3/27, Moritz Lennert [EMAIL PROTECTED]:
I didn't see anything different with GRASS_DEBUG, however when I try
well, my fault, DEBUG variable exists only as gisenv variable not
environment variable.
with g.gisenv set=DEBUG=3, wxgrass freezes when I try to display a
vector map. To
Hi all,
I'm preparing WinGRASS-6.3.0RC6 Self Installer. In addition to RC6 build
(naturally) I added some Windows registry keys (Name, Version and InstallPath),
modified the script that creates grass63.bat (changing set PATH=%PATH%;. to
set PATH=.;%PATH%) and rewrote README file.
I
GRASS GIS wrote:
#104: saving display to tiff or ppm garbled when NVIZ is not top window
--+-
Reporter: dylan| Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
[EMAIL PROTECTED] wrote:
Notes and suggestions about modifications, addings and removals in it
will be highly appreciated.
I would reduce the missing modules section to just:
i.class
i.ortho.photo
i.points
i.vpoints
r.li
r.terraflow
rather
#104: saving display to tiff or ppm garbled when NVIZ is not top window
--+-
Reporter: dylan| Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: minor
Moritz Lennert pisze:
On 11/01/08 09:51, Benjamin Ducke wrote:
Does anyone know what the restrictions on DBF field
names are? Length?
8 chars
Add 2:
DBF column names are limited to 10 characters (DBF API definition) [1]
Special characters?
You should probably avoid anything
On Thu, Mar 27, 2008 at 7:53 PM, Glynn Clements
[EMAIL PROTECTED] wrote:
2) More a question to Glynn: I see r.terraflow is still missing. I guess
this hasn't been backported to 6.3releasebranch ?
No, not yet.
Now yes:
http://trac.osgeo.org/grass/changeset/30767
Markus
On Thu, March 27, 2008 19:53, Glynn Clements wrote:
Moritz Lennert wrote:
1) ODBC and maybe MySQL might be good things to add. Especially the
first, as this would potentially give access to Win-specific databases.
Does the ODBC driver work with Windows ODBC?
Oh, I just assumed it would,
[EMAIL PROTECTED] wrote:
I reinstalled Python (2.5.2) + Python Extensions for Windows (Build
210 - py2.5) + WxPython (2.8.7.1 - unicode - py25) but I still have
the same errror (follows):
http://www.webalice.it/marco.pasetti/temp/grass_bugs/bug002.png
My first guess is that it's related
GRASS GIS wrote:
#104: saving display to tiff or ppm garbled when NVIZ is not top window
--+-
Reporter: dylan| Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Hi Moritz,
ODBC and maybe MySQL might be good things to add
They are actually in my wish list, along with jpeg support, FFMPEG, xerces
and some other things.
I just need a day of 48 hours ;-) ... But I think that waiting for some
months more until I'll take my degree will be enough!
Marco
On Thu, March 27, 2008 22:46, Marco Pasetti wrote:
Hi all,
Thanks for all the suggestions: I modified the document, and finally it
sounds good for me:
http://www.webalice.it/marco.pasetti/temp/README.html
So, let's start the poll! ;-)
Just one last remark: IIRC, for PostgreSQL you only
Hi Moritz,
Just one last remark: IIRC, for PostgreSQL you only provide the libpg.dll,
not the entire postgresql installation.
This should be mentioned. And what about sqlite ? Did you include the
sqlite.exe ?
For PostgreSQL I provide only libpq.dll, while for SQLite I provide *all the
build*,
Hi Glynn,
How could that be if all works well with tcl/tk GUI?
I tried, and g.region works perfectly if I open GRASS with tcl/tk GUI.
Marco
-Messaggio originale-
Da: Glynn Clements [mailto:[EMAIL PROTECTED]
Inviato: giovedì 27 marzo 2008 22.24
A: [EMAIL PROTECTED]
Cc:
On Thu, March 27, 2008 23:06, Marco Pasetti wrote:
Hi Moritz,
Just one last remark: IIRC, for PostgreSQL you only provide the
libpg.dll,
not the entire postgresql installation.
This should be mentioned. And what about sqlite ? Did you include the
sqlite.exe ?
For PostgreSQL I provide only
I could solve as adding the following note after *with GEOS, Expat,
PostgreSQL and SQLite support enabled:
The current WinGRASS package contains a complete build of all the items
listed above, except for PostgreSQL, for which it contains only the
libpq.dll dynamic library.
What do you think
#104: saving display to tiff or ppm garbled when NVIZ is not top window
--+-
Reporter: dylan| Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: minor
Marco Pasetti wrote:
ODBC and maybe MySQL might be good things to add
They are actually in my wish list, along with jpeg support, FFMPEG, xerces
and some other things.
JPEG support doesn't actually mean anything.
None of the Makefiles use the JPEG variables (JPEGLIB, JPEGLIBPATH and
Marco Pasetti wrote:
How could that be if all works well with tcl/tk GUI?
I tried, and g.region works perfectly if I open GRASS with tcl/tk GUI.
The path, maybe? Windows uses %PATH% to locate DLLs.
Of course, there are other reasons why the call might fail, e.g. it
could be a problem with
If using --with-tiff and --without-jpeg works, either your TIFF library
doesn't have JPEG support, or it can find the JPEG library without any
assistance. Either way, adding --with-jpeg won't make any difference.
Yes, currently TIFF library doesn't have JPEG support (as this libjpeg is
not
#104: saving display to tiff or ppm garbled when NVIZ is not top window
--+-
Reporter: dylan| Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: minor
I'm afraid folks.. I'm a gigantic idiot!!!
I supposed to work with the *package version* that has all the dlls in an
unique folder, while I was launching grass from the *original* msys
environment, where pgsql.dll is placed in the specific pgsql/lib folder!!!
(Glynn, as usual you were right!!!)
Hi Moritz,
personally, I think the information about the GDAL, proj, etc are minor
compared to the info about postgresql.
Maybe you could just add a ** with a note packages containing libraries and
binaries, all others only contain library files, or something similar.
Please, check if it works
I've downloaded the spearfish dataset now.
nick
***
WARNING: This e-mail (including any attachments) may contain legally
privileged, confidential or private information and may be protected by
copyright. You may only use it if
I downloaded and tried to install WinGRASS-6.3.0RC6 on Windows XP.
The main installation proceeds fine, but fails when it is time to install
the sample dataset.
I think this is because the installer is attempting to link to the internet
to fetch the sample dataset, but cannot get through my
47 matches
Mail list logo
