Re: R: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

Marco: > But this would open a *pandora's box*, because on this way I should > specify also what files I exactly provide from other stuffs (such as > tiff, gdal, proj) those [ie tiffinfo, gdalinfo, gdalwarp, gdal_translate, and cs2cs] would all be very useful things to provide. Hamish

Re: [GRASS-dev] Current state of wxPython GUI

On Mar 27, 2008, at 1:29 PM, [EMAIL PROTECTED] wrote: Message: 4 Date: Thu, 27 Mar 2008 17:47:11 +0100 (CET) From: [EMAIL PROTECTED] Subject: Re: [GRASS-dev] Current state of wxPython GUI To: grass-dev@lists.osgeo.org Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain;charset=iso-8

[GRASS-dev] Re: [GRASS GIS] #106: wxgrass: zoom to computational region does not respect resolution set with g.region

On Mar 27, 2008, at 3:10 AM, [EMAIL PROTECTED] wrote: Date: Thu, 27 Mar 2008 10:03:45 - From: "GRASS GIS" <[EMAIL PROTECTED]> Subject: [GRASS-dev] Re: [GRASS GIS] #106: wxgrass: zoom to computational region does not respect resolution set with g.region To: undisclosed-recipients:; Me

[GRASS-dev] WinGRASS-6.3.0RC6

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 offic

[GRASS-dev] WinGRASS

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

R: R: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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

[GRASS-dev] WinGRASS-6.3.0RC6 & Python GUI

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!!!) S

[GRASS-dev] Re: [GRASS GIS] #104: saving display to tiff or ppm garbled when NVIZ is not top window

#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

R: R: [GRASS-dev] WinGRASS-6.3.0RC6 & Python GUI

