[GRASS-dev] on the fly grass location

[Paolo Cavallini]

Hi all.
As it has been discussed earlier, having location generated (and 
destroyed) on the fly would help a lot the casual qgis grass user to 
approach grass. The idea is to run an analysis by loading (r.external, 
v.external, v.in.ogr) data, generating a location from it, run, save the 
results as tif or shp, and destroy the location at the end, all without 
users noticing it (but explaining for future reuse).
The good news is that here at the hackfest we got a voulnteer willing to 
help with the coding (preferably in Python). Welcome Peter Loewe!

Anybody willing to help him with the first steps?
All the best.
--
http://www.faunalia.it/pc
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] on the fly grass location

[Markus Neteler]

On Sun, Nov 14, 2010 at 9:54 AM, Paolo Cavallini  wrote:
> Hi all.
> As it has been discussed earlier, having location generated (and destroyed)
> on the fly would help a lot the casual qgis grass user to approach grass.
> The idea is to run an analysis by loading (r.external, v.external, v.in.ogr)
> data, generating a location from it, run, save the results as tif or shp,
> and destroy the location at the end, all without users noticing it (but
> explaining for future reuse).
> The good news is that here at the hackfest we got a voulnteer willing to
> help with the coding (preferably in Python). Welcome Peter Loewe!

Great, Peter!

> Anybody willing to help him with the first steps?

Sure - note that all ingredients are already there including the
"demolocation" which
comes with any GRASS binary package. Maybe that's easier discussed
over chat?

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #830: wxgui loading error for GRASS7 on Ubuntu 9.10

[GRASS GIS]

#830: wxgui loading error for GRASS7 on Ubuntu 9.10
+---
 Reporter:  isaacullah  |   Owner:  grass-...@…  
 Type:  defect  |  Status:  new  
 Priority:  major   |   Milestone:  7.0.0
Component:  Default | Version:  svn-trunk
 Keywords:  libgdal |Platform:  Linux
  Cpu:  x86-64  |  
+---
Changes (by aghisla):

  * keywords:  Ubuntu, fails to load, GUI => libgdal


Comment:

 I can reproduce the error on Fedora 13 64bit.

 1. configure - make - no make install

 2. run ./bin.i686-pc-linux-gnu/grass70

 No library error running the correct architecture executable.

 Maybe make install chooses the wrong architecture?

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] refreshing GRASS toolbox

[Paolo Cavallini]

Hi all.
We have been doing a number of improvements on the QGIS GRASS Toolbox, 
mainly polishing the interface and making it more compliant with general 
GUI rules of QGIS. Hope you'll like it. More work is to be done.
Robert Szczepanek kindly volunteered to prepare new icons, with a style 
uniform with the newgis icon set. You can see a sample done for db.* 
commands. It is a major task, so let's hope he'll be able to carry on 
speedy ;)
I would like to have a peer review of the new icons as they come out, to 
be sure they are easy to understand for everybody (at least as 
understandable than current ones, surely more beautiful).
So please follow the process, and send your comments. Probably the best 
thing would be if Robert can pload the new icons to 
http://grass.osgeo.org/wiki/GRASS-QGIS_relevant_module_list, where we 
can collect qualified comments before adding them to the toolbox.

Looking forward for your collaboration.
All the best.
--
http://www.faunalia.it/pc
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #1216: NVIZ fails to display any text

[GRASS GIS]

#1216: NVIZ fails to display any text
-+--
 Reporter:  marisn   |   Owner:  grass-...@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  6.4.1
Component:  Tcl/Tk NVIZ  | Version:  svn-develbranch6 
 Keywords:   |Platform:  Linux
  Cpu:  Unspecified  |  
-+--
 As reported on user ML, there are problems with recent Xorg releases and
 displaying any text (legend labels, north arrow text etc) in NVIZ. Those
 features will fail to render at all if there are problems with fonts.

 For some strange reason, line 3105 at src/togl.c is returning NULL on most
 (all?) sane font names that where working just fine some time a go.

 If somebody has an idea why XLoadQueryFont() fails on most of font names,
 it's the right time to reveal it :)

 Tested with current develbranch_6 and Xorg 1.9.1 RC2.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: on the fly grass location

[Roger Bivand]

Markus Neteler wrote:
> 
> On Sun, Nov 14, 2010 at 9:54 AM, Paolo Cavallini 
> wrote:
>> Hi all.
>> As it has been discussed earlier, having location generated (and
>> destroyed)
>> on the fly would help a lot the casual qgis grass user to approach grass.
>> The idea is to run an analysis by loading (r.external, v.external,
>> v.in.ogr)
>> data, generating a location from it, run, save the results as tif or shp,
>> and destroy the location at the end, all without users noticing it (but
>> explaining for future reuse).
>> The good news is that here at the hackfest we got a voulnteer willing to
>> help with the coding (preferably in Python). Welcome Peter Loewe!
> 
> Great, Peter!
> 
>> Anybody willing to help him with the first steps?
> 
> Sure - note that all ingredients are already there including the
> "demolocation" which
> comes with any GRASS binary package. 
> 

The GRASS R package was for GRASS5, and does not work with GRASS 6. A better
mechanism is provided in the spgrass package as initGRASS(). The code of the
R function sets the environment variables, etc., for a location generated on
the fly (with an .GRASSRC file) in the running R temporary directory. When R
exits, the location goes away.

Roger


Markus Neteler wrote:
> 
> Maybe that's easier discussed over chat?
> 
> Markus
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
> 
> 


-
Roger Bivand
Economic Geography Section
Department of Economics
Norwegian School of Economics and Business Administration
Helleveien 30
N-5045 Bergen, Norway

-- 
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/on-the-fly-grass-location-tp5737110p5737837.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] on the fly grass location

[Markus Neteler]

On Sun, Nov 14, 2010 at 10:24 AM, Markus Neteler  wrote:
> On Sun, Nov 14, 2010 at 9:54 AM, Paolo Cavallini  
> wrote:
>> Hi all.
>> As it has been discussed earlier, having location generated (and destroyed)
>> on the fly would help a lot the casual qgis grass user to approach grass.
>> The idea is to run an analysis by loading (r.external, v.external, v.in.ogr)
>> data, generating a location from it, run, save the results as tif or shp,
>> and destroy the location at the end, all without users noticing it (but
>> explaining for future reuse).
>> The good news is that here at the hackfest we got a voulnteer willing to
>> help with the coding (preferably in Python). Welcome Peter Loewe!
>
> Great, Peter!
>
>> Anybody willing to help him with the first steps?
>
> Sure - note that all ingredients are already there including the
> "demolocation" which comes with any GRASS binary package.
> Maybe that's easier discussed over chat?

Forgot to mention this Wiki page
http://grass.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev