<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.gis.grass.devel">
    <title>gmane.comp.gis.grass.devel</title>
    <link>http://blog.gmane.org/gmane.comp.gis.grass.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47891"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47890"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47889"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47887"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47886"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47882"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47876"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47875"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47873"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47872"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47871"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47870"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47868"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47853"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47849"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47848"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47845"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47841"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47839"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gis.grass.devel/47838"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47891">
    <title>pyGRASS: Report #1</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47891</link>
    <description>&lt;pre&gt;Hi all!

as reported in the new web page [0] of the pyGRASS project, at the moment you
can interact with a raster map in this way (read-only): ::

    # import the raster function
    &amp;gt;&amp;gt;&amp;gt; import obj
    # instantiate a Raster
    &amp;gt;&amp;gt;&amp;gt; dtm = obj.Raster('dtm')
    # open the raster in read mode 'r'
    &amp;gt;&amp;gt;&amp;gt; dtm.open()
    # get access
    &amp;gt;&amp;gt;&amp;gt; for row in dtm[:5]: print(row[:3])
    [718.0910034179688, 717.8709716796875, 717.551025390625]
    [718.0910034179688, 717.8709716796875, 717.551025390625]
    [718.0910034179688, 717.8709716796875, 717.551025390625]
    [718.0910034179688, 717.8709716796875, 717.551025390625]
    [718.0910034179688, 717.8709716796875, 717.551025390625]
    &amp;gt;&amp;gt;&amp;gt; dtm[5][:3]
    [718.051025390625, 717.7310180664062, 717.4210205078125]
    &amp;gt;&amp;gt;&amp;gt; dtm.close()

Any hint or suggestion are welcome! The Raster class use only the grass ctypes
library.

This report and the following ones will be available to the wiki page [1].

[0] http://code.google.com/p/pygrass/
[1]
http://grass.osgeo.org/wiki/GRASS_&lt;/pre&gt;</description>
    <dc:creator>Pietro</dc:creator>
    <dc:date>2012-05-25T14:57:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47890">
    <title>"d.rast -h" adds a map layer in wxGUI</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47890</link>
    <description>&lt;pre&gt;Hi!

In grass_trunk (compiled today), the command "d.rast -h" executed in the
"Command console" tab, within GRASS GIS Layer Manager, adds a "-h" entry in
the "Map layers" tab/list.

Of course no map "-h" does exist. Moreover, it would be nice for the wx-
command-console to automatically translate "-h" to "-help".

Thanks, Nikos

ps- playing a bit around with the latest wxGUI (within from/using
grass_trunk). I wish many of the rich features in the (may I call it) wx-
command-console (?) had been available long ago within the "default" grass-
shell :-/
&lt;/pre&gt;</description>
    <dc:creator>Nikos Alexandris</dc:creator>
    <dc:date>2012-05-25T14:38:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47889">
    <title>[GRASS GIS] #1664: Texts in command dialogs are garbled</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47889</link>
    <description>&lt;pre&gt;#1664: Texts in command dialogs are garbled
----------------------------------+-----------------------------------------
 Reporter:  wenzeslaus            |       Owner:  grass-dev&amp;lt; at &amp;gt;…              
     Type:  defect                |      Status:  new                      
 Priority:  normal                |   Milestone:                           
Component:  Default               |     Version:  unspecified              
 Keywords:  encoding translation  |    Platform:  MSWindows 7              
      Cpu:  Unspecified           |  
----------------------------------+-----------------------------------------
 Generated command dialogs show garbled texts. It does not apply to buttons
 and other strings which comes directly from Python code. It applies to
 string which comes from module option description (but with some
 translation activated).

 Acutes and other diacritics signs are shown before letters. However this
 is detail and it can differ between languages/encodings.

 It is necessary &lt;/pre&gt;</description>
    <dc:creator>GRASS GIS</dc:creator>
    <dc:date>2012-05-25T09:09:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47887">
    <title>[GRASS GIS] #1663: Tabs in C source code</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47887</link>
    <description>&lt;pre&gt;#1663: Tabs in C source code
--------------------------------+-------------------------------------------
 Reporter:  wenzeslaus          |       Owner:  grass-dev&amp;lt; at &amp;gt;…              
     Type:  defect              |      Status:  new                      
 Priority:  normal              |   Milestone:                           
