On Tue, Nov 24, 2009 at 8:10 AM, Paolo Cavallini cavall...@faunalia.it wrote:
maven apache ha scritto:
does the grass support windows 7 system?
We are finding that 7 is more or less the same as vista (marketing... ;) ):
GRASS
used from QGIS plugin crashes at about the same commands as in
Hi,
I have been using r.param.scale and inverting DEM method for identifying
peaks. I am specifically interested in finding the high spots on a
landscape; not just the highest single cell. It has been suggested that
r.prominence may be of help. I realise that this comes in a file that needs
to be
Markus Neteler ha scritto:
On Tue, Nov 24, 2009 at 8:10 AM, Paolo Cavallini cavall...@faunalia.it
wrote:
maven apache ha scritto:
does the grass support windows 7 system?
We are finding that 7 is more or less the same as vista (marketing... ;) ):
GRASS
used from QGIS plugin crashes at
On Tue, Nov 24, 2009 at 11:03 AM, Paolo Cavallini cavall...@faunalia.it wrote:
Markus Neteler ha scritto:
On Tue, Nov 24, 2009 at 8:10 AM, Paolo Cavallini cavall...@faunalia.it
wrote:
maven apache ha scritto:
does the grass support windows 7 system?
We are finding that 7 is more or less the
Markus Neteler ha scritto:
We have installed OSGeo4W-QGIS-GRASS here on XP today.
It delivered a version from May 2009 which is about 2000 SVN
revisions ago. Is there hope to get a fresh recompile from the
SVN 6.4 release branch? Or did we miss anything?
AFAIK, you're right - any volunteer
On Tue, 24 Nov 2009, Glynn Clements wrote:
Create the location anyhow and set the region from a map once you've
imported one.
If for some reason you need suitable bounds before you've imported any
maps you can use use m.proj -i ... to convert lat-lon coordinates to
projected coordinates (but
Hi Markus,
Thanks much. I saw that.
What we are looking for are some guidelines or script to create
anaglyphs within GRASS. We want to use the 3D perspective of an
anaglyph to map stream terraces. This is commonly done in
geomorphology using paper stereo pairs and glasses. With an
I did something like this recently. I didn't know about the wiki page, but it
ended up similar to that process: take two snapshots in NVIZ, then merge them
together to produce the anaglyph.
For the anaglyph, on the Mac there is a nice program called Red Green to do
this. It can do all the
On Sun, 22 Nov 2009, Glynn Clements wrote:
In particular, if you have *raster* data in an LCC projection, you need to
know its bounds in LCC, otherwise you don't really have any data, just an
array of numbers.
I want to re-do the layers so they're all correct. Starting with the DEM,
here's
On Tue, 24 Nov 2009, Rich Shepard wrote:
If I correctly understand what you wrote above, I use the projection
information when importing the data, but leave the bounds undefined. Once
the import is completed I can then run 'g.region rast=elevation10' to set
the bounds in appropriate units.
From the US Census TIGER files I imported the 'edges' (streets) using
v.in.ogr and using the projection information in the *.prj file. This worked
well, except that 'g.region -p' shows lat/lon geographic coordinates:
GRASS 6.4.0svn (streets):/usr4/grassbase g.region -p
projection: 3
Hi,
2009/11/24 Rich Shepard rshep...@appl-ecosys.com:
From the US Census TIGER files I imported the 'edges' (streets) using
v.in.ogr and using the projection information in the *.prj file. This worked
well, except that 'g.region -p' shows lat/lon geographic coordinates:
GRASS 6.4.0svn
hello, anyone know where I can use the command shortestpath so you can get
all distances from the points of interest of a network and print them in a
matrix, just as the command v.distance.
thanks for any response
Ricardo
Estudiante de ultimo semestre de ING. TOPOGRAFICA
On Tue, 24 Nov 2009, Martin Landa wrote:
you cannot define a different spatial reference systems (SRS) for mapsets
in one location. Data in one location need to be in the same SRS. This is
fundamental feature of the GRASS database - A LOCATION is defined by its
coordinate system, map projection
On Tue, 24 Nov 2009, Rich Shepard wrote:
True. I completely forgot about this. With a new location/mapset I can
now use v.proj to move it over.
I'm still missing something. Defined a new location (streetsLCC) and
mapset (rbs). Ran the following command successfully:
GRASS 6.4.0svn
Hi Rich,
I have a general theory that may help you:
Assumptions:
-Very well defined LOCATION parameters is the foundation to perfectly combine
maps of different sources.
-The experience tells me that some data are even in the correct reference
system, but sometimes the info that comes with it
On Tue, 24 Nov 2009, Pablo Carreira wrote:
Assumptions:
-Very well defined LOCATION parameters is the foundation to perfectly combine
maps of different sources.
-The experience tells me that some data are even in the correct reference system, but
sometimes the info that comes with it
The wxPython GUI has a bug: when UTM is specified as the projection, we
cannot change the zone from the default 30...
Today a have seen this bug in wx, it looks like the zone box is hidden.
You may create a custom proj.4 parameters to bypass this problem
Look at this site:
Rich Shepard wrote:
True. I completely forgot about this. With a new location/mapset I can
now use v.proj to move it over.
I'm still missing something. Defined a new location (streetsLCC) and
mapset (rbs). Ran the following command successfully:
GRASS 6.4.0svn
Markus,
Making an anaglyph in GRASS turned out to be trivially easy. My RA,
Isaac came up with the simplest idea. Just put one image of the stereo
pairs into the red channel of r.composite and the other image into the
blue channel and the green channel. If you don't need to create a
20 matches
Mail list logo