>The path, maybe? Windows uses %PATH% to locate DLLs. All needed paths have been added to %PATH% for grass63.bat and to $PATH for grass63 (as I launch GRASS using grass63 -wxpython from MSYS console) Marco -Messaggio originale- Da: Glynn Clements [mailto:[EMAIL PROTECTED] Inviato: vener

R: R: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

>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 presen

Re: R: [GRASS-dev] WinGRASS-6.3.0RC6 & Python GUI

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 t

Re: R: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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 J

Re: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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, but I imagine it would have to be comp

[GRASS-dev] Re: [GRASS GIS] #104: saving display to tiff or ppm garbled when NVIZ is not top window

#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

R: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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 abo

Re: R: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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 pro

R: [GRASS-dev] WinGRASS-6.3.0RC6 & Python GUI

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: grass-dev@lists.o

R: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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*, t

Re: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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

R: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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

Re: [GRASS-dev] Re: [GRASS GIS] #104: saving display to tiff or ppm garbled when NVIZ is not top window

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

[GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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! ;-) Marco ___ grass-dev mailing list grass-dev@lists.osgeo.org http://

Re: [GRASS-dev] WinGRASS-6.3.0RC6 & Python GUI

[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 rela

Re: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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 w

Re: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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 ___

Re: [GRASS-dev] table only creation in v.in.ascii

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 non-a

[GRASS-dev] Re: [GRASS GIS] #104: saving display to tiff or ppm garbled when NVIZ is not top window

#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

Re: R: [GRASS-dev] WinGRASS-6.3.0RC6 & Python GUI

Hi Marco, 2008/3/27, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: [snip] > > [EMAIL PROTECTED] /usr/local/bin > > $ grass63 -wxpython > > Cleaning up temporary files. > > Starting GRASS ... > > WARNING: Attention! > > WARNING: Locking is not supported on Windows! > > GRASS GUI should be wxpython > >

Re: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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? > 2) More a question to Glynn: I see r.terraflow is still missing. I guess > this

Re: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

[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

Re: [GRASS-dev] Current state of wxPython GUI

[EMAIL PROTECTED] wrote: > 2. The GRASS init shell script now dumps this message twice to the console: > > "To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details." > > I guess it attempts to run something with su privileges? Nope. Apparently, Ubuntu p

Re: [GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

On 27/03/08 17:46, [EMAIL PROTECTED] wrote: http://www.webalice.it/marco.pasetti/temp/README.html Notes and suggestions about modifications, addings and removals in it will be highly appreciated. - How to submit bugs ? preferably here: http://trac.osgeo.org/grass/ but possibly on wingrass

Re: [GRASS-dev] Re: [GRASS GIS] #104: saving display to tiff or ppm garbled when NVIZ is not top window

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

Re: [GRASS-dev] Current state of wxPython GUI

>> IndexError: list index out of range > > should be also fixed in trunk now OK, that works now. > >> 2. The GRASS init shell script now dumps this message twice to the console: >> >> "To run a command as administrator (user "root"), use "sudo ". >> See "man sudo_root" for details." >> >> I

[GRASS-dev] WinGRASS-6.3.0RC6 Self Installer

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 c

[GRASS-dev] Re: [GRASS-user] modify feature's values interactively

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. T

Re: [GRASS-dev] Current state of wxPython GUI

Hi, 2008/3/27, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > 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 >

[GRASS-dev] Re: [GRASS GIS] #104: saving display to tiff or ppm garbled when NVIZ is not top window

#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

Re: [GRASS-dev] r.watershed and flow directions

On Mar 26, 2008, at 8:31 PM, Andrew Danner wrote: Luca, The Terrastream direction coding for single flow direction is as follows 1 = Water flows east 2 = SE 4 = S 8 = SW 16 = W 32 = NW 64 = N 128 = NE Or pictorially 32 64 128 16 x 1 8 4 2 In the MFD case, values do NOT represen

Re: [GRASS-dev] Current state of wxPython GUI

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" % self.listOfLocations[self.lbloca

Re: [GRASS-dev] Current state of wxPython GUI

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 seem

Re: [GRASS-dev] Current state of wxPython GUI

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: > > "Erro

Re: [GRASS-dev] backporting help for SVN

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 \ $(

Re: [GRASS-dev] Current state of wxPython GUI

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

[GRASS-dev] Re: [GRASS-user] modify feature's values interactively

On 27/03/08 14:12, Martin Landa wrote: Hi, 2008/3/27, Moritz Lennert <[EMAIL PROTECTED]>: [snip] Is there a way to activate a "debug" mode in wxgrass to log what happens behind the screen ? yes, export GRASS_WX_DEBUG=[0-5] log attached. export GRASS_DEBUG=[0-5] I didn't see anything

[GRASS-dev] [GRASS GIS] #109: wxgrass - d.vect and d.vect.chart: changing default checkbox options in GUI results in KeyError

#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 |

Re: [GRASS-dev] r.watershed and swap memory

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 d

[GRASS-dev] Re: [GRASS-user] modify feature's values interactively

Hi, 2008/3/27, Moritz Lennert <[EMAIL PROTECTED]>: [snip] > Is there a way to activate a "debug" mode in wxgrass to log what happens > behind the screen ? yes, export GRASS_WX_DEBUG=[0-5] you can combine with export GRASS_DEBUG=[0-5] Martin -- Martin Landa * http://gama.fsv.cvut.cz/~landa

[GRASS-dev] Re: [GRASS-user] modify feature's values interactively

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 in database through drive

[GRASS-dev] Re: [GRASS-user] modify feature's values interactively

[moving this to -dev] On 27/03/08 13:27, Hamish wrote: Martin: http://grass.gdf-hannover.de/wiki/Image:Wxgui-vector-querying-gnulinux.png Moritz: Cool ! 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 connect

[GRASS-dev] Current state of wxPython GUI

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

Re: [GRASS-dev] r.watershed and swap memory

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 16=

[GRASS-dev] Re: [GRASS GIS] #104: saving display to tiff or ppm garbled when NVIZ is not top window

#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

[GRASS-dev] Re: [GRASS GIS] #106: wxgrass: zoom to computational region does not respect resolution set with g.region

#106: wxgrass: zoom to computational region does not respect resolution set with g.region --+- Reporter: mlennert | Owner: martinl Type: enhancement | Status: assigned

R: [GRASS-dev] WinGRASS-6.3.0RC6 & Python GUI

Hi, I installed NumPy, but it solved only the first *item* in the error list; I have the same error screenshot (Execution Failed: 'g.region.exe -u -g -p -c') and then Traceback (most recent call last): File "C:/MSYS/local/grass-6.3.0RC6/etc/wxpython/wxgui.py", line 1358, in sys.exit(m

[GRASS-dev] Re: [GRASS GIS] #106: wxgrass: zoom to computational region does not respect resolution set with g.region

#106: wxgrass: zoom to computational region does not respect resolution set with g.region --+- Reporter: mlennert | Owner: martinl Type: enhancement | Status: assigned

[GRASS-dev] Re: [GRASS GIS] #106: wxgrass: zoom to computational region does not respect resolution set with g.region

#106: wxgrass: zoom to computational region does not respect resolution set with g.region --+- Reporter: mlennert | Owner: martinl Type: enhancement | Status: assigned

[GRASS-dev] Re: [GRASS GIS] #106: wxgrass: zoom to computational region does not respect resolution set with g.region

#106: wxgrass: zoom to computational region does not respect resolution set with g.region ---+ Reporter: mlennert | Owner: martinl Type: defect| Status: assigned Prio

[GRASS-dev] Re: [GRASS GIS] #108: wxgrass: trying to add legend gives UnicodeDecodeError

#108: wxgrass: trying to add legend gives UnicodeDecodeError ---+ Reporter: mlennert | Owner: grass-dev@lists.osgeo.org Type: defect| Status: new Priority: major | Mile

[GRASS-dev] Re: [GRASS GIS] #107: wxgrass: trying to set options for scalebar or legend gives TypeError

#107: wxgrass: trying to set options for scalebar or legend gives TypeError ---+ Reporter: mlennert | Owner: grass-dev@lists.osgeo.org Type: defect| Status: new Pr

[GRASS-dev] Re: [GRASS GIS] #106: wxgrass: zoom to computational region does not respect resolution set with g.region

#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

[GRASS-dev] [GRASS GIS] #108: wxgrass: trying to add legend gives UnicodeDecodeError

quot;, line 133, in Render stderr=None) File "/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 b

Re: [GRASS-dev] backporting help for SVN

William Kyngesburye wrote: > I backported some minor Mac-only bugfixes. They have worked well for > me so far. And I did manually apply them to my recent RC binaries, > and haven't heard of any problems. A couple were build fixes, so they > would only affect those that compiled SVN sourc

[GRASS-dev] [GRASS GIS] #107: wxgrass: trying to set options for scalebar or legend gives TypeError

pected keyword argument 'layer' 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] [GRASS GIS] #106: wxgrass: zoom to computational region does not respect resolution set with g.region

grass svn-head 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

R: [GRASS-dev] WinGRASS-6.3.0RC6 & Python GUI

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 retry

[GRASS-dev] WinGRASS-6.3.0RC6 & Python GUI

Hi all, 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

Re: [GRASS-dev] spam filter for web list?

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

Re: [GRASS-dev] New GRASS icons

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 a