Component:  Default             |     Version:  unspecified              
 Keywords:  indent tabs spaces  |    Platform:  All                      
      Cpu:  All                 |  
--------------------------------+-------------------------------------------
 I assume that GRASS C source code should be indented with spaces, more
 precisely with spaces only. And more over, mixing tabs and spaces is a bad
 practice.

 But C source files contains both spaces and tabs.

 For example changeset r47676 "code layout fixes with indent" only adds
 another tabs which are mixed with spaces. Here is a part of file worker.c
 (http://trac.osgeo.org/grass/browser/grass/trunk/raster/r&lt;/pre&gt;</description>
    <dc:creator>GRASS GIS</dc:creator>
    <dc:date>2012-05-25T08:20:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47886">
    <title>[GRASS GIS] #1662: Caching bug in 3D raster librarywith large data</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47886</link>
    <description>&lt;pre&gt;#1662: Caching bug in 3D raster library with large data
-------------------------------------+--------------------------------------
 Reporter:  huhabla                  |       Owner:  grass-dev&amp;lt; at &amp;gt;…              
     Type:  defect                   |      Status:  new                      
 Priority:  critical                 |   Milestone:  7.0.0                    
Component:  Raster3D                 |     Version:  svn-trunk                
 Keywords:  3D raster, tiles, cache  |    Platform:  Linux                    
      Cpu:  x86-32                   |  
-------------------------------------+--------------------------------------
 There is a strange bug that appeared on an Intel Atom netbook while
 converting a list of raster maps into a 3D raster map. Operating system is
 a 32 Bit Ubuntu linux:

 {{{
 GRASS 7.0.svn (etopo_epsg4326): t.rast.to.rast3 input=temptest
 output=temptest
  100%
 Creating 3D raster map
 ERROR: Rast3d_cache_hash_remove_name: name not in hashtable
 ERROR: Un&lt;/pre&gt;</description>
    <dc:creator>GRASS GIS</dc:creator>
    <dc:date>2012-05-25T07:59:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47882">
    <title>Image Segmentation - Summer of Code</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47882</link>
    <description>&lt;pre&gt;Hi,

Thanks everyone for the nice greetings, I'm very impressed with how polite
and helpful the GRASS community is.

There is a wiki [1] and source code repository [2] for the Image
Segmentation - Google Summer of Code project.

The mentors for the project have already provided a lot of advice, if there
is anyone else with an interest in segmentation you are welcome to add to
the Specifications or other areas of the wiki.

For the "code" I have started an outline, but I think there are still too
many questions to call it pseudocode yet!.  Many of the questions are for
myself to research and answer.  Of course, I welcome input and suggestions
for all of it, but some of the bigger questions are:

1.  How to best deal with images that are larger then available memory.  (I
assume too much disk I/O would be slow, but simple tiling could lead to
poor segmentation at the tile borders.)

2.  How to find neighbors. (Is this already available somewhere in GRASS?)

3.  Would any functions would be useful as a general l&lt;/pre&gt;</description>
    <dc:creator>Eric Momsen</dc:creator>
    <dc:date>2012-05-24T17:29:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47876">
    <title>reducing screen clutter</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47876</link>
    <description>&lt;pre&gt;Periodically, there are complaints about 'screen clutter' with GRASS. I realized yesterday that a big cause of this is that each time a module is called, a new instance of its dialog opens. So if you use v.buffer but don't close the dialog, and then call v.buffer again GRASS opens a second v.buffer dialog...and a third and a fourth, etc. So there seems to be the need to have the wxPython parser module to just bring the window for a module to the front if it is already open instead of opening another instance. Sounds simple but is probably somewhat complicated of course. But it would help the clutter problem a great deal.

Michael


_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &amp;amp;
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics &amp;amp; Complexity 
Professor of Anthropology, School of Human Evolution &amp;amp; Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarto&lt;/pre&gt;</description>
    <dc:creator>Michael Barton</dc:creator>
    <dc:date>2012-05-24T10:19:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47875">
    <title>stop button in GUI?</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47875</link>
    <description>&lt;pre&gt;There is a "stop" button in the GUI of all modules. When I press it, the GUI dialog returns to a state where I can reinitiate the module process. But looking in my system monitor, the old process is still continuing. Is this the case for all systems or just the Mac? If for all systems, the "stop" button seems somewhat misleading.

Michael

_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &amp;amp;
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics &amp;amp; Complexity
Professor of Anthropology, School of Human Evolution &amp;amp; Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu&amp;lt;http://csdc.asu.edu/&amp;gt;





_______________________________________________
grass-dev mailing list
grass-dev&amp;lt; at &amp;gt;lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev&lt;/pre&gt;</description>
    <dc:creator>Michael Barton</dc:creator>
    <dc:date>2012-05-24T08:04:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47873">
    <title>[GRASS GIS] #1661: Wish: port the new wxgui histogram plotting tool from grass7 to grass6</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47873</link>
    <description>&lt;pre&gt;#1661: Wish: port the new wxgui histogram plotting tool from grass7 to grass6
-------------------------+--------------------------------------------------
 Reporter:  mlennert     |       Owner:  grass-dev&amp;lt; at &amp;gt;…              
     Type:  enhancement  |      Status:  new                      
 Priority:  normal       |   Milestone:  6.4.3                    
Component:  wxGUI        |     Version:  unspecified              
 Keywords:  histogram    |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------
 Michael's wxgui histogram tool in trunk is _very_ nice and useful. Any
 chance that this could be backported to the grass6 line ?

 Moritz

&lt;/pre&gt;</description>
    <dc:creator>GRASS GIS</dc:creator>
    <dc:date>2012-05-23T14:56:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47872">
    <title>v.distance values bogus in GRASS 6.4.2 also</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47872</link>
    <description>&lt;pre&gt;So the values for point to line distances are just as bad in GRASS 6.4.2 as they are in GRASS 7. Any suggestions on how to get this information for a latlon region?

Michael 
_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &amp;amp;
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics &amp;amp; Complexity 
Professor of Anthropology, School of Human Evolution &amp;amp; Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu





_______________________________________________
grass-dev mailing list
grass-dev&amp;lt; at &amp;gt;lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev&lt;/pre&gt;</description>
    <dc:creator>Michael Barton</dc:creator>
    <dc:date>2012-05-23T14:48:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47871">
    <title>another bug in v.distance</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47871</link>
    <description>&lt;pre&gt;Forgot to mention that the table selection pull-downs do not work in any version of the v.distance GUI--from 6.4.2 to 7.0

Michael
_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &amp;amp;
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics &amp;amp; Complexity 
Professor of Anthropology, School of Human Evolution &amp;amp; Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu





_______________________________________________
grass-dev mailing list
grass-dev&amp;lt; at &amp;gt;lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev&lt;/pre&gt;</description>
    <dc:creator>Michael Barton</dc:creator>
    <dc:date>2012-05-23T14:47:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47870">
    <title>broken stuff in vector modules</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47870</link>
    <description>&lt;pre&gt;Hi,

I don't use the vector modules a lot and so they don't get a lot of testing from me. I'm trying to do a project with someone that uses vector module and I find that some key things are broken. The following apply to GRASS 7 and GRASS 6.4.3.

1) v.distance gives bogus results for point to line distance uploads in a latlon region. For example, the distance uploaded from one site point to the nearest waterway is 5767967.05475, yet measuring this with the distance tool gives a much more reasonable 33211 m. The uploaded distance is off by an order of 173X -- an enormous error. Nothing in the docs says that you cannot use v.distance with latlon regions. 

2) To get around this, I thought I'd try to get the length of the line that connects each site point with its nearest waterway (a v.distance option). But when I tried to make a new table for this in the table manager, I find that I cannot access the "table description" section of the "manage layers" page in the attribute table manager. This is again because &lt;/pre&gt;</description>
    <dc:creator>Michael Barton</dc:creator>
    <dc:date>2012-05-23T14:43:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47868">
    <title>Summer of Code is upon us</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47868</link>
    <description>&lt;pre&gt;Hi,

as Anne noted in her Hello World message*, the Summer of Code has just
begun.  [*] http://lists.osgeo.org/pipermail/soc/2012-May/001734.html


In case you missed the selection efforts, GRASS was funded for 3 projects
this year.


They are:

(see the wiki for detailed links)
   http://grass.osgeo.org/wiki/GRASS_SoC_Ideas_2012#Accepted_Ideas


   1.  Python high level map interaction for GRASS GIS (abstract)

          Student: Pietro Zambelli 
          Mentor: Sören Gebbert 
          Backup mentors: Luca Delucchi, Martin Landa 
          Wiki page: GRASS SoC Ideas 2012/High level map interaction 

H:--- pythonize the grass py libs; the wiki page demonstrates the idea well


   2. GRASS GIS WxGui front end for vector analysis modules (abstract)

          Student: Stepan Turek 
          Mentor: Martin Landa 
          Backup mentor: Markus Metz 
          Wiki page: GRASS GSoC 2012 WxGUI front end for vector analysis modules 

H:--- interactive v.net gui app (d.path^2, dynamically redraw network paths&lt;/pre&gt;</description>
    <dc:creator>Hamish</dc:creator>
    <dc:date>2012-05-22T11:27:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47853">
    <title>on the subject of toolboxes ...</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47853</link>
    <description>&lt;pre&gt;Hi,


before any work begins on this in earnest at the code sprint, I'd just
like to reiterate my take on the toolbox idea. i.e., (and insofar as I
understand the proposal as it exists!) any move towards splitting up
GRASS's build system and distribution package(s) would be a really
really huge mistake.


I would like to offer an alternate proposal which solves the same "new
user confronted with an overwhelming 747 cockpit of controls" problem,
but which does not splinter the core software.

Namely, implement "views" in the wxGUI preferences section, with
tick boxes where you can hide or show groups of modules as desired.
A core set of common modules would always be ticked in a greyed-out box,
and an "enable all" button would be present. Beyond that you can pick
and choose.

As our use cases vary widely, simply breaking up into "Core, Beginner,
Advanced" is too simplistic, and rather a grouping based on keyword
clusters (e.g. "remote sensing", "terrain analysis", ...) would be
more useful..


anyway, this ne&lt;/pre&gt;</description>
    <dc:creator>Hamish</dc:creator>
    <dc:date>2012-05-20T01:51:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47849">
    <title>[GRASS GIS] #1660: RFE: add new batch= command line option to main grass7 startup script</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47849</link>
    <description>&lt;pre&gt;#1660: RFE: add new batch= command line option to main grass7 startup script
-----------------------------+----------------------------------------------
 Reporter:  hamish           |       Owner:  grass-dev&amp;lt; at &amp;gt;…              
     Type:  enhancement      |      Status:  new                      
 Priority:  normal           |   Milestone:  7.0.0                    
Component:  Startup          |     Version:  svn-trunk                
 Keywords:  GRASS_BATCH_JOB  |    Platform:  All                      
      Cpu:  All              |  
-----------------------------+----------------------------------------------
 Hi,

 to make running GRASS_BATCH_JOBs a bit easier to use (and to avoid the
 common :-) mistake of not `unset`ing it after), it would be nice if the
 main grass7 startup script could parse the command line argv[] options for
 batch=, check that the script exists and is executable, then use it
 instead of looking for a GRASS_BATCH_JOB enviro variable?

 perhaps with that done GRASS_B&lt;/pre&gt;</description>
    <dc:creator>GRASS GIS</dc:creator>
    <dc:date>2012-05-19T03:24:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47848">
    <title>PIxel-wise regression contribution</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47848</link>
    <description>&lt;pre&gt;Hi there

I would like to contribute a script that I have used in my research to
the broader field.  The script carries out linear regression, except
that rather than using two rasters for the x and y variables, it uses
any number of pairs of rasters, allowing the regression to be carried
out across a time series, resulting in a slope, intercept and R^2 values
for each pixel.

The crunch is that it is written in perl, as this is what I know best
and it serves me well.  I have done my best to conform to the stated
standards, and I have produced a fairly detailed manual page.  This will
give you a better idea of what the script does, with examples.  I attach
the script and html here.  I hope that you will consider making it
available to others.

Here at James Cook University, by the way, we are encouraging a switch
from problematic and costly proprietary software to GRASS GIS.  I am a
major fan of GRASS, particularly on a Linux platform, and I am pleased
that more and more students are listening.  You should s&lt;/pre&gt;</description>
    <dc:creator>Damien O'Grady</dc:creator>
    <dc:date>2012-05-18T23:45:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47845">
    <title>[GRASS GIS] #1659: v.net.salesman - add cat to nodeerror output</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47845</link>
    <description>&lt;pre&gt;#1659: v.net.salesman - add cat to node error output
-------------------------+--------------------------------------------------
 Reporter:  gfleming     |       Owner:  grass-dev&amp;lt; at &amp;gt;…              
     Type:  enhancement  |      Status:  new                      
 Priority:  normal       |   Milestone:  6.4.3                    
Component:  Default      |     Version:  unspecified              
 Keywords:               |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------
 When graph creation fails like this:

 ERROR: Destination node [56802] is unreachable from node [56811]

 It would be really useful to know the cats of the offending nodes, not
 just their internal DGlib node ids. This would help find the error in the
 network.

&lt;/pre&gt;</description>
    <dc:creator>GRASS GIS</dc:creator>
    <dc:date>2012-05-17T08:17:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47841">
    <title>NetCDF build support and r3.out.netcdf in GRASS 7</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47841</link>
    <description>&lt;pre&gt;Dear all,
JFYI i have added a new module called "r3.out.netcdf" to GRASS 7 that
allows the export of 3D raster maps as NetCDF files. A special feature
is that the vertical units time and space are supported, hence the
export of space time voxel cubes is now possible.

I have added NetCDF build support to the configure script, as
r3.out.netcdf needs the NetCDF library to run. The Makefile variables
NETCDFLIBS and NETCDFCFLAGS can now be used to link the NetCDF library
to GRASS 7 modules.

Best regards
Soeren
&lt;/pre&gt;</description>
    <dc:creator>Sören Gebbert</dc:creator>
    <dc:date>2012-05-16T22:09:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47839">
    <title>[GRASS GIS] #1658: g.rename, g.copy do not ask for --overwrite, they just do it</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47839</link>
    <description>&lt;pre&gt;#1658: g.rename, g.copy do not ask for --overwrite, they just do it
-----------------------------------------+----------------------------------
 Reporter:  hamish                       |       Owner:  grass-dev&amp;lt; at &amp;gt;…              
     Type:  defect                       |      Status:  new                      
 Priority:  major                        |   Milestone:  6.5.0                    
Component:  Default                      |     Version:  svn-develbranch6         
 Keywords:  g.rename, g.copy, overwrite  |    Platform:  Linux                    
      Cpu:  x86-64                       |  
-----------------------------------------+----------------------------------
 Hi,

 discovered in devbr6, but may happen in other branches too:

 {{{
 G65&amp;gt; r.mapcalc one=1
  100%
 G65&amp;gt; r.mapcalc two=2
  100%
 G65&amp;gt; g.rename one,two
 Rename raster &amp;lt;one&amp;gt; to &amp;lt;two&amp;gt;
 G65&amp;gt; r.info -r two
 min=1
 max=1
 G65&amp;gt; echo $GRASS_OVERWRITE

 G65&amp;gt; r.mapcalc three=3
  100%
 G65&amp;gt; g.copy three,two
 Copy raster&lt;/pre&gt;</description>
    <dc:creator>GRASS GIS</dc:creator>
    <dc:date>2012-05-16T20:43:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47838">
    <title>r.mapcalc in trunk with pthreads broken</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47838</link>
    <description>&lt;pre&gt;I am observing corrupted output from r.mapcalc in trunk if compiled
--with-pthread. The result is not identical to the one obtained
--without-pthread. The mapcalc expression included the functions
eval(), min(), and max(), in case that helps. Open a ticket?

Markus M
&lt;/pre&gt;</description>
    <dc:creator>Markus Metz</dc:creator>
    <dc:date>2012-05-16T16:01:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gis.grass.devel/47832">
    <title>Adding NetCDF to GRASS7 configure</title>
    <link>http://comments.gmane.org/gmane.comp.gis.grass.devel/47832</link>
    <description>&lt;pre&gt;Dear all,
i would like to add a new configure option to enable NetCDF support in
GRASS7. The new module r3.out.netcdf that exports 3d raster maps as
three dimensional (space or space + time) NetCDF files and several
other planed modules will need this library. My question is how to
integrate NetCDF in the configuration process? I have patched the
files "configure.in"  and "Platform.make.in". Do i need to modify any
additional files? How should i generate the configure script with
autoconf, so that it is compatible with the current configure script?

The "configure.in" and "Platform.make.in" patch is attached.

Many thanks in advance.
Best regards
Soeren
_______________________________________________
grass-dev mailing list
grass-dev&amp;lt; at &amp;gt;lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev&lt;/pre&gt;</description>
    <dc:creator>Sören Gebbert</dc:creator>
    <dc:date>2012-05-16T08:58:03</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.gis.grass.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.gis.grass.devel</link>
  </textinput>
</rdf:RDF>

