Michael Barton wrote:
Unfortunately, the new wxPython digitizing tool and new integrated 3D
view does not yet work with Windows. There are good people working on
it--and they could always use more help.
Michael
Hi Michael,
Thanks for your quick reply. Since I assume that
Dominik wrote:
Since I assume that both GUIs use the v.digit programm,
No, they are completely different. The v.digit version available
in Tcl/Tk GIS.m is C + Tcl/Tk written by Radim Glynn.
The Vdigit that is used in the wxPython GUI is C++ + wxPython
written by Martin.
You might also try the
http://trac.osgeo.org/grass/ticket/654Is this bug fixed? If yes , in which
version?
I download the grass6.4 rc5 and I found the problem still exist.
___
grass-user mailing list
grass-user@lists.osgeo.org
maven wrote:
http://trac.osgeo.org/grass/ticket/654
Is this bug fixed? If yes , in which version? I
download the grass6.4 rc5 and I found the problem still exist.
the bug is in RC5.
it has been fixed in the source code (SVN) but a new release has not
been issued yet incorporating that change.
Hallo!
Is there an easy solution to insert values from v.net report into it's
table?
I did it external with sqlite creating a new table from a join and
connected my vectormap to that. But when I eg. add a node, I don't want
to redo the hole procedure.
Information given from v.net nreport
Hi all.
At GFOSS.it, we just decided to increase the donations we receive on
behalf of projects that adhered to the microdonation initiative
(currently GRASS and QGIS), by adding one euro from our budget to every
euro donated. I hope this will be appreciated.
So now your donations have now more
Hi,
another question..:
is it possible to break lines from the network on nodes?
I need that to describe and query connections between the nodes.
Thanks again!
Achim
___
grass-user mailing list
grass-user@lists.osgeo.org
Hi all!
I like QGIS' bugfixing initiative [*]. I wonder if a similar attempt to
specifically support (financially) bugfixing in GRASS (e.g. critical
bugs, Most Wanted Enhancements) is possible/wanted/desired etc.
By is possible I mean if funding coordinators are available to
organise something.
Hi,
can the following semi-interactive edge tracing on raster task be realized
using the current GRASS modules ?
* Data: A raster map (think: Landsat RGB, Corinne landcover or alike)
* Input: The user provides two points, both being located on/near a border
between two areas in the raster map
Hi Peter!
peter:
...
* Task: Some combination of GRASS modules derives a shortest path (a
subset of pixels, not a vector) between the two given points which is
plotted along the contrast changes of the raster data.
There is i.zc and I think r.gauss (an add-on provided by Jachym [1])
that
2009/7/3 Hamish hamis...@yahoo.com
maven wrote:
http://trac.osgeo.org/grass/ticket/654
Is this bug fixed? If yes , in which version? I
download the grass6.4 rc5 and I found the problem still exist.
the bug is in RC5.
it has been fixed in the source code (SVN) but a new release has not
Hi Peter,
peter.loewe wrote:
the straightforward approach to write out a raster to
either a JPG or a PNG via r.out.gdal WITHOUT additional
createopt-parameters results in errors (r.out.png works fine
,though).
Where are the missing parameters documented? Are there
examples anywhere
Michael Barton wrote:
Although I, too, was initially turned off by this, I've
become an increasingly strong supporter of this approach
over time. Sometimes I even think that we would be better
off to get away from all semblance of word processor and
graphic programs in the UI in order to
hamish-2 wrote:
steps used?
for me on Linux it works:
{
[x] New map
new vector map name= test_map1
Display commands = d.rast elevation.dem
}
whole command looks like:
v.digit -n map=test_map1 {bgcmd=d.rast elevation.dem}
Hi Hamish,
Just typed in the command, just as
Dominik wrote:
Just typed in the command, just as shown in your example, but still the
result remains the same: I can start to create vectors (point, line an
polygon) but the raster file (an imported ERDAS Imagine 9.2 file) which
shall serve as a source is not being loaded into the digitizing
hamish-2 wrote:
perhaps the computational region settings do not match the map?
try g.region rast=your_background_map before running v.digit.
Hi Hamish,
I tried it and it finally worked! You really helped me to get out of
trouble!
Thank you very much,
Dominik
--
View this message in
(grass-6.4.0svn on Ubuntu JJ 64-bit)
I am trying to r.proj the greek aster_gdem from the wgs84
(epsg:4326) to hgrs87 (epsg:2100) grass-location. I get the error below.
Anybody else facing problems?
Nikos
---
r.proj aster_gdem out=aster_gdem location=wgs84 mapset=PERMANENT
That is very generous of GFOSS.it, and it will make a big difference
for both of these projects.
Thanks,
John
On Jul 3, 2009, at 2:59 AM, Paolo Cavallini wrote:
Hi all.
At GFOSS.it, we just decided to increase the donations we receive on
behalf of projects that adhered to the microdonation
On Fri, Jul 3, 2009 at 12:41 PM, Nikos
Alexandrisnikos.alexand...@felis.uni-freiburg.de wrote:
Hi all!
I like QGIS' bugfixing initiative [*]. I wonder if a similar attempt to
specifically support (financially) bugfixing in GRASS (e.g. critical
bugs, Most Wanted Enhancements) is
On Wed, Jun 10, 2009 at 3:27 PM, selastefansy...@gmx.de wrote:
Hi,
has anyone ever performed atmospheric correction with i.atcorr on ASTER L1B
images? I am wondering because there are no templates for geometrical
conditions or sensor bands (like there are for Landsat, Modis, AVHRR etc.).
If
Nikos:
(grass-6.4.0svn on Ubuntu JJ 64-bit)
I am trying to r.proj the greek aster_gdem from the wgs84
(epsg:4326) to hgrs87 (epsg:2100) grass-location. I get the error below.
...
Allocating memory and reading input map...
ERROR: Error writing segment file
...maybe it's just too big. I
Nikos:
(grass-6.4.0svn on Ubuntu JJ 64-bit)
I am trying to r.proj the greek aster_gdem from the wgs84
(epsg:4326) to hgrs87 (epsg:2100) grass-location. I get the error below.
...
Allocating memory and reading input map...
ERROR: Error writing segment file
...maybe it's just too big.
Nikos wrote:
Allocating memory and reading input map...
ERROR: Error writing segment file
--%---
Allocating memory and reading input map...
100%
Projecting...
WARNING: map [ASTGTM_N41E025_dem] - unable to write row 0
ERROR: Failed writing raster map ASTGTM_N41E025_dem
row 0
Hamish:
How big is the region?
Nikos already wrote:
Input:
Cols: 39601 (39601)
Rows: 28801 (28801)
...
Output:
Cols: 32473 (32473)
Rows: 29734 (29735)
try the r.proj memory= option.
Hamish
___
grass-user mailing list
Nikos:
Allocating memory and reading input map...
ERROR: Error writing segment file
--%---
Allocating memory and reading input map...
100%
Projecting...
WARNING: map [ASTGTM_N41E025_dem] - unable to write row 0
ERROR: Failed writing raster map ASTGTM_N41E025_dem
row 0
25 matches
Mail list logo
