Dear all,
I am trying to create ps maps with the grass function ps.map
I would have 2 questions:
- How can I reduce the number of tickbars on the colortable ?
- How is it possible to print the labels of vector data ?
Thanks in advance,
Jessica
_
Hi,
After implementing gain and bias correction and topographic
correction, I get very low values for landsat data data
for example range of values of band1:
GRASS 6.3.1svn (p112r056):~ r.info lsat7_2000.toar.1 -r
min=0.030303
max=0.372067
[Raster MASK present]
GRASS 6.3.1svn (p112r056):~
jessica gervais wrote:
I am trying to create ps maps with the grass function ps.map
I would have 2 questions:
- How can I reduce the number of tickbars on the colortable ?
adjust the height(??) and/or the range sub-instructions.
it should auto-scale and with some trial and error you can get
Hi,
I didn't follow the full discussion, but this one might be at least of
scientific interest regarding the TOP50-CD/DVDs:
http://www.mfraenz.de/top50/index.html
Regards,
Peter
--
Dr. Peter Löwe
[EMAIL PROTECTED]
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen
r.horizon elevin=srtm3_stel step=45 horizon=horizon_45 coord=4275945
coord= should be x,y not just a single number.
So the parser knows to expect two numbers, in the option setup code should
include the line:
parm.coord-key_desc = east,north;
for i in `seq 92 304`; do
r.sun2 -s
Hello,
I am looking for a way to create a square buffer for a point vector so that
each point is in the end the centroid of a square with defined side length.
I though about r.mapcalc statements to grow north-south and west-east and then
somehow create an area from this square. But I have no
On Mon, 2008-06-16 at 07:03 -0700, Hamish wrote:
r.horizon elevin=srtm3_stel step=45 horizon=horizon_45 coord=4275945
coord= should be x,y not just a single number.
So the parser knows to expect two numbers, in the option setup code should
include the line:
parm.coord-key_desc =
Nikos:
r.horizon elevin=srtm3_stel step=45 horizon=horizon_45 coord=4275945
Hamish:
coord= should be x,y not just a single number.
So the parser knows to expect two numbers, in the
option setup code should include the line:
parm.coord-key_desc = east,north;
(added in SVN)
I
Martin,
I think using vectors and some scripting will be the way to go here.
A simple script should be something like this:
1. create a new polygon vector with v.edit
2. for each point in your points vector get the x and y coords (v.to.db or
maybe v.report)
3. calculate the vertices of your
A small bug (?)
In grass-6.3.1svn if I do g.region -c I get a D:M:S output and not
decimal degrees. Now I want to use m.proj to have decimal degrees
but I always get the following error:
read: 201: Illegal option -n
___
grass-user
Nikos:
In grass-6.3.1svn if I do g.region -c I get
a D:M:S output and not decimal degrees.
'g.region -cg'
Now I want to use m.proj to have decimal degrees
but I always get the following error:
read: 201: Illegal option -n
?
m.proj wants DMS in PROJ.4 style, i.e. 123d45'56
a
Hi lists,
I built GRASS 6.3.0 on Vista (Home Premium) through the usual MSYS/MinGW
envrironment.
It works fine on my machine, and it seems that it solved the following bugs:
http://trac.osgeo.org/grass/ticket/111
http://trac.osgeo.org/grass/ticket/118
But I need more tests, from both XP and
I will be out of the office starting 16.06.2008 and will not return until
21.07.2008.
I will respond to your message when I return.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
I would rather rasterize at different grain size the same vector layer and
then vectorize it. Just using g.region, v.to.rast, and r.to.vect
respectively
Best
On Mon, Jun 16, 2008 at 10:10 AM, Jonathan Aguero-Valverde [EMAIL PROTECTED]
wrote:
Martin,
I think using vectors and some scripting
14 matches
Mail list logo