I am out of the office from Fri 12/02/2011 until Wed 12/07/2011.
Geachte mevrouw, mijnheer,
Op het moment kan ik uw mail niet beantwoorden. Voor dringende zaken kunt u
zich wenden tot het secretariaat van het EMI:
marion.linneb...@rivm.nl, T 030-2742913
anne.marie.van.kl...@rivm.nl, T 030-274857
Unfortunately not all bugs are fixed. Tested with trunk r49481
Start v.clean from menu:
Traceback (most recent call last):
File "/home/maris/soft/grass_trunk/dist.x86_64-unknown-
linux-gnu/etc/gui/wxpython/wxgui.py", line 1144, in
OnVectorCleaning
win = VectorCleaningFrame(parent = self, cmd =
Thanks. If r.viewshed is fast enough, a Python script could be built that uses
r.viewshed to replicate many of the aspects of r.cva.
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Chan
Markus Neteler wrote:
> how about replacing r.los with r.viewshed?
needs fixing:
grass65/dist.i686-pc-linux-gnu/include/grass/iostream/replacementHeapBlock.h:146:
warning: 'str' may be used uninitialized in this function
(3 times).
Hamish
___
grass
Michael wrote:
> How does r.viewshed differ from r.los?
basically it is faster and it scales to large regions well.
I don't know the exact O()ness level of it, but r.los becomes very quickly
slower after the region size gets bigger than a smallish amount of rows x
columns, to the point where it b
How does r.viewshed differ from r.los?
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 48
Glynn Clements wrote:
> import grass.script as grass
> env = os.environ.copy()
> env['GRASS_MESSAGE_FORMAT'] = 'gui'
> p = grass.start_command(..., stderr = grass.PIPE, env = env)
> # read from p.stderr
> p.wait()
>
> If you need to capture both stdout and std
On Thu, Dec 1, 2011 at 1:25 AM, Markus Metz
wrote:
> Dylan Beaudette wrote:
>> Just noticed a nasty bug when using v.db.dropcolumn and v.db.join with a
>> sqlite back-end. This seems to happen whenever a table is modified using the
>> 'coltypes' as reported by the GRASS-DB API:
>>
>> Here are the
#1444: g.parser does not filter for duplicate output map statements
--+-
Reporter: neteler | Owner: grass-dev@…
Type: defect | Status: reopened
Priority: minor|
+1 from me, looking forward to using r.viewshed on some massive maps-
would be nice to have it in the standard install of GRASS.
Dylan
On Thu, Dec 1, 2011 at 12:52 PM, Hamish wrote:
> Markus Neteler wrote:
>> how about replacing r.los with r.viewshed?
>
> I'm supportive of that, starting with tr
#1358: WinGRASS 6.4.1: SQLite driver errors: `Unable to open database'
-+--
Reporter: rvanderweide | Owner: grass-dev@…
Type: defect | Status: new
Markus Neteler wrote:
> how about replacing r.los with r.viewshed?
I'm supportive of that, starting with trunk. (too
late for 6.4.2) r.los just doesn't scale.
still one final small detail with the color rules
I'd like to see:
https://trac.osgeo.org/grass/ticket/390
It requires knowing the ra
Ops, wrong post. I wanted to send it to the users maling list.
I'll post it there.
sorry,
giovanni
2011/12/1 G. Allegri
> I resume (first as a repeat to myself) what I've learned from the various
> email on the topic
>
> Vectors can be:
>
> LEVEL 1:
> - no topology -> very limited use
> LEVEL
2011/12/1 Markus Neteler :
> how about replacing r.los with r.viewshed?
+1
Martin
--
Martin Landa * http://geo.fsv.cvut.cz/~landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hi,
how about replacing r.los with r.viewshed?
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
I resume (first as a repeat to myself) what I've learned from the various
email on the topic
Vectors can be:
LEVEL 1:
- no topology -> very limited use
LEVEL 2:
- unclean topology -> limited use
- clean topology -> full support
I previously thought that LEVEL 2 was only possible for clean top
Thanks very much! ;)
giovanni
2011/12/1 Markus Neteler
> On Thu, Dec 1, 2011 at 7:57 AM, Glynn Clements
> wrote:
> ...
> > If you want to parse the output, set GRASS_MESSAGE_FORMAT=gui in the
> > environment when running the command and read from the command's
> > stderr; e.g.
> >
> >i
Hi,
2011/11/24 Martin Landa :
> Please feel free to comment the new layout. It took almost one day to
> reorganize classes to the new modules/packages. I am expecting some
> bugs (mainly wrongly imported modules), I hope that code will be
> stabilized within few days. Please note, that `make distc
Hi,
a couple of points--
* Radim said many times: v.in.ogr's cleaning and v.clean are not
the same thing. (with a number of !! added) He explained it and
understood it always better than I ever could, so check in the
mailing list archives for details.
* GRASS is a topological GIS. so when data i
#1444: g.parser does not filter for duplicate output map statements
--+-
Reporter: neteler | Owner: grass-dev@…
Type: defect | Status: reopened
Priority: minor|
Personally,
I dislike the "non-topological data is also valid data"
perspective. GIS and spatial analysis are inherently
topological. From my point of view, the only distinction
that applies is whether that data contains topological
errors in its structure, or not.
GRASS 6 has been designed as
I think Roger's question below merits reflection, so I forward it to the
developer's list.
Moritz
Original Message
Subject:Re: [GRASS-user] overlapping areas seem valid to v.build: why?
Date: Wed, 30 Nov 2011 10:09:15 -0800
From: Roger André
To: Markus Metz
C
Dylan Beaudette wrote:
> Just noticed a nasty bug when using v.db.dropcolumn and v.db.join with a
> sqlite back-end. This seems to happen whenever a table is modified using the
> 'coltypes' as reported by the GRASS-DB API:
>
> Here are the coltypes reported from a vector newly imported
>
>
On Thu, Dec 1, 2011 at 7:57 AM, Glynn Clements wrote:
...
> If you want to parse the output, set GRASS_MESSAGE_FORMAT=gui in the
> environment when running the command and read from the command's
> stderr; e.g.
>
> import grass.script as grass
> env = os.environ.copy()
> env['
Martin Landa wrote:
> > building grass 7 with `make -j 8` on a muti-cpu machine ends with a
> > build error in the wxpython docs dir. `cd gui/wxpython/` and running
> > `make` has no error, so I suspect it is just a Makefile dependency thing.
>
> http://lists.osgeo.org/pipermail/grass-dev/2011-N
25 matches
Mail list logo
