On 20 March 2013 03:01, Yann Chemin wrote:
> yes r.patch is a good alternative, but it means writing to disk etc.
> Was more thinking of a display memory thingy.
Unfortunately, in wxGUI maps are rendered to files (by d.* modules)
and then read to wxGUI. (That's probably why it is slow.)
_
>> /home/vasek/dev/grass/trunk/lib/external/shapelib/dbfopen.c
>> /home/vasek/dev/grass/trunk/lib/external/shapelib/shpopen.c
>
> I can't see any K&R style declarations in these files. It's possible
> that the SHPAPI_CALL macro is confusing Doxygen.
>
It is easy to confuse Doxygen. Thanks for the f
Vaclav Petras wrote:
> we still have K&R style functions in C code? They work the same but I
> though that they were rewritten.
>
> Doxygen warns about this in these files:
>
> /home/vasek/dev/grass/trunk/lib/raster3d/volume.c
Fixed in r55463.
> /home/vasek/dev/grass/trunk/lib/external/shapel
Thank you Doug,
yes r.patch is a good alternative, but it means writing to disk etc.
Was more thinking of a display memory thingy.
Been thinking about the virtual rasters indeed, maybe will have a
look, any C code page you could direct me to?
Cheers,
Yann
On 20 March 2013 05:39, Newcomb, Doug
Hi,
2013/3/19 Sören Gebbert :
> It seems to be a good idea.
> However, i have to apply the 3D raster patch[1] then as soon as
> possible to get the voxel stuff working with large data. But this will
> bring the risk of losing backward compatibility .
Patch that removes the buggy LRE compress
Yann,
If I have a large number of layers, I usually do it from a command line or
with a script. I done r.patch with over 100 layers in one command ( before
I discovered gdalbuildvirt :-))
Doug
On Tue, Mar 19, 2013 at 4:36 AM, Vaclav Petras wrote:
> On 19 March 2013 09:31, Yann Chemin wrote:
>
On Tue, Mar 19, 2013 at 9:32 PM, Sören Gebbert
wrote:
> Please exclude the temporal GIS stuff in the tech-preview 7.0 release,
> since so many manual pages are still missing.
This reason is too weak :) I think that excluding it is way more work that
writing draft manual pages. I can assist with t
On Tue, Mar 19, 2013 at 9:31 PM, Vaclav Petras wrote:
> Hi,
>
> we still have K&R style functions in C code?
Officially no. We made the migration to ANSI C in 2002 or so
(would have to look it up).
> They work the same but I
> though that they were rewritten.
>
> Doxygen warns about this in the
2013/3/19 Markus Metz :
> I like the idea of a tech-preview release of GRASS7!
>
+1
> I think that no more (or at least not many) major changes will go into
> GRASS 7, apart from the wxGUI code base. Therefore it would IMHO be
> very beneficial to get more feedback on GRASS 7 in order to detect a
Hi,
recently programming manual for vector library was updated. The main
addition is FAQ page [1]. Questions were answered by MarkusM. Thank
you Markus. I hope that more questions will be added and answered in
the future.
The smaller changes includes removing of last Doxygen entries from
dglib an
Hi,
2013/3/19 Sören Gebbert :
> It seems to be a good idea.
> However, i have to apply the 3D raster patch[1] then as soon as
> possible to get the voxel stuff working with large data. But this will
> bring the risk of losing backward compatibility .
this will happen time by time... We have
It seems to be a good idea.
However, i have to apply the 3D raster patch[1] then as soon as
possible to get the voxel stuff working with large data. But this will
bring the risk of losing backward compatibility .
Please exclude the temporal GIS stuff in the tech-preview 7.0 release,
since so
Hi,
we still have K&R style functions in C code? They work the same but I
though that they were rewritten.
Doxygen warns about this in these files:
/home/vasek/dev/grass/trunk/lib/raster3d/volume.c
/home/vasek/dev/grass/trunk/lib/external/shapelib/dbfopen.c
/home/vasek/dev/grass/trunk/lib/extern
The 2 biggest issues I've run into teaching with GRASS 7 has been 1) the
difficulty of getting a Linux version and 2) the common 'missing dll' problem
for Windows.
Michael
__
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropolog
On Tue, Mar 19, 2013 at 7:55 PM, Markus Metz
wrote:
> I like the idea of a tech-preview release of GRASS7!
Me, too.
> I think that no more (or at least not many) major changes will go into
> GRASS 7, apart from the wxGUI code base.
We should also remember that this will go towards 7.0 and then
On Tue, Mar 19, 2013 at 6:24 PM, Patrice Dumas wrote:
> On Tue, Mar 19, 2013 at 02:39:33PM +0100, Anna Kratochvílová wrote:
>> Hi all,
>>
>> I would like to change minimal required version of wxPython [1].
>> Currently we support (theoretically) version 2.8.1.1 (released 2007).
>> I suggest to cha
I like the idea of a tech-preview release of GRASS7!
I think that no more (or at least not many) major changes will go into
GRASS 7, apart from the wxGUI code base. Therefore it would IMHO be
very beneficial to get more feedback on GRASS 7 in order to detect and
fix remaining bugs.
I also like yo
I think that this is a good idea for GRASS 7. We shouldn't really do it with
GRASS 6.
I like going to at least Python 2.5 also.
Michael
__
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social
On Tue, Mar 19, 2013 at 02:39:33PM +0100, Anna Kratochvílová wrote:
> Hi all,
>
> I would like to change minimal required version of wxPython [1].
> Currently we support (theoretically) version 2.8.1.1 (released 2007).
> I suggest to change it to 2.8.10.1 (2009), for example 2.8.10.1 was
> shipped
I think this is a good idea.
At the moment, GRASS 7 seems stable and everything or almost everything is
working for Mac. There are a few issues, but not major ones. One thing I
remember is a problem with the display of north arrows. Volume display is still
unstable, but that is a problem with
Hi Anna,
2013/3/19 Anna Kratochvílová :
> I would like to change minimal required version of wxPython [1].
> Currently we support (theoretically) version 2.8.1.1 (released 2007).
> I suggest to change it to 2.8.10.1 (2009), for example 2.8.10.1 was
> shipped with Ubuntu 10.04 LTS. The reason is ob
Ciao Anna,
On Tue, Mar 19, 2013 at 2:39 PM, Anna Kratochvílová
wrote:
> Hi all,
>
> I would like to change minimal required version of wxPython [1].
> Currently we support (theoretically) version 2.8.1.1 (released 2007).
> I suggest to change it to 2.8.10.1 (2009), for example 2.8.10.1 was
> ship
#1759: Selecting maps in dropdown menu: slider to move up/down maps does not
work
-+--
Reporter: pvanbosgeo | Owner: grass-dev@…
Type: defect | Status: reopened
Pri
Hi all,
I would like to change minimal required version of wxPython [1].
Currently we support (theoretically) version 2.8.1.1 (released 2007).
I suggest to change it to 2.8.10.1 (2009), for example 2.8.10.1 was
shipped with Ubuntu 10.04 LTS. The reason is obvious: wxGUI is limited
by this requirem
On 18/03/13 23:04, Markus Neteler wrote:
On Fri, Jan 11, 2013 at 9:53 AM, Rainer M Krug wrote:
...
Following the discussion, I would like to install GRASS 7 weekly snapshot. I relized the
"Binary"
link (http://grass.osgeo.org/download/software/) but it points back to the
Linux Download page,
On 19 March 2013 09:31, Yann Chemin wrote:
> OK found Ctrl+Shift+L in wxGUI
>
Yes, it is my favorite feature. I use it even to find and add one map.
However, there is some issue with many layers in layer manager. If you
load more than 20 (?) layers (maps) only some of them will be
rendered. There
OK found Ctrl+Shift+L in wxGUI
Thanks !
Yann
On 19 March 2013 13:56, Yann Chemin wrote:
> I am dealing with hourly Microwave data that are not covering the
> whole World in each layer.
>
> To have a decent presentation map of the data, I'd like to get a set
> (say 30-50 layers) displayed in one
I am dealing with hourly Microwave data that are not covering the
whole World in each layer.
To have a decent presentation map of the data, I'd like to get a set
(say 30-50 layers) displayed in one go.
OK I could do it with the png driver in a script (which is what it may
eventually become), but
28 matches
Mail list logo
