[GRASS-user] Extract coordinates of vertices/nodes

Greetings, Being quite in Grass, I am trying to find a way to extract geographic coordinates of vertices and nodes (by the way I am struggling a little to understand the differences between those two concepts) for polygons or lines. Do you have any idea how to proceed? Cheers So.L. -- View

[GRASS-user] Re: Extract coordinates of vertices/nodes

Hi Sophie, v.out.ascii format=standard might help. Here is the manual: http://grass.itc.it/grass64/manuals/html64_user/v.out.ascii.html Afterwards you can write a simple script to extract the coordinates from the ascii-output. schorschli -- View this message in context:

Re: [GRASS-user] Extract coordinates of vertices/nodes

On 04/28/2010 12:12 PM, Sophie Leguedois wrote: Greetings, Being quite in Grass, I am trying to find a way to extract geographic coordinates of vertices and nodes (by the way I am struggling a little to understand the differences between those two concepts) for polygons or This might

[GRASS-user] v.vol.idw

Hi, I was wondering what happened to the above command in the new releases of GRASS. I am quite sure I did use it in GRASS 5 and possibly early versions of 6 but it seems it got lost somewhere along the road. Is there any reason for this? Does anyone remember in what version of GRASS for

[GRASS-user] osm import

Hamish, In a recent post [1], you said that to import OSM maps, one can use v.in.ogr, but I don't see a driver for OSM maps in ogr. Could you explain ? Thanks ! Moritz [1]http://lists.osgeo.org/pipermail/grass-user/2010-January/054253.html ___

[GRASS-user] Problem after import using r.in.ascii

Greetings Herbivores, This is the first time that I've created a location and mapset fo my own and I'm trying to import TRMM precipitation data into GRASS using r.in.ascii. I have an existing CSV file that has the headers lat, long and precip. The precipitation is a floating point number to two

Re: [GRASS-user] TopoFlow and GRASS (or any continuous distributed hydrologic model)

I would like to be able to model groundwater and surface water flow for some particular watersheds with usgs gauging stations. The gauging stations are to help parameterize/validate the modeled discharge. I would then like to be able to try and predict probability of intermittance, or, in other

Re: [GRASS-user] TopoFlow and GRASS (or any continuous distributed hydrologic model)

r.gwflow can help with the groundwater flow. The r.watershed module can help with where streams in basins originate and go to the outlet. The add-on of r.stream.extract can use weighting parameters to adjust where the streams start (eg. increase accumulation in wet areas, decrease accumulation

[GRASS-user] i.atcorr returns all NULL values

Hello, I'm using i.atcorr to perform atmospheric corrections on Landsat 5 TM data and something peculiar seems to happen arbitrarily to some of the data. For the most part everything works fine, but for some of the bands the result is a raster layer that is filled with nothing but NULL values.

Re: [GRASS-user] Extract coordinates of vertices/nodes

2010/4/28 Micha Silver mi...@arava.co.il On 04/28/2010 12:12 PM, Sophie Leguedois wrote: Greetings, Being quite in Grass, I am trying to find  a way to extract geographic coordinates of vertices and nodes (by the way I am struggling a little to understand the differences between those two

[GRASS-user] Re: [GRASS-dev] New version of the r.landscape.evol.py Landscape Evolution module uploaded to the GRASS Addons repository.

Isaac Ullah wrote: [The new r.landscape.evol.py] takes advantage of the advanced MFD flow routing capabilities of the newly updated r.watershed module, which produced more accurate stream networks, and flow accumulation values. Nice, but r.landscape.evol.py works only with the GRASS 6.5

[GRASS-user] Re: [GRASS-dev] New version of the r.landscape.evol.py Landscape Evolution module uploaded to the GRASS Addons repository.

Isaac Ullah wrote: Yes, this is certainly true. We have kept backwards compatibility with a flag to use r.terraflow if the user has GRASS 6.4 or less. GRASS 6.4 is the next stable release for some time to come, thus new addons for GRASS 6.x should IMHO be tailored for 6.4. Either you advocate

Re: [GRASS-user] Problem after import using r.in.ascii

Hanlie Pretorius wrote: I have an existing CSV file that has the headers lat, long and precip. The precipitation is a floating point number to two decimal places. The coordinates in the CSV file define the centre of a quarter degree square. The first set of coordinates in the file is

Re: [GRASS-user] New version of the r.landscape.evol.py Landscape Evolution module uploaded to the GRASS Addons repository.

Le 27/04/2010 23:59, Isaac Ullah a écrit : Dear GRASS users/developers, I'm happy to announce that the Mediterranean Landscapes Dynamics Project has released a brand new version of our landscape evolution script r.landscape.evol.py. It can be downloaded from the GRASS ADDONS SVN

[GRASS-user] Re: [GRASS-dev] New version of the r.landscape.evol.py Landscape Evolution module uploaded to the GRASS Addons repository.

The reality is that this kind of modeling works well and is accurate for the new MFD routine in r.watershed but does not work nearly as well with r.terraflow or with SFD in r.watershed. Helena originally proposed this for r.flow, which is how we started out several years ago. However, as